Application sharing method and device

Abstract

The invention provides an application sharing method and device, and relates to the technical field of terminals. The method comprises the following steps: detecting a first operation of clicking a first link, wherein the first link is used for accessing a cloud; in response to the first operation, sending a first message to the cloud according to the first link, the first message being used for requesting to access a first application; receiving a second link from the cloud, the second link carrying first information and second information, the first information indicating access to the first application, and the second information indicating a jump type of the second link; and opening the second link according to the jump type of the second link. According to the method in the embodiment of the invention, the terminal equipment can be guided to the application of the specified type, and the user experience can be improved.

Description

Technical Field

[0001] The present application relates to the field of terminal technology, and in particular to a method and device for application sharing. Background Art

[0002] With the continuous development of science and technology, the functions of terminal devices are becoming more and more powerful. In order to provide users with a richer experience, more and more applications are being installed on terminal devices.

[0003] When using an application, users can share content with other users. For example, users can share a sharing link with other users on a social platform, and other users can jump to a specific page after clicking the sharing link. However, the existing sharing mechanism has many limitations that affect the user experience. Summary of the invention

[0004] The embodiments of the present application provide a method and device for application sharing, which can direct terminal devices to applications of a specified type, thereby improving user experience.

[0005] In a first aspect, a method for sharing an application is provided, which is applied to a first terminal device, and includes: detecting a first operation of clicking a first link, where the first link is used to access the cloud; in response to the first operation, sending a first message to the cloud according to the first link, where the first message is used to request access to a first application; receiving a second link from the cloud, where the second link carries first information and second information, where the first information indicates access to the first application, and the second information indicates a jump type of the second link; and opening the second link according to the jump type of the second link.

[0006] In an embodiment of the present application, a first message for requesting access to a first application is sent to the cloud, a second link is received from the cloud, and the second link is opened according to the jump type of the second link. This allows the first terminal device to access a first application of a specified type, thereby directing the terminal device to an application of the specified type, thereby improving the user experience.

[0007] At the same time, when a first operation of clicking a first link is detected, the first terminal device obtains a second link for accessing the first application through the cloud without considering the operating environment of the terminal device. Therefore, full-platform sharing of the application can be achieved.

[0008] In some possible implementations, the first message includes an identifier corresponding to the first application and a first operating environment of the first terminal device.

[0009] In an embodiment of the present application, the second link is obtained from the cloud, and the first operating environment of the first terminal device is sent to the cloud, so that the first application accessed through the second link is more suitable for the first terminal device, and the operating effect of the first application can be better, thereby improving the user experience.

[0010] At the same time, sending the first operating environment of the first terminal device to the cloud makes the first application accessed through the second link more suitable for the first terminal device, which can also improve the success rate of application sharing and avoid the situation where the first terminal device cannot open the second link, thereby improving the user experience.

[0011] In some possible implementations, the jump type includes a redirect jump, a deep link jump, and / or a global link jump.

[0012] In some possible implementations, the first operating environment includes one or more of the following: operating system type, browser type, and device manufacturer.

[0013] In some possible implementations, the first link carries an identifier corresponding to the first application.

[0014] In a second aspect, a method for application sharing is provided, which is applied to a second terminal device, including: detecting a second operation, the second operation being used to request a link for sharing a first application; in response to the second operation, sending a second message to the cloud, the second message being used to request the link for sharing the first application; and receiving the first link from the cloud, the first link being used to access the cloud.

[0015] In an embodiment of the present application, the first application can be shared by accessing the first link in the cloud. Therefore, when sharing the first application, there is no need to consider the operating environment of the terminal device, thereby achieving full-platform sharing of the application.

[0016] In some possible implementations, the first link carries an identifier corresponding to the first application.

[0017] In some possible implementations, the method also includes: detecting a third operation, wherein the third operation is used to input a jump type, jump link, parameter conversion rule, and / or priority corresponding to the first operating environment; sending a third message to the cloud, wherein the third message is used to configure the jump type, jump link, parameter conversion rule, and / or priority corresponding to the first operating environment.

[0018] In an embodiment of the present application, the user can dynamically configure the jump type, jump link, parameter conversion rule, and / or priority corresponding to the first operating environment, which can improve the flexibility and diversity of application sharing methods, thereby improving the user experience.

[0019] At the same time, the user dynamically configures the jump type, jump link, parameter conversion rules, and / or priority corresponding to the first operating environment, so that the shared user can open the specified type of application according to the user's intention. For example, when conducting commercial promotion, through the dynamic configuration of the operator, the shared user can open the specified type of application according to the operation intention, which can further enhance the user experience.

[0020] Furthermore, by the user configuring the jump type, jump link, parameter conversion rules, and / or priority corresponding to the first operating environment, the first application opened by the shared terminal device can be more adapted to the terminal device, and the operation effect of the first application can be better, thereby further improving the user experience.

[0021] In some possible implementations, the jump type includes a redirect jump, a deep link jump, and / or a global link jump.

[0022] In some possible implementations, the first operating environment includes one or more of the following: operating system type, browser type, and device manufacturer.

[0023] According to a third aspect, a method for application sharing is provided, which is applied to the cloud, and includes: receiving a first message from a first terminal device, the first message being used to request access to a first application; sending a second link to the first terminal device according to the first message, the second link carrying first information and second information, the first information indicating access to the first application, and the second information indicating a jump type of the second link.

[0024] In an embodiment of the present application, a second link is sent to a first terminal device according to a first message, and the first message carries a jump type of the second link, so that the first terminal device can open the second link according to the jump type of the second link, so that the first terminal device can access a first application of a specified type, thereby directing the terminal device to a specific application, which can improve the user experience.

[0025] At the same time, the second link for accessing the first application is obtained through the cloud, without considering the operating environment of the terminal device, so the full-platform sharing of the application can be achieved.

[0026] In some possible implementations, the first message includes an identifier corresponding to the first application and a first operating environment of the first terminal device.

[0027] In an embodiment of the present application, the first message includes a first operating environment of the first terminal device. Sending a second link to the first terminal device according to the first message can make the first application accessed through the second link more suitable for the first terminal device, and can make the operation effect of the first application better, thereby improving the user experience.

[0028] At the same time, the first application accessed through the second link is more suitable for the first terminal device, which can improve the success rate of application sharing and avoid the situation where the first terminal device cannot open the second link, thereby improving the user experience.

[0029] In some possible implementations, the jump type includes a redirect jump, a deep link jump, and / or a global link jump.

[0030] In some possible implementations, sending the second link to the first terminal device according to the first message includes: generating the second link according to the first message and a preset rule; and sending the second link to the first terminal device.

[0031] In some possible implementations, the preset rule includes a jump type, a jump link, and / or a parameter conversion rule corresponding to the first operating environment.

[0032] In some possible implementations, the first operating environment is one of a plurality of operating environments, and the preset rule includes a jump type, a jump link, a parameter conversion rule, and / or a priority corresponding to each of the plurality of operating environments.

[0033] In some possible implementations, the operating environment includes one or more of the following: operating system type, browser type, and device manufacturer.

[0034] In some possible implementations, the method further includes: receiving a second message from a second terminal device, the second message being used to request a link for sharing the first application; and sending a first link to the second terminal device in response to the second message, the first link being used to access the cloud.

[0035] In an embodiment of the present application, the first application can be shared by accessing the first link in the cloud. Therefore, when sharing the first application, there is no need to consider the operating environment of the terminal device, thereby achieving full-platform sharing of the application.

[0036] In some possible implementations, the first link carries an identifier corresponding to the first application.

[0037] In some possible implementations, the method further includes: receiving a third message from the second terminal device, wherein the third message is used to configure a jump type, jump link, parameter conversion rule, and / or priority corresponding to the first operating environment of the first terminal device.

[0038] In an embodiment of the present application, the user can dynamically configure the jump type, jump link, parameter conversion rule, and / or priority corresponding to the first operating environment through a third message, which can enhance the flexibility and diversity of application sharing methods, thereby enhancing the user experience.

[0039] At the same time, the user dynamically configures the jump type, jump link, parameter conversion rules, and / or priority corresponding to the first operating environment, so that the shared user can open the specified type of application according to the user's intention. For example, when conducting commercial promotion, through the dynamic configuration of the operator, the shared user can open the specified type of application according to the operation intention, which can further enhance the user experience.

[0040] Furthermore, by the user configuring the jump type, jump link, parameter conversion rules, and / or priority corresponding to the first operating environment, the first application opened by the shared terminal device can be more adapted to the terminal device, and the operation effect of the first application can be better, thereby further improving the user experience.

[0041] In a fourth aspect, a terminal device is provided, comprising a module or unit for executing the method in the first aspect or any possible implementation manner of the first aspect.

[0042] In a fifth aspect, a terminal device is provided, comprising a module or unit for executing the method in the second aspect or any possible implementation manner of the second aspect.

[0043] In a sixth aspect, a server is provided, comprising a module or unit for executing the method in the third aspect or any possible implementation manner of the third aspect.

[0044] In the seventh aspect, a terminal device is provided, comprising: a processor and a memory, wherein the processor is coupled to the memory, and the memory is used to store a computer program (also referred to as code, or instruction). When the computer program is executed by the processor, the terminal device executes the method in the first aspect or any possible implementation of the first aspect.

[0045] In some possible implementations, the terminal device also includes a memory coupled to the processor.

[0046] In some possible implementations, there are one or more processors and / or there are one or more memories.

[0047] In some possible implementations, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0048] In an eighth aspect, a terminal device is provided, comprising: a processor and a memory, wherein the processor is coupled to the memory, and the memory is used to store a computer program (also referred to as code, or instruction). When the computer program is executed by the processor, the terminal device executes the method in the second aspect or any possible implementation of the second aspect.

[0049] In some possible implementations, the terminal device also includes a memory coupled to the processor.

[0050] In some possible implementations, there are one or more processors and / or there are one or more memories.

[0051] In some possible implementations, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0052] In the ninth aspect, a server is provided, comprising: a processor and a memory, wherein the processor is coupled to the memory, and the memory is used to store a computer program (also referred to as code, or instruction). When the computer program is executed by the processor, the server executes the method in the third aspect or any possible implementation of the third aspect.

[0053] In some possible implementations, the server further includes a memory coupled to the processor.

[0054] In some possible implementations, there are one or more processors and / or there are one or more memories.

[0055] In some possible implementations, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

[0056] In the tenth aspect, a computer-readable storage medium is provided, on which a computer program (also referred to as code, or instruction) is stored. When the computer program runs on a computer, the computer executes a method in any one of the above aspects or any possible implementation of any one of the aspects.

[0057] In the eleventh aspect, a computer program product is provided, comprising: a computer program (also referred to as code, or instruction), which, when executed on a computer, enables the computer to execute a method in any one of the above aspects or any one of the possible implementations of any one of the aspects.

[0058] In the twelfth aspect, a chip is provided, comprising: a processor and a memory, wherein the memory is used to store a computer program (also referred to as code, or instruction), and the processor is used to call and run the computer program stored in the memory, so that a device (such as a server or a terminal device) equipped with the chip executes a method in any one of the above aspects or any one of the possible implementations of any one of the aspects.

[0059] In an embodiment of the present application, a first message for requesting access to a first application is sent to the cloud, a second link is received from the cloud, and the second link is opened according to the jump type of the second link. This allows the first terminal device to access a first application of a specified type, thereby directing the terminal device to an application of the specified type, thereby improving the user experience.

[0060] At the same time, when a first operation of clicking a first link is detected, the first terminal device obtains a second link for accessing the first application through the cloud without considering the operating environment of the terminal device. Therefore, full-platform sharing of the application can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] Figure 1 A schematic diagram of application sharing in an embodiment.

[0062] Figure 2 A schematic diagram of generating H5 links for various types of applications in one embodiment.

[0063] Figure 3 A schematic diagram of sharing an H5 link through a social platform in an embodiment.

[0064] Figure 4 A schematic diagram of selecting a sharing method for an application in an embodiment.

[0065] Figure 5 A schematic diagram of generating a sharing link according to a sharing method in an embodiment.

[0066] Figure 6 It is a schematic structural diagram of a terminal device in an embodiment of the present application.

[0067] Figure 7 is a schematic diagram of the software architecture of a terminal device in an embodiment of the present application;

[0068] Figure 8 It is a schematic diagram of an application scenario in an embodiment of the present application.

[0069] Fig. 9 It is a schematic diagram of a system architecture in an embodiment of the present application.

[0070] Fig.10 It is a schematic diagram of another application scenario in an embodiment of the present application.

[0071] Fig.11 It is a schematic flowchart of an application sharing method provided in an embodiment of the present application.

[0072] Fig.12 It is a schematic flowchart of another application sharing method provided in an embodiment of the present application.

[0073] Fig.13 It is a schematic structural diagram of an application sharing device provided in one embodiment of the present application.

[0074] Fig.14 It is a schematic structural diagram of an application sharing device provided in another embodiment of the present application.

[0075] Fig.15 It is a schematic structural diagram of an application sharing device provided in yet another embodiment of the present application.

[0076] Fig.16 It is a schematic structural diagram of the device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0077] In the following description, for the purpose of explanation rather than limitation, specific details such as specific system structures and technologies are provided to facilitate a thorough understanding of the embodiments of the present application.

[0078] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or combinations thereof.

[0079] It should also be understood that the term “and / or” used in the specification and appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0080] In the description of the present application specification and the appended claims, the terms "first", "second", "third", etc. are only used to distinguish the descriptions and cannot be understood as indicating or implying relative importance.

[0081] References to "one embodiment" or "some embodiments" etc. described in the specification of this application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0082] In addition, the “plurality” mentioned in the embodiments of the present application may be interpreted as two or more than two.

[0083] There are many types of applications (APP) (also called applications) on terminal devices, including Android applications, iOS applications, Mini programs, quick apps, H5 apps, etc. Among them, Android apps and iOS apps can be native apps installed on terminal devices, and native apps can provide users with a better experience; Mini programs, quick apps, and H5 apps can be lightweight apps that do not require installation and can achieve wider device coverage.

[0084] The same application can also include multiple types of applications, for example, This can include native applications such as Android applications and iOS applications, as well as Light applications such as mini programs, quick applications, and H5 applications.

[0085] Generally, the operation of each application requires the support of the corresponding operating environment. For example, the operation of Android applications depends on the Android operating system (OS), and the operation of iOS applications depends on the iOS operating system. The operation of the applet depends on The operation of quick applications depends on the quick application engine, and the operation of H5 applications depends on the browser.

[0086] When using an application, a user can share the application with other users. For example, a user can share a sharing link with other users on a social platform, and other users can jump to a specific page after clicking the sharing link. It should be noted that the application sharing described in the embodiments of the present application can refer to sharing the application (i.e., the application) with other users, or it can refer to sharing the content in the application with other users, which is not limited in the present application. For ease of description, it will be uniformly described as application sharing in the subsequent embodiments.

[0087] like Figure 1 As shown, developers can develop various types of applications, such as Android applications 11, iOS applications 12, Mini Program 13, and H5 Application 14; Users can use the sharing function provided within the application to share the application to various social platforms, such as 110. 120 , microblog 130 , and message 140 .

[0088] When a user shares an application's sharing link (or sharing page) on a social platform, friends can open the content in the application through the sharing link. However, if the friend's terminal device lacks the operating environment to run the application, the sharing fission of the application will be interrupted.

[0089] The browser is the most widely used software on terminal devices. Each terminal device has a browser installed in its system, and many social software have built-in browsers. In order to ensure successful application sharing and avoid the situation where the shared application cannot be opened, a common method of application sharing is to share the application's H5 link (the application's H5 link can open the application's corresponding H5 application). The H5 link can basically ensure the successful opening of the application.

[0090] For example, Figure 2 As shown, application 21 can be an Android application, application 22 can be an iOS application, application 23 can be an H5 application, and application 24 can be a HarmonyOS meta-service (or, can also be called a HarmonyOS application). When sharing these applications, H5 links corresponding to these applications can be generated and shared to social platforms.

[0091] When sharing various types of applications, you can generate an H5 link based on the content path of the application and share the H5 link of the application on the social platform. At this time, other users can click the H5 link in the social platform to jump to the H5 application corresponding to the application, thereby realizing the sharing of the application.

[0092] For example, the process of sharing an H5 link through a social platform can be as follows: Figure 3As shown, in step 1, developers can develop various types of applications; in step 2, user A can use various types of applications, such as Android application 31, iOS application 32, Mini program 33, and H5 application 34; Step 3, user A can use the sharing function in the application to share the H5 link of the application to the social platform, for example, 310 and 320; Step 4, user B can click the H5 link of the shared application on the social platform; Step 5, the browser can open the H5 application (corresponding to the shared application).

[0093] However, the experience of opening shared content through a web page (such as an H5 link) is usually very poor. It can only ensure that the sharing of the application is not interrupted (or in other words, the shared application can be opened). Moreover, this sharing method cannot guide users to a specified type of application with a better experience (such as the native application corresponding to the application). The shared application will be limited to a specific range.

[0094] Users can also share apps through other methods. Another common method of sharing apps is for users to select the social app channel to share the app. Figure 4 When a user shares an application, a sharing control 410 will pop up, prompting the user to select a sharing method (or sharing channel) for the application, such as Figure 4 The controls shown are "Private Message and Group" 411, " Friends” 412, “Friends Circle” 413, 414, " "Space" 415, "Alipay Friends" 416, "SMS" 417, "Send Email" 418.

[0095] After the user selects, the application can generate a corresponding sharing link based on the sharing method selected by the user. Figure 5 As shown, the application can be an Android application in the Android system, an iOS application in the iOS system, In The sharing module of the app can include adapters corresponding to various sharing methods. When sharing, you can The adapter 510 generates the corresponding Mini Program 51; When the user passes When sharing, you can Adapter 520 generates Mini program 52; when the user chooses to copy the link, an H5 link 53 can be generated through an H5 adapter 530; when the user chooses to share via a QR code, a QR code image 54 corresponding to the H5 link can be generated through a QR code adapter 540.

[0096] However, an application shared on a social platform can only be shared on that platform and cannot be shared on other platforms. For example, Mini programs can only be internal sharing; unable to direct users to a specific type of application with a better experience, for example, unable to Users of mini programs and H5 applications are redirected back to the native applications of the application. They cannot be redirected to specified types of applications according to the specified logic, and operators cannot dynamically configure the diversion rules.

[0097] To sum up, the existing sharing mechanism has many limitations, which will affect the user experience.

[0098] Based on the above technical problems, the embodiment of the present application proposes a method and device for application sharing, which can guide terminal devices to applications of a specified type and realize full-platform sharing of applications. The embodiment of the present application is described in detail below in conjunction with the accompanying drawings.

[0099] The application sharing method proposed in the embodiment of the present application can be applied to terminal devices. The terminal device in the embodiment of the present application can be a mobile phone, a tablet computer, a laptop computer, a personal computer (ultra-mobile personal computer, UMPC), a personal digital assistant (personal digital assistant, PDA), a smart watch, a wearable device, a vehicle-mounted device, an augmented reality (augmented reality, AR) device, a virtual reality (virtual reality, VR) device, a vehicle-mounted device, a smart screen, a smart car, a smart TV, a smart speaker, etc. The embodiment of the present application does not limit the specific form of the terminal device.

[0100] See also Figure 6 , Figure 6 A schematic structural diagram of a terminal device according to an embodiment of the present application is shown.

[0101] The terminal device 600 may include a processor 610, an external memory interface 620, an internal memory 621, a universal serial bus (USB) interface 630, a charging management module 640, a power management module 641, a battery 642, an antenna 1, an antenna 2, a mobile communication module 650, a wireless communication module 660, a sensor module 670, a button 680, and a display screen 690, etc. Among them, the sensor module 670 may include a pressure sensor 670A, a gyroscope sensor 670B, an acceleration sensor 670C, a temperature sensor 670D, a touch sensor 670E, and the like.

[0102] It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the terminal device 600. In other embodiments of the present application, the terminal device 600 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0103] The processor 610 may include one or more processing units, for example, the processor 610 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated into one or more processors. The controller may generate an operation control signal according to the instruction opcode and the timing signal to complete the control of fetching and executing instructions.

[0104] The processor 610 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 610 is a cache memory. The memory may store instructions or data that the processor 610 has just used or cyclically used. If the processor 610 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 610, and thus improves the efficiency of the system.

[0105] In some embodiments, the processor 610 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0106] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 610 may include multiple groups of I2C buses. The processor 610 may be coupled to the touch sensor 670E, the charger, etc. through different I2C bus interfaces. For example, the processor 610 may be coupled to the touch sensor 670E through the I2C interface, so that the processor 610 communicates with the touch sensor 670E through the I2C bus interface to realize the touch function of the terminal device 600.

[0107] The UART interface is a universal serial data bus for asynchronous communication. The bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is generally used to connect the processor 610 and the wireless communication module 660. For example, the processor 610 communicates with the Bluetooth module in the wireless communication module 660 through the UART interface to realize the Bluetooth function. The MIPI interface can be used to connect the processor 610 to peripheral devices such as the display screen 690. The MIPI interface includes a camera serial interface (CSI), a display serial interface (DSI), etc. In some embodiments, the processor 610 and the display screen 690 communicate through the DSI interface to realize the display function of the terminal device 600.

[0108] The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface can be used to connect the processor 610 with the display screen 690, the wireless communication module 660, the sensor module 670, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0109] The USB interface 630 is an interface that complies with the USB standard specification, and specifically can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 630 can be used to connect a charger to charge the terminal device 600, and can also be used to transmit data between the terminal device 600 and peripheral devices. It can also be used to connect headphones to play audio through the headphones. The interface can also be used to connect other terminal devices, such as AR devices, etc.

[0110] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present application is only a schematic illustration and does not constitute a structural limitation on the terminal device 600. In other embodiments of the present application, the terminal device 600 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0111] The charging management module 640 is used to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 640 may receive charging input from a wired charger through the USB interface 630. In some wireless charging embodiments, the charging management module 640 may receive wireless charging input through a wireless charging coil of the terminal device 600. While the charging management module 640 is charging the battery 642, it may also power the terminal device through the power management module 641.

[0112] The power management module 641 is used to connect the battery 642, the charging management module 640 and the processor 610. The power management module 641 receives input from the battery 642 and / or the charging management module 640, and supplies power to the processor 610, the internal memory 621, the display screen 690, and the wireless communication module 660. The power management module 641 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc. In some other embodiments, the power management module 641 can also be set in the processor 610. In other embodiments, the power management module 641 and the charging management module 640 can also be set in the same device.

[0113] The wireless communication function of the terminal device 600 can be implemented through antenna 1, antenna 2, mobile communication module 650, wireless communication module 660, modem processor and baseband processor.

[0114] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in terminal device 600 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0115] The mobile communication module 650 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the terminal device 600. The mobile communication module 650 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 650 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 650 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 650 can be set in the processor 610. In some embodiments, at least some of the functional modules of the mobile communication module 650 can be set in the same device as at least some of the modules of the processor 610.

[0116] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor displays an image or video through the display screen 690. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 610 and be set in the same device as the mobile communication module 650 or other functional modules.

[0117] The wireless communication module 660 can provide wireless communication solutions including wireless local area networks (WLAN) (such as Wi-Fi networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., applied to the terminal device 600. The wireless communication module 660 can be one or more devices integrating at least one communication processing module. The wireless communication module 660 receives electromagnetic waves via the antenna 2, modulates the frequency of the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 610. The wireless communication module 660 can also receive the signal to be sent from the processor 610, modulate the frequency of it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0118] In some embodiments, the antenna 1 of the terminal device 600 is coupled to the mobile communication module 650, and the antenna 2 is coupled to the wireless communication module 660, so that the terminal device 600 can communicate with the network and other devices through wireless communication technology. The wireless communication technology 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), BT, GNSS, WLAN, NFC, FM, and / or IR technology. 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).

[0119] The terminal device 600 implements the display function through a GPU, a display screen 690, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 690 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 610 may include one or more GPUs, which execute program instructions to generate or change display information.

[0120] The display screen 690 is used to display images, videos, etc. The display screen 690 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. In some embodiments, the terminal device 600 may include 1 or N display screens 690, where N is a positive integer greater than 1.

[0121] The digital signal processor is used to process digital signals, and can process not only digital image signals but also other digital signals. For example, when the terminal device 600 is selecting a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0122] Video codecs are used to compress or decompress digital videos. The terminal device 600 may support one or more video codecs. Thus, the terminal device 600 may play or record videos in various coding formats, such as moving picture experts group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0123] NPU is a neural network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transmission mode between neurons in the human brain, it can quickly process input information and can also continuously self-learn. Through NPU, applications such as intelligent cognition of the terminal device 600 can be realized, such as image recognition, face recognition, voice recognition, text understanding, etc.

[0124] The external memory interface 620 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device 600. The external memory card communicates with the processor 610 through the external memory interface 620 to implement a data storage function, such as saving files such as videos in the external memory card.

[0125] The internal memory 621 can be used to store computer executable program codes, which include instructions. The internal memory 621 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as an image playback function, etc.), etc. The data storage area may store data created during the use of the terminal device 600 (such as a phone book, etc.), etc. In addition, the internal memory 621 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 610 executes various functional applications and data processing of the terminal device 600 by running instructions stored in the internal memory 621 and / or instructions stored in a memory provided in the processor.

[0126] The pressure sensor 670A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 670A can be set on the display screen 690. There are many types of pressure sensors 670A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. The capacitive pressure sensor can be a parallel plate including at least two conductive materials. When a force acts on the pressure sensor 670A, the capacitance between the electrodes changes. The terminal device 600 determines the intensity of the pressure according to the change in capacitance. When a touch operation acts on the display screen 690, the terminal device 600 detects the touch operation intensity according to the pressure sensor 670A. The terminal device 600 can also calculate the touch position according to the detection signal of the pressure sensor 670A. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities can correspond to different operation instructions. For example: when a touch operation with a touch operation intensity less than the first pressure threshold acts on the short message application icon, an instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold acts on the short message application icon, an instruction to create a new short message is executed.

[0127] The gyroscope sensor 670B can be used to determine the motion posture of the terminal device 600. In some embodiments, the angular velocity of the terminal device 600 around three axes (i.e., x, y, and z axes) can be determined by the gyroscope sensor 670B. The gyroscope sensor 670B can be used for navigation and somatosensory game scenes.

[0128] The acceleration sensor 670C can detect the magnitude of the acceleration of the terminal device 600 in all directions (generally three axes). When the terminal device 600 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of the terminal device and applied to applications such as horizontal and vertical screen switching and pedometers.

[0129] The temperature sensor 670D is used to detect temperature. In some embodiments, the terminal device 600 uses the temperature detected by the temperature sensor 670D to execute a temperature processing strategy. For example, when the temperature reported by the temperature sensor 670D exceeds a threshold, the terminal device 600 performs a reduction in the performance of a processor located near the temperature sensor 670D to reduce power consumption and implement thermal protection. In other embodiments, when the temperature is lower than another threshold, the terminal device 600 heats the battery 642 to avoid abnormal shutdown of the terminal device 600 due to low temperature. In other embodiments, when the temperature is lower than another threshold, the terminal device 600 performs a boost on the output voltage of the battery 642 to avoid abnormal shutdown caused by low temperature.

[0130] The touch sensor 670E is also called a "touch control device". The touch sensor 670E can be set on the display screen 690, and the touch sensor 670E and the display screen 690 form a touch screen, also called a "touch control screen". The touch sensor 670E is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 690. In other embodiments, the touch sensor 670E can also be set on the surface of the terminal device 600, which is different from the position of the display screen 690.

[0131] The key 680 includes a power button, a volume button, etc. The key 680 may be a mechanical key or a touch key. The terminal device 600 may receive key input and generate key signal input related to user settings and function control of the terminal device 600.

[0132] The software system of the terminal device 600 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. For example, the software system of the terminal device 600 may adopt an Android operating system (OS), a Harmony OS, or iOS with a layered architecture. The embodiment of the present application takes the Android system with a layered architecture as an example to exemplify the software structure of the terminal device 600.

[0133] Figure 7 It is a software structure block diagram of the terminal device 600 in the embodiment of the present application.

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

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

[0136] like Figure 7 As shown, the application package may include camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message and other applications.

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

[0138] like Figure 7 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, and the like.

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

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

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

[0142] The phone manager is used to provide communication functions of the terminal device 600, such as management of call status (including connection, disconnection, etc.).

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

[0144] 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, the terminal device vibrates, the indicator light flashes, etc.

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

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

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

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

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

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

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

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

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

[0154] See also Figure 8 , Figure 8 A schematic diagram of an application scenario provided by an embodiment of the present application is shown.

[0155] like Figure 8 As shown, the users of this application may include users and operators; the usage scenarios of this application include: users share applications with other users, operators share applications when promoting advertisements, and users or operators configure sharing experiences (for example, operators configure their sales intentions to prioritize the launch of certain types of applications when certain conditions are met); the application types supported by this application may include: Android applications, iOS applications, Mini programs, Hongmeng Meta-Services, H5 applications, etc.; the social platforms supported by this application may include: Etc.; The cloud services provided by this application may include: generating a sharing link that is universal for all platforms in the cloud sharing service, configuring application startup rules in the sharing service operation portal (portal), and users accessing the corresponding application through the sharing link according to the startup rules.

[0156] See also Fig. 9 , Fig. 9 A schematic diagram of a system architecture provided by an embodiment of the present application is shown.

[0157] like Fig. 9 As shown, the system architecture may include: cloud 910, operator 920, user 930 and application 940. The operator 920 may be an operator and promoter of the application; the user 930 may be a user of the application; the application 940 may include various types of applications, such as Android application 941, iOS application 942, Mini-programs 943, H5 applications 944, and Hongmeng meta-services 945; the cloud 910 can provide a variety of functions for application sharing, such as generating sharing links, configuring application startup rules and application access services, etc. The cloud 910 may include a sharing service operation portal 911 and a sharing service 912 ( Fig. 9 (not shown in the figure), wherein the sharing service operation portal 911 can generate sharing links and configure application startup rules, and the sharing service 912 can provide application access services and open specified types of applications according to the startup rules and the user's (terminal device) operating environment.

[0158] See also Fig.10 , Fig.10 A schematic diagram showing another application scenario provided by an embodiment of the present application is shown.

[0159] like Fig.10 As shown, the operator can apply for the sharing link of the application from the sharing service operation portal, and can also configure the startup rules of the application through the sharing service operation portal; the sharing service operation portal can import the startup rules configured by the operator into the configuration database, and the configuration database can be set in the sharing service; the user can click on the sharing link and access the sharing service; the sharing service can open the specified type of application (corresponding to the sharing link) based on the sharing link.

[0160] The sharing service operation portal can be accessed through a web page or an application programming interface (API). For example, a user can open a web page corresponding to the sharing service operation portal, and request the sharing service operation portal to generate a sharing link through the web page (such as clicking a sharing control or link in the web page). The user can also enter the startup rules of the application in the web page to configure the startup rules in the sharing service operation portal; or the user can also call the API corresponding to the sharing service operation portal, and request the sharing service operation portal to generate a sharing link through the API. The user can also enter the startup rules of the application through the API to configure the startup rules in the sharing service operation portal.

[0161] It should be noted that in the above embodiment, only the cloud including the sharing service operation portal and the sharing service is taken as an example. The cloud in the embodiment of the present application may include more or fewer modules (or units) than shown in the figure, and the function for application sharing provided by the cloud can also be performed by more or fewer modules (or units). This application does not limit the component modules in the cloud and the functions corresponding to each component module.

[0162] Next, we will continue to take the cloud including the sharing service operation portal and sharing service as an example. Fig.11 and Fig.12 The method for application sharing provided in the embodiment of the present application is exemplified.

[0163] Fig.11 1100 is a schematic flow chart of a method for application sharing provided by the present application. The method 1100 may include S1110 to S1140, and each step is described in detail below. Optionally, when the cloud includes a sharing service operation portal and a sharing service, the steps performed by the cloud in the following method 1100 may be performed by the sharing service.

[0164] S1110: The first terminal device detects a first operation of clicking a first link.

[0165] The first terminal device may be a terminal device of the shared application. For example, an operator or user may generate a sharing link and send the sharing link to the first terminal device, and the first terminal device may open the application or a corresponding page in the application through the sharing link.

[0166] In some embodiments, the first link may be used to access the cloud. Optionally, the first link may be understood as a link for sharing the first application, for example, a sharing link generated by an operator or user and shared to the first terminal device as described in the above embodiments.

[0167] In some embodiments, the first link may carry an identifier corresponding to the first application. For example, the identifier (app id) corresponding to the first application may be 1. In this way, the first link may indicate to the first terminal device and / or the cloud the application that the first link requests to access.

[0168] In some embodiments, the first link may also carry a path or address of a specified page in the first application. In this way, the first link may indicate to the first terminal device and / or the cloud the specified page in the application that the first link requests to access.

[0169] In some embodiments, the first link may be a uniform resource locator (URL). For example, the first link may be:

[0170] http: / / share-service-domain / app-id / ${page-path}? ${var1}=${value1}&${var2}=${value2}

[0171] Wherein, share-service-domain may represent the domain name of the first link, and app-id may represent the identifier corresponding to the first application. Optionally, http: / / share-service-domain / app-id / may be a fixed value, for example, http: / / redirect.company.com / 1 / .

[0172] Among them, ${page-path} can represent the path of the specified page in the first application, and ${var1}=${value1} and ${var2}=${value2} can represent parameter key-value pairs. Optionally, there can be no or more parameter key-value pairs. For example, if the specified page in the first application is the about page of the application, and the parameter key-value pair is parameterless, then the path (such as ${page-path}?${var1}=${value1}&${var2}=${value2} in the first link) can be http: / / redirect.company.com / 1 / about. If the specified page in the first application is the about page, and the parameter key-value pair carries the parameter "language is English", then the path is http: / / redirect.company.com / 1 / about?language=en.

[0173] The first operation may refer to the user clicking the first link or a control corresponding to the first link on the display screen of the first terminal device.

[0174] S1120, in response to the first operation, the first terminal device sends a first message to the cloud according to the first link.

[0175] The first message may be used to request access to the first application. Optionally, when the user clicks the first link, the first terminal device may be triggered to send the first message to the cloud.

[0176] Optionally, the first message may include an identifier corresponding to the first application and a first operating environment of the first terminal device. The operating environment may include one or more of the following: operating system type, browser type, and device manufacturer. For example, the first operating environment may include one or more of the following: operating system type of the first terminal device, browser type of the first terminal device, and device manufacturer of the browser (or first terminal device). Optionally, the operating system type in the embodiment of the present application may be an Android system, a Hongmeng system, or an iOS system, etc.

[0177] In an embodiment of the present application, the second link is obtained from the cloud, and the first operating environment of the first terminal device is sent to the cloud. The first message includes an identifier corresponding to the first application and the first operating environment of the first terminal device. This can make the first application accessed through the second link more suitable for the first terminal device, and can make the operation effect of the first application better, thereby improving the user experience.

[0178] At the same time, sending the first operating environment of the first terminal device to the cloud makes the first application accessed through the second link more suitable for the first terminal device, which can also improve the success rate of application sharing and avoid the situation where the first terminal device cannot open the second link, thereby improving the user experience.

[0179] In some embodiments, the first message may be a hypertext transfer protocol (http) request message. For example, the first message may carry a first link and a first field, the first link includes an identifier corresponding to the first application, and the first field includes the first operating environment.

[0180] Optionally, the first field may be the USER-AGENT field in the request header of the http request message. When accessing the first link, the USER-AGENT field may be "Mozilla / 5.0 (iPhone; CPU iPhone OS 5_1like Mac OS X) AppleWebKit / 534.46 (KHTML, like Gecko) Mobile / 9B176 MicroMessenger / 4.3.2", where iPhone in the USER-AGENT field may indicate that the user's mobile phone system is iOS, and MicroMessenger may indicate that the device manufacturer of the browser is

[0181] It should be noted that, when multiple browsers are installed in the first terminal device, the browser type of the first terminal device may refer to the type of the browser that opens the first link in the first terminal device.

[0182] S1130, the cloud sends a second link to the first terminal device based on the first link.

[0183] The second link may open an application or a corresponding page in the application. Optionally, the second link may carry the first information and the second information. Optionally, the first information may indicate access to the first application. Optionally, the second information may indicate a jump type of the second link.

[0184] Among them, the jump type may include redirect jump (such as H5 redirect jump), deep link jump, and / or universal link jump. For example, redirect jump may refer to redirecting to the target page in an application or application through a web page (Web); deep link jump may also be called scheme jump, which may refer to pulling up the target page in the application or application corresponding to deep links (or scheme) through a browser; global link may refer to carrying a global link in the returned link (such as web hypertext markup language (html)), and launching the target page in the application or application in the iOS system through the global link.

[0185] Optionally, deep links redirection can be applied to Android system. For a detailed introduction to deep links redirection, please refer to the following link:

[0186] https: / / developer.android.com / training / app-links / deep-linking?hl=zh-cn

[0187] Optionally, universal links redirection can be applied to iOS system. For a detailed introduction to universal links redirection, please refer to the following link:

[0188] https: / / developer.apple.com / ios / universal-links /

[0189] In some embodiments, before the above S1130, the method 1100 may further include step S1150, which is as follows:

[0190] S1150, the cloud generates a second link according to the first message and preset rules.

[0191] The preset rules may include a jump type, a jump link, and / or a parameter conversion rule corresponding to the first operating environment. The jump link may refer to a jump link corresponding to the first link, and the parameter conversion rule may indicate a rule (or method) for converting a parameter key-value pair in the first link into a parameter key-value pair in the second link. Optionally, the preset rules may be stored in a database in the cloud.

[0192] In some embodiments, the preset rules may include jump types, jump links, parameter conversion rules, and / or priorities corresponding to multiple operating environments, and the first operating environment may be one of the multiple operating environments. At this time, the preset rules may also include the priority corresponding to each operating environment in the multiple operating environments. For example, the preset rules may include jump types, jump links, parameter conversion rules, and / or priorities corresponding to each operating environment in the multiple operating environments. Optionally, the priority may be a value of 0 to 10, and a larger value may indicate a lower priority.

[0193] In some embodiments, the cloud can traverse preset rules based on the first operating environment carried in the first message to determine the jump type, jump link, and parameter conversion rule that match the first operating environment. Optionally, when the first operating environment matches multiple groups of jump types, jump links, and parameter conversion rules, the jump type, jump link, and parameter conversion rule that match the first operating environment are determined based on the priority of each group of jump types, jump links, and parameter conversion rules.

[0194] For example, the cloud can obtain preset rules from the database according to the app id in the first link. The preset rules may include multiple startup rules (such as each startup rule can indicate the jump type, jump link, parameter conversion rule, and priority corresponding to an operating environment), corresponding to multiple operating environments respectively, and traverse all startup rules from high to low according to the priority. Taking the preset rules including two startup rules as an example, these two startup rules can be cycled in sequence. The priority of the first startup rule is 0, and the corresponding operating environment is the iOS operating system. The jump type is global link jump, the jump link is applink: / / link-domain / ${params}, and the parameter conversion rule is direct assignment; the priority of the second startup rule is 1, the jump type is redirect jump, the jump link is http: / / h5-domain / ${params}, and the parameter conversion rule is direct assignment. Among them, the second startup rule can be a guaranteed startup rule, that is, a startup rule executed when other rules do not meet the conditions.

[0195] It should be noted that the jump type, jump link, parameter conversion rule, and priority corresponding to the operating environment can be set to full match (AND) or single match (OR), where full match may refer to that the jump type, jump link, parameter conversion rule, and priority corresponding to an operating environment need to be matched in their entirety, and single match may refer to that one or more of the jump type, jump link, parameter conversion rule, and priority corresponding to an operating environment need to be matched.

[0196] In some embodiments, the cloud can determine the second information, that is, the jump type of the second link, according to the jump type matching the first operating environment. For example, the cloud can use the jump type matching the first operating environment as the jump type of the second link.

[0197] In some embodiments, the cloud can determine the second link based on the jump link and parameter conversion rules matched by the first operating environment. For example, continuing to take the preset rules including the above two startup rules as an example, if the operating system of the first terminal device is iOS system and the device manufacturer of the browser is Then the matching condition of the first startup rule "the operating system is iOS" is met. At this time, it can be determined that the jump type of the second link is a global link jump. The jump link of the first startup rule is applink: / / link-domain / ${params}, and the parameter conversion rule is direct assignment. The parameter key-value pair in the first link (such as "about?language=en") can be used to directly assign the parameter key-value pair in the jump link, that is, the generated second link can be applink: / / link-domain / about?language=en.

[0198] Optionally, if the operating system of the first terminal device is the Android system, the above-mentioned second startup rule is satisfied. At this time, it can be determined that the jump type of the second link is a redirect jump, and the jump link of the second startup rule is http: / / h5-domain / ${params}. The parameter conversion rule is direct assignment, and the parameter key-value pair in the first link (such as "about?language=en") can be used to directly assign the parameter key-value pair in the jump link, that is, the generated second link can be http: / / h5-domain / about?language=en.

[0199] In some embodiments, when the second link carries the first information for indicating access to the first application, the generated second link may be applink: / / link-domain / 1 / about?language=en, where "1" may be an identifier corresponding to the first application, and may be used to indicate access to the first application.

[0200] S1140: The first terminal device opens the second link according to the jump type of the second link.

[0201] In the embodiment of the present application, the first application can be shared by accessing the second link in the cloud. Therefore, when sharing the first application, there is no need to consider the operating environment of the terminal device, thereby achieving full-platform sharing of the application.

[0202] The first terminal device can open the second link in a variety of different ways according to the jump type of the second link.

[0203] For example, in S1140a, if the jump type of the second link is H5 redirect jump, the cloud can return the second link (such as http: / / h5-domain / about?language=en) to the first terminal device through a redirect request message, and accordingly, the browser can access the H5 application pointed to by the second link.

[0204] For another example, in S1140b, if the jump type of the second link is a deep link jump, when the first terminal device receives the second link, the browser of the first terminal device can launch the application pointed to by the second link (such as example-scheme: / / about?language=en).

[0205] For another example, in S1140c, if the jump type of the second link is a global link jump, when the first terminal device receives the second link, the browser of the first terminal device can launch the application pointed to by the second link (such as applink: / / link-domain / ${params}).

[0206] In an embodiment of the present application, a first message for requesting access to a first application is sent to the cloud, a second link is received from the cloud, and the second link is opened according to the jump type of the second link. This allows the first terminal device to access a first application of a specified type, thereby directing the terminal device to an application of the specified type, thereby improving the user experience.

[0207] At the same time, when a first operation of clicking a first link is detected, the first terminal device obtains a second link for accessing the first application through the cloud without considering the operating environment of the terminal device. Therefore, full-platform sharing of the application can be achieved.

[0208] The above embodiment describes a method for a first terminal device to access a first application based on a first link. Fig.12 , taking the cloud including a sharing service operation portal and a sharing service as an example, an embodiment of a second terminal device obtaining a first link through the cloud is introduced.

[0209] It should be noted that when the cloud includes fewer modules (or units) than shown in the figure, Fig.12 The actions performed by the sharing service operation portal and the sharing service can all be performed by the cloud or this module (or unit) in the cloud; when the cloud may include more modules (or units) than shown in the figure, Fig.12 The actions performed by the sharing service operation portal and the sharing service can be respectively performed by these modules (or units), and no limitation is made to this in the embodiments of the present application.

[0210] Fig.12 12 is a schematic flow chart of a method for application sharing provided by the present application. The method 1200 may include S1210 to S1280, and each step is described in detail below.

[0211] S1210: The second terminal device detects a second operation.

[0212] The second operation may be used to request a link for sharing the first application.

[0213] In some embodiments, the second operation can be understood as the user clicking on a control or link on the display screen of the second terminal device for requesting to share the first application. For example, the user can click on a link corresponding to the access sharing service operation portal on the display screen of the second terminal device, and the link can be used to request to share the first application.

[0214] S1220: In response to the second operation, the second terminal device sends a second message to the sharing service operation portal.

[0215] The second message may be used to request the link for sharing the first application.

[0216] S1230: In response to the second message, the sharing service operation portal may send a fourth message to the sharing service.

[0217] Optionally, the fourth message may be used to indicate that the second terminal device requests to share a link of the first application, or the fourth message may be used to indicate that the second terminal device requests to share the first application.

[0218] In some embodiments, upon receiving the fourth message, the sharing service may assign an identifier to the first application (or may also be referred to as an identifier corresponding to the first application or an identifier of the first application). Optionally, the identifier may be a unique identifier in the cloud application system. For example, the identifier (app id) assigned by the sharing service to the first application may be 1.

[0219] In some embodiments, upon receiving the fourth message, the sharing service may generate a first link. Optionally, the first link may be used to access the cloud. Optionally, the first link may be understood as a link for sharing the first application, for example, a sharing link generated by an operator or user and shared to the first terminal device as described in the aforementioned embodiments.

[0220] The detailed description of the first link may refer to the embodiment of the above method 1100, which will not be repeated here. For example, the first link may be:

[0221] http: / / share-service-domain / app-id / ${page-path}? ${var1}=${value1}&${var2}=${value2}

[0222] Among them, share-service-domain can represent the domain name of the first link, app-id can represent the identifier corresponding to the first application, ${page-path} can represent the path of the specified page in the first application, ${var1}=${value1} and ${var2}=${value2} can represent parameter key-value pairs.

[0223] S1240: The sharing service may send a fifth message to the sharing service operation portal.

[0224] Optionally, the fifth message may carry an identifier corresponding to the first application and the first link.

[0225] S1250: The sharing service operation portal sends a first link to the second terminal device.

[0226] In some embodiments, the sharing service operation portal may send an identifier corresponding to the first application and the first link to the second terminal device.

[0227] In an embodiment of the present application, the first application can be shared by accessing the first link in the cloud. Therefore, when sharing the first application, there is no need to consider the operating environment of the terminal device, thereby achieving full-platform sharing of the application.

[0228] In some embodiments, the method 1200 may further include step S1260, which is as follows:

[0229] S1260: The second terminal device detects a third operation.

[0230] The third operation can be used to input the jump type, jump link, parameter conversion rule, and / or priority corresponding to the first operating environment. Optionally, the jump type, jump link, parameter conversion rule, and / or priority corresponding to the first operating environment can be stored in a database in the cloud as a preset rule (or a startup rule in the preset rule). For example, the user can enter the jump type, jump link, and / or parameter conversion rule corresponding to the first operating environment in the web page corresponding to the access sharing service operation portal through the display screen of the second terminal device.

[0231] Among them, the jump type may include redirect jump (such as H5 redirect jump), deep link (scheme) jump, and / or global link (universal links) jump, the jump link may refer to the jump link corresponding to the first link, and the parameter conversion rule may indicate the rule (or method) for converting the parameter key-value pair in the first link into the parameter key-value pair in the second link.

[0232] In an embodiment of the present application, the user can dynamically configure the jump type, jump link, parameter conversion rule, and / or priority corresponding to the first operating environment, which can improve the flexibility and diversity of application sharing methods, thereby improving the user experience.

[0233] At the same time, the user dynamically configures the jump type, jump link, parameter conversion rules, and / or priority corresponding to the first operating environment, so that the shared user can open the specified type of application according to the user's intention. For example, when conducting commercial promotion, through the dynamic configuration of the operator, the shared user can open the specified type of application according to the operation intention, which can further enhance the user experience.

[0234] Furthermore, by the user configuring the jump type, jump link, parameter conversion rules, and / or priority corresponding to the first operating environment, the first application opened by the shared terminal device can be more adapted to the terminal device, and the operation effect of the first application can be better, thereby further improving the user experience.

[0235] In some embodiments, the user can input the jump type, jump link, parameter conversion rule corresponding to multiple operating environments (the multiple operating environments include the first operating environment), and at this time, the user can configure the priority corresponding to each operating environment. For example, the user can enter the jump type, jump link, parameter conversion rule, and priority corresponding to the first operating environment in the web page corresponding to the sharing service operation portal through the display screen of the second terminal device.

[0236] Optionally, the jump type, jump link, parameter conversion rule, and / or priority corresponding to one of the multiple operating environments may be configured as a guaranteed startup rule, that is, a startup rule executed when other rules do not meet the conditions.

[0237] It should be noted that in S1260, if the jump type, jump link, parameter conversion rule, and / or priority corresponding to only one operating environment can be entered at a time in the web page corresponding to the sharing service operation portal, and the user needs to enter the jump type, jump link, parameter conversion rule, and / or priority corresponding to multiple operating environments, then the user can make multiple entries in the web page corresponding to the sharing service operation portal; if the jump type, jump link, parameter conversion rule, and / or priority corresponding to multiple operating environments can be entered at a time in the web page corresponding to the sharing service operation portal, and the user needs to enter the jump type, jump link, parameter conversion rule, and / or priority corresponding to multiple operating environments, then the user can make one entry in the web page corresponding to the sharing service operation portal.

[0238] In some embodiments, the method 1200 may further include step S1270, which is as follows:

[0239] S1270: The second terminal device sends a third message to the sharing service operation portal.

[0240] The third message may be used to configure a jump type, a jump link, a parameter conversion rule, and / or a priority corresponding to the first operating environment.

[0241] In some embodiments, if the user inputs jump types, jump links, parameter conversion rules, and / or priorities corresponding to multiple operating environments (the multiple operating environments include the first operating environment), then the second terminal device may send the jump types, jump links, parameter conversion rules, and / or priorities corresponding to the multiple operating environments (the multiple operating environments include the first operating environment) to the sharing service operation portal through a third message, or the second terminal device may also send the jump types, jump links, parameter conversion rules, and / or priorities corresponding to the multiple operating environments (the multiple operating environments include the first operating environment) to the sharing service operation portal multiple times.

[0242] In some embodiments, the method 1200 may further include step S1280, which is as follows:

[0243] S1280: The sharing service operation portal sends a sixth message to the sharing service.

[0244] The sixth message may carry the jump type, jump link, parameter conversion rule, and / or priority corresponding to the first operating environment.

[0245] In some embodiments, if the user inputs jump types, jump links, parameter conversion rules, and / or priorities corresponding to multiple operating environments (multiple operating environments including the first operating environment), then the sharing service operation portal sends the jump types, jump links, parameter conversion rules, and / or priorities corresponding to the multiple operating environments (multiple operating environments including the first operating environment) to the sharing service through a sixth message, or the sharing service operation portal may also send the jump types, jump links, parameter conversion rules, and / or priorities corresponding to the multiple operating environments (multiple operating environments including the first operating environment) to the sharing service multiple times.

[0246] In some embodiments, the sharing service may store (or record) the jump type, jump link, parameter conversion rule, and / or priority corresponding to the first operating environment. For example, the sharing service may store the jump type, jump link, parameter conversion rule, and / or priority corresponding to the first operating environment in a database.

[0247] Optionally, the sharing service may return a response message to the sharing service operation portal to indicate that the jump types, jump links, parameter conversion rules, and / or priorities corresponding to the multiple operating environments (the multiple operating environments include the first operating environment) are configured successfully.

[0248] Optionally, the sharing service operation portal may also return a response message to the second terminal device to indicate that the jump types, jump links, parameter conversion rules, and / or priorities corresponding to the multiple operating environments (the multiple operating environments include the first operating environment) are configured successfully.

[0249] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0250] Combination of the above Figures 1 to 12 , describes the method embodiment of the present application in detail, and the following is combined with Figures 13 to 16 , describes the device embodiment of the present application in detail. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the parts not described in detail can refer to the previous method embodiment.

[0251] Fig.13 is a schematic structural diagram of an application sharing device provided in an embodiment of the present application. Fig.13 As shown, the device 1300 includes a detection unit 1310, a sending unit 1320, a receiving unit 1330 and an opening unit 1340, which are specifically as follows:

[0252] A detection unit 1310 is configured to detect a first operation of clicking a first link, where the first link is used to access the cloud;

[0253] A sending unit 1320, configured to send a first message to the cloud according to the first link in response to the first operation, where the first message is used to request access to a first application;

[0254] The receiving unit 1330 is configured to receive a second link from the cloud, where the second link carries first information and second information, where the first information indicates access to the first application, and the second information indicates a jump type of the second link;

[0255] The opening unit 1340 is configured to open the second link according to the jump type of the second link.

[0256] Optionally, the first message includes an identifier corresponding to the first application and a first operating environment of the device 1300 .

[0257] Optionally, the jump type includes a redirect jump, a deep link jump, and / or a global link jump.

[0258] Optionally, the first operating environment includes one or more of the following: operating system type, browser type, and device manufacturer.

[0259] Optionally, the first link carries an identifier corresponding to the first application.

[0260] Fig.14 is a schematic structural diagram of an application sharing device provided in an embodiment of the present application. Fig.14 As shown, the device 1400 includes a detection unit 1410, a sending unit 1420 and a receiving unit 1430, which are specifically as follows:

[0261] A detection unit 1410 is configured to detect a second operation, where the second operation is used to request sharing of a link of the first application;

[0262] A sending unit 1420, configured to send a second message to the cloud in response to the second operation, wherein the second message is used to request the link for sharing the first application;

[0263] The receiving unit 1430 is configured to receive a first link from the cloud, where the first link is used to access the cloud.

[0264] Optionally, the first link carries an identifier corresponding to the first application.

[0265] Optionally, the detection unit 1410 is further configured to: detect a third operation, wherein the third operation is used to input a jump type, a jump link, a parameter conversion rule, and / or a priority corresponding to the first operating environment;

[0266] A third message is sent to the cloud, where the third message is used to configure a jump type, a jump link, a parameter conversion rule, and / or a priority corresponding to the first operating environment.

[0267] Optionally, the jump type includes a redirect jump, a deep link jump, and / or a global link jump.

[0268] Optionally, the first operating environment includes one or more of the following: operating system type, browser type, and device manufacturer.

[0269] Fig.15 is a schematic structural diagram of an application sharing device provided in an embodiment of the present application. Fig.15 As shown, the device 1500 includes a receiving unit 1510 and a sending unit 1520, which are specifically as follows:

[0270] The receiving unit 1510 is configured to receive a first message from a first terminal device, where the first message is used to request access to a first application;

[0271] The sending unit 1520 is used to send a second link to the first terminal device according to the first message, where the second link carries first information and second information, where the first information indicates access to the first application, and the second information indicates a jump type of the second link.

[0272] Optionally, the first message includes an identifier corresponding to the first application and a first operating environment of the first terminal device.

[0273] Optionally, the jump type includes a redirect jump, a deep link jump, and / or a global link jump.

[0274] Optionally, the sending unit 1520 is specifically used to: generate the second link according to the first message and a preset rule; and send the second link to the first terminal device.

[0275] Optionally, the preset rule includes a jump type, a jump link, and / or a parameter conversion rule corresponding to the first operating environment.

[0276] Optionally, the first operating environment is one of a plurality of operating environments, and the preset rule includes a jump type, a jump link, a parameter conversion rule, and / or a priority corresponding to each of the plurality of operating environments.

[0277] Optionally, the operating environment includes one or more of the following: operating system type, browser type, and device manufacturer.

[0278] Optionally, the receiving unit 1510 is also used to: receive a second message from a second terminal device, the second message is used to request a link for sharing a first application; the sending unit 1520 is also used to: send a first link to the second terminal device in response to the second message, the first link is used to access the device 1500.

[0279] Optionally, the first link carries an identifier corresponding to the first application.

[0280] Optionally, the receiving unit 1510 is further used to: receive a third message from the second terminal device, wherein the third message is used to configure a jump type, jump link, parameter conversion rule, and / or priority corresponding to the first operating environment of the first terminal device.

[0281] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0282] Fig.16 It is a schematic structural diagram of a device provided in one embodiment of the present application. Fig.16 The dotted line in the figure indicates that the unit or module is optional. The device 1600 can be used to implement the method described in the above method embodiment. The device 1600 can be a chip or application sharing device.

[0283] The device 1600 may include one or more processors 1610. The processor 1610 may support the device 1600 to implement the method described in the method embodiment above. The processor 1610 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0284] The apparatus 1600 may further include one or more memories 1620. The memory 1620 stores a program, which can be executed by the processor 1610, so that the processor 1610 executes the method described in the above method embodiment. The memory 1620 may be independent of the processor 1610 or integrated in the processor 1610.

[0285] The apparatus 1600 may further include a transceiver 1630. The processor 1610 may communicate with other devices or chips through the transceiver 1630. For example, the processor 1610 may transmit and receive data with other devices or chips through the transceiver 1630.

[0286] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of the present application. Their specific functions and technical effects can be found in the method embodiment part and will not be repeated here.

[0287] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.

[0288] The embodiment of the present application also provides a terminal device, the terminal device includes at least one memory, at least one processor, and a computer program stored in the at least one memory and executable on the at least one processor, and when the processor executes the computer program, the terminal device implements the steps in any of the above-mentioned method embodiments. Exemplarily, the structure of the terminal device can be as follows: Figure 6 shown.

[0289] An embodiment of the present application also provides a server, wherein the terminal device includes at least one memory, at least one processor, and a computer program stored in the at least one memory and executable on the at least one processor, and when the processor executes the computer program, the server implements the steps in any of the above-mentioned method embodiments.

[0290] An embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program. When the computer program is executed by a computer, the computer implements the steps in any of the above method embodiments.

[0291] An embodiment of the present application provides a computer program product. When the computer program product is executed on a terminal device, the terminal device implements the steps in any of the above method embodiments.

[0292] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, which can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable storage medium may at least include: any entity or device that can carry the computer program code to the device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electric carrier signal, a telecommunication signal, and a software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disk. In some jurisdictions, according to legislation and patent practice, a computer-readable storage medium cannot be an electric carrier signal and a telecommunication signal.

[0293] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0294] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0295] In the embodiments provided in the present application, it should be understood that the disclosed devices / terminal equipment and methods can be implemented in other ways. For example, the device / terminal equipment embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0296] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0297] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.

Claims

1. A method for sharing an application, applied to a first terminal device, characterized in that: The method comprises: detecting a first operation of clicking a first link, where the first link is used to access a cloud; In response to the first operation, sending a first message to the cloud according to the first link, where the first message is used to request access to a first application; receiving a second link from the cloud, wherein the second link carries first information and second information, wherein the first information indicates access to the first application, and the second information indicates a jump type of the second link; The second link is opened according to the jump type of the second link.

2. The method according to claim 1, characterized in that The first message includes an identifier corresponding to the first application and a first operating environment of the first terminal device.

3. The method according to claim 1 or 2, characterized in that: The jump types include redirect jump, deep link jump, and / or global link jump.

4. The method according to claim 2, characterized in that: The first operating environment includes one or more of the following: operating system type, browser type, and device manufacturer.

5. The method according to any one of claims 1 to 4, characterized in that The first link carries an identifier corresponding to the first application.

6. A method for sharing an application, applied to a second terminal device, characterized in that: The method comprises: A second operation is detected, where the second operation is used to request a link for sharing the first application; In response to the second operation, sending a second message to the cloud, where the second message is used to request the link for sharing the first application; A first link is received from the cloud, where the first link is used to access the cloud.

7. The method according to claim 6, characterized in that The first link carries an identifier corresponding to the first application.

8. The method according to claim 6 or 7, characterized in that: The method further comprises: A third operation is detected, where the third operation is used to input a jump type, a jump link, a parameter conversion rule, and / or a priority corresponding to the first operating environment; A third message is sent to the cloud, where the third message is used to configure a jump type, a jump link, a parameter conversion rule, and / or a priority corresponding to the first operating environment.

9. The method according to claim 8, characterized in that The jump types include redirect jump, deep link jump, and / or global link jump.

10. The method according to claim 8 or 9, characterized in that: The first operating environment includes one or more of the following: operating system type, browser type, and device manufacturer.

11. A method for sharing an application, applied to the cloud, characterized in that: The method comprises: Receiving a first message from a first terminal device, where the first message is used to request access to a first application; A second link is sent to the first terminal device according to the first message, wherein the second link carries first information and second information, wherein the first information indicates access to the first application, and the second information indicates a jump type of the second link.

12. The method according to claim 11, characterized in that The first message includes an identifier corresponding to the first application and a first operating environment of the first terminal device.

13. The method according to claim 11 or 12, characterized in that: The jump types include redirect jump, deep link jump, and / or global link jump.

14. The method according to any one of claims 11 to 13, characterized in that The sending the second link to the first terminal device according to the first message includes: Generate the second link according to the first message and a preset rule; Send the second link to the first terminal device.

15. The method according to claim 14, characterized in that The preset rules include jump types, jump links, and / or parameter conversion rules corresponding to the first operating environment.

16. The method according to claim 15, characterized in that The first operating environment is one of a plurality of operating environments, and the preset rule includes a jump type, a jump link, a parameter conversion rule, and / or a priority corresponding to each operating environment in the plurality of operating environments.

17. The method according to claim 16, characterized in that The operating environment includes one or more of the following: operating system type, browser type, and device manufacturer.

18. The method according to any one of claims 11 to 17, characterized in that The method further comprises: receiving a second message from a second terminal device, where the second message is used to request sharing of a link to the first application; In response to the second message, a first link is sent to the second terminal device, where the first link is used to access the cloud.

19. The method according to claim 18, characterized in that The first link carries an identifier corresponding to the first application.

20. The method according to claim 18 or 19, characterized in that The method further comprises: A third message is received from the second terminal device, where the third message is used to configure a jump type, a jump link, a parameter conversion rule, and / or a priority corresponding to the first operating environment of the first terminal device.

21. A terminal device, characterized in that: include: A processor and a memory, wherein the processor is coupled to the memory, and the memory is used to store a computer program, and when the computer program is executed by the processor, the terminal device executes the method as described in any one of claims 1 to 5 or the method as described in any one of claims 6 to 10.

22. A server, characterized in that: include: A processor and a memory, wherein the processor is coupled to the memory, and the memory is used to store a computer program, and when the computer program is executed by the processor, the server executes the method according to any one of claims 11 to 20.

23. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 20.

24. A chip, characterized in that: include: A processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that a server or terminal device equipped with the chip executes the method as described in any one of claims 1 to 20.

Images