Application permission activation method, medium and electronic device

Abstract

The present application relates to the field of communication technology, and provides 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, and promote the application ecology of smart wearable devices and the like to be more prosperous. The method includes: in response to the operation of opening a first application installed in a first device, the first device determines the permission activation status of the first application; when the permission activation status is not activated, the first device sends a first message to the second device, and the first message includes the device type of the first device and the permission activation status of the first application; when the second device determines that the device type is a preset type and the permission activation status is not activated, the second application in the second device is opened, and the second application has an associated relationship with the first application; the second device uses the second application to activate the permissions of the first application; the second device sends a second message to the first device, and the second message is used to indicate that the permissions of the first application have been activated.

Description

Technical Field

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

[0002] Some wearable devices such as mobile phones and smart watches have rich hardware resources and can be connected to the Internet independently. In order to attract more ecosystem developers, the equipment manufacturers of these electronic devices support paid application downloads through the application market, and support paid service activation through in-app payment 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 the sports watch series are based on the real-time operating system (RTOS) system, and their hardware resources are limited. They can neither support independent networking nor independent watch-side application markets, and cannot realize the paid download function of applications and the in-app payment function, which leads to the slow development of the sports watch ecosystem of the RTOS system. Summary of the invention

[0003] 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 ecology of smart wearable devices, and attract more developers to develop more ecological applications on devices such as sports watches.

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

[0005] 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;

[0006] 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 a permission activation state of the first application;

[0007] When the second device determines that the device type is a preset type and the permission activation state is not activated, opening a second application in the second device, the second application has an associated relationship with the first application;

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

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

[0010] 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 of 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.

[0011] In this way, the second device can use the second application to activate the first application or in-application service with which the second device has an associated relationship through the application market. Furthermore, the second device notifies the first device that the first application or the service has been activated, so that the first device can use the first application or the service normally to achieve cross-device activation. Then, even if the first device cannot connect to the Internet and cannot support an independent application market, the activation of the installed first application can be completed.

[0012] In a possible implementation of the first aspect above, the method further includes: if the permission activation state is not activated, 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.

[0013] 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 time, so as to subsequently use the second application to activate the first application across devices.

[0014] 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, the third message being used to obtain a device type of the first device and a permission activation status of the first application.

[0015] The third message may be a device query message described below. At this time, the second device actively reports the third message so that the second device can activate the corresponding application in time later.

[0016] 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 permissions of the first application.

[0017] Among them, the second application interface can be the activation interface mentioned below, and can interact with the application market used by the second device.

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

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

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

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

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

[0023] The fourth message may be an installation query message, and the fifth and sixth messages may be installation response messages described below. Thus, the interface for downloading the second application in the second device may be automatically opened, or the interface of the second application may be automatically opened, so that the user can quickly and conveniently activate the first application.

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

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

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

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

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

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

[0030] In a possible implementation manner 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.

[0031] In a possible implementation of the first 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 recognition method. In this way, authorization management of permissions of the first application is facilitated, and the user has the permission to use the first application only after successful activation.

[0032] In a possible implementation of the first 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. In this way, even if the first device does not support the payment function, the first application can be paid through the second device, and the cross-device payment function can be implemented to achieve cross-device application activation.

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

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

[0035] 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;

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

[0037] In this way, information transmission between the first application and the second application can be achieved, so that the second device can activate the first application in the first device across devices through the second application.

[0038] In a second aspect, an embodiment of the present application provides an application permission activation method, which is applied to a first device, and the method includes:

[0039] 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;

[0040] 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 a permission activation state of the first application;

[0041] The first device receives a second message from the second device, where the second message is used to indicate that 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.

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

[0043] If the permission activation status is not activated, 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.

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

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

[0046] 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;

[0047] 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;

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

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

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

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

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

[0053] In a possible implementation manner of the second aspect above, 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.

[0054] In a possible implementation manner 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 recognition method.

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

[0056] 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;

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

[0058] In a third aspect, an embodiment of the present application provides an application permission activation method, which is applied to a second device, and the method includes:

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

[0060] When the second device determines that the device type is a preset type and the permission activation state is not activated, opening a second application in the second device, the second application has an associated relationship with the first application;

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

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

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

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

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

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

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

[0068] In a possible implementation manner 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.

[0069] In a possible implementation manner 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 recognition method.

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

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

[0072] 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;

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

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

[0075] 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 an application permission activation method as in the second aspect and any possible implementation thereof, or, an application permission activation method as in the third aspect and any possible implementation thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0076] Figure 1 According to some embodiments of the present application, a schematic diagram of a scenario in which a mobile phone or a smart watch downloads an application through an application market is shown;

[0077] Figure 2 According to some embodiments of the present application, a schematic diagram of an application download interface of an application market in a mobile phone is shown;

[0078] Figure 3 According to some embodiments of the present application, a schematic diagram of an interface for paid downloading of applications in a smart watch is shown;

[0079] Figure 4 According to some embodiments of the present application, a schematic diagram of a scenario in which a mobile phone or a smart watch obtains services in a third-party application APP based on an application market is shown;

[0080] Figure 5 According to some embodiments of the present application, a schematic diagram of interface changes of an in-app payment process in a smartwatch is shown;

[0081] Figure 6 According to some embodiments of the present application, a software structure block diagram of a mobile phone is shown;

[0082] Figure 7 According to some embodiments of the present application, a schematic diagram of an application permission activation scenario is shown;

[0083] Figure 8 According to some embodiments of the present application, a flowchart of a method for activating application permissions is shown;

[0084] Fig. 9 According to some embodiments of the present application, a schematic diagram of an application permission activation scenario is shown;

[0085] Fig.10 According to some embodiments of the present application, a flowchart of a method for activating application permissions is shown;

[0086] Fig.11 According to some embodiments of the present application, a schematic diagram of an application permission activation scenario is shown;

[0087] Fig.12According to some embodiments of the present application, a flowchart of a method for activating application permissions is shown;

[0088] Fig.13 According to some embodiments of the present application, a flowchart of a method for activating application permissions is shown;

[0089] Fig.14 According to some embodiments of the present application, a schematic diagram of the structure of a mobile phone is shown;

[0090] Fig.15 According to some embodiments of the present application, a schematic structural diagram of a sports watch is shown. DETAILED DESCRIPTION

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

[0092] The application permission activation method provided in the embodiment of the present application can be applied to the scenario of activating an application (Application, App) and / or activating an internal service of an application. For example, an in-application service can be a prop, a business, etc. It can be understood that after an application or an internal service of an application is activated, the permission of the application or the service is opened, and the user can use the application or the service normally.

[0093] 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 application is updated in an electronic device and then restarted, or activating an internal service when the service is used for the first time in an application of the electronic device.

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

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

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

[0097] Next, the technologies related to paid purchase of applications and in-app services are introduced.

[0098] In some related technologies, mobile phones and smart watches can download applications independently and for a fee through the application market. Figure 1 The figure shows a scenario diagram of a mobile phone or smart watch downloading 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 interact with the cloud application market server based on the account and the application's identity document (ID) to complete the process of successful download after payment. That is, the mobile phone or smart watch interacts with the application market server based on the account + APP ID + payment method through the application market APP and downloads 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.

[0099] Among them, the application market, also known as the app store, is a software distribution channel through which ordinary users can browse and download various applications. The application market has become an application distribution channel connecting application developers and users, and is the foundation for building an ecosystem.

[0100] Reference Figure 2 , shows a schematic diagram of an application download interface of an application market in a mobile phone, the interface 20 includes information of multiple applications, such as application icons, names (i.e., APP IDs), categories, profile information, and installation buttons or paid installation buttons. For example, Figure 2 The interface 20 shown includes multiple applications such as application 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 by 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., the paid installation button) 22.

[0101] Reference Figure 3 , shows a schematic diagram of the interface for paid downloading of applications in a smartwatch, the interface 30 includes information of application B, such as a rating of 3.3, a capacity of 20.28MB, etc., and a "￥6" button (i.e., a paid installation button) 31. When a user clicks the "￥6" button 31, the smartwatch can be triggered to pay and download application B from the application market server.

[0102] It is understandable that when a mobile phone or smart watch performs a payment operation, the user is required to enter sensitive information such as a payment password.

[0103] Therefore, the above-mentioned solution of paying to download apps through the app market for mobile phones and smart watches depends on the device side being able to support networking, the device side being able to support an independent app market, and the device side supporting the ability to store sensitive information at a high security level, which means that the hardware capabilities and computing power of the device are relatively high. Obviously, hardware-constrained devices such as sports watches cannot independently complete the paid activation of apps.

[0104] 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, mobile phones or smart watches can interact with cloud servers through the IAP kit and the independent application market on the smart watch side to realize in-app payment. Figure 4 The figure shows a scenario diagram of a mobile phone or smartwatch obtaining services from 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.

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

[0106] Reference Figure 5 The figure shows a schematic diagram of the interface changes of the in-app payment process in a smart watch. Figure 5The interface 51 of the third-party application M is shown, and the interface 51 includes props such as props 511 and props 512. Some props are props to be paid, and other props are props that have been paid or props that do not need to be paid. For example, prop 511 is a prop to be paid. After the user clicks the icon of prop 511, the smart watch can jump to the purchase interface 52, and the purchase interface 52 includes prompt information (such as "Coupon Product 1") and "￥3" and a purchase button 521. After the user clicks the purchase button 521, the smart watch can jump to the payment interface 53, and the payment interface 53 includes the prompt information "In-app Payment" and a payment QR code 531. The user completes the payment by scanning the payment QR code 531 through the smart watch or by scanning the payment QR code 531 through a mobile phone or other device. Then, after the payment is completed, the prop 511 is activated, and the user can use the prop 511 normally. At this time, the above-mentioned prop 511 is a service to be paid in the application.

[0107] Then, the above-mentioned solution of independent payment for mobile phones and smart watches to activate in-app services depends on the device side being able to support networking, the device side being able to support an independent application market, and the device side supporting the ability to store sensitive information at a high security level. In addition, the device side also needs to provide an IAP kit for cross-application communication and support interface communication between third-party applications and independent application markets. That is, it places high demands on the hardware capabilities and computing power of the device. Obviously, hardware-constrained devices such as sports watches cannot complete in-app payments independently, nor can they activate in-app services independently.

[0108] It should be noted that mobile phones and smart watches are usually full-scale devices with rich hardware resources. However, sports watches and other devices are usually limited in hardware resources and are lightweight devices. They do not support networking or independent application markets, and thus cannot independently complete the in-app payment activation function.

[0109] 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 application activation. 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 device side such as sports watches.

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

[0111] 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, and 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 that activation functions such as payment functions of ecological applications and in-application payment functions cannot be realized.

[0112] In some embodiments, the first device may obtain software packages of one or more applications through other electronic devices, thereby installing one or more applications in the first device. For example, a sports watch may be pre-connected to a mobile phone or a computer, and obtain software packages of one or more applications through the mobile phone or the computer. However, although an application is installed in the first device, the application or the service within the application cannot be activated independently, for example, the activation operation corresponding to the paid function cannot be completed.

[0113] The second device provided in the embodiments of the present application includes but is not limited to the above-mentioned mobile phone, and may also be other devices such as a tablet computer and a laptop computer. In some embodiments, the above-mentioned second device may be a full-scale device (or heavyweight device), which usually has a large-capacity battery, does not require ultra-low power consumption, and needs to have high performance to ensure user experience. In addition, the second device usually supports networking, supports downloading and activating applications and in-application services through application markets, etc.

[0114] In some embodiments of the present application, the first device and the second device may belong to the same manufacturer. In addition, a device management application is installed in the second device to manage the application in the first device.

[0115] As an example, the first device in the embodiment of the present application is a sports watch, and the second device is a mobile phone. In addition, a management application, such as a sports health application, is installed in the mobile phone to manage the installation of applications in the sports watch connected to the mobile phone. It can be understood that in some embodiments, the above-mentioned sports health application can be used as an application market on the sports watch side.

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

[0117] In some embodiments, a distributed communication software development kit (SDK) is deployed in both the mobile phone 100 and the sports watch 200, which is a middleware for providing a distributed interface to realize distributed communication between the mobile phone 100 and the sports watch 200. The above-mentioned distributed communication SDK can be deployed in the software architecture of the mobile phone and the sports watch. In addition, more specifically, the mobile phone 100 and the sports watch 200 use a distributed interface to adopt a communication technology such as Bluetooth technology to transmit messages.

[0118] In some embodiments, the software system of the mobile phone 100 may adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present invention takes the Android system of the layered architecture as an example to exemplify the software structure of the mobile phone 100.

[0119] Figure 6 It is a software structure block diagram of the mobile phone 100 according to an embodiment of the present application.

[0120] The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system library, and the kernel layer.

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

[0122] like Figure 6 As shown, 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.

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

[0124] like Figure 6 As shown, 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, etc.

[0125] 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, capture the screen, etc.

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

[0127] The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.

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

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

[0130] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, an electronic device vibrates, an indicator light flashes, etc.

[0131] 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, so as to realize the in-application payment function.

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

[0133] Android Runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.

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

[0135] The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

[0136] The system library may 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.

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

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

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

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

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

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

[0143] Next, refer to Figure 7 As shown, it is a schematic diagram of an application permission activation scenario provided in an embodiment of the present application.

[0144] like Figure 7 As shown, the mobile phone 100 side includes the following applications:

[0145] Application market: You can download and install third-party applications on the mobile phone (referred to as third-party application 1, i.e. the second application).

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

[0147] Third-party application 1: can integrate the distributed communication SDK of the equipment manufacturer and the third-party application (i.e., third-party application 2) on the sports watch 200 side to realize distributed communication, 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.

[0148] like Figure 7 As shown, the watch 200 includes the following applications:

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

[0150] 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 the watch version of the same application.

[0151] Specifically, Figure 7 In the scenario shown in FIG. 1 , the mobile phone 100 can download the watch version of the third-party application (i.e., the third-party application 2) through the device management application, connect to the sports watch 200 through Bluetooth, and then send the watch version of the third-party application 2 to the sports watch 200 for installation, thus achieving Figure 7 The mobile phone version of the third-party application 1 on the mobile phone 100 side communicates with the third-party application 2 on the sports watch 200 side through the distributed communication SDK to activate the third-party application 2 on the sports watch 200 side, that is, to achieve Figure 7 The "2. Activate watch-side application" is shown. And the mobile phone 100 side downloads and installs the third-party application 1 through the application market, that is, Figure 7 Then, 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 application market activation service payment, that is, Figure 7 "4. Activate service payment" is displayed.

[0152] Next, in Figure 7 Based on the scenario shown, refer to Figure 8 The following is a flow chart of a method for activating application permissions provided by an embodiment of the present application. Specifically, Figure 8 The application permission activation method shown mainly takes the paid activation method as an example to illustrate the process of activating the in-application service of the third-party application 2.

[0153] Specifically, Figure 8 The method shown includes the following steps:

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

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

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

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

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

[0159] In some embodiments, the sports watch 200 may install and start the third-party application 2 for the first time, or start the third-party application 2 for the first time after updating.

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

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

[0162] In some embodiments, the service activation status of the third-party application 2 may refer to the activation status of the entire service of the third-party application 2, that is, the permission of the service activation status to the entire service of the third-party application 2. Then, when the service activation status of the third-party application 2 is activated, it means that the permission of the entire service in the third-party application 2 is open and can be used; when the service activation status is not activated, it means that the permission of the entire service in the third-party application 2 is not open and cannot be used normally.

[0163] In some embodiments, the service activation state of the third-party application 2 may refer to the activation state of a service (referred to as service 1) in the third-party application 2, that is, the service activation state corresponds to the usage rights of the service 1. Then, when the service activation state of the third-party application 2 is activated, it means that the rights of service 1 in the third-party application 2 are open and can be used; when the service activation state is not activated, it means that the rights of service 1 in the third-party application 2 are not open and cannot be used normally.

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

[0165] 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, the third-party application 1 on the mobile phone 100 side is directly pulled up to start the activation process.

[0166] It can be 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.

[0167] S3b: Start the third-party application 1.

[0168] It can be understood 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 .

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

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

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

[0172] In some embodiments, after the third-party application 1 is downloaded and started on the mobile phone 100 side, the third-party application 1 can be used to call the interface of the distributed communication SDK to obtain the device type connected to the sports watch 200 and the activation status of the third-party application 2 on the sports watch 200 side. When the device type is a sports watch and the third-party application 2 is in an inactive state, the mobile phone 100 starts the activation service, and the in-app payment for the third-party application 2 is completed in the mobile phone 100, thereby realizing the commercialization closed loop of the third-party application 2 on the sports watch 200 side.

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

[0174] In some embodiments, the information of a device may include the device type, such as a sports watch or a smart watch. Then, when the information of the sports watch 200 is a sports watch and the third-party application 2 has not been activated, the mobile phone 100 can start the third-party application 1 to complete the activation, so as to realize the service activation of the third-party application 2 on the sports watch 200 side, thereby obtaining the use right of the activated service of the third-party application 2. When the information of the sports watch 200 is smart, the mobile phone 100 will not process it, for example, there is no need to download the third-party application 1.

[0175] In some embodiments, the device type of a device may include a lightweight device or a full-scale device. Then, when the information of the sports watch 200 is a lightweight device and the third-party application 2 has not been activated, the mobile phone 100 can start the third-party application 1 to complete the activation, so as to realize the service activation of the third-party application 2 on the sports watch 200 side, thereby obtaining the use right of the activation service of the third-party application 2. When the information of the sports watch 200 is a full-scale device, the mobile phone 100 will not process it, for example, there is no need to download the third-party application 1.

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

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

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

[0179] 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".

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

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

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

[0183] In this way, the third-party application 1 on the mobile phone 100 starts the in-app payment of the third-party application 2 on the sports watch 200 according to the service activation status and device type of the third-party application 2 on the sports watch 200, and completes the activation service of the third-party application 2 on the watch side. Therefore, the sports watch can realize the payment activation of the in-app service of the third-party application without supporting an independent application market and supporting networking.

[0184] exist Figure 8 The method shown is based on the reference Fig. 9 , shows a schematic diagram of an application permission activation scenario provided by an embodiment of the present application. Fig. 9 The scenario shown takes the device management application as a sports and health application, the third-party application 1 on the mobile phone 100 side as the third-party application 1, and the third-party application 2 on the sports watch 200 side as an example to illustrate the solution of the user manually operating the mobile phone 100 to open the application market to download the third-party application 1 on the mobile phone 100 side.

[0185] like Fig. 9As shown, the third-party application 2 on the sports watch 200 side 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 prompt information, such as "Please click to download / or open the mobile phone side application to activate". Subsequently, according to the installation status of the third-party application 1 on the mobile phone 100 side, jump to the download interface 92 of the application market in the mobile phone 100 to download the third-party application 1 on the mobile phone 100 side, and then start the third-party application 1 on the mobile phone 100 side and display the interface 93 of the third-party application 1 on the mobile phone 100. The mobile phone 100 side determines that the device type of the connected sports watch 200 is a sports watch and the third-party application 2 on the watch side is not activated, then starts the activation service payment, and then pays through the payment QR code 94. The payment is successful, the third-party application 2 on the sports watch 200 side is activated, and the service activation status of the third-party application 2 on the watch side is modified. When the sports watch 200 opens the third-party application 2 on the watch side again, the running interface 95 of the third-party application 2 on the watch side can be displayed normally, so as to have the authority to use the third-party application 2 normally.

[0186] Next, combine Fig.10 right Fig. 9 The specific process of the method for activating application permissions in the scenario shown is described. Specifically, Fig.10 The method shown includes the following steps:

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

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

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

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

[0191] In some embodiments, the sports watch 200 may display Fig. 9 A prompt interface 91 is shown.

[0192] 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 payment; if it is a smart watch, no payment is made.

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

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

[0195] 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. Furthermore, 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.

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

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

[0198] In some other embodiments, if the third-party application 1 on the mobile phone side needs to be paid 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.

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

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

[0201] 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 phone-side third-party application 2 in the mobile phone 100, thereby realizing the subsequent cross-device application activation process.

[0202] exist Figure 8 The method shown is based on the reference Fig.11 , shows a schematic diagram of an application permission activation scenario provided by an embodiment of the present application. Fig.11The scenario shown uses the device management application as a sports and health application to illustrate the solution of the mobile phone 100 automatically jumping to the download interface of the third-party application 1 in the application market, or automatically opening the third-party application 1 on the mobile phone 100 side.

[0203] like Fig.11 As shown, the third-party application 2 on the sports watch 200 side is not activated. When it is opened for the first time, the user is prompted, and the prompt interface 111 of the sports watch 200 includes the prompt information "Please click to download / or open the mobile phone side application to activate". Subsequently, according to the installation status of the third-party application 1 on the mobile phone 100 side, jump to the interface 112 of the third-party application 1 on the mobile phone 100 side, that is, the mobile phone side third-party application 1 has been installed in the mobile phone 10. The mobile phone 100 side determines that the connected device type is a sports watch and the third-party application 2 on the watch side is not activated, then starts the activation service payment, and then pays through the payment QR code 113. The payment is successful, the third-party application 2 on the sports watch 200 side is activated, and the service activation status of the third-party application 2 on the watch side is modified. When the sports watch 200 opens the third-party application 2 on the watch side again, the interface 114 of the third-party application 2 on the watch side can be displayed normally, and the third-party application 2 has the authority to be used normally.

[0204] Next, combine Fig.12 right Fig.11 The specific process of the method for activating application permissions in the scenario shown is described. Specifically, Fig.12 The method shown includes the following steps:

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

[0206] 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 for installation via Bluetooth.

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

[0208] 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 installation response message returned by the mobile phone 100 through the interface of the distributed communication interface SDK is received, and the installation response message is used to indicate whether the corresponding mobile phone-side third-party application is installed in the mobile phone 100.

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

[0210] In some embodiments, the sports watch 200 can send a download 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 download interface of the mobile phone side third-party application 1 in the application market. The download jump message contains the ID (such as the name) of the third-party application 1. Then, the mobile phone 100 can automatically jump to the download interface of the mobile phone side third-party application 1 in the application market according to the download jump message. Furthermore, the user can click on the "download" and other controls in the download interface to trigger the mobile phone 100 to start downloading the mobile phone side third-party application 1.

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

[0212] 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 phone side third-party application 1, and the start jump message contains 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.

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

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

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

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

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

[0218] Reference Fig.13 As shown, a method for activating application permissions provided in an embodiment of the present application includes the following steps:

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

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

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

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

[0223] The above-mentioned service activation status may be the permission activation status of the overall 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.

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

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

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

[0227] As an example, the prompt interface displayed by the sports watch 200 may be: Fig. 9 The prompt interface 91, or Fig.11 The prompt interface 111 in.

[0228] 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-side third-party application 1 in the application market.

[0229] In some embodiments, before S1306, the sports watch 200 sends an installation query message to the mobile phone 100 through the distributed interface to request to query the installation status of the third-party application 1 in the mobile phone 100. Then, the sports watch 200 receives an installation response message from the mobile phone 100. Among them, the mobile phone 100 can return an installation response message through the distributed communication interface SDK, and the installation response message is used to indicate whether the corresponding mobile phone side third-party application 1 is installed in the mobile phone 100. In this way, in S1306, if the mobile phone 100 does not install the third-party application 1, the sports watch 200 sends a download jump message to the mobile phone 100 to instruct the mobile phone 100 to automatically open the download interface of the mobile phone side third-party application 1 in the application market, and the download jump message contains the ID (such as the name) of the third-party application 1. Then, the mobile phone 100 can automatically jump to the download interface of the mobile phone side third-party application 1 in the application market according to the download jump message. Then, the user can click on the "download" and other controls in the download interface to trigger the mobile phone 100 to start downloading the mobile phone side third-party application 1.

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

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

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

[0233] It can be understood that the mobile phone 100 can open the third-party application 1 automatically or manually.

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

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

[0236] 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 the predetermined conditions, the mobile phone 100 displays an activation interface for activating application permissions.

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

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

[0239] In some other embodiments, after the mobile phone 100 is connected to the sports watch 200, the device type of the sports watch 200 has been stored. Therefore, the mobile phone 100 exchanges information with the sports watch 200 through the distributed communication SDK to determine the service activation status of the third-party application on the sports watch 200 side. The mobile phone determines whether it is necessary to activate the application on the mobile phone 100 side based on the device type of the sports watch 200 stored in it and the information on the service activation status obtained from the sports watch 200.

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

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

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

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

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

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

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

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

[0248] 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 operating interface of the third-party application, so that the third-party application 2 can be used normally.

[0249] In this way, the application permission activation method provided in the embodiment of the present application is that lightweight devices such as sports watches do not need to be connected to the Internet or support an independent application market. The same application can 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.

[0250] like Fig.14 , which is a schematic diagram of the hardware structure of the mobile phone 100.

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

[0252] It is to be understood that the structure illustrated in 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 in the figure, or combine some components, or separate some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0253] The processor 110 may include one or more processing units, for example, a central processing unit CPU (Central Processing Unit), a graphics processor GPU (Graphics Processing Unit), a digital signal processor DSP, a microprocessor MCU (Micro-programmed Control Unit), an AI (Artificial Intelligence) processor or a programmable logic device FPGA (Field Programmable Gate Array) and other processing modules or processing circuits. Among them, different processing units can be independent devices or integrated in one or more processors. A storage unit can be set 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.

[0254] The power module 140 may include a power source, a power management component, etc. The power source may be a battery. The power management component is used to manage the charging of the power source and the power supply of the power source to other modules. In some embodiments, the power management component includes a charging management module and a power management module. The charging management module is used to receive charging input from the charger; the power management module is used to connect the power source, the charging management module and the processor 110. The power management module receives input from the power source and / or the charging management module, and supplies power to the processor 110, the display screen 102, the camera 170, and the wireless communication module 120.

[0255] The mobile communication module 130 may include, but is not limited to, an antenna, a power amplifier, a filter, an LNA (Low noise amplifier), etc. The mobile communication module 130 may provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the mobile phone 100. The mobile communication module 130 may receive electromagnetic waves through an antenna, and perform filtering, amplification, and other processing on the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 130 may 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 may be arranged in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 130 may be arranged 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).

[0256] The wireless communication module 120 may include an antenna, and transmit and receive electromagnetic waves via the antenna. The wireless communication module 120 may 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., which are applied to the mobile phone 100. The mobile phone 100 may communicate with the network and other devices through wireless communication technology.

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

[0258] The display screen 102 is used to display a human-computer interaction interface, images, videos, etc. The 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 or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light emitting diode (QLED), etc. For example, the display screen 102 can display a setting interface, an access interface, etc. of a DRM copyright protected file.

[0259] The sensor module 190 may include a proximity light 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.

[0260] 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 arranged in the processor 110, or some functional modules of the audio module 150 can be arranged in the processor 110. In some embodiments, the audio module 150 can include a speaker, an earpiece, a microphone, and an earphone interface.

[0261] The camera 170 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element converts the optical signal into an electrical signal, and then transmits the electrical signal to the ISP (Image Signal Processing) to convert it into a digital image signal. The mobile phone 100 can realize the shooting function through the ISP, the camera 170, the video codec, the GPU (Graphic Processing Unit), the display screen 102 and the application processor.

[0262] 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 a data storage function. The universal serial bus 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 10010, for example, to read the phone number stored in the SIM card, or to write the phone number into the SIM card.

[0263] In some embodiments, the mobile phone 100 further includes a button 101, a motor, an indicator, etc. Among them, the button 101 may include a volume button, a power on / off button, etc. The motor is used to make the mobile phone 100 vibrate, for example, vibrate when the user's mobile phone 100 is called to prompt the user to answer the call of the mobile phone 100. The indicator may include a laser indicator, a radio frequency indicator, an LED indicator, etc.

[0264] like Fig.15 , which 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 an embodiment of the present application, the body of the sports watch 200 may include a touch screen 101 (also called a touch panel), a display screen 102, a housing (the housing includes a front housing ( Fig.15 not shown) and the bottom case ( Fig.15 ), as well as 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, etc.

[0265] The functional components of the sports watch 200 are introduced below:

[0266] The touch screen 101 may also be called a touch panel, and 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.

[0267] The display screen 102 can be used to display information input by the user or prompt information provided to the user and 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 is transmitted to the processor 103 to determine the type of touch event, and then the processor 103 provides corresponding visual output on the display screen 102 according to 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.

[0268] The processor 103 is used for system scheduling, controlling the touch screen 101, the display screen 102, supporting the processing of the wireless communication unit 106, etc. The microcontroller unit 104 is used for controlling the sensor, calculating the sensor data, communicating with the processor 103, etc. The sensor may include a motion sensor 107, or other sensors.

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

[0270] The wireless communication unit 106, the sports watch 200 realizes wireless communication with other electronic devices (such as mobile phones, tablet computers, etc.) through the wireless communication unit 106, for example, it can include wireless communication solutions such as Bluetooth (bluetooth, BT), near field communication technology (near field communication, NFC), infrared technology (infrared, IR), etc. 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.

[0271] The power management system 109 is used to connect to the power source 108 to supply 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 , and the like.

[0272] Understandably, Fig.15 The structure shown is only a specific structure for realizing the function of the sports watch 200 in the technical solution of the present application. Sports watches 200 having other structures and realizing similar functions are also applicable to the technical solution of the present application and are not limited here.

[0273] The various embodiments of the mechanism disclosed in the present 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.

[0274] Program code can be applied to input instructions to perform the functions described in this application and generate output information. The output information can be applied to one or more output devices in a known manner. For the 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.

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

[0276] 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, instructions may be distributed over a network or through other computer-readable media. Therefore, machine-readable media may include any mechanism for storing or transmitting information in a machine (e.g., computer) readable form, including, but not limited to, floppy disks, optical disks, optical disks, 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, machine-readable media include any type of machine-readable media suitable for storing or transmitting electronic instructions or information in a machine (e.g., computer) readable form.

[0277] In the accompanying drawings, some structural or method features may be shown in a specific arrangement and / or order. However, it should be understood that such a specific arrangement and / or order may not be required. Instead, 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 structural or method features in a particular figure does not mean that such features are required in all embodiments, and in some embodiments, these features may not be included or may be combined with other features.

[0278] 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 method 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 proposed by the present application. In addition, in order to highlight the innovative part of the present application, the above-mentioned device embodiments of the present application do not introduce units / modules that are not closely related to solving the technical problems proposed by the present application, which does not mean that there are no other units / modules in the above-mentioned device embodiments.

[0279] It should be noted that in the examples and description of this patent, relational terms such as first and second, etc. are only used 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 including 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, the elements defined by the sentence "including one" do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0280] Although the present application has been illustrated and described with reference to certain preferred embodiments thereof, it will be apparent to 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 present 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 not activated, opening a second application in the second device, the second application is associated with the first application; wherein the preset type indicates that the first device does not have a permission activation function for the application, and the second device has a permission activation function for the application; The second device uses the second application to activate the permission of the first 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, the third message is sent 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, characterized in that: 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, characterized in that 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 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.

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 state 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 permission to use the entire business of the first application or 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 a 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 permission of the first application has been activated, wherein the permission of the first application is 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 state is not activated, and the second application has an associated relationship with the first application; wherein the preset type indicates that the first device does not have the permission activation function for the application, and the second device has the permission activation function for the 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 claim 14, 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, characterized in that The method further comprises: The first device modifies the permission activation state of the first application to activated according to the second message.

20. The method according to claim 14, characterized in that 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.

21. The method according to claim 14, 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.

22. The method according to claim 14, 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.

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 by the first device; When the second device determines that the device type is a preset type and the permission activation state is not activated, opening a second application in the second device, the second application is associated with the first application; wherein the preset type indicates that the first device does not have a permission activation function for the application, and the second device has a permission activation function for the application; The second device uses the second application to activate the permission of the first 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, a second application interface is displayed, where the second application interface is used to activate the permission 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 permission to use the entire business of the first application or permission to use a service in the first application.

29. The method according to claim 24, 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.

30. The method according to claim 24, 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.

31. The method according to claim 24, 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.

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 as described in any one of claims 14 to 23, or the application permission activation method as described in any one of claims 24 to 32.

Images