A method, device and computer equipment for customizing native page jump adaptation

Abstract

The embodiment of the present application belongs to the field of software development and financial technology, and relates to a customized native page jump adaptation method. The embodiment of the present application configures the native page of the APP operation module into a card, generates a mapping relationship between the native page and the operation module including the routing key of the native page, delivers the mapping relationship to the user terminal for local caching, and matches the mapping relationship with the version information of the user terminal and stores it in the back end; after receiving the user's request to access the APP operation module, an H5 intermediate page and a random key are returned to the user, and the user searches for the routing key of the native page from the mapping relationship in the local cache according to the random key, and jumps the H5 intermediate page and the native page according to the routing key of the native page, which can reduce the communication cost of operation and development that supports native routing jump. Operation only needs to pay attention to the jump interface, and development does not need to pay attention to whether the corresponding version of the APP / device meets the jump requirements, thereby optimizing the operation plan.

Description

Technical Field

[0001] The present application relates to the fields of software development and financial technology, and in particular to a method, apparatus, computer device and readable storage medium for customizing native page jump adaptation. Background Art

[0002] In order to provide customers with a good experience, the first-level pages of the APP, such as My, Home, Workbench, etc., are still using native pages. This is especially true for APPs that support functions such as shopping, social networking, interactive games, and resource transfer. When operations are configuring operational touchpoints, when changes are made to native pages or when functions need to be introduced or new products are promoted, it is necessary to jump between H5 pages. If the page is a native page, the operation needs to communicate with the development whether the jump is supported, and the operation needs to know the page routing key, APP / device version information, etc. corresponding to the native page, which increases the cost of communication between development and operations. Summary of the Invention

[0003] The purpose of the embodiments of the present application is to propose a customized native page jump adaptation method, device, computer equipment and readable storage medium, which can reduce the communication costs of operations and development that support native routing jumps. Operations do not need to pay attention to jump links, but only need to pay attention to jump interfaces, and development does not need to pay attention to whether the corresponding version of APP / device meets the jump requirements, thereby optimizing the operation plan.

[0004] In order to solve the above technical problems, the embodiment of the present application provides a customized native page jump adaptation method, which adopts the following technical solutions:

[0005] Receive a mapping relationship between a native page and an operation module sent by a user terminal, wherein the mapping relationship includes a routing key of the native page;

[0006] The mapping relationship is delivered to the user terminal for local caching, and the mapping relationship is matched with the version information of the user terminal and then stored in the backend;

[0007] Receive a request from the user terminal to access the APP operation module;

[0008] An H5 intermediate page and a random key are returned to the user terminal, so that the user terminal searches for the routing key of the native page from the mapping relationship in the local cache according to the random key, and jumps between the H5 intermediate page and the native page according to the routing key of the native page.

[0009] Furthermore, the step of delivering the mapping relationship to the user terminal for local caching includes:

[0010] According to different card configurations of the native page, the mapping relationship is delivered to the user terminal through active access or message push for local caching.

[0011] Furthermore, the H5 intermediate page and the native page are redirected via a bridge method.

[0012] Furthermore, the step of redirecting the H5 intermediate page and the native page according to the routing key of the native page specifically includes:

[0013] Intercept the H5 intermediate page and random key through the backend interceptor interface;

[0014] Searching for the routing key of the native page and the version information of the user terminal stored in the backend according to the random key;

[0015] Convert the H5 intermediate page and native page based on the version information of the user terminal.

[0016] Furthermore, the mapping relationship between the native page and the operation module is generated by carding the native page of the APP operation module.

[0017] Furthermore, the interceptor obtains the native routing key through backend interaction for redirection.

[0018] In order to solve the above technical problems, the embodiment of the present application further provides a customized native page jump adaptation device, including:

[0019] A first receiving module is configured to receive a mapping relationship between a native page and an operation module sent by a user terminal, wherein the mapping relationship includes a routing key of the native page;

[0020] A reaching and storage module, configured to reach the mapping relationship to the user terminal for local caching, and to match the mapping relationship with the version information of the user terminal and store it in the backend;

[0021] The second receiving module is used to receive a request from a user to access the APP operation module;

[0022] The search and jump module is used to return an H5 intermediate page and a random key to the user terminal, so that the user terminal can search the routing key of the native page from the mapping relationship of the local cache according to the random key, and jump between the H5 intermediate page and the native page according to the routing key of the native page.

[0023] Furthermore, the search and jump module 404 includes:

[0024] An interception submodule, configured to intercept the H5 intermediate page and random key through the backend interceptor interface;

[0025] A search submodule, configured to search the routing key of the native page and the version information of the user terminal stored in the backend according to the random key;

[0026] The conversion submodule is used to convert the H5 intermediate page and the native page according to the version information of the user terminal.

[0027] In order to solve the above technical problems, the embodiment of the present application further provides a computer device, which adopts the following technical solution:

[0028] The computer device includes a memory and a processor, the memory stores computer-readable instructions, and the processor implements the steps of the customized native page jump adaptation method when executing the computer-readable instructions.

[0029] In order to solve the above technical problems, the embodiment of the present application further provides a computer-readable storage medium, which adopts the following technical solution:

[0030] The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the customized native page jump adaptation method.

[0031] Compared with the existing technology, the embodiments of the present application have the following main beneficial effects: the present application configures the native page of the APP operation module into a card, generates a mapping relationship between the native page and the operation module including the routing key of the native page, delivers the mapping relationship to the user terminal for local caching, and matches the mapping relationship with the version information of the user terminal and stores it in the back end; after receiving the user's request to access the APP operation module, an H5 intermediate page and a random key are returned to the user. The user searches for the routing key of the native page from the mapping relationship in the local cache according to the random key, and jumps to the H5 intermediate page and the native page according to the routing key of the native page, which can reduce the communication cost of operation and development that supports native routing jumps. Operations do not need to pay attention to jump links, but only need to pay attention to jump interfaces, and development does not need to pay attention to whether the corresponding version of APP / device meets the jump requirements, thereby optimizing the operation plan. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the solutions in this application, a brief introduction will be given below to the drawings required for use in the description of the embodiments of this application. Obviously, the drawings described below are some embodiments of this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0033] Figure 1is an exemplary system architecture diagram to which the present application may be applied;

[0034] Figure 2 This is a flowchart of an embodiment of a custom native page jump adaptation method according to the present application;

[0035] Figure 3 This is a flowchart of the steps of redirecting the H5 intermediate page and the native page according to the routing key of the native page in step 204 of this application;

[0036] Figure 4 This is a structural diagram of an embodiment of a custom native page jump adaptation device according to the present application;

[0037] Figure 5 It is a structural diagram of an embodiment of a computer device according to the present application. DETAILED DESCRIPTION

[0038] Unless otherwise defined, all technical and scientific terms used herein have the same meanings as commonly understood by those skilled in the art to which this application belongs. The terms used in the specification of the application are for the purpose of describing specific embodiments only and are not intended to limit this application. The terms "including" and "having" and any variations thereof in the specification and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusions. The terms "first", "second", etc. in the specification and claims of this application or the above-mentioned drawings are used to distinguish different objects, not to describe a specific order.

[0039] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0040] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings.

[0041] like Figure 1 As shown, system architecture 100 may include terminal devices 101, 102, 103, a network 104, and a server 105. Network 104 is a medium for providing communication links between terminal devices 101, 102, 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables.

[0042] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as web browser applications, shopping applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0043] Terminal devices 101, 102, and 103 can be various electronic devices with display screens and support web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture E custom native page jump adaptation perts Group Audio Layer III, Moving Picture Experts Compression Standard Audio Layer 3), MP4 (Moving Picture E custom native page jump adaptation perts Group Audio Layer IV, Moving Picture Experts Compression Standard Audio Layer 4) players, laptop computers and desktop computers, etc.

[0044] The server 105 may be a server that provides various services, such as a background server that provides support for web pages displayed on the terminal devices 101 , 102 , and 103 .

[0045] It should be noted that the customized native page jump adaptation method provided in the embodiment of the present application is generally executed by a server / terminal device, and accordingly, the customized native page jump adaptation device is generally set in the server / terminal device.

[0046] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is merely illustrative. Any number of terminal devices, networks and servers may be provided as required.

[0047] Continue to refer Figure 2 , shows a flow chart of an embodiment of a method for customizing native page jump adaptation according to the present application. The method for customizing native page jump adaptation includes the following steps:

[0048] Step 201 : Card-based configuration is performed on the native page of the APP operation module, and a mapping relationship between the native page and the operation module is generated. The mapping relationship includes a routing key of the native page.

[0049] In this embodiment, the APP may be an application program that supports functions such as shopping, social networking, interactive games, and resource transfer.

[0050] In this embodiment, the native page refers to a page that does not require a network request and is displayed differently depending on the APP version. Correspondingly, the intermediate page of the front-end H5 refers to a page that requires a network request to load and can be modified according to the version and is applicable to all versions of the APP.

[0051] The mapping relationship between the above-mentioned native page and the operation module is generated by configuring the native page of the APP operation module in a card-based configuration. APP operators need to specify the native page corresponding to the jump of the operation module in the operation background, that is, specify the card-based configuration of the jump native page, and configure the mapping relationship between the native page and the operation module. The mapping relationship includes the routing key of the native page, such as the A homepage pop-up configuration -> jump to the learning area of ​​the discovery page. At this time, a mapping relationship of the routing key of the native page -> mapping the learning area of ​​the discovery page is generated; card-based configuration, for example, there is a pop-up box on the homepage, and it is necessary to specify that it jumps to application A after the user clicks it. The operator will map the two cards in the interface, that is, pop-up box A -> application A; for another example, there is a banner on the homepage, and it is necessary to specify that the user jumps to the active H5 page after clicking it. The operator will associate the card banner with the custom H5 link card (activity card) in the interface.

[0052] Step 202: The mapping relationship is delivered to the user terminal for local caching, and the mapping relationship is matched with the version information of the user terminal and then stored in the backend.

[0053] Furthermore, the step of delivering the mapping relationship to the user terminal for local caching includes:

[0054] According to different card configurations of the native page, the mapping relationship is delivered to the user terminal through active access or message push for local caching.

[0055] In this embodiment, the mapping relationship can be reached to the user terminal through active reach or message push according to the different card configurations of the native page by the APP operation module. If it is a pop-up window, it will be actively reached through query after the user logs in. If it is a message push, it will be reached through a scheduled task JOB. Active reach means that when the user logs in to the APP, the corresponding operation content is displayed at the location where it is filtered and screened according to the operation reach conditions for display. The reach of the operation content is queried by the active behavior triggered by the user login; for example, a banner pop-up window is actively triggered after the user logs in, and it is displayed by actively querying whether it meets the display conditions. As for message reach, the reach group is reached through a scheduled task query, and then the message is sent through the group to reach the user. The messages that have been reached will not be recycled due to the removal of the operation content, but the active reach will be recycled. Message push is reached through a scheduled task JOB that regularly queries the configured messages. Then, based on the triggering conditions of the message (what kind of group of people to push to, for example, if it rains in Guangzhou, configure the push content to be sent to 4S stores in Guangzhou), the scheduled task will query the message that needs to be pushed, query the Guangzhou 4S store outlets based on the push conditions, and then refine the outlets to the people, and trigger the message to the people through the message center.

[0056] When the user terminal is reached, the device can find the native corresponding routing key through the mapping relationship between the routing key of the native page->discovery page learning area configuration, and record the routing relationship corresponding to this key to the local cache of the device. At the same time, according to the version number of the user terminal, the routing matching situation is returned to the backend for storage, that is, it is recorded as the version number corresponding to the native interface routing key relationship, for example: appVersion>=2.1.0->discovery page learning area (find_dock_learn) is stored in the backend, so that it can be directly adapted and converted when the jump link of the page returns.

[0057] Step 203: Receive a user's request to access the APP operation module and return an H5 intermediate page and a random key to the user.

[0058] In this embodiment, the electronic device (eg Figure 1 The server / terminal device shown in the figure can receive a user's request to access the APP operation module via a wired connection or a wireless connection and return an H5 intermediate page and a random key to the user. It should be noted that the above-mentioned wireless connection methods may include but are not limited to 3G / 4G / 5G connections, WiFi connections, Bluetooth connections, WiMAX connections, Zigbee connections, UWB (ultra wideband) connections, and other wireless connection methods currently known or developed in the future.

[0059] Receive a user's request to access the APP operation module and return a H5+random key jump link to the user based on the module requested. The H5 link is an intermediate page. The H5 and native jumps are performed through the native routing key in the local device cache. Indirect jumps can be performed through the bridge method.

[0060] In step 204, the user searches for the routing key of the native page from the mapping relationship in the local cache according to the random key, and jumps between the H5 intermediate page and the native page according to the routing key of the native page.

[0061] In this embodiment, each native jump card corresponds to a native routing key, and the native page needs to use this routing key to find the corresponding page. When configuring the operation content, the operation generates a key when making the card configuration. This key is the key that identifies the intermediate page to which the H5 link jumps. When it is provided to H5 for native jump, it is passed to the native page. The native page then uses the random key value of H5 to find the native page corresponding to the key stored in the local device. Therefore, the user clicks -> H5 intermediate page + random key -> random key is given to the native page. The native page then jumps to the corresponding native page through the relationship between the locally stored random key and the native page key.

[0062] The relationship between the random key and the native page key is transparently transmitted to the user terminal. There are two ways:

[0063] When the user logs in, the key mapping relationship is provided with an interface to refresh to the user's local device when the user is idle (after actions such as swiping to log in);

[0064] Message transparent transmission, that is, after the operation change selection is triggered, the message parameters added in the message center are transparently transmitted, that is, when the device-related information is cached and sent to the user at a regular interval, the key corresponding relationship is transparently transmitted and stored by the native.

[0065] The process is that after the user clicks on the content of the operation position, they will be redirected to an intermediate page. This intermediate page is an H5 page with a random key parameter. H5 passes the random key to the native page. The native page finds the corresponding native key by looking for the mapping relationship of the key pushed by the backend, and then jumps.

[0066] Further, such as Figure 3 As shown, in the above step 204, the steps of redirecting the H5 intermediate page and the native page according to the routing key of the native page specifically include:

[0067] Step 301: intercept the H5 intermediate page and random key through the backend interceptor interface;

[0068] Step 302: searching the routing key of the native page and the version information of the user terminal stored in the backend according to the random key;

[0069] Step 303: Convert the H5 intermediate page and the native page according to the version information of the user terminal.

[0070] In this embodiment, when a user accesses the APP operation module, the back-end interceptor interface uniformly intercepts the access request, intercepts the H5 intermediate page and the random key, and then searches for the user terminal version number and the corresponding native page routing key stored in the back-end according to the random key to convert the return jump link. At the unified interceptor of the back-end operation module, the return link hit relationship and the APP / device version number are converted into the corresponding native jump route, and processed according to the APP / device version number. If it is lower than the version number, the H5 link is returned to prompt the user to upgrade. If it is greater than or equal to the version number, the corresponding native route jump is returned to the APP user with the native routing key.

[0071] Specifically, you can jump by obtaining the native routing key through back-end interaction, rather than through the native routing key stored locally on the device. The interceptor performs a back-end native key query on the middle page of H5. There is a place here for dynamic pilot testing. For example, when people in some local areas want to jump to other applications or display different pages, they can switch the back-end and perform link conversion through configuration. The back-end returns through the interface for link adaptation. For example, to jump to a native interface, this key needs to be above version 2.15.0 to be displayed. If the user's APP version is 2.0.0 and has not been upgraded, then the interface displayed should be an upgrade reminder interface, otherwise the user will not be able to participate in the event, etc.

[0072] In summary, the embodiment of the present invention configures the native page of the APP operation module into a card, generates a mapping relationship between the native page and the operation module including the routing key of the native page, delivers the mapping relationship to the user terminal for local caching, and matches the mapping relationship with the version information of the user terminal and stores it in the back end; after receiving the user's request to access the APP operation module, an H5 intermediate page and a random key are returned to the user, and the user searches for the routing key of the native page from the mapping relationship in the local cache according to the random key, and jumps the H5 intermediate page and the native page according to the routing key of the native page, which can reduce the communication cost of operation and development that supports native routing jumps. Operations do not need to pay attention to jump links, but only need to pay attention to jump interfaces, and development does not need to pay attention to whether the corresponding version of the APP / device meets the jump requirements, thereby optimizing the operation plan.

[0073] The embodiments of the present application can acquire and process relevant data based on artificial intelligence technology. Artificial Intelligence (AI) is the theory, method, technology, and application system that uses digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use knowledge to achieve optimal results.

[0074] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing related hardware via computer-readable instructions. The computer-readable instructions can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes in the above-described method embodiments. The aforementioned storage medium can be a non-volatile storage medium such as a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0075] It should be understood that although the steps in the flowcharts of the accompanying drawings are shown in sequence as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the flowcharts of the accompanying drawings may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0076] Further references Figure 4 , as a response to the above Figure 2 The present application provides an embodiment of a custom native page jump adaptation device. Figure 2 Corresponding to the method embodiment shown, the device can be specifically applied to various electronic devices.

[0077] like Figure 4 As shown, the customized native page jump adaptation device 400 of this embodiment includes:

[0078] A first receiving module 401 is configured to receive a mapping relationship between a native page and an operation module sent by a user terminal, wherein the mapping relationship includes a routing key of the native page;

[0079] The access and storage module 402 is used to access the mapping relationship to the user terminal for local caching, and match the mapping relationship with the version information of the user terminal and store it in the backend;

[0080] The second receiving module 403 is used to receive a request from a user to access the APP operation module;

[0081] The search and jump module 404 is used to return an H5 intermediate page and a random key to the user terminal, so that the user terminal can search for the routing key of the native page from the mapping relationship of the local cache according to the random key, and jump between the H5 intermediate page and the native page according to the routing key of the native page.

[0082] The search and jump module 404 includes:

[0083] The interception submodule 4041 is used to intercept the H5 intermediate page and the random key through the backend interceptor interface;

[0084] A search submodule 4042 is configured to search the routing key of the native page and the version information of the user terminal stored in the backend according to the random key;

[0085] The conversion submodule 4043 is used to convert the H5 intermediate page and the native page according to the version information of the user terminal.

[0086] To solve the above technical problems, the present application also provides a computer device. Figure 5 , Figure 5 This is a basic structural block diagram of the computer device in this embodiment.

[0087] The computer device 5 includes a memory 51, a processor 52, and a network interface 53 that are interconnected through a system bus. It should be noted that the figure only shows a computer device 5 with components 51-53, but it should be understood that it is not required to implement all the components shown, and more or fewer components can be implemented instead. Among them, those skilled in the art can understand that the computer device here is a device that can automatically perform numerical calculations and / or information processing according to pre-set or stored instructions, and its hardware includes but is not limited to microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), embedded devices, etc.

[0088] The computer device may be a desktop computer, notebook computer, PDA, cloud server, etc. The computer device may interact with the user via a keyboard, mouse, remote control, touchpad, or voice control device.

[0089] The memory 51 includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (e.g., SD, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 51 can be an internal storage unit of the computer device 5, such as the hard disk or memory of the computer device 5. In other embodiments, the memory 51 can also be an external storage device of the computer device 5, such as a plug-in hard disk equipped on the computer device 5, a smart memory card (SMC), a secure digital (SD) card, a flash card, etc. Of course, the memory 51 can also include both the internal storage unit of the computer device 5 and its external storage device. In this embodiment, the memory 51 is generally used to store the operating system and various application software installed on the computer device 5, such as computer-readable instructions for a custom native page jump adaptation method. In addition, the memory 51 can also be used to temporarily store various types of data that have been output or are to be output.

[0090] In some embodiments, the processor 52 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip. The processor 52 is generally used to control the overall operation of the computer device 5. In this embodiment, the processor 52 is used to execute computer-readable instructions or process data stored in the memory 51, such as computer-readable instructions for executing the custom native page jump adaptation method.

[0091] The network interface 53 may include a wireless network interface or a wired network interface. The network interface 53 is generally used to establish a communication connection between the computer device 5 and other electronic devices.

[0092] The present application also provides another embodiment, namely, providing a computer-readable storage medium, which stores computer-readable instructions, and the computer-readable instructions can be executed by at least one processor to enable the at least one processor to perform the steps of the above-mentioned custom native page jump adaptation method.

[0093] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0094] Obviously, the embodiments described above are only some of the embodiments of the present application, rather than all of the embodiments. The preferred embodiments of the present application are given in the accompanying drawings, but they do not limit the patent scope of the present application. The present application can be implemented in many different forms. On the contrary, the purpose of providing these embodiments is to make the understanding of the disclosure of the present application more thorough and comprehensive. Although the present application has been described in detail with reference to the aforementioned embodiments, for those skilled in the art, it is still possible to modify the technical solutions described in the aforementioned specific embodiments, or to make equivalent replacements for some of the technical features therein. Any equivalent structure made using the contents of the present application specification and the accompanying drawings, directly or indirectly used in other related technical fields, is also within the scope of patent protection of the present application.

Claims

1. A custom native page jump adaptation method, characterized in that: The steps include: Receive a mapping relationship between a native page and an operation module sent by a user terminal, wherein the mapping relationship includes a routing key of the native page, and the mapping relationship between the native page and the operation module is generated by carding the native page of the APP operation module; The mapping relationship is delivered to the user terminal for local caching, and the mapping relationship is matched with the version information of the user terminal and then stored in the backend; Receive a request from the user terminal to access the APP operation module; Returning an H5 intermediate page and a random key to the user terminal, so that the user terminal can search the routing key of the native page from the mapping relationship in the local cache according to the random key, and jump between the H5 intermediate page and the native page according to the routing key of the native page; The step of redirecting the H5 intermediate page and the native page according to the routing key of the native page specifically includes: Intercept the H5 intermediate page and random key through the backend interceptor interface; Searching for the routing key of the native page and the version information of the user terminal stored in the backend according to the random key; Convert the H5 intermediate page and native page based on the version information of the user terminal.

2. The method for customizing native page jump adaptation according to claim 1, characterized in that: The step of delivering the mapping relationship to the user terminal for local caching includes: According to different card configurations of the native page, the mapping relationship is delivered to the user terminal through active access or message push for local caching.

3. The method for customizing native page jump adaptation according to claim 2, characterized in that: The H5 intermediate page and the native page are redirected via a bridge method.

4. The method for customizing native page jump adaptation according to claim 1, characterized in that: The interceptor obtains the native routing key through backend interaction for jump.

5. A custom native page jump adaptation device, characterized in that: include: A configuration and generation module, configured to configure the native page of the APP operation module in a card-based manner and generate a mapping relationship between the native page and the operation module, wherein the mapping relationship includes the routing key of the native page. The mapping relationship between the native page and the operation module is generated by configuring the native page of the APP operation module in a card-based manner; A reaching and storage module, configured to reach the mapping relationship to the user terminal for local caching, and to match the mapping relationship with the version information of the user terminal and store it in the backend; The receiving and returning module is used to receive user requests to access the APP operation module and return an H5 intermediate page and a random key to the user; The search and jump module is used for the user to search the routing key of the native page from the mapping relationship of the local cache according to the random key, and jump between the H5 intermediate page and the native page according to the routing key of the native page; The search and jump module includes: an interception submodule, a search submodule and a conversion submodule, wherein: The interception submodule is used to intercept the H5 intermediate page and random key through the back-end interceptor interface; The search submodule is used to search the routing key of the native page and the version information of the user terminal stored in the backend according to the random key; The conversion submodule is used to convert the H5 intermediate page and the native page according to the version information of the user terminal.

6. The customized native page jump adaptation device according to claim 5, characterized in that: The search and jump module includes: An interception submodule, configured to intercept the H5 intermediate page and random key through the backend interceptor interface; A search submodule, configured to search the routing key of the native page and the version information of the user terminal stored in the backend according to the random key; The conversion submodule is used to convert the H5 intermediate page and the native page according to the version information of the user terminal.

7. A computer device comprising a memory and a processor, wherein the memory stores computer-readable instructions, and the processor implements the steps of the customized native page jump adaptation method according to any one of claims 1 to 4 when executing the computer-readable instructions.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the customized native page jump adaptation method according to any one of claims 1 to 4.

Images