Mobile client uniform resource locator processing method and apparatus

Abstract

This invention discloses a method and apparatus for processing Uniform Resource Locators (URLs) on mobile clients, relating to the field of computer technology. The method includes: obtaining a URL from the mobile client; invoking a URL resolver to decompose the URL and obtain the domain name, subdirectories, and parameters extracted from it; matching a target tool in the mobile client's function call tool list based on the decomposed domain name; and launching the function and / or page pointed to by the URL based on the target tool, the decomposed subdirectories, and the parameters. This invention improves the consistency and flexibility of launching functions or pages by using pre-defined URLs, and reduces the development cost of launching functions or pages.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method and apparatus for processing Uniform Resource Locators (URLs) on mobile clients. Background Technology

[0002] This section is intended to provide background or context for the embodiments of the invention set forth in the claims. The description herein is not an admission that it is prior art simply because it is included in this section.

[0003] In today's booming mobile internet era, push notification services are often provided to enhance user activity and engagement on individual mobile clients or to guide module usage. Some message processing requires the mobile client to call specific modules or pages. Currently, the mobile client's handling of push notifications calling specific modules or pages is as follows: The mobile client and server agree on the required supported functions or page types and specify their type values. After receiving the push message, the mobile client parses the dictionary data transmitted by the server through the push notification channel, reads the type identifier, reads other fields required for that type in the dictionary based on the type value, and determines whether the type value is in the previously agreed-upon list of supported functions or page types. If it is within the agreed-upon range, the corresponding function call logic code or page redirection logic code is executed; otherwise, no processing is performed or a general placeholder page is redirected.

[0004] With the proliferation of various mobile client applications, interconnectivity is needed to broaden the service capabilities of individual mobile clients. This allows users to invoke other mobile clients and access their specific services while using a single mobile client. These specific services include, but are not limited to, social sharing and opening mini-programs. Currently, the solution for handling such needs is to include the necessary dependent SDK code in each page that needs to invoke the specific services of other mobile clients. This involves calling the service activation logic code provided by the SDK to achieve the function of invoking other mobile clients or their specific services.

[0005] Currently, the dictionary data passed by the parsing server through the message push channel contains cumbersome type fields and business fields. Furthermore, the SDK code that functions that invoke other mobile clients or their specific services depend on needs to be extensively imported throughout the project. If you want to change the invoked mobile client or function, you need to modify the mobile client code and redeploy a new version, and the code is not universal. Summary of the Invention

[0006] This invention provides a method for processing Uniform Resource Locators (URLs) on mobile clients, which enables the invocation of functions or pages through pre-defined URLs. This improves the consistency and flexibility of invoking functions or pages and reduces the development cost of invoking functions or pages. The method includes:

[0007] Obtain the Uniform Resource Locator (URL) of the mobile client;

[0008] Invoke the Uniform Resource Locator (URL) resolver to disassemble the URL and obtain the domain name, subdirectory, and parameters extracted from the URL.

[0009] Based on the domain name obtained from the splitting, the target tool is matched in the list of function call tools in the mobile client;

[0010] Based on the target tool, the resulting subdirectories, and the parameters, invoke the function and / or page pointed to by the Uniform Resource Locator.

[0011] This invention also provides a mobile client Uniform Resource Locator (URL) processing device, used to invoke functions or pages through pre-set URLs, thereby improving the consistency and flexibility of the invoked functions or pages and reducing the development cost of the invoked functions or pages. The device includes:

[0012] The data acquisition module is used to acquire the Uniform Resource Locator (URL) of the mobile client;

[0013] The data disassembly module is used to call the Uniform Resource Locator (URL) resolver to disassemble the URL and obtain the domain name, subdirectory and parameters split from the URL.

[0014] The target tool matching module is used to match the target tool in the list of function call tools in the mobile client based on the domain name obtained from the splitting.

[0015] The function invocation module is used to invoke the function and / or page pointed to by the Uniform Resource Locator based on the target tool, the subdirectories obtained from the splitting, and the parameters.

[0016] This invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the above-described mobile client Uniform Resource Locator (URL) processing method.

[0017] This invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described mobile client Uniform Resource Locator (URL) processing method.

[0018] This invention also provides a computer program product, which includes a computer program that, when executed by a processor, implements the above-described mobile client Uniform Resource Locator (URL) processing method.

[0019] In this embodiment of the invention, the mobile client Uniform Resource Locator (URL) processing scheme obtains the URL of the mobile client; calls a URL resolver to decompose the URL and obtain the domain name, subdirectory, and parameters extracted from it; matches the target tool in the function call tool list of the mobile client based on the decomposed domain name; and invokes the function and / or page pointed to by the URL based on the target tool, the decomposed subdirectory, and the parameters. Compared with the existing technology that parses dictionary data transmitted by the server through the message push channel, which contains cumbersome type fields and business fields; and where the SDK code required to invoke other mobile clients or their specific services needs to be extensively introduced throughout the project, and if the invoked mobile client or function needs to be changed, the mobile client code needs to be modified and a new version needs to be released, and the code is not universal, the scheme of invoking functions or pages through pre-defined URLs improves the consistency and flexibility of invoking functions or pages, and reduces the development cost of invoking functions or pages. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0021] Figure 1 This is a flowchart illustrating the mobile client unified resource locator processing method in an embodiment of the present invention;

[0022] Figure 2 This is a schematic diagram of the implementation environment of the mobile client unified resource locator processing method in this embodiment of the invention;

[0023] Figure 3 This is a flowchart illustrating the processing of Uniform Resource Locators (URLs) on a mobile client in an embodiment of the present invention.

[0024] Figure 4 This is a flowchart of the mobile client's Uniform Resource Locator (URL) processing in another embodiment of the present invention;

[0025] Figure 5 This is a schematic diagram of the architecture of the Uniform Resource Locator (URL) resolver and the function invocation tool in an embodiment of the present invention;

[0026] Figure 6 This is a schematic diagram of the structure of the mobile client unified resource locator processing device in an embodiment of the present invention;

[0027] Figure 7 This is a schematic diagram of the structure of a mobile client unified resource locator processing device in another embodiment of the present invention;

[0028] Figure 8 This is a schematic diagram of the structure of a mobile client unified resource locator processing device in another embodiment of the present invention. Detailed Implementation

[0029] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings. Here, the illustrative embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

[0030] The acquisition, storage, use, and processing of data in this application all comply with the relevant provisions of national laws and regulations.

[0031] In this document, the term "and / or" merely describes a relationship, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. Furthermore, the term "at least one" in this document means any combination of at least two of any one or more elements. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0032] In the description of this specification, the terms "comprising," "including," "having," and "containing" are open-ended terms, meaning that they include but are not limited to. The terms "an embodiment," "a specific embodiment," "some embodiments," and "for example," etc., refer to specific features, structures, or characteristics described in connection with that embodiment or example that are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, or characteristics described can be combined in any suitable manner in one or more embodiments or examples. The order of steps involved in the various embodiments is used to illustrate the implementation of this application, and the order of steps is not limited and can be adjusted appropriately as needed.

[0033] Mobile client: In contrast to server, it refers to a program that runs on a mobile terminal and provides local services to customers.

[0034] Uniform Resource Locator (URL): A method of representing the location of information on the World Wide Web service of the Internet.

[0035] The inventors discovered that the dictionary data transmitted by the parsing server through the message push channel contained cumbersome type fields and business fields. At the same time, the SDK code that the function of calling up other mobile clients or their specific services depends on needs to be introduced extensively throughout the project. If you want to change the called mobile client or function, you need to modify the mobile client code and redeploy the version, and the code is not universal.

[0036] To achieve consistent and flexible invocation of functions or pages, embodiments of the present invention provide a mobile client Uniform Resource Locator (URL) processing method. This method uses pre-defined URLs to invoke functions or pages, improving the consistency and flexibility of function or page invocation and reducing the development cost of invoking functions or pages. Figure 1 As shown, the method includes:

[0037] Step 101: Obtain the Uniform Resource Locator (URL) for the mobile client;

[0038] Step 102: Call the Uniform Resource Locator (URL) resolver to disassemble the URL and obtain the domain name, subdirectory, and parameters extracted from the URL.

[0039] Step 103: Based on the domain name obtained from the splitting, match the target tool in the list of function call tools in the mobile client;

[0040] Step 104: Based on the target tool, the resulting subdirectories, and the parameters, invoke the function and / or page pointed to by the Uniform Resource Locator.

[0041] The implementation environment of this invention is as follows Figure 2As shown, the system includes a mobile terminal 100, a second mobile terminal 200, and a server 300. The mobile terminal 100 and the second mobile terminal 200 include, but are not limited to, mobile phones, smartwatches, and tablets. A mobile client runs on the mobile terminal 100, and a second mobile client runs on the second mobile terminal 200. The server 300 interacts with the mobile terminal 100 via a wired or wireless network, pushing data to the mobile client running on the mobile terminal 100. The second mobile terminal 200 transmits data to the mobile client of the mobile terminal 100 via the second mobile client when a user clicks a button to trigger an event. Furthermore, the system includes other channels that provide materials containing data to the mobile client of the mobile terminal 100. These other channels may include web pages capable of generating and providing materials, other mobile clients, and computer software programs. Materials include, but are not limited to, QR codes, barcodes, voice recordings containing Uniform Resource Locators (URLs), and images containing URLs.

[0042] In one embodiment, before performing step 101, the mobile client Uniform Resource Locator (URL) processing flow is as follows: Figure 3 As shown, the process includes: a mobile client receiving data pushed by a server 300, the data including display data and a Uniform Resource Locator (URL); pushing the display data to the user interface of the mobile client, whereby the display data is shown to the user of the mobile client; and, upon receiving a signal from the user of the mobile client clicking on the user interface to display the data, starting to acquire the URL from the data pushed by the server.

[0043] In one embodiment, before performing step 101, the mobile client Uniform Resource Locator (URL) processing flow is as follows: Figure 4 As shown, it includes: receiving data transmitted by a second mobile client; parsing the transmitted data, wherein the data includes a Uniform Resource Locator (URL).

[0044] In one embodiment, prior to performing step 101, materials from other channels are read, wherein other channels may include: web pages capable of generating and providing materials, other mobile clients, and computer software programs. Materials include, but are not limited to, QR codes, barcodes, audio containing Uniform Resource Locators (URLs), and images containing URLs; data in the materials is parsed, the data including URLs.

[0045] In one embodiment, the Uniform Resource Locator (URL) further includes a protocol header, which can be customized according to business needs.

[0046] In specific implementation, before executing step 103, the protocol header is obtained by splitting the Uniform Resource Locator (URL), and the URL is used to perform security verification. After the security verification result shows that the URL belongs to a pre-set list of protocol headers, the target tool is matched from the list of function call tools in the mobile client based on the domain name obtained by splitting the URL.

[0047] In one embodiment, the method further includes: creating a Uniform Resource Locator (URL) resolver and a list of function invocation tools, wherein the resolver includes a mapping between domain names and tools; when a new function and / or page is created, registering the new function and / or page in the tool list; obtaining the domain name corresponding to the new function and / or page, and adding the mapping between the domain name and the registered tools to the resolver.

[0048] Specifically, the mobile client needs to pre-create a Uniform Resource Locator (URL) resolver and a list of function invocation tools. The resolver includes the mapping between domain names and tools. When new functions and / or pages need to be created as the project is updated and iterated, the new functions and / or pages are registered in the tool list. The domain name corresponding to the new function and / or page is obtained, and the mapping between the domain name and the registered tools is added to the resolver. The next time the function and / or page is invoked, it can directly point to the function and / or page through the corresponding target tool.

[0049] In a specific embodiment, such as Figure 5 As shown, the architecture of the Uniform Resource Locator (URL) resolver and function invocation tool is as follows: The resolver includes the mapping between domain names and tools, and determines the location of the domain name in the function invocation tool list (e.g., ...). Figure 5 The target tool is matched from the tools shown (tool 1, tool 2, tool 3, etc.). Based on the target tool, the subdirectories and parameters obtained from the decomposition of the Uniform Resource Locator (URL), the function and / or page pointed to by the URL is invoked (e.g., ...). Figure 5 (The functions shown are 11, 21, 31, page 12, page 22, page 32, etc.)

[0050] For example, a Uniform Resource Locator (URL) takes the following form:

[0051] safe: / / m.test.com.miniprogram / weixin? param={“appId”:”123456”,...}

[0052] Wherein, safe is the protocol header that is accepted by agreement, m.test.com.miniprogram is the domain name of the function or page to be invoked (in the example, it is the mini-program function), weixin is the subdirectory in the main category of the invoked function, and param is the parameter (in key-value pair form) required to call the function or page.

[0053] In one embodiment, the present invention provides a mobile client Uniform Resource Locator (URL) processing system, the system comprising:

[0054] A server is used to push data to mobile clients, the data including display data and Uniform Resource Locators;

[0055] The second mobile client is used to provide data containing Uniform Resource Locators to the mobile client;

[0056] Mobile client, used for:

[0057] The system receives data pushed by the server, the data including display data and Uniform Resource Locators (URLs); pushes the display data to the user interface of the mobile client, and displays the display data to the user of the mobile client in the user interface; after receiving a signal from the user of the mobile client to click on the user interface to display data, it begins to acquire the URLs in the data pushed by the server.

[0058] And / or read data transmitted by the second mobile client; parse the transmitted data, which includes a Uniform Resource Locator;

[0059] And / or read materials from other channels, wherein other channels may include: web pages, other mobile clients, and computer software programs capable of generating and providing materials. Materials include, but are not limited to, QR codes, barcodes, audio containing Uniform Resource Locators (URLs), and images containing URLs; parse data in the materials, wherein the data includes URLs;

[0060] After obtaining the Uniform Resource Locator (URL) of the mobile client, the URL resolver is invoked to disassemble the URL and obtain the protocol header, domain name, subdirectory, and parameters extracted from it; the security of the URL is then verified based on the extracted protocol header.

[0061] Once the security check result indicates that the protocol header does not belong to the pre-defined protocol header list, processing of the Uniform Resource Locator (URL) is stopped.

[0062] After the security verification result indicates that it belongs to the pre-defined protocol header list, the target tool is matched in the function call tool list of the mobile client based on the domain name obtained from the splitting; based on the target tool, the split subdirectories and parameters, the function and / or page pointed to by the Uniform Resource Locator is invoked;

[0063] The Uniform Resource Locator (URL) resolver and the list of function invocation tools are created in advance, including: creating a URL resolver and a list of function invocation tools, wherein the resolver includes the mapping between domain names and tools; when a new function and / or page is created, registering the new function and / or page in the tool list; obtaining the domain name corresponding to the new function and / or page, and adding the mapping between the domain name and the registered tools to the resolver.

[0064] In summary, the mobile client Uniform Resource Locator (URL) processing method provided by this invention obtains the protocol header, domain name, subdirectory, and parameters by parsing the acquired custom URL. It performs security checks on the protocol header, and for headers conforming to the security list, it performs a joint judgment on the domain name and subdirectory to match the target function or page, and then passes the parameters to invoke the target function or page. A single custom URL can be used to invoke a function or page, eliminating the need to configure cumbersome type and business fields. Furthermore, the SDK that the function depends on does not need to be included in all required functions throughout the project; it only needs to be included once in the mobile client function or page invocation system. Moreover, functions or pages registered in the aforementioned function or page invocation system can be dynamically matched without code modification. This improves the consistency and flexibility of function invocation and page redirection, and reduces the development cost of calling the same function or page in different scenarios.

[0065] This invention also provides a mobile client Uniform Resource Locator (URL) processing device, as described in the following embodiments. Since the principle by which this device solves the problem is similar to that of the mobile client URL processing method, the implementation of this device can refer to the implementation of the mobile client URL processing method; repeated details will not be elaborated further.

[0066] Figure 6 This is a schematic diagram of the structure of the mobile client Uniform Resource Locator (URL) processing device in an embodiment of the present invention, applied to a mobile client, such as... Figure 6 As shown, the device includes:

[0067] Data acquisition module 01 is used to acquire the Uniform Resource Locator (URL) of the mobile client;

[0068] Data parsing module 02 is used to call the Uniform Resource Locator (URL) resolver, disassemble the URL, and obtain the domain name, subdirectory, and parameters split from the URL.

[0069] The target tool matching module 03 is used to match the target tool in the list of function call tools in the mobile client based on the domain name obtained from the splitting.

[0070] Function Invocation Module 04 is used to invoke the function and / or page pointed to by the Uniform Resource Locator based on the target tool, the split subdirectories and parameters.

[0071] In one embodiment, such as Figure 7 As shown, the mobile client unified resource locator processing device in this embodiment of the invention further includes:

[0072] The security verification module 05 is used to perform security verification on the Uniform Resource Locator (URL) based on the protocol header obtained from the split domain name before matching the target tool in the function call tool list of the mobile client. After the security verification result is that it belongs to the pre-set protocol header list, the URL is further processed.

[0073] In one embodiment, the data acquisition module 01 is specifically used for:

[0074] Before obtaining the Uniform Resource Locator (URL) of the mobile client, data pushed by the server is received, including display data and URLs.

[0075] The display data will be pushed to the user interface of the mobile client, and the display data will be shown to the user of the mobile client.

[0076] Upon receiving a signal from a mobile client user clicking on the user interface to display data, the system begins retrieving Uniform Resource Locators (URLs) from the data pushed by the server.

[0077] In one embodiment, the data acquisition module 01 is specifically used for:

[0078] Read the data transmitted from the second mobile client;

[0079] The transmitted data is parsed, and the data includes a Uniform Resource Locator (URL).

[0080] In one embodiment, the data acquisition module 01 is specifically used for:

[0081] Read materials, including but not limited to QR codes, barcodes, voice messages containing Uniform Resource Locators (URLs), and images containing URLs;

[0082] Parse the data in the material, which includes Uniform Resource Locators (URLs).

[0083] In one embodiment, such as Figure 8 As shown, the mobile client unified resource locator processing device in this embodiment of the invention further includes:

[0084] Module 06 is used to create a Uniform Resource Locator (URL) resolver and a list of function invocation tools. The resolver includes the mapping between domain names and tools. When a new function and / or page is created, the new function and / or page is registered in the tool list. The domain name corresponding to the new function and / or page is obtained, and the mapping between the domain name and the registered tools is added to the resolver.

[0085] In one embodiment, the security verification module 05 is specifically used to: stop processing the Uniform Resource Locator after the security verification result shows that the verification protocol header does not belong to the pre-set protocol header list.

[0086] This invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the above-described mobile client Uniform Resource Locator (URL) processing method.

[0087] This invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described mobile client Uniform Resource Locator (URL) processing method.

[0088] This invention also provides a computer program product, which includes a computer program that, when executed by a processor, implements the above-described mobile client Uniform Resource Locator (URL) processing method.

[0089] In this embodiment of the invention, the mobile client Uniform Resource Locator (URL) processing scheme differs from existing technologies that resolve dictionary data transmitted by the server via message push channels. These solutions involve resolving cumbersome type and business fields within the dictionary data, requiring extensive SDK code integration across the entire project to invoke other mobile clients or their specific services. Furthermore, changing the invoked mobile client or function necessitates modifying the mobile client code and re-releasing the solution, resulting in incompatible code. The present invention obtains the mobile client's URL; invokes a URL resolver to decompose the URL, extracting the domain name, subdirectories, and parameters; matches the target tool in the mobile client's function invocation tool list based on the decomposed domain name; and invokes the function and / or page pointed to by the URL based on the target tool, the decomposed subdirectories, and the parameters. This allows for the invocation of functions or pages using pre-defined URLs, improving consistency and flexibility while reducing development costs.

[0090] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0091] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0092] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0093] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0094] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A mobile client uniform resource locator processing method, characterized by, The application is applied to a mobile client, and comprises the following steps: a uniform resource locator of the mobile client is acquired; a uniform resource locator resolver is called to disassemble the uniform resource locator, and a domain name, a subdirectory and parameters separated from the uniform resource locator are acquired; a target tool is matched from a tool list of the mobile client according to the domain name; a function and / or a page pointed by the uniform resource locator are started according to the target tool, the subdirectory and the parameters; the uniform resource locator resolver and the tool list of the function are constructed, the domain name of the new function and / or the page is obtained, and the domain name and the corresponding relationship of the registered tool are added to the resolver; the uniform resource locator further comprises a protocol header; 2. The method of claim 1, wherein, before the target tool is matched from the tool list of the mobile client according to the domain name, the following step is further included: the uniform resource locator is security checked according to the protocol header; the target tool is matched from the tool list of the mobile client according to the domain name, and the following step is included: after the security checking result is that the protocol header belongs to a preset protocol header list, the target tool is matched from the tool list of the mobile client according to the domain name. before the uniform resource locator of the mobile client is acquired, the following step is further included:

3. The method of claim 1, wherein, data pushed by a server is received, and the data comprises display data and a uniform resource locator; the display data is pushed to a user interface of the mobile client, and the display data is displayed to a user of the mobile client on the user interface; after a signal that the display data of the user interface is clicked by the user of the mobile client is received, the uniform resource locator in the data pushed by the server is acquired. the following steps are further included:

4. The method of claim 1, wherein, data transmitted by a second mobile client is received; the transmitted data is parsed, and the data comprises a uniform resource locator. the following steps are further included:

5. The method of claim 1, wherein, a material is read, and the material comprises but is not limited to a two-dimensional code, a bar code, a voice containing a uniform resource locator and a picture containing a uniform resource locator; data in the material is parsed, and the data comprises a uniform resource locator. the mobile client comprises but is not limited to software running on the following terminals:

6. The method of claim 1, wherein, a mobile phone, a smart watch and a tablet computer. the following step is further included:

7. The method of claim 2, wherein, after the security checking result is that the protocol header does not belong to the preset protocol header list, the processing of the uniform resource locator is stopped. The application is applied to a mobile client, and comprises the following steps:

8. A mobile client uniform resource locator processing apparatus, characterized by, a data acquisition module is used to acquire a uniform resource locator of the mobile client; a data parsing module is used to call a uniform resource locator resolver to disassemble the uniform resource locator, and a domain name, a subdirectory and parameters separated from the uniform resource locator are acquired; ​ The target tool matching module is configured to match a target tool from the function calling tool list of the mobile client according to the domain name obtained by the splitting; The function invoking module is configured to invoke the function and / or page pointed by the uniform resource locator according to the target tool, the subdirectory and the parameter obtained by the splitting; The creating module is further configured to: create a uniform resource locator resolver and a function calling tool list, the resolver including the correspondence between the domain name and the tool; register the new function and / or page in the tool list when the new function and / or page is created; and add the domain name corresponding to the new function and / or page to the resolver according to the correspondence between the registered tool. The architecture of the uniform resource locator resolver and the function calling tool is that: the target tool is matched from the function calling tool list according to the domain name, and the function and / or page pointed by the uniform resource locator is invoked according to the target tool, the subdirectory and the parameter obtained by the splitting of the uniform resource locator.

9. The apparatus of claim 8, wherein, The security verification module is further configured to: Before the target tool is matched from the function calling tool list of the mobile client according to the domain name obtained by the splitting, the uniform resource locator is subjected to security verification according to the protocol header obtained by the splitting, and the processing of the uniform resource locator is continued when the security verification result is that the protocol header belongs to the pre-set protocol header list.

10. The apparatus of claim 8, wherein, The data acquisition module is specifically configured to: Before the uniform resource locator of the mobile client is acquired, data pushed by a server is received, the data including display data and the uniform resource locator; The display data is pushed to a user interface of the mobile client, and the display data is displayed to a user of the mobile client on the user interface; After a signal is received that the user of the mobile client clicks the display data of the user interface, the acquisition of the uniform resource locator in the data pushed by the server is started.

11. The apparatus of claim 8, wherein, The data acquisition module is specifically configured to: receive data transmitted by a second mobile client; parse the transmitted data, the data including the uniform resource locator.

12. The apparatus of claim 8, wherein, The data acquisition module is specifically configured to: read a material, the material including but not limited to a two-dimensional code, a bar code, a voice including the uniform resource locator and a picture including the uniform resource locator; parse the data in the material, the data including the uniform resource locator.

13. The apparatus of claim 9, wherein, The security verification module is specifically configured to: stop the processing of the uniform resource locator when the security verification result is that the verification protocol header does not belong to the pre-set protocol header list.

14. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, The processor executes the computer program to implement the method in any one of claims 1 to 7.

15. A computer-readable storage medium, characterized in that, The computer readable storage medium stores the computer program, and the computer program is executed by the processor to implement the method in any one of claims 1 to 7.

16. A computer program product, characterised in that, The computer program product includes the computer program, and the computer program is executed by the processor to implement the method in any one of claims 1 to 7.

Images