Download method, communication system, device, readable medium and program product

Abstract

The present application relates to the technical field of software engineering design, and in particular to a download method, a communication system, a device, a readable medium and a program product. In the method, during the release phase of resources such as an application, application description information is synchronously released to servers in a plurality of regions whilst releasing the application description information and an application entity to a service in a region where a designated service location is located. In this way, when a user searches for resources such as an application by means of an application market, etc., of a user equipment, the user equipment can find application description information released on a server in each region without obstacles, and provides an application search result to the user on the basis of the found application description information. Moreover, the user equipment can further switch a usage location to a corresponding service location where a found application is released, so as to acquire relevant application entity resources for installation and usage. Thus, an improvement in the usage experience of a user searching for and downloading an application in an application market is facilitated.

Description

Downloading method, communication system, device, readable medium and program product

[0001] The present application claims priority to the Chinese patent application No. 202410703832.3, filed on May 31, 2024, and entitled "Downloading method, communication system, device, readable medium and program product", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the technical field of software engineering design, and particularly relates to a downloading method, a communication system, a device, a readable medium and a program product. BACKGROUND

[0003] When a user installs an application (APP) on a terminal device, the user usually needs to search for a corresponding application package resource in an application market according to an application name, and then download and install the application.

[0004] However, different applications may be released in different countries or regions. For example, an A application may not be released in a country A but may be released in a country B. Therefore, when a user in the country A searches for the A application in an application market of the terminal device, the user may not be able to find a corresponding application installation package, and the user's demand for downloading and installing the A application cannot be met. SUMMARY

[0005] The present application provides a downloading method, a communication system, a device, a readable medium and a program product. When a user searches for an application resource through an application market of a user device, the user device can search for application description information released on a regional server based on the downloading method provided by the present application, and provide the user with an application search result based on the searched application description information. In addition, the user device can further switch to a service region corresponding to the searched application to obtain related application entity resources for installation and use. In this way, the user experience of searching for and downloading applications in the application market can be improved.

[0006] In a first aspect, the present application provides a downloading method applied to a first device, wherein a currently set service region of the first device corresponds to a first service region, and the method comprises: detecting a first operation of a user in a first application, wherein the first operation indicates obtaining a first resource; determining that a release region of the first resource is a second service region; in response to the first operation, switching the service region of the first device to the second service region, and displaying the first resource in the first application.

[0007] For example, the first device can be a user device, such as the user device 10 exemplified in the following embodiments. The first application can be an application market, or a music application or a video application, etc. Correspondingly, the first resource indicated by the first operation can be an application program, a music or a video, etc. In some embodiments, the first operation can be an operation of indicating to view or install an application searched in the application market. In other embodiments, the first operation can also be an operation of indicating to download or play a music or a video searched in the music application or the video application, etc. without limitation.

[0008] The resource description information (e.g. application description information) of the first resource can be published to the first service region at the same time as being published to the second service region. The first resource can be published to the second service region. The first service region and the second service region can be different countries or regions. In this way, the first application (e.g. application market) running on the user device can display a relevant interface for obtaining the first resource, and can detect the first operation of the user in the first application. Based on this, the user device (i.e. first device) can trigger a switch from the current service region (i.e. first service region) to the publishing region of the first resource (i.e. second service region) in response to the first operation, to obtain and display the first resource. In this way, the user experience of searching and downloading an application or other resource in the application market or other application can be improved.

[0009] In a possible implementation of the first aspect, the first resource includes first description information and a first resource file, wherein the publishing region of the first description information includes a plurality of regions, and the plurality of regions include the second service region and the first service region; and the publishing region of the first resource file includes the second service region.

[0010] For example, the application description information of an application can be published to servers in a plurality of regions, and the application entity of the application can be published to a server in the region to which the second service region belongs.

[0011] In a possible implementation of the first aspect, detecting the first operation of the user in the first application includes: detecting a search operation of the user in the first application, wherein the search operation indicates to search for the first resource; based on the first application accessing the second device to search for the first description information corresponding to the first resource, and displaying a first search result generated based on the first description information in the first application; and detecting the first operation of the user in the first application corresponding to the first operation of the user on the first resource in the first search result.

[0012] For example, the search operation of the user in the first application can be an operation that the user inputs an application name and the like in a search interface of an application market to search for a first resource (e.g., a target application). The second device can be an application market server that deploys an application market server. The application market server can provide first description information (e.g., application description information) of the first resource published in a plurality of regions in an information database to a corresponding application market client. Correspondingly, a user device that installs the application market client can display a search result (e.g., the first search result) of the target application based on the application description information.

[0013] Based on this, the first operation of the user in the first application can be an operation that the user clicks a view control to view the target application in a display interface related to the search result of the target application.

[0014] In a possible implementation of the first aspect, determining that the publishing region of the first resource is the second service region includes: obtaining publishing region information of the first resource file; and determining that the publishing region of the first resource is the second service region based on the publishing region information of the first resource file.

[0015] For example, the publishing region information of the first resource file can be stored on a server (including the second device) in a plurality of regions where the corresponding first description information is published. The publishing region information can include, for example, information such as the name of a country or region where the application entity of the target application is published, without limitation.

[0016] In a possible implementation of the first aspect, switching the use region of the first device to the second service region in response to the first operation includes: sending, to the second device, a switching request indicating that the first service region is switched to the second service region; and updating the use region to the second service region based on a notification returned by the second device that the service region is switched successfully.

[0017] For example, when the user device detects that the user clicks the view control to view the target application, the user device can trigger sending a switching request to a server (e.g., the second device) in a region to which the first service region belongs to request switching of the currently set use region (i.e., the first service region).

[0018] In a possible implementation of the first aspect, sending, to the second device, the switching request indicating that the first service region is switched to the second service region includes: displaying a first interface of the first application, where the first interface is used to prompt the user to confirm whether to switch the service region; and in response to a second operation of the user confirming to switch the service region, sending, to the second device, the switching request indicating that the first service region is switched to the second service region.

[0019] For example, the user device can display a prompt interface for prompting the user to switch the service location when detecting the user's operation of clicking the view control to view the related operation of the target application. Then, the user device can trigger the sending of a switching request to the server (e.g., the second device) in the region of the first service location to request the switching of the currently set use location when detecting the user's operation of confirming the switching of the service location on the prompt interface, e.g., detecting the user's operation of clicking the "OK" control.

[0020] In a possible implementation of the first aspect, the use location currently set by the first device is related to the first account logged in by the first device, and the first device accesses the third device corresponding to the first account, and based on the notification of the successful switching of the service location returned by the second device, the receiving of the notification of the successful switching of the service location returned by the third device through the second device is included.

[0021] For example, the third device can be an account server for managing the first account logged in by the user device (i.e., the first device). Correspondingly, the process of switching the service location of the user device can be implemented by sending a switching request to the third device through the second device. The third device (e.g., the account server) can reset the use location of the first account, e.g., set to the second service location, in response to the switching request of the user device forwarded by the second device (e.g., the application market server in the region of the first service location). After the setting is completed, the account server can return a notification of the successful switching to the user device through the application market server.

[0022] In a possible implementation of the first aspect, the region of the first service location is the same as the region of the second service location, the second device corresponds to a server in the region of the first service location or the second service location, and the displaying of the first resource in the first application includes: displaying a second interface of the first application, where the second interface is used to indicate the installation or playing of the first resource; detecting a third operation of the user indicating the installation or playing of the first resource, and sending a download request of the first resource to the second device; obtaining the first resource returned by the second device, and displaying a third interface of the first application, where the display content of the third interface includes the first resource.

[0023] For example, when the region to which the current use location (i.e., the first service location) of the user equipment belongs is the same as the region to which the publishing location (i.e., the second service location) of the first resource belongs, the server corresponding to the interaction of the user equipment sending a related request before and after switching the service location is the same server, for example, both are the second device. At this time, when the user equipment detects a third operation of the user indicating to install or play the first resource, the user equipment can continue to send a corresponding download request to the second device. The third operation may, for example, be an operation of the user clicking an installation control in an application download interface, which can trigger an application entity of a target application and install the target application. In some other embodiments, the third operation may, for example, also be an operation of the user clicking to play a target music in a music playing interface or the user clicking to play a target video in a video playing interface, which is not limited herein.

[0024] In a possible implementation of the first aspect, the region to which the first service location belongs is different from the region to which the second service location belongs, the server corresponding to the region to which the first service location belongs corresponds to the second device, and the server corresponding to the region to which the second service location belongs corresponds to the third device. Displaying the first resource in the first application includes: displaying a second interface of the first application, where the second interface is used to indicate to install or play the first resource; detecting a third operation of the user indicating to install or play the first resource, and sending a download request corresponding to the first resource to the third device; obtaining the first resource returned by the third device, and displaying a third interface of the first application, where the display content of the third interface includes the first resource.

[0025] For example, when the region to which the current use location (i.e., the first service location) of the user equipment belongs is the same as the region to which the publishing location (i.e., the second service location) of the first resource belongs, the server corresponding to the interaction of the user equipment sending a related request before and after switching the service location is the same server, for example, both are the second device. At this time, when the user equipment detects a third operation of the user indicating to install or play the first resource, the user equipment can continue to send a corresponding download request to the second device. The third operation may, for example, be an operation of the user clicking an installation control in an application download interface, which can trigger an application entity of a target application and install the target application, which is not repeated herein.

[0026] In a possible implementation of the first aspect, the display content of the second interface is related to the first resource published in the second service location; and the display content of the second interface further includes one or more of the following data related to the first resource:

[0027] The score data corresponding to the first resource; the download or installation times statistical result corresponding to the first resource; the comment data corresponding to the first resource; the security detection result corresponding to the first resource; the detailed introduction data corresponding to the first resource; and the recommended resource matched with the first resource.

[0028] For example, the second interface can be an application download interface. Correspondingly, the score data can be, for example, a score of a target application, such as “4.0” points, etc.; the download or installation times statistical result can be, for example, the installation times of the target application, such as “880,000 times of installation”, etc.; the comment data can be, for example, a user usage evaluation of the target application; the security detection result can be, for example, an indication that the target application “passes the security detection”; and the recommended resource can be, for example, a recommended application of the same or similar type as the target application, etc. This is not limited herein.

[0029] In a possible implementation of the first aspect, the first resource includes any one of an application program, music, or a video.

[0030] In a possible implementation of the first aspect, when the first resource is an application program, detecting the first operation of the user in the first application includes: detecting an operation of the user on the first search result indicating to view or install the first resource.

[0031] In a possible implementation of the first aspect, when the first resource is music or a video, detecting the first operation of the user in the first application includes: detecting an operation of the user on the first search result indicating to download or play the first resource.

[0032] In a second aspect, the present application provides a communication system including a first device and a second device, wherein the first device is currently set to use a first service area, and the first device is configured to send a first acquisition request for a first resource to the second device in response to detecting a first operation of a user in a first application, wherein the first operation indicates to acquire the first resource.

[0033] The second device is configured to return first description information of the first resource to the first device in response to the first acquisition request sent by the first device, wherein the first description information includes publishing area information of the first resource.

[0034] The first device is configured to determine, according to the publishing area information of the first resource, that the publishing area of the first resource is a second service area; and the first device switches the use area to the second service area and sends a second acquisition request for a first resource file of the first resource to the second device based on the second service area.

[0035] The second device is configured to return the first resource file to the first device in response to the second acquisition request sent by the first device.

[0036] In a possible implementation of the second aspect, the first device further sends a third obtaining request for the first resource file of the first resource to a third device corresponding to a server of a region to which the second service location belongs, based on the second service location.

[0037] The third device returns the first resource file to the first device in response to the third obtaining request sent by the first device.

[0038] In a possible implementation of the second aspect, the first description information is published in a plurality of regions, and the plurality of regions include a region to which the first service location belongs and a region to which the second service location belongs; and the first resource file is published in the second service location.

[0039] In a third aspect, the present application provides an electronic device, including: one or more processors; one or more memories; the one or more memories store one or more programs, when the one or more programs are executed by the one or more processors, the electronic device performs the downloading method provided in the first aspect and the various possible implementations of the first aspect.

[0040] In a fourth aspect, the present application provides a computer readable medium, the readable medium stores instructions, when the instructions are executed on a computer, the computer performs the downloading method provided in the first aspect and the various possible implementations of the first aspect.

[0041] In a fifth aspect, the present application provides a computer program product, including computer programs / instructions, when the computer programs / instructions are executed by a processor, the downloading method provided in the first aspect and the various possible implementations of the first aspect is implemented.

[0042] The advantages of the second aspect to the fifth aspect can refer to the related description of the first aspect and the various possible implementations of the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0043] FIG. 1 shows a schematic diagram of an application publishing and downloading scenario to which a downloading method is applicable.

[0044] FIG. 2a shows a schematic diagram of a setting interface of an application market displayed by a mobile phone according to an embodiment of the present application.

[0045] FIG. 2b shows a schematic diagram of a prompt interface of an application market displayed by a mobile phone according to an embodiment of the present application.

[0046] FIG. 3a shows a schematic diagram of an application publishing process according to an embodiment of the present application.

[0047] Fig. 3b is a diagram illustrating a setting of a release rule corresponding to an application release process according to an embodiment of the present application.

[0048] Fig. 4a is a diagram illustrating an interface change for searching an application in an application market according to an embodiment of the present application.

[0049] Fig. 4b is a diagram illustrating an interface change for downloading an application in an application market according to an embodiment of the present application.

[0050] Fig. 5a is a diagram illustrating an application scenario of a downloading method according to Embodiment 1 of the present application.

[0051] Fig. 5b is a diagram illustrating an implementation flow of a downloading method according to Embodiment 1 of the present application.

[0052] Fig. 6a is a diagram illustrating a release process of application description information and an application entity according to an embodiment of the present application.

[0053] Fig. 6b is a diagram illustrating a composition of release information of application description information according to an embodiment of the present application.

[0054] Fig. 6c is a diagram illustrating a composition of release information of an application entity according to an embodiment of the present application.

[0055] Fig. 7 is a diagram illustrating a matching process of an application market server matching application description information in response to a search request according to an embodiment of the present application.

[0056] Fig. 8a is a diagram illustrating a composition of data table for setting prompt information related to a first application according to an embodiment of the present application.

[0057] Fig. 8b is a diagram illustrating a composition of data table for setting related instructions for switching a service location for downloading a first application according to an embodiment of the present application.

[0058] Fig. 9a is a diagram illustrating an interface change corresponding to a display of a mobile phone in response to a user confirming a switching of a service location according to an embodiment of the present application.

[0059] Fig. 9b is a diagram illustrating a prompt interface of a switching failure according to an embodiment of the present application.

[0060] Fig. 10a is a diagram illustrating an installation management interface for prompting a completion of a download according to an embodiment of the present application.

[0061] Fig. 10b is a diagram illustrating an application installation interface for prompting a completion of a download according to an embodiment of the present application.

[0062] Fig. 10c is a diagram illustrating an application installation interface for prompting a completion of an installation according to an embodiment of the present application.

[0063] Fig. 11a shows an application scenario of another downloading method provided by Embodiment 2 of the present application.

[0064] Fig. 11b shows an implementation flow of another downloading method provided by Embodiment 2 of the present application.

[0065] Fig. 12 shows a hardware structure of a user equipment provided by the present application.

[0066] Fig. 13 shows an operating system software structure of a user equipment provided by the present application. DETAILED DESCRIPTION

[0067] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions of the embodiments of the present application will be described in detail below with reference to the accompanying drawings and specific embodiments.

[0068] It can be understood that the terminal device in the embodiments of the present application can also be referred to as a terminal, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), etc. The terminal device can be a mobile phone, a smart television, a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc.

[0069] It should be further stated that the steps in the methods and processes in the embodiments of the present application are numbered for ease of reference, rather than to limit the sequence, and if there is a sequence between the steps, the written description shall prevail.

[0070] Fig. 1 shows an application publishing and downloading scenario to which a downloading method is applicable.

[0071] As shown in Figure 1, this scenario includes user device 10, server 20, and developer device 30, involving the application release phase and the application download / installation phase. User device 10 can access server 20 by running an installed application marketplace (a type of application downloader) to obtain the application installation package that the user is looking for, such as Android. TM The application package (APK) is then used to respond to user actions by downloading and installing the corresponding application. Developer device 30 can publish the completed application installation package to server 20 for user device 10 to download.

[0072] The application release phase can include the "release application" process shown in Figure 1, where developers or operators can use developer device 30 to release the completed application to server 20. The application download / installation phase can include the "download application" process shown in Figure 1, where user device 10 can respond to user operations, based on the application name or related description information entered by the user, search for the application specified by the user, and access server 20 to obtain the corresponding application installation package for further installation, running, etc.

[0073] It's understandable that application releases vary by region. For example, some applications can be downloaded in country A or region A because during the application's release phase, the corresponding installation package and related information are uploaded to a server in the designated country or region. This server stores the uploaded installation package and related information according to the specified country or region and makes it available for search and download by user devices within that designated country or region. Therefore, if a user's device searching for the aforementioned application is currently set to a different country or region (other than country A or region A), such as country B, the server accessing the application will not store the relevant information, making it impossible to find and download the application.

[0074] It is understood that the aforementioned user device 10 may include various terminal devices, such as the aforementioned laptops, mobile phones, tablets, smartwatches, etc., without limitation. The aforementioned server 20 may include application servers, file servers, database servers, etc., without limitation. The aforementioned developer device 30, as a terminal device used by developers or operators, may also include electronic devices such as laptops, tablets, and desktop computers, without limitation. Developers or operators may include, but are not limited to, technical personnel or managers who have invested time and effort in developing the corresponding applications.

[0075] As mentioned above, since different applications can be released in different countries or regions, the current application market cannot meet the requirement of downloading the application released in other service regions by the user. In order to solve this problem, some user equipment 10 can support switching service regions to search and download the application released in the corresponding service region.

[0076] Referring to FIG. 2a, the user can select the "country / region" option 102 on the setting interface 101 of the application market running on the mobile phone 100 to enter the setting interface 103. Generally, the country displayed by default in the "country / region" option 102 can be the service region associated with the account currently logged in the mobile phone 100, for example, country A. Further, the user can click the "change country or region" option 104 on the setting interface 103 to select the country or region to be switched. Correspondingly, the mobile phone 100 can display the prompt interface 105 shown in FIG. 2b when the user operates the service region, reminding the user of some effects that may be caused by switching the service region. If the user clicks the "OK" control 106, the user equipment 10, for example, the mobile phone 100, can display the service region option interface 107.

[0077] Continuing to refer to FIG. 2b, the service region option interface 107 can display various countries or regions that support switching, including countries A to K shown in FIG. 2b. The user can slide up on the interface 107 to find the country or region to be switched, or the user can also input the name of the country or region to be switched in the search box 108 on the interface 107 to find the service region and switch.

[0078] After completing the switching of the service region, the application market running on the mobile phone 100 can access the server 20 of the service region (for example, country or region) to which the switched service region belongs, search for the application installation package specified by the user, and download and install. Based on this, the application market can essentially be an application that provides a download function, that is, a download application, which is not limited here.

[0079] However, the above-mentioned method of switching the service region to meet the requirement of downloading the application released in other service regions by the user shown in FIGS. 2a to 2b is complicated to operate, and the user needs to know the country or region corresponding to the application to be downloaded / installed in advance. If the user does not know, the user cannot accurately search for the application released in other service regions using the above-mentioned method. Thus, the user experience is still poor.

[0080] Therefore, there is an urgent need for a resource management scheme that can facilitate the user to download the application released in other service regions.

[0081] To solve the above problems, the present application provides a downloading method. Specifically, the method synchronously publishes application description information (i.e. resource description information) to servers in multiple regions while publishing application entity (i.e. resource entity) and application description information to servers in a designated region during the publishing stage of an application or the like. In this way, when a user searches for an application or the like through an application market or the like of a user device, the user device can search for the application description information published on the servers in the regions without any obstacles, and provide the user with an application search result based on the searched application description information. In this way, the use experience of the user in searching for an application through an application market is improved. The application description information can include information indicating a designated publishing region (e.g. a country or a region) of the application. The application entity can be a file such as an installation package of the application, which can also be referred to as a resource file.

[0082] Based on this, if the user wants to further view the detailed information of the searched application and download the application or the like, the user device can switch the currently set region to the designated region of the resource based on the information of the region of the designated publishing region in the application description information. In this way, the user does not need to manually switch the currently set region of the user device, and can quickly switch to the region (e.g. a country or a region) of the published application, download / acquire the application entity on the server in the region, and further install and run the application or the like. In this way, the user operation is greatly simplified in the process of downloading the application across regions, and the use experience of downloading an application through an application market or the like is improved.

[0083] It can be understood that the type of resource to which the above-mentioned downloading method provided by the present application is applicable, i.e. the above-mentioned published or downloaded resource, can not be limited to the above-mentioned application, and in other embodiments, the above-mentioned published or downloaded resource can include music or video or the like, which is not limited herein. Correspondingly, the corresponding resource description information can be music description information or video description information or the like, and the corresponding resource entity can be a music file or a video file or the like, which is not limited herein.

[0084] It can be understood that the servers in multiple regions to which the above-mentioned application description information is published can include servers in multiple regions to which the application can be published, or servers in regions planned by a commercial plan in which the application participates or the like. The publishing region of the application entity can be one or more servers in the servers in multiple regions, or one or more countries or regions covered by the same server.

[0085] Referring to Figure 3a, for example, a developer can use developer device 30 to publish the application description information of application A to servers in the regions of countries A, B, C, and D, while publishing the application entity to servers other than those in the region of country A. That is, the application entity is only published to servers in the regions of countries B, C, and D. For example, when publishing the application description information of application A, the developer can select multiple countries as shown in Figure 3b, including countries A, B, C, and D, all of which can be selected. When publishing the application entity of application A, the developer can select some countries or not select others. For example, in Figure 3b, country A is not selected, while countries B, C, and D are selected. Figure 3b shows the publishing rules that the developer can set for application A.

[0086] The application description information can be stored in the information database of the corresponding server, and the application entity can be stored in the entity database of the corresponding server. When the application market client running on user device 10 searches for an application from the application market server in country A, it can obtain the application description information corresponding to the application without any obstacles, and thus display the search results for the application in the application market client.

[0087] Referring again to Figure 3a, when a user selects to view the detailed information of the application displayed in the search results above and to download the application, the application market client running on the user device 10 can switch the service location to country B, country C, or country D to access the server in the region to which the application belongs and obtain the application entity of the application.

[0088] When the application market client running on user device 10 switches service locations, it can display a prompt interface to the user indicating that downloading the corresponding application will switch service locations. Furthermore, user device 10 can initiate the service location switch process after the user confirms the switch. The specific implementation process of user device 10 initiating the service location switch will be described in detail below in conjunction with relevant services, and will not be elaborated upon here.

[0089] As described above, the user device 10, based on the download method provided in this application, displays a response interface for users searching for applications, music, videos, etc., which may differ from existing response interfaces. For example, when responding to a user's operation of searching for application resources in an application market, the user device 10 may display controls for the user to view or install the application when displaying the search results for that application resource. Similarly, when responding to a user's operation of searching for music resources in a music application or video resources in a video application, the user device 10 may display controls for the user to play or download the music or video when displaying the search results for that music or video resource, and so on. No further limitations are imposed here.

[0090] As an example, Figures 4a and 4b show schematic diagrams of the relevant interfaces for searching for and downloading applications in the app store.

[0091] Referring to Figure 4a, based on the download method provided in this application, the user enters the name of the application they want to find in the search interface 410 of the application market, such as application A. Application A may be an application released in country B, but the current service location of mobile phone 100 is set to country A. When the user finishes entering the name and clicks "Search" in the search box 411, mobile phone 100 can still find search results for application A. The search results may include, for example, "application A" which is the same as the application name entered by the user, as well as "application A1", "application A2", etc., which are similar to the application name entered by the user, without limitation. Among them, "application A1", "application A2", etc., can also be applications released from other service locations.

[0092] In addition, the search interface 410 can also recommend applications that users may like, referring to the "You may also like" section of Figure 4a, as well as applications B, C, D, etc. that may be related to application A that the user searched for. These applications can be matched and displayed based on application description information released in multiple countries or regions. The country or region corresponding to these applications can be the service location currently set by mobile phone 100, or it can be a different service location than the service location currently set by mobile phone 100, without any restrictions.

[0093] Referring again to Figure 4a, when a user clicks the view control 412 corresponding to "Application A" in the search interface 410, the mobile phone 100 can respond to the user's operation and display a prompt interface 420. This prompt interface 420 can display a prompt message 421, suggesting that the user switch the currently set service location to any country from B to D to obtain the corresponding application entity resources. For example, the content displayed in the prompt message 421 could be something like, "This application is not available in the current region; you need to switch the country / region to B to obtain it." In some embodiments, the prompt message 421 may also include reminders about the potential impacts of switching the service location, which will not be elaborated here. The method for determining the service location prompted by the prompt message 421 may include, but is not limited to, the following:

[0094] ① Based on the preset target handover location, determine the service location for which you are prompted to switch. This target handover location can be set in a corresponding data table, which can be referred to in Figure 8a below and related descriptions, and will not be elaborated here.

[0095] ② Based on the user's selection actions on the relevant selection interface, determine the service location to be switched.

[0096] ③ Based on the regions of each country with application entity resources, prioritize countries or regions within the same region as the current service location as the service location to prompt for switching.

[0097] ④ Based on the frequency of users selecting a country or region to switch to, prioritize countries or regions with higher user selection frequency as service locations for prompting switching.

[0098] ⑤ Based on the download / installation volume of the application searched by the user in the corresponding country or region, prioritize the country or region with the larger download volume as the service location to prompt switching.

[0099] ⑥ Based on the release location of the latest version of the searched application, determine the country or region where the latest version is available, and use this as the service location to prompt you to switch.

[0100] On the aforementioned prompt interface 420, users can confirm the switch of service location by clicking the "OK" control 422, or cancel the switch of service location by clicking the "Cancel" control 423.

[0101] Referring to Figure 4b, if the user clicks the "OK" control 422 on the prompt interface 420, the mobile phone 100 can respond to the user's operation by displaying the application download interface 430. The application download interface 430 can display more information related to application A, such as the application A's rating, download / installation statistics, user-uploaded reviews based on user experience, and information indicating that it has "passed security testing." The application download interface 430 can also display an installation control 431, which can display the data size of the application entity corresponding to application A, such as "5.3MB," etc., without limitation. Clicking the installation control 431 will trigger the application market running on the mobile phone 100 to download application A. After the download is complete, the application market running on the mobile phone 100 can continue to install application A.

[0102] It is understandable that the application download interface shown in Figure 4b above can be generated based on the application entity resources provided by the server in the service location after the user device 10 is switched, such as the region of country B. That is, the interface can display relevant information about the application released in the service location after the switch, such as country B.

[0103] Based on the download method provided in this application, server 20 can respond to application search requests initiated by the application market, provide search results to the application market based on application description information published in multiple countries or regions, and also provide the application market with download links or resource access links for the application entities corresponding to the search results. Therefore, in some embodiments of this application, server 20 may include application market servers for each of the aforementioned regions. That is, the servers for countries A, B, C, and D shown in Figure 3a can all be server 20. To distinguish the application market servers for each region, the application market servers for each region will be described below as: application market server 20a for country A, application market server 20b for country B, application market server 20c for country C, and application market server 20d for country D.

[0104] It is understandable that if the service location switched by user device 10 in response to a user's operation to download an application is the same as the service location currently set by user device 10, that is, the server 20 accessed is an application market server in the same region, for example, both are application market servers 20a in country A, then after switching service locations, user device 10 can continue to send download requests for the searched application to application market server 20a and obtain the corresponding application entity resources.

[0105] If the service location switched by user equipment 10 in response to a user's operation to download an application is different from the service location currently set by user equipment 10, that is, the server 20 accessed is an application market server in a different region, such as application market server 20b in country B and application market server 20a in country A, then after switching the service location, user equipment 10 can send a download request for the searched application to the server in the switched service location (e.g., application market server 20b) to obtain the corresponding application entity resources.

[0106] It is understood that the process by which the application market switches the service location to the country or region where the application is published after the user confirms the switch may include the process by which the application market requests server 20 to send a service location switch instruction to the account server associated with the user's logged-in account, and the process by which the account server responds to the instruction by modifying the service location associated with the user's logged-in account to the country or region where the searched application is published. Furthermore, the download method provided in this application may include the management of the release of the corresponding resource during the release phase, and the management of the search and download of the corresponding resource during the download phase, without any limitations herein.

[0107] The following section continues to use an application as an example, combining embodiments of different scenarios and related figures to describe in detail the specific implementation process of the download method provided in this application.

[0108] The following section, in conjunction with Example 1, describes the specific implementation process of the download method provided in this application in a scenario where the service location is in the same region before and after the switch.

[0109] Example 1

[0110] In this embodiment of the application, the service location of user equipment 10 before and after the switch can be the same region. Correspondingly, the server accessed by the application market client running on user equipment 10 before and after the switch can be the same server.

[0111] Figure 5a illustrates an application scenario in which the server accessed by the application market client before and after switching service locations is the same server, according to an embodiment of this application.

[0112] As shown in Figure 5a, the service location of the application market client running on user device 10 before switching is, for example, country A, and the service location after switching is, for example, country E or country F, etc. However, the application market server in the regions of country A and country E or F is application market server 20a. The service location set by user device 10 before switching can be set by the account server 40 corresponding to the logged-in account. The process of user device 10 switching service locations can be achieved through interaction between application market server 20a and account server 40.

[0113] In the scenario shown in Figure 5a, user device 10 can access application market server 20a to query application description information and download application entity resources before and after switching service locations. As mentioned earlier, this application description information and application entity resources can be uploaded and published by developers through developer device 30.

[0114] As an example, Figure 5b illustrates a schematic diagram of the implementation process of a download method according to an embodiment of this application. This implementation process involves the interaction between user device 10, application market server 20a, developer device 30, and account server 40.

[0115] Specifically, as shown in Figure 5b, the implementation process may include the following steps 501 to 521:

[0116] 501: Application market server 20a obtains application description information and application entities uploaded by developer device 30, where the application description information is published on servers in multiple regions.

[0117] For example, after completing development and testing during the application development phase, developers or operators can publish the corresponding application to a designated country or region via developer device 30. This designated country or region is the service location where the application entity is published. Simultaneously, developers or operators can publish the application description information of the corresponding application to more service locations, such as simultaneously publishing it on servers in multiple regions. These multiple regions can cover the service location currently set on user device 10 and the service location specified by the application entity, without limitation.

[0118] It is understandable that the aforementioned release process essentially involves uploading data related to the developed application to a server in a specified country or region. This application-related data can include application description information to describe the application, as well as the application entity for installing the application. The application description information can be in the form of text or strings, and as information to identify the application, it includes at least the application's identification information, such as the application name, package name, and application icon. The application description information may also include an application description that introduces the application and relevant information such as the application category corresponding to the application's type.

[0119] As an example, Figure 6a illustrates a schematic diagram of the publishing process of application description information and application entities according to an embodiment of this application.

[0120] As shown in Figure 6a, when developers publish applications through developer device 30, they can choose to upload application description information to application market servers in countries A and E, as well as other countries, and this application description information can be stored in the information databases of each server. Furthermore, when developers publish applications through developer device 30, they can choose to publish the application entity to country E instead of country A. In some other embodiments, developers can also choose to publish the application entity to country A instead of country E. However, in this embodiment, countries A and E can belong to the same region, and the application market server 20a in that region can allocate isolated data storage spaces for countries A and E in the information database and entity database, respectively. That is, application description information can be uploaded to the data storage spaces allocated to multiple countries by the application market servers in each region, while the application entity can be uploaded to the data storage space corresponding to the specified country or region of publication; no restrictions are placed here.

[0121] It is understood that the service location currently set by the user equipment 10 can also be called the usage location, that is, the service location used by the user equipment 10 to run the application market client. Based on this, the service location currently set by the user equipment 10 can also be described as the currently set usage location.

[0122] As an example, Figure 6b shows a schematic diagram of the composition of application description information publication information according to an embodiment of this application.

[0123] As shown in Figure 6b, the publishing information corresponding to the application description information published by developer device 30 may include, but is not limited to: application name (corresponding value is "XX Music"), package name (corresponding value is "com.android.musical"), application icon (corresponding value is "https: / / xxx.com"), application description (corresponding value is "This application is a xxxxxxxxxx"), application category (corresponding value is "audio, video, entertainment"), etc., and there are no restrictions here.

[0124] Referring to Figure 3a above, the application description information can be uploaded to the information database provided by the application market server 20a for storage and management. Then, the application market server 20a can use the application description information corresponding to each application stored in the information database to match the corresponding application description information for the application searched by the user on the user device 10. For details, please refer to the relevant steps and descriptions below, which will not be repeated here.

[0125] The aforementioned application entities can be the installation packages of the corresponding applications, for those running Android. TM The user device 10 of the system may contain an executable file of type ".apk".

[0126] As an example, Figure 6c shows a schematic diagram of the composition of the publishing information of an application entity according to an embodiment of this application.

[0127] As shown in Figure 6c, the publishing information corresponding to the application entity published by the developer device 30 may include, but is not limited to, fields such as: package name (corresponding value is "com.android.musically") and application entity (corresponding value is "https: / / yyy.com").

[0128] It is understood that the package name and value of the application description information shown in Figure 6b can correspond to the package name and value of the application entity shown in Figure 6c, and the two can be the same. Furthermore, the application icon and value shown in Figure 6b can correspond to the application entity and value shown in Figure 6c, and their corresponding reading paths "https: / / xxx.com" and "https: / / yyy.com" can correspond to the same directory or subdirectory.

[0129] Referring to Figure 3a above, the application entity can be uploaded to the entity database provided by the application market server 20a for storage and management. Then, the application market server 20a can use the application entities corresponding to each application stored in the entity database to match the corresponding application entities for the application searched by the user on the user device 10. For details, please refer to the relevant steps and descriptions below, which will not be repeated here.

[0130] 502: User device 10 detected a user searching for a target application.

[0131] For example, a user can use user device 10 to search for an application they want to install, i.e., the target application mentioned above. This target application can be a payment application, a browser application, a game application, a music application, or a video application, etc., without limitation. Correspondingly, the application market client running on user device 10 can detect the user's search for the target application and, in response to this user operation, continue to execute step 503 below, requesting the search for the target application from the corresponding application market server.

[0132] 503: User equipment 10 sends a search request for the target application to application market server 20a.

[0133] For example, the search request may carry identification information such as the application name of the target application. An application market server may be deployed on the application market server 20a to respond to requests initiated by the application market client. When the application market client running on the user device 10 detects a user's search for a target application, it may send a search request for the target application to the application market server 20a. This request may be used to request the application market server to search for relevant information about the target application from the information database provided by the application market server 20a, such as the application description information corresponding to the target application.

[0134] 504: The application marketplace server 20a responded to the search request and matched the application description information of the target application.

[0135] For example, in response to a received search request for a target application, the application market server 20a retrieves application description information related to the target application from an information database. Referring to Figure 6a above, the application market server 20a may, for example, retrieve application description information corresponding to the target application based on the application name of the target application. This application description information may include the application name, package name, and application icon of the target application, or it may include text and characters corresponding to the application description.

[0136] It is understood that the application market server 20a can search the information database for application description information that matches the application name and other information carried in the search request. Simultaneously, when receiving a search request from the user device 10, the application market server 20a can also obtain the service location information set for the account logged into by the user device 10.

[0137] As an example, Figure 7 illustrates a schematic diagram of the matching process where an application marketplace server responds to a search request by matching application description information.

[0138] As shown in Figure 7, the application market client running on user device 10 can initiate a search request for applications to application market server 20a based on the usage location set by the account server 40 accessed by the logged-in account, i.e., the currently set service location mentioned above. Correspondingly, server 20a in the region where country A is located can respond to the search request and search whether the application description information of the corresponding application is stored. It can be understood that this search process may include searching the data storage space allocated to country A and country E in the information database of server 20a, which will not be elaborated here. Similarly, user device 10 whose current service location is a country or region in another region can search for relevant application descriptions from the application market server in its region, which can be referred to in step 1104 of embodiment 2 below, which will not be elaborated here.

[0139] 505: Application market server 20a returns application description information of the target application to user device 10.

[0140] For example, the application market server 20a can return the application description information of the target application matched above as a search or search result to the application market client running on the user device 10.

[0141] 506: User device 10 displays a search result display interface based on application description information to introduce the target application.

[0142] For example, based on the application description information of the target application returned by the application market server 20a, the user device 10 can display a search results display interface corresponding to the target application. This search results display interface can present a relevant introduction to the target application and its application icon.

[0143] Referring to Figure 4a above, in response to a user's search request for application A, user device 10, such as mobile phone 100, can interact with application market server 20a to execute steps 503 to 506 above, and can display the search results in search interface 410. These search results may include, for example, "Application A" (which is the same as the application name entered by the user), and similar applications such as "Application A1," "Application A2," etc. For details, please refer to the relevant descriptions in Figure 4a above, which will not be elaborated upon here.

[0144] 507: User device 10 detected that the user indicated on the search results page to view the target application.

[0145] For example, user device 10 detects an action by the user instructing them to view a target application on the search results interface. For instance, refer to the action shown in Figure 4a above, where the user clicks the view control 412 corresponding to "Application A" on the search interface 410. This action can instruct user device 10 to display more application-related information and controls for downloading the application, etc. Specific details can be found in the interface changes and related descriptions shown in Figures 4a to 4b above, which will not be elaborated upon here.

[0146] 508: User equipment 10 sends a request to application market server 20a to obtain the service location published for the application entity of the target application.

[0147] For example, in response to the user's instruction to view the target application on the search results interface, user device 10 can send a request to application market server 20a to obtain the service location corresponding to the application entity of the target application. As mentioned above, the service location corresponding to the application entity is also the country or region specified by the developer or operator for the corresponding application. The relevant service location information can also be stored in the entity database, along with the corresponding application entity.

[0148] 509: The application market server 20a returns to the user device 10 the service location and / or service location switching prompt information corresponding to the application entity of the target application.

[0149] For example, the application market server 20a can match the application entity corresponding to the target application and the service location information published by the application entity from the entity database based on the target application information requested by the user device 10. This matching process can be implemented, for example, using information provided by a preset data table, which can be referred to in Figure 8a below. Simultaneously, the application market server 20a can generate a unified service location switching prompt message for display on the user device 10 based on preset service location switching prompt text. Furthermore, the title of the service location switching effect displayed on the corresponding service location switching prompt interface shown on the user device 10 can also be uniformly obtained from the application market server 20a.

[0150] As an example, Figure 8a shows a schematic diagram of the information composition of a data table for setting prompt information related to a target application, according to an embodiment of this application.

[0151] Referring to Figure 8a, taking application A as an example, the relevant information data table for application A may include, but is not limited to, the following fields and their corresponding values: application name (value: "Application A"), application icon (value: "https: / / xxx.com"), target service location (value: "Country E"), service location switching prompt text (value: "This application is not available in the current region; you need to switch your country / region to Country E to access it"), and service location switching impact title (value: "Before clicking 'OK,' please ensure you accept the following impact: XXXX"). The target service location refers to the country or region where the target application is specifically published, such as Country E.

[0152] Figure 8b illustrates a schematic diagram of the information composition of a data table used to set instructions for switching service locations when downloading a target application, according to an embodiment of this application.

[0153] Referring to Figure 8b, the application market server 20a can also store the account token sent to the account server when switching to the target service location. The value of this token can indicate the target service location to be switched to. For example, when the application market server 20a sends the account token 40 with the value "Switch the service location of the current account to country E XX", it can instruct the account server to switch the service location to the server in the region of country E.

[0154] In some embodiments, the application market server 20a may also match the target application with data stored in the entity database, such as the number of times the target application has been downloaded and reviews in the application market, based on the target application information requested by the user device 10. This data may be collected data that is fed back to the application market server 20a by each application market client in real time, which will not be elaborated here.

[0155] In other embodiments, the service location and / or service switching prompt information returned by user equipment 10 in step 509 may also be returned to user equipment 10 along with the application description information of the target application when executing step 505. Correspondingly, the search request sent by user equipment 10 to application market server 20a in step 503 may carry not only a search request or acquisition request for the application description information, but also an acquisition request for the server and / or service switching prompt information published by the application entity of the target application. This application does not impose any restrictions on this.

[0156] 510: User equipment 10 displays a prompt message asking for a change of service location.

[0157] For example, after receiving the relevant information about the designated service location of the target application returned by the application market server 20a, as well as the preset prompt text for switching the service location and the title of the impact of switching the service location, the user equipment 10 can display the corresponding prompt information for switching the service location and the prompt information for the impact of switching the service location.

[0158] As an example, referring to Figure 9a, the prompt interface 910 displayed on mobile phone 100 can show prompt messages 911 and 912. Prompt message 911 may, for example, indicate "This application is not providing service in the current region. You need to switch your country / region to E to obtain it." For details, refer to prompt message 421 and related descriptions displayed on prompt interface 420 in Figure 4a above. Prompt message 912 may, for example, indicate "Before clicking 'OK,' please ensure you accept the following consequences: XXXX," to remind the user to confirm the potential impact of switching service locations and avoid any adverse effects on the user experience. The prompt interface 910 also displays an "OK" control 913 and a "Cancel" control 914. The "OK" control 913 is used to confirm the switch to a different service location, and the "Cancel" control 914 is used to cancel the switch. The specific results of the user's operation of these controls can be found in the content and related descriptions of step 511 below, and will not be elaborated upon here.

[0159] In other embodiments, the prompt message for switching service locations displayed by user equipment 10 can also be generated automatically. For example, user equipment 10 can generate the above-mentioned prompt message for switching service locations when it obtains the relevant service location information of the corresponding application published by application market server 20a. This is not a limitation.

[0160] 511: User equipment 10 detected that the user has decided to switch service locations.

[0161] For example, referring to Figure 9a, if a user clicks the "OK" control 913 on the prompt interface 910, it indicates agreement to switch service locations. Correspondingly, the user device 10, such as mobile phone 100, can detect this user operation, that is, it can detect the user's confirmation of switching service locations. Afterwards, the user device 10, such as mobile phone 100, continues to execute the interaction process with the application market server 20a described in steps 512 to 516 below. Then, the user device 10, such as mobile phone 100, can display the application download interface 920 shown in Figure 9a. Specific interactions and further changes to the display interface can be found in the steps and related descriptions below, and will not be repeated here.

[0162] 512: User equipment 10 sends a request to application market server 20a to switch service locations.

[0163] For example, based on the user's decision to switch service locations, user equipment 10 can generate a corresponding service location switch request and send it to application market server 20a. This service location switch request can request that the service location currently set by user equipment 10 be switched to the service location specified for the target application, such as country E.

[0164] 513: Application Market Server 20a sends a request to Account Server 40 to switch service locations.

[0165] For example, when the application market server 20a receives a request from the user device 10 to switch service locations, it can send a request to the account server 40 corresponding to the account that the user device 10 is logged into, in order to request the account server 40 to reset the service location for the user device 10, for example, to set the country E that the application entity was specified to publish as the new service location for the user device 10.

[0166] It is understandable that after user device 10 is powered on and used, before downloading the required app from the app store, the user usually needs to log in to the device's owner account. In this login scenario, user device 10 can initiate an account login request to account server 40 based on the user's actions of the logged-in account. Correspondingly, after successfully verifying the account information requested for login, account server 40 can return a successful account login result and the corresponding set service location to user device 10. This service location can be, for example, the country or region selected by the user when registering the account on user device 10, or the default country or region corresponding to the default account, etc., without restriction.

[0167] 514: Account server 40 returns a notification to application market server 20a that the service location switch was successful.

[0168] For example, the notification returned above may include a result indicating that the service location has been successfully switched or that the service location switch has been completed. This result may be a preset string or text, etc., without limitation.

[0169] 515: Application Market Server 20a returns a notification to User Equipment 10 that the service location switch was successful.

[0170] 516: User device 10 updates the service location and displays the download interface for the corresponding target application.

[0171] For example, based on the received notification, user device 10 can refresh the relevant interface of the application market, or exit and restart the application market to update the service location currently set in the application market.

[0172] As an example, the download interface displayed after the user device 10 updates the service location can refer to the application download interface 920 shown in Figure 9a above.

[0173] As shown in Figure 9a, the application download interface 920 can display more information related to application A, such as application A's rating, download / installation statistics, user reviews based on user experience, and information indicating that it has "passed security testing." The application download interface 920 can also display an installation control 921, which can display the size of the application entity corresponding to application A, such as "5.3MB," etc., without any restrictions. When the user clicks the installation control 921, it triggers the application market running on the phone 100 to download application A. This download process can be referred to in Figure 4b above and its related description, and will not be repeated here.

[0174] In other embodiments, the user device 10 may also fail to switch service locations even if the user agrees to do so. For example, if the user device 10, application market server 20a, and account server 40 fail to execute the above steps 512 to 514, the user device 10 may display the prompt interface 930 shown in FIG9b. As shown in FIG9b, the prompt interface 930 may display a prompt box 931. The prompt message displayed in the prompt box 931 may be, for example, "Switching failed, please try again later" or other content, which is not limited here.

[0175] It is understandable that the user may also click the "Cancel" control 914 on the prompt interface 910 shown in Figure 9a above to cancel the switch of service location, that is, the user can also refuse to switch service locations. At this time, the user device 10 can respond to the user's operation and return to the search interface of the application market, such as the search interface 410 shown in Figure 4a above.

[0176] 517: User device 10 detected an operation by which the user instructed to download the target application.

[0177] For example, referring to Figure 9a above, the user's instruction to download the target application could be, for instance, the user clicking the installation control 921 on the application download interface 920. Correspondingly, the user device 10 can detect this user operation and then continue to execute steps 518 to 521 to complete the download and installation process of the corresponding application.

[0178] 518: User equipment 10 sends a download request for the corresponding target application to application market server 20a.

[0179] For example, user equipment 10 can send a corresponding download request to application market server 20a in response to the detected user instruction to download the target application. This download request can be used to request the application market server 20a to obtain the application entity corresponding to the target application for installation, that is, to request the download of the application entity corresponding to the target application.

[0180] It is understood that after switching service locations, user equipment 10 can send the aforementioned download request to the server in the region of the new service location. If the server in the region of the new service location is the same as the server in the region of the previous service location, for example, both are application market servers 20a, then application market servers 20a can continue to perform the following step 519 to respond to the aforementioned download request.

[0181] 519: Application Market Server 20a responds to the download request and obtains the application entity corresponding to the target application.

[0182] For example, since the service location after the switch (e.g., country E) belongs to the same region as country A, the application market server 20a can respond to a download request for a target application sent by the user device 10 by matching the application entity corresponding to the target application from the entity database stored in the application entity database. The server in this publishing location can be understood as the server in the region where the target application is published. The information database on the application market server 20a can store the application description information of the target application, and the entity database can also store application entity data. Referring to Figure 7 above, the application market server 20a, which has relevant application entity resources, can provide responses to the search request or the download request. For example, the application market server 20a can obtain the application entity corresponding to the target application from the entity database used to store application entity resources.

[0183] 520: The application market server 20a returns the application entity corresponding to the target application to the user device 10.

[0184] For example, the application market server 20a can return the application entity of the target application obtained from the entity database as a response to the download request to the user device 10, that is, return the application entity corresponding to the target application to the user device 10.

[0185] 521: User device 10 displays the interface related to the completion of the download or the interface related to the installation of the target application.

[0186] For example, after receiving the application entity corresponding to the target application returned by the application market server 20a, the user device 10 can display a relevant interface indicating that the download has been completed. Referring to the installation management interface 010 shown in Figure 10a, the "Downloading" option of the installation management interface 010 can display the application being downloaded and the application that is "Installing" after the download is complete. It can be understood that when the application is installed, it can be displayed under the "Installed" option of the installation management interface 010 shown in Figure 10a, which will not be elaborated here. It can also be understood that the "Installing" displayed on the installation management interface 010 can also indicate that the user device 10 is installing the target application; therefore, this interface can also be described as a relevant interface for installing the target application.

[0187] In other embodiments, the interface displayed by the user equipment 10 for installing the target application may also be shown in Figure 10b or Figure 10c.

[0188] As shown in Figure 10b, the application installation interface 020 displayed by user device 10 can display an indicator control 021 indicating that application A is in the "installing" state. As shown in Figure 10c, the application installation interface 030 displayed by user device 10 can display an "open" control 031 indicating that application A has been installed and can be opened and run. It can be understood that in the application installation interface 020 shown in Figure 10b, if the application is installed, that is, the state changes from "installing" to "completed installation", the application installation interface 020 displayed by user device 10 can change to the application installation interface 030 shown in Figure 10b, and the aforementioned indicator control 021 can be switched to the "open" control 031, which will not be elaborated here.

[0189] It is understood that the download method provided in this application can be realized through the interaction process shown in Figure 5b between user device 10, application market server 20a, developer device 30, and account server 40. This method enables user device 10 to seamlessly search for various versions of applications released in different countries on servers in the same region, ensuring that users can find the applications they want in the application market, thus improving the user experience. Furthermore, when a user wants to download and install a searched application, user device 10 can also switch from the currently set service location to the service location where the application is released through the interaction between application market server 20a and account server 40, and download the corresponding application entity resources from the server in the same region as the service location where the application is released and the service location where user device 10 was previously located, and then install and run the application. This process can be completed without the user manually switching the service location, which also improves the user experience.

[0190] The following section, in conjunction with Example 2, describes the specific implementation process of the download method provided in this application in scenarios where the service location is in a different region before and after the switch.

[0191] Example 2

[0192] In this embodiment of the application, the service location of user equipment 10 before and after the switch may be different. Correspondingly, the servers accessed by the application market client running on user equipment 10 before and after the switch may be different servers.

[0193] Figure 11a illustrates a scenario where an application market client accesses different servers before and after switching service locations, according to an embodiment of this application.

[0194] As shown in Figure 11a, the service location of the application market client running on user device 10 before switching might be, for example, country A, and the service location after switching might be, for example, country B. However, the application market server for country A is application market server 20a, and the application market server for country B is application market server 20b. The service location set by user device 10 before switching could be set by the account server 40 corresponding to the logged-in account. The process of user device 10 switching service locations can be achieved through interaction between application market server 20a and account server 40.

[0195] In the scenario shown in Figure 11a, before switching service locations, user device 10 can access application market server 20a to query application description information; and after switching service locations, user device 10 can access application market server 20b to download application entity resources. As mentioned above, the application description information and application entity resources can be uploaded and published by developers through developer device 30.

[0196] As an example, Figure 11b illustrates a schematic diagram of the implementation process of a download method according to an embodiment of this application. This implementation process involves the interaction between user device 10, application market server 20a, application market server 20b, developer device 30, and account server 40.

[0197] Specifically, as shown in Figure 11b, the implementation process may include the following steps 1101 to 1121:

[0198] 1101: Application market server 20a and application market server 20b obtain application description information uploaded by developer device 30, and application market server 20b obtains application entity uploaded by developer device 30.

[0199] For example, when developers or operators publish an application, they can upload the application description information to the corresponding application market server in each region, such as application market server 20a and application market server 20b. In other embodiments, the server for uploading the application description information may also include application market servers in other regions, such as application market server 20c and application market server 20d as illustrated in Figure 3 above.

[0200] 1102: User device 10 detected a user searching for a target application.

[0201] 1103: User equipment 10 sends a search request for the target application to application market server 20a.

[0202] 1104: Application Market Server 20a responds to a search request and matches the application description information of the target application.

[0203] The specific execution process of steps 1102 to 1103 above can be referred to the relevant description of steps 502 to 503 in the above embodiment 1, and will not be repeated here.

[0204] Referring to Figure 7 above, user device 10, currently serving country B, can search for applications from application market server 20b in country B to obtain application description information such as strings corresponding to the searched applications. Similarly, user device 10, currently serving country C, can search for applications from application market server 20c in country C to obtain application description information. User device 10, currently serving country D, can search for applications from application market server 20d in country D to obtain application description information, and so on.

[0205] 1105: Application market server 20a returns application description information of the target application to user device 10.

[0206] 1106: User device 10 displays the search results interface for the target application based on application description information.

[0207] 1107: User device 10 detected that the user indicated to view the target application on the search results interface.

[0208] 1108: User equipment 10 sends a request to application market server 20a to obtain the service location published for the application entity of the target application.

[0209] 1109: The application market server 20a returns to the user device 10 the service location and / or service location switching prompt information corresponding to the application entity of the target application.

[0210] 1110: User equipment 10 displays a prompt message asking for a change of service location.

[0211] 1111: User equipment 10 detected that the user has decided to switch service locations.

[0212] The specific execution process of steps 1105 to 1111 above can be referred to the relevant description of steps 505 to 511 in the above embodiment 1, and will not be repeated here.

[0213] 1112: User equipment 10 sends a request to application market server 20a to switch service locations.

[0214] 1113: Application Market Server 20a sends a request to Account Server 40 to switch service locations.

[0215] For example, in the embodiments of this application, the above-mentioned request to send a service location switch can instruct the application market client running on user equipment 10 to switch the service location currently set to country B (i.e., the target service location).

[0216] 1114: Account server 40 returns a notification to application market server 20a that the service location switch was successful.

[0217] 1115: Application Market Server 20a returns a notification to User Equipment 10 that the service location switch was successful.

[0218] The specific execution process of steps 1112 to 1115 above can be referred to the relevant description of steps 512 to 515 in the above embodiment 1, and will not be repeated here.

[0219] 1116: User device 10 updates the service location and displays the download interface for the corresponding target application.

[0220] For example, after user device 10 updates its service location, the service location set accordingly becomes the switched service location, such as country B. At this time, the download interface for the corresponding target application displayed on user device 10 can be generated by application-related information provided by the application market server 20b of country B.

[0221] 1117: User equipment 10 detected an operation by which the user instructed to download the target application.

[0222] 1118: User equipment 10 sends a download request for the corresponding target application to application market server 20b.

[0223] For example, user equipment 10 can send a download request to application market server 20b in the region to which the target service location belongs, based on the switched target service location. This download request can correspond to a target application and is used to request the application entity resources of the target application, etc.

[0224] 1119: In response to a download request, the application market server 20b accesses the server where the target application is published and obtains the application entity corresponding to the target application.

[0225] For example, the application market server 20b can respond to a download request for a target application sent by the user device 10 by matching the application entity corresponding to the target application from the entity database stored in which the application entity of the target application is stored.

[0226] 1120: Application market server 20b returns the application entity corresponding to the target application to user device 10.

[0227] For example, the application market server 20b can return the application entity of the target application obtained from the entity database as a response to the download request to the user device 10, that is, return the application entity corresponding to the target application to the user device 10.

[0228] 1121: User device 10 displays the interface related to the completion of the download or the interface related to the installation of the target application.

[0229] For example, after receiving the application entity corresponding to the target application returned by the application market server 20b, the user equipment 10 can display a relevant interface indicating that the download has been completed. This interface can be referred to Figures 10a to 10c and related descriptions in Embodiment 1 above, and will not be repeated here.

[0230] It is understood that the download method provided in this application can be realized through the interaction process shown in Figure 11b between user device 10, application market server 20a, application market server 20b, developer device 30, and account server 40. This method enables user device 10 to seamlessly search for various versions of applications published on servers in different regions, ensuring that users can find the applications they want in the application market, thus improving the user experience. Furthermore, when a user wants to download and install a searched application, user device 10 can also switch from the currently set service location to the service location where the application is published through the interaction between application market server 20a and account server 40, and download the corresponding application entity resources from the server in the region where the application is published, thereby installing and running the application. This process can be completed without the user manually switching the service location, which also improves the user experience.

[0231] Figure 12 illustrates a hardware structure diagram of a user device according to an embodiment of this application. It is understood that the user device may include, for example, a mobile phone 100, a tablet computer, a smartwatch, or other terminals, and is not limited thereto.

[0232] User equipment 10 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identity module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0233] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the user equipment 10. In other embodiments of this application, the user equipment 10 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0234] Processor 110 may include one or more processing units, such as application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU). These different processing units may be independent devices or integrated into one or more processors.

[0235] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0236] In this embodiment of the application, the processor 110 of the mobile phone 100 can generate operation control signals through the controller to control the fetching and execution of instructions, so as to implement the corresponding steps in the interaction process shown in FIG5 above, or to implement the steps in the implementation process shown in FIG11 above, and realize the download method provided by this application, which will not be elaborated here.

[0237] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the aforementioned memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0238] In some embodiments, the processor 110 may include one or more interfaces. Interfaces 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 SIM card interface, and / or a universal serial bus (USB) interface, etc.

[0239] USB port 130 is a USB standard compliant interface, specifically a Mini USB port, Micro USB port, USB Type-C port, etc. USB port 130 can be used to connect a charger to charge user device 10, and can also be used for data transfer between user device 10 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as AR devices.

[0240] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the user equipment 10. In other embodiments of this application, the user equipment 10 may also adopt different interface connection methods or a combination of multiple interface connection methods as described in the above embodiments.

[0241] The wireless communication function of user equipment 10 can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor, and baseband processor.

[0242] Antennas 1 and 2 are used to transmit and receive electromagnetic wave signals. Each antenna in user equipment 10 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

[0243] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the user equipment 10. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via the antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via the antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0244] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates 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 processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0245] The wireless communication module 160 can provide solutions for wireless communication applications on user equipment 10, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0246] In some embodiments, antenna 1 of user equipment 10 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling user equipment 10 to communicate with networks and other devices via wireless communication technology. The aforementioned 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 technologies, etc. The aforementioned GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0247] User device 10 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0248] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Mini-LED, a Micro-LED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, user equipment 10 may include one or N displays 194, where N is a positive integer greater than 1.

[0249] User device 10 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0250] Camera 193 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, user equipment 10 may include one or N cameras 193, where N is a positive integer greater than 1.

[0251] The external storage interface 120 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the user device 10. The external storage card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external storage card.

[0252] Internal memory 121 can be used to store executable program code, including instructions. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of user device 10 (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. Processor 110 executes various functional applications and data processing of user device 10 by running instructions stored in internal memory 121 and / or instructions stored in memory located within the processor.

[0253] User equipment 10 can implement audio functions, such as music playback and recording, through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, and an application processor.

[0254] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A can be disposed on display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When force is applied to pressure sensor 180A, the capacitance between the electrodes changes. User equipment 10 determines the pressure intensity based on the change in capacitance. When a touch operation is applied to display screen 194, user equipment 10 detects the intensity of the touch operation based on pressure sensor 180A. User equipment 10 can also calculate the touch position based on the detection signal from pressure sensor 180A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation commands.

[0255] The fingerprint sensor 180H is used to collect fingerprints. The user equipment 10 can utilize the characteristics of the collected fingerprints to achieve fingerprint unlocking, accessing application locks, taking photos with fingerprints, and answering calls with fingerprints. In this embodiment, when the user equipment 10 logs into an account or downloads some applications, it can also verify the user's identity through the fingerprint sensor 180H before logging into the corresponding account and downloading applications from the application market.

[0256] Touch sensor 180K, also known as a "touch device," can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touchscreen." Touch sensor 180K detects touch operations applied to or near it. The touch sensor can transmit 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 display screen 194. In other embodiments, touch sensor 180K may also be located on the surface of user equipment 10, in a different position than display screen 194.

[0257] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. User equipment 10 can receive button input and generate key signal inputs related to user settings and function control of user equipment 10.

[0258] Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. For example, different vibration feedback effects can correspond to touch operations performed on different applications (such as taking photos, playing audio, etc.). Motor 191 can also correspond to different vibration feedback effects for touch operations performed on different areas of the display screen 194. Different application scenarios (such as time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

[0259] Indicator 192 can be an indicator light, used to indicate charging status, power changes, or to indicate messages, missed calls, notifications, etc.

[0260] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to make contact with or separate from the user equipment 10.

[0261] Figure 13 illustrates a schematic diagram of the operating system software structure of a user device according to an embodiment of this application.

[0262] It is understood that the operating system of user device 10 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses the layered architecture Android system as an example to exemplify the system software structure of user device 10.

[0263] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, Android... TM The system is divided into four layers, from top to bottom: application layer, application framework layer, and Android.TM runtime (Android) TM runtime and system libraries, as well as the kernel layer.

[0264] As shown in Figure 13, the application layer can include a series of application packages. These application packages can include applications such as camera, gallery, calendar, calling, maps, navigation, WLAN, Bluetooth, music, video, SMS, and an app store.

[0265] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0266] The application framework layer may include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

[0267] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0268] Content providers store and retrieve data, making that data accessible to applications. This data can include videos, images, audio, phone calls made and received, browsing history and bookmarks, phone books, etc.

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

[0270] The phone manager is used to provide communication functions for user device 10. For example, it manages call status (including connection, hang-up, etc.).

[0271] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0272] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of completed downloads or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating electronic devices, and flashing indicator lights.

[0273] Android TM The runtime includes the core libraries and the virtual machine. Android TM runtime is responsible for Android TM System scheduling and management.

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

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

[0276] System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0277] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0278] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

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

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

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

[0282] This application also provides a computer program product for implementing the download methods provided in the above embodiments.

[0283] Various embodiments of the mechanisms disclosed in this application can be implemented in hardware, software, firmware, or combinations of these implementation methods. Embodiments of this application can be implemented as computer program modules or module code executable on a programmable system, the programmable system including at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

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

[0285] Module code can be implemented using a high-level modular language or an object-oriented programming language to communicate with the processing system. Assembly language or machine language can also be used to implement module code when needed. In fact, the mechanisms described in this application are not limited to any particular programming language. In either case, the language can be a compiled language or an interpreted language.

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

[0287] In this specification, the reference to "an embodiment" or "an embodiment" means that a specific feature, structure, or characteristic described in connection with the embodiment is included in at least one exemplary implementation or technology disclosed according to an embodiment of this application. The appearance of the phrase "in an embodiment" in various places in the specification does not necessarily refer to the same embodiment.

[0288] The disclosure of embodiments of this application also relates to means for performing operations in text. This means may be specifically constructed for the claimed purpose or may include a general-purpose computer selectively activated or reconfigured by a computer program stored in a computer. Such a computer program may be stored on a computer-readable medium, such as, but not limited to, any type of disk, including floppy disks, optical disks, CD-ROMs, magneto-optical disks, read-only memory (ROM), random access memory (RAM), EPROM, EEPROM, magnetic or optical cards, application-specific integrated circuits (ASICs), or any type of medium suitable for storing electronic instructions, and each may be coupled to a computer system bus. Furthermore, the computer mentioned in the specification may include a single processor or may employ an architecture involving multiple processors for increased computing power.

[0289] Furthermore, the language used in this specification has been primarily chosen for readability and instructional purposes and may not have been chosen to depict or limit the disclosed subject matter. Therefore, the embodiments disclosed herein are intended to illustrate, and not limit, the scope of the concepts discussed herein.

Claims

1. A downloading method, applied to a first device, characterized in that, The current usage location of the first device corresponds to the first service location, and, The method includes: A first action by a user in a first application is detected, wherein the first action indicates the acquisition of a first resource; The location where the first resource was published is determined to be the second service location; In response to the first operation, the location of use of the first device is switched to the second service location, and the first resource is displayed in the first application.

2. The method according to claim 1, characterized in that, The first resource includes first description information and a first resource file, wherein, The first description information is published in multiple regions, and the multiple regions include the second service location and the first service location; The location where the first resource file is published includes the second service location.

3. The method according to claim 2, characterized in that, The detection of the user's first action in the first application includes: A user's search operation in the first application is detected, wherein the search operation indicates a search for the first resource; Based on the first application accessing the second device, the first description information corresponding to the first resource is searched, and the first search result generated based on the first description information is displayed in the first application; Corresponding to the user's first operation on the first resource in the first search result, the user's first operation in the first application is detected.

4. The method according to claim 3, characterized in that, Determining the publishing location of the first resource as the second service location includes: Obtain the publication location information of the first resource file; Based on the publishing location information of the first resource file, the publishing location of the first resource is determined to be the second service location.

5. The method according to claim 4, characterized in that, The step of switching the usage location of the first device to the second service location in response to the first operation includes: Send a handover request to the second device, instructing it to switch from the first service location to the second service location; and, Based on the notification of successful service location switch returned by the second device, the usage location is updated to the second service location.

6. The method according to claim 5, characterized in that, Sending a handover request to the second device, instructing it to switch from the first service location to the second service location, includes: The first interface of the first application is displayed, wherein the first interface is used to prompt the user to confirm whether to switch service locations; In response to the second operation of the user confirming the switch of service location, a switch request is sent to the second device to instruct the first service location to be switched to the second service location.

7. The method according to claim 6, characterized in that, The current location set on the first device is related to the first account logged into on the first device, and the first account logged into on the first device corresponds to accessing the third device. The notification of successful service location handover returned by the second device includes: Receive a notification from the third device that the service location switch was successful, returned by the second device.

8. The method according to claim 5, characterized in that, The region to which the first service location belongs is the same as the region to which the second service location belongs, and the second device corresponds to a server in either the region to which the first service location or the region to which the second service location belongs. Displaying the first resource in the first application includes: Display a second interface of the first application, wherein the second interface is used to instruct the installation or playback of the first resource; Upon detecting a third operation instructing the user to install or play the first resource, a download request corresponding to the first resource is sent to the second device; The first resource returned by the second device is obtained, and a third interface of the first application is displayed, wherein the content displayed on the third interface includes the first resource.

9. The method according to claim 5, characterized in that, The regions to which the first service location belongs are different from the regions to which the second service location belongs. The server in the region to which the first service location belongs corresponds to the second device, and the server in the region to which the second service location belongs corresponds to the third device. and, Displaying the first resource in the first application includes: Display a second interface of the first application, wherein the second interface is used to instruct the installation or playback of the first resource; Upon detecting a third operation instructing the user to install or play the first resource, a download request corresponding to the first resource is sent to the third device; The first resource returned by the third device is obtained, and a third interface of the first application is displayed, wherein the content displayed on the third interface includes the first resource.

10. The method according to claim 8 or 9, characterized in that, The content displayed on the second interface is related to the first resource published in the second service location; and, The content displayed on the second interface also includes one or more of the following data related to the first resource: The rating data corresponding to the first resource; The download or installation count statistics corresponding to the first resource; The comment data corresponding to the first resource; The security detection result corresponds to the first resource; Detailed information corresponding to the first resource; Recommended resources that match the first resource.

11. The method according to any one of claims 3 to 7, characterized in that, The first resource includes any one of applications, music, and videos.

12. The method according to claim 11, characterized in that, Corresponding to the first resource being an application, detecting the user's first operation in the first application includes: The system detected that the user responded to the first search result indicating that they wanted to view or install the first resource.

13. The method according to claim 11, characterized in that, Corresponding to the first resource being music or video, detecting the user's first operation in the first application includes: The system detected a user's action in response to a search result indicating that the first resource should be downloaded or played.

14. A communication system, characterized in that, It includes a first device and a second device, wherein the current usage location of the first device corresponds to a first service location, wherein, The first device is used to respond to a detected first operation by a user in a first application and send a first acquisition request for a first resource to the second device, wherein the first operation indicates acquisition of the first resource; The second device is used to respond to the first acquisition request sent by the first device and return the first description information of the first resource to the first device, wherein the first description information includes the publishing location information of the first resource; The first device is used to determine the publishing location of the first resource as the second service location based on the publishing location information of the first resource; and, The first device switches the usage location to the second service location and sends a second request to the second device for the first resource file of the first resource based on the second service location; The second device is used to respond to the second acquisition request sent by the first device and return the first resource file to the first device.

15. The system according to claim 14, characterized in that, It also includes a third device, which corresponds to a server in the region to which the second service location belongs, wherein, The first device switches the usage location to the second service location and sends a third request to the third device for the first resource file of the first resource based on the second service location; The third device is used to respond to the third acquisition request sent by the first device and return the first resource file to the first device.

16. The system according to claim 14 or 15, characterized in that, The first description information is published in multiple regions, including the region to which the first service location belongs and the region to which the second service location belongs; and, The location where the first resource file is published includes the second service location.

17. An electronic device, characterized in that, include: One or more processors; One or more memories; the one or more memories storing one or more programs, which, when executed by the one or more processors, cause the electronic device to perform the download method according to any one of claims 1 to 13.

18. A computer-readable medium, characterized in that, The readable medium stores instructions that, when executed on a computer, cause the computer to perform the download method according to any one of claims 1 to 13.

19. A computer program product, characterized in that, Includes a computer program / instruction that, when executed by a processor, implements the download method according to any one of claims 1 to 13.

Images