Protocol-based routing hopping method and device, electronic equipment and storage medium

Abstract

The embodiment of the application provides a protocol-based routing jump method and device, electronic equipment and a storage medium, and belongs to the field of data processing. The method comprises the following steps: predefining a pseudo-link routing protocol, wherein the pseudo-link routing protocol is used to indicate the correspondence between a target page parameter and a pseudo-protocol jump link; extracting the target page parameter from the target page based on the pseudo-link routing protocol, and obtaining the corresponding pseudo-protocol jump link according to the target page parameter; obtaining a page jump request, wherein the page jump request comprises the pseudo-protocol jump link; and performing jump of the target page according to the pseudo-protocol jump link. The embodiment of the application realizes jump between multiple pages through the pseudo-protocol jump link, unifies the entrance and exit of multiple technology stacks, facilitates unified maintenance and management in the development process, and guarantees the unity and consistency in the version iteration process.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of artificial intelligence, in particular to a protocol-based routing jump method and device, electronic equipment and storage medium. BACKGROUND

[0002] With the increase of business, the number of pages is increasing, and users often need to realize mutual jump between different pages. At present, in the project development process, the jump of the page, which is a basic service, will face the following problems:

[0003] (1) In the mixed APP development of multiple technologies, the use of each technology stack is different, so the way of jumping pages will be very different. If it is not unified, it will cause chaos of pages and difficulty in maintaining business.

[0004] (2) The project development often faces various changes, especially after multiple version iterations, other page jumps will gradually increase. However, the gradually increasing jumps are not uniformly managed, resulting in code logic coupling a large number of business judgments and version compatibility problems, high time and manpower cost of project maintenance.

[0005] (3) In the APP development process, in order to increase the operation activity or interface with other external APP, it will involve the scene of jumping from the Html5 page and external backflow. The existing technology is to develop the whole specific scene, which has single function and poor expansibility. SUMMARY

[0006] The main purpose of the embodiments of the present application is to provide a protocol-based routing jump method and device, electronic equipment and storage medium, which aims to provide a unified external interface protocol, facilitate unified maintenance and management in the development process, and maintain uniformity and consistency in the version iteration process.

[0007] To achieve the above purpose, the first aspect of the embodiments of the present application proposes a protocol-based routing jump method, which comprises:

[0008] Predefining a pseudo-link routing protocol, the pseudo-link routing protocol is used to indicate the corresponding relationship between the target page parameter and the pseudo-protocol jump link;

[0009] Extracting the target page parameter from the target page based on the pseudo-link routing protocol, and obtaining the corresponding pseudo-protocol jump link according to the target page parameter;

[0010] Obtaining a page jump request, the page jump request comprising a pseudo-protocol jump link;

[0011] Jumping to the target page according to the pseudo-protocol jump link.

[0012] In some embodiments, the pseudo-link routing protocol comprises: a general jump pseudo-protocol identification string, a preset string, a protocol string and a path string;

[0013] The jump to the target page according to the pseudo-protocol jump link comprises:

[0014] According to the general jump pseudo-protocol identification string, the identity of the pseudo-protocol jump link is determined;

[0015] According to the preset string, the adaptive protocol is determined;

[0016] According to the protocol string, the page type of the target page is determined;

[0017] According to the path string, the page path information of the target page is determined;

[0018] According to the identity of the pseudo-protocol jump link, the adaptive protocol, the page type of the target page and the page path information of the target page, the jump to the target page is performed.

[0019] In some embodiments, the page type comprises a native page type, the native page type comprises a first native page type and a second native page type, the first native page type is defined as a native page carrying a page number, and the second native page type is defined as a native page not carrying a page number,

[0020] If the page type is a native page type, the jump to the target page according to the pseudo-protocol jump link comprises:

[0021] It is judged whether the native page type of the target page is the first native page type or the second native page type;

[0022] If the native page type of the target page is the second native page type, the target page parameter is obtained from the pseudo-protocol jump link, and the jump to the target page is performed through a backdoor protocol jump mode.

[0023] In some embodiments, the jump to the target page according to the pseudo-protocol jump link further comprises:

[0024] If the native page type of the target page is the first native page type, the jump to the target page is performed through the page number.

[0025] In some embodiments, the specific steps of the backdoor protocol jump mode are:

[0026] Get the corresponding activity class name through the target page parameter, and then get the corresponding uniform jump class through reflection. The uniform jump class is used as the start page parameter for jump.

[0027] Get the corresponding page path information in the path string through the page parameter splicing symbol, get the key-value pair of the corresponding parameter, and store it in a uniform page jump protocol set.

[0028] Create a Bundle object, and put the key-value of the corresponding parameter into the Bundle object from the uniform page jump protocol set.

[0029] Put the encapsulated Bundle object into the start page parameter to complete the page jump.

[0030] In some embodiments, the receiving client sends a page jump request, the page jump request includes a pseudo-protocol jump link, and the target page is jumped according to the pseudo-protocol jump link, specifically including

[0031] Listen to the page jump request sent by the application program;

[0032] When the page jump request is listened to, the pseudo-protocol jump link included in the current page jump request is identified and extracted;

[0033] Parse the pseudo-protocol jump link to obtain the target page parameter,

[0034] According to the target page parameter, the corresponding target page jump method is obtained;

[0035] According to the target page jump method, the target page is jumped.

[0036] In some embodiments, the steps of the target page jump method include:

[0037] Get the start byte and end byte of the target page parameter from the pseudo-link routing protocol by searching for a preset string;

[0038] Get the characters between the start byte and the end byte to obtain the target page parameter;

[0039] According to the end byte, get the path string from the pseudo-link routing protocol;

[0040] According to the page splicing parameter connector, read multiple page splicing parameters from the path string.

[0041] To achieve the above purpose, a second aspect of the embodiment of the present application proposes a protocol-based routing jump device, which comprises:

[0042] The routing protocol module is configured to predefine a pseudo-link routing protocol, and the pseudo-link routing protocol is configured to indicate a correspondence between a target page parameter and a pseudo-protocol jump link.

[0043] The pseudo-link obtaining module is configured to extract the target page parameter from the target page based on the pseudo-link routing protocol, and obtain the corresponding pseudo-protocol jump link according to the target page parameter.

[0044] The receiving module is configured to receive a page jump request sent by a client, and the page jump request comprises the pseudo-protocol jump link.

[0045] The page jump module is configured to jump to the target page according to the pseudo-protocol jump link.

[0046] To achieve the above object, a third aspect of the embodiments of the present application provides an electronic device, which comprises a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for realizing connection communication between the processor and the memory, and the program is executed by the processor to realize the method in the first aspect.

[0047] To achieve the above object, a fourth aspect of the embodiments of the present application provides a storage medium, which is a computer readable storage medium, and is used for computer readable storage, and the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to realize the method in the first aspect.

[0048] The protocol-based routing jump method and device, the electronic device and the storage medium provided by the present application realize the jump between multiple pages through the pseudo-protocol jump link, unify the entrance and exit of multiple technology stacks, facilitate unified maintenance and management in the development process, and ensure the uniformity and consistency in the version iteration process. BRIEF DESCRIPTION OF DRAWINGS

[0049] Figure 1 is a flowchart of the protocol-based routing jump method provided by the embodiments of the present application;

[0050] Figure 2 is a flowchart of step S102 in Figure 1 ​

[0051] Figure 3 is Figure 1 the routine flowchart of step S104 in

[0052] Figure 4 is the flowchart of step S104 when the page type is a native page;

[0053] Figure 5 is Figure 4 the flowchart of the backdoor protocol jump way of step S402 in

[0054] Figure 6 is Figure 1 the flowchart of steps S103 and S104 in

[0055] Figure 7 is Figure 6 the flowchart of step S605 in

[0056] Figure 8 is a structural schematic diagram of the protocol-based route jump device provided by the embodiments of the present application;

[0057] Figure 9 is a hardware structural schematic diagram of the electronic device provided by the embodiments of the present application. DETAILED DESCRIPTION

[0058] In order to make the objects, technical solutions and advantages of the present application clearer, the present application is further described in detail below in combination with the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application, and are not used to limit the present application.

[0059] It should be noted that although the functional modules are divided in the device schematic diagram, and the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a manner different from the module division in the device or the order in the flowchart. The terms "first", "second", etc. in the specification, claims and the above drawings are used to distinguish similar objects, and do not necessarily describe a specific order or sequence.

[0060] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present application belongs. The terms used herein are only for the purpose of describing the embodiments of the present application, and are not intended to limit the present application.

[0061] Moreover, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the

[0062] The block diagrams in the drawings show only the functionality of the features and can not imply any particular physical or architectural arrangement of the devices, systems, or methods. That is, the functionality can be implemented in a single device, in multiple devices, or in a single module or circuit. Also, the functionality can be implemented in hardware, software, or a combination of hardware and software.

[0063] The flow diagrams depicted in the drawings show the functionality of the described embodiments. The flow diagrams can not be a complete description of the functionality of the described embodiments. That is, the described embodiments can include additional functionality that is not depicted in the flow diagrams.

[0064] First, several terms involved in the present application are analyzed:

[0065] Artificial Intelligence (AI): is a new technical science of researching, developing the theory, method, technology and application system for simulating, extending and expanding human intelligence; Artificial intelligence is a branch of computer science, and artificial intelligence tries to understand the essence of intelligence and produce a new intelligent machine that can react in a similar way to human intelligence. The research in this field includes robots, language recognition, image recognition, natural language processing and expert systems. Artificial intelligence can simulate the information process of human consciousness and thinking. Artificial intelligence is also the theory, method, technology and application system of using digital computer or digital computer controlled machine to simulate, extend and expand human intelligence, to perceive the environment, acquire knowledge and use knowledge to obtain the best results.

[0066] HyperText Markup Language 5 (HTML5): is a language description method for building web content. The content seen by the user when using any means to browse the web is originally in HTML format. It is converted into recognizable information in the browser through some technical processing. It is composed of different technologies and has been widely used in the Internet.

[0067] Flutter: Flutter is an open-source UI toolkit by Google that helps developers to build beautiful, natively compiled applications for mobile, web, and desktop from a single codebase.

[0068] React Native: React Native is an open-source cross-platform mobile application development framework published by Facebook.

[0069] With the increase of business, the number of pages is increasing, and users often need to jump between different pages. At present, in the process of project development, the page jump, a basic service, will face the following problems:

[0070] (1) In the mixed APP development of multiple technologies, the use of each technology stack is different, resulting in great differences in the way of jumping pages. If not unified, it will cause chaos in pages and difficulty in maintaining business.

[0071] (2) During project development, various changes are often encountered, especially after multiple version iterations, other page jumps are gradually added. However, the gradually added jumps are not uniformly managed, resulting in code logic coupling of a large number of business judgments and version compatibility problems, high time and labor costs for project maintenance.

[0072] (3) In the process of APP development, in order to increase the operation activities or interface with other external APP, it will involve the scene of jumping from Html5 page and external backflow. The existing technology is to develop the entire specific scene, which has single function and poor expansibility.

[0073] Based on this, the embodiment of the application provides a protocol-based routing jump method and device, electronic equipment and storage medium, aiming to provide a unified external interface protocol, facilitating unified maintenance and management during development, and maintaining uniformity and consistency during version iteration.

[0074] The protocol-based routing jump method and device, electronic equipment and storage medium provided by the application predefine a pseudo-link routing protocol, which is used to indicate the correspondence between target page parameters and pseudo-protocol jump links; extract target page parameters from the target page based on the pseudo-link routing protocol, and obtain the corresponding pseudo-protocol jump link according to the target page parameters; receive the page jump request sent by the client, the page jump request including the pseudo-protocol jump link; and jump to the target page according to the pseudo-protocol jump link. The embodiment of the application realizes the jump between multiple pages through the pseudo-protocol jump link, unifies the entrance and exit of multiple technology stacks, facilitates unified maintenance and management during development, and ensures uniformity and consistency during version iteration.

[0075] The recommendation method and device, the electronic device and the storage medium provided in the embodiments of the present application are described in detail as follows. First, the recommendation method in the embodiments of the present application is described.

[0076] The embodiments of the present application can acquire and process related data based on artificial intelligence technology. Artificial intelligence (AI) is a theory, method, technology and application system for simulating, extending and expanding human intelligence by using a digital computer or a machine controlled by a digital computer, perceiving an environment, acquiring knowledge and using the knowledge to obtain optimal results.

[0077] The basic technologies of artificial intelligence generally include technologies such as sensors, special artificial intelligence chips, cloud computing, distributed storage, big data processing, operation / interaction systems, mechatronics and the like. The software technologies of artificial intelligence mainly include computer vision technology, robot technology, biometric technology, speech processing technology, natural language processing technology and machine learning / deep learning and the like.

[0078] The protocol-based routing jump method provided in the embodiments of the present application relates to the field of artificial intelligence. The protocol-based routing jump method provided in the embodiments of the present application can be applied in a terminal, can be applied in a server end, and can also be software running in the terminal or the server end. In some embodiments, the terminal can be a smart phone, a tablet computer, a notebook computer, a desktop computer or the like; the server end can be configured as an independent physical server, can be configured as a server cluster or a distributed system composed of multiple physical servers, can also be configured as a cloud server providing basic cloud computing services such as cloud service, cloud database, cloud computing, cloud function, cloud storage, network service, cloud communication, middleware service, domain name service, security service, CDN and big data and artificial intelligence platform; and the software can be an application implementing the protocol-based routing jump method, but is not limited to the above forms.

[0079] The application is operable with numerous general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and / or configurations that can be suitable for use with the application include personal computers, server computers, handheld or laptop devices, tablet devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. The application can be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, and the like, that perform particular tasks or implement particular abstract data types. The application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in local and remote computer storage media including memory storage devices.

[0080] Figure 1 is an optional flowchart of a protocol-based route hopping method provided by an embodiment of the application, Figure 1 The method in the above embodiment can include, but is not limited to, steps S101 to S104.

[0081] In step S101, a pseudo-link route protocol is predefined, which is used to indicate the correspondence between a target page parameter and a pseudo-protocol hopping link.

[0082] It should be understood that the pseudo-link route protocol is a general hopping protocol designed by unified preset rules, and the page hopping is implemented by the pseudo-protocol hopping link, so as to ensure that the entrances of the page hopping are unified. It can be applied to IOS and Android systems, so that the hopping mode between pages in the application does not need to be implemented in advance, and even if the version has been released, the hopping between pages can still be conveniently implemented. For example, the current page includes two virtual keys, the two virtual keys correspond to two pseudo-protocol hopping links, and the two virtual keys can hop to the A page and the B page respectively, so that the target pages in the pseudo-protocol hopping links corresponding to the two virtual keys are the A page and the B page respectively. The pseudo-link route protocol can be used to obtain the pseudo-protocol hopping link corresponding to the target page parameter.

[0083] In step S102, the target page parameter is extracted from the target page based on the pseudo-link route protocol, and the corresponding pseudo-protocol hopping link is obtained according to the target page parameter.

[0084] It should be understood that the target page refers to a page that can be hopped to by the pseudo-protocol hopping link, the type of the target page parameter is determined according to the pseudo-link route protocol, and the target page parameter refers to a target page identifier, a target page address, etc. When the hopping page needs to pass parameters, the target page parameter also includes a page splicing parameter.

[0085] In step S103, a page jump request is acquired, and the page jump request includes a pseudo-protocol jump link.

[0086] It should be understood that the execution subject of the present application can be a page jump processing device, and can also be a terminal or a server, and the specific implementation is not limited herein. The server is taken as an example for description in the embodiments of the present application.

[0087] In the embodiments of the present application, the server specifically refers to a background server of a preset function module, and the preset function module specifically refers to a module with certain specific software functions, such as a push module, a mobile payment module, an image recognition module, a voice recognition module, etc. Under the trend of Internet openness, the function module can be made into a software development kit (SDK), and the application program integrates the SDK, so that the software function corresponding to the function module can be used.

[0088] For example, a page jump request sent by a client is received, and the page jump request includes a pseudo-protocol jump link.

[0089] The client herein refers to an application program on a terminal device that can send request information to a routing server, and the application program is also called APP, which can run in Android, IOS or other similar systems. The page jump request is a request for page jump, which can be triggered by starting an application to open a homepage or by clicking a key in a certain page to jump to a target page. The pseudo-protocol jump link refers to the pseudo-protocol jump link obtained in step S102.

[0090] In step S104, the target page is jumped according to the pseudo-protocol jump link.

[0091] It should be understood that the jump method of the corresponding target page can be obtained according to the pseudo-protocol jump link, and then the jump method is used to jump to the corresponding target page. The jump method can be a conventional URL link jump method or a self-defined jump method.

[0092] The embodiments of the present application realize the jump between multiple pages through the pseudo-protocol jump link, unify the entrances and exits of multiple technology stacks, facilitate the unified maintenance and management in the development process, and ensure the uniformity and consistency in the version iteration process.

[0093] It should be noted that the pseudo-link routing protocol in step S101 specifically includes a general jump pseudo-protocol identification string, a preset string, a protocol string and a path string.

[0094] Exemplarily, the function of the universal jump pseudo-protocol identification string in the embodiment of the present application is to identify whether the link is a pseudo-protocol jump link, and the universal jump pseudo-protocol identification string can be represented as https: / / esales-local / ask_bob#visit?.

[0095] The function of the preset string in the embodiment of the present application is to adapt to read the corresponding protocol, and the preset string can be represented as jumpUrl.

[0096] The function of the protocol string in the embodiment of the present application is to represent the page type of the target page, and the page type value is the type of the technology stack adopted by the page. Exemplarily, the embodiment of the present application specifies four page types for the business scenario, including a native page, an HTML5 page, a Flutter page and a React Native page. The native page refers to the native page of the system, such as an IOS system, an Android system or other systems. Exemplarily, the protocol string of the native page can be represented as aipage: / / ; the protocol string of the HTML5 page can be represented as http: / / or https: / / ; the protocol string of the Flutter page can be represented as flutter: / / ; and the protocol string of the React Native page can be represented as pai: / / .

[0097] It should be understood that the above is only described for specific examples, and these examples only facilitate the description and do not form any limitation on the protection scope of the present disclosure. The page types of the present disclosure, and the specific representations of the page type corresponding protocol strings, can be extended in any way. Any existing or newly developed page type can be implemented by the technical solution of the present disclosure, and the protocol string corresponding to each page type can be set or modified as needed.

[0098] The function of the path string in the embodiment of the present application is to provide the page path information of the target page, such as 1001&name=zhuanli in the native page, www.baidu.com in the HTML5 page, pages / index / index in the Flutter page, and redpacket / practiceResult in the React Native page.

[0099] It should be understood that the developer can determine the target jump parameters to be obtained according to the pseudo-link routing protocol, so that the target page parameters are extracted from the target page based on the pseudo-link routing protocol in step S102, and the corresponding pseudo-protocol jump link is obtained according to the target page parameters, as shown in Figure 2 , which specifically includes the following steps:

[0100] Step S201, extracting a target page parameter from a target page, the target page parameter including a page type and page path information of the target page;

[0101] Step S202, obtaining a corresponding protocol string according to the page type, bringing in a path string according to the page path information, and then combining a general jump pseudo-protocol identification string and a preset string to generate a pseudo-protocol jump link of the corresponding page.

[0102] It should be understood that the general jump pseudo-protocol identification string and the preset string in the pseudo-link routing protocol are uniform strings predefined by the developer, and are irrelevant to the target page parameter. The general jump pseudo-protocol identification string and the preset string are the same for different target pages, while the protocol string and the path string are related to the target page and need to be obtained through the target page parameter.

[0103] It should be understood that the pseudo-protocol jump link in the embodiment of the application is composed of a general jump pseudo-protocol identification string + a preset string + a protocol string + a path string, that is, https: / / esales-local / ask_bob#visit?+jumpUrl=+page type+page path.

[0104] For example, when the page type is a native page, the pseudo-protocol jump link can be represented as https: / / esales-local / ask_bob#visit?jumpUrl=aipage: / / 1001&name=zhuanli. It should be noted that the native page here is a page for which a corresponding page number is defined in advance, and 1001 in the path string is the page number.

[0105] For example, when the page type is an HTML5 page, the pseudo-protocol jump link can be represented as https: / / esales-local / ask_bob#visit?jumpUrl=https: / / xxxxxxxx.

[0106] For example, when the page type is a Flutter page, the pseudo-protocol jump link can be represented as https: / / esales-local / ask_bob#visit?jumpUrl=flutter: / / pages / index / index

[0107] For example, when the page type is a ReactNative page, the pseudo-protocol jump link can be represented as https: / / esales-local / ask_bob#visit?jumpUrl=pai: / / redpacket / practiceResult.

[0108] It should be understood that the above is only described for specific examples, which are only for convenience of illustration and do not form any limitation on the protection scope of the present disclosure. The pseudo-protocol jump link of the present disclosure can be extended, and any existing or newly developed pseudo-protocol jump link can be implemented by the technical solution of the present disclosure.

[0109] It should be noted that the jump to the target page according to the pseudo-protocol jump link in step S104 is described with reference to Figure 3 , which specifically includes the following steps:

[0110] Step S301: determining the identity of the pseudo-protocol jump link according to the general jump pseudo-protocol identification string;

[0111] It should be understood that in addition to the https: / / esales-local / ask_bob#visit?above representing the general jump pseudo-protocol identification string, a person skilled in the art can customize the format and content of the general jump pseudo-protocol identification string as needed, and the general jump pseudo-protocol identification string of all pseudo-protocol jump links is the same, so once it is identified that the current link contains the general jump pseudo-protocol identification string, it can be determined that the link is a pseudo-protocol jump link.

[0112] Step S302: determining the adaptation protocol according to the preset string;

[0113] It should be understood that the preset string is a string pre-set by the terminal, and the adaptation protocol of the pseudo-protocol jump link is determined according to the preset string, and the preset string of all pseudo-protocol jump links is the same.

[0114] Step S303: determining the page type of the target page according to the protocol string;

[0115] It should be understood that different protocol strings correspond to a page type, that is, the type of the technology stack adopted by the target page, and the corresponding target page jump method can be determined and selected through the page type. In the present embodiment, the protocol string definitions of four page types are given, and a person skilled in the art should understand that in the future development of front-end technology, developers can add corresponding protocol strings according to newly added page types to adapt to more technology stacks.

[0116] Step S304, determining the page path information of the target page according to the path string;

[0117] It should be understood that the page path information is a key parameter in the target page jump method, so after the target page jump method corresponding to the page type is determined in step S303, the page path information of the target page needs to be determined through the path string.

[0118] Step S305, jumping to the target page according to the identity recognition of the pseudo-protocol jump link, the adaptive protocol, the page type of the target page and the page path information of the target page.

[0119] It should be understood that first, the current link is determined to be a pseudo-protocol jump link through the general jump pseudo-protocol identification string, and then the page type of the target page is determined through the adaptive protocol, so as to obtain the corresponding target page jump method, and finally the target page jump method is executed according to the page path information to complete the jump of the target page.

[0120] It should be noted that in some embodiments, the native page type is divided into two types according to the difference of the target page jump method, including a first native page type and a second native page type, the first native page type is defined as a native page carrying a page number, and the second native page type is defined as a native page not carrying a page number.

[0121] It should be understood that the native page carrying the page number refers to the native page with the corresponding page number defined in advance, and the native page not carrying the page number refers to all native pages without the page number except the first native page type.

[0122] Reference Figure 4 As shown in FIG. 1, when the page type is a native page, step S104 jumps to the target page according to the pseudo-protocol jump link, specifically including:

[0123] S401, judging whether the native page type of the target page is the first native page type or the second native page type;

[0124] It should be noted that the native page type is confirmed through the protocol string, and in the embodiment of the application, the protocol string of the first native page type is defined as aipage: / / , and the protocol string of the second native page type is defined as native: / / .

[0125] For example, a pseudo-protocol jump link of the first native page type can be represented as https: / / esales-local / ask_bob#visit?jumpUrl=aipage: / / 1001&name=zhuanli, wherein 1001 in the path string is the page number.

[0126] For example, a pseudo-protocol jump link for a second native page type can be represented as https: / / esales-local / ask_bob#visit?jumpUrl=native: / / iOSName=KDEAISellGroundViewController&androidName=xxxx.

[0127] S402, If the native page type of the target page is the second native page type, then obtain the target page parameters from the pseudo protocol redirection link and redirect the target page through the backdoor protocol redirection method;

[0128] It should be understandable that when the protocol string in the pseudo-protocol redirect link is native: / / , the current target page is considered to be a second native page type. In this case, it is not possible to directly redirect to the target page by page number. Instead, a backdoor protocol redirection method is required. To implement the backdoor protocol redirection method, the target page parameters need to be obtained from the pseudo-protocol redirect link. The target page parameters are usually obtained from the path string.

[0129] In some embodiments, redirecting to the target page based on a pseudo-protocol redirect link further includes:

[0130] S403, if the target page's native page type is the first native page type, then redirect to the target page using the page number.

[0131] It should be noted that when the native page type of the target page is the first native page type, it means that the target page is a native page with a predefined corresponding page number. You can directly jump to the target page by page number. Just like HTML5 pages, Flutter pages, and React Native pages, you do not need to reserve the corresponding page in advance to achieve the jump.

[0132] It should be noted that the reference Figure 5 As shown, the specific steps of the backdoor protocol jump method in step S402 are as follows:

[0133] Step S501: Obtain the corresponding activity class name through the target page parameters, then obtain the corresponding unified jump class through reflection, and use the unified jump class as the startup page parameter for jump;

[0134] Step S502: Obtain the corresponding page path information from the path string by using the page parameter concatenation operator, obtain the key-value pairs of the corresponding parameters, and store them in a unified page redirection protocol set;

[0135] Step S503, create a Bundle object, take out the corresponding field from the uniform page jump protocol set, and put the key value of the corresponding parameter into the Bundle object;

[0136] Step S504, put the packaged Bundle object into the start page parameter to complete the page jump.

[0137] Exemplary, a pseudo-protocol jump link of the second native page type is https: / / esales-local / ask_bob#visit?jumpUrl=native: / / iOSName=KDEAISellGroundViewController&androidName=xxxx, we define IOSName to map to the corresponding ViewController, and AndroidName to map to the corresponding Android page. The following describes the specific implementation of the backdoor protocol jump method using the Android end as an example:

[0138] Exemplary, in step S501, the corresponding activity class name is obtained through the target page parameter, and then the corresponding uniform jump class is obtained through reflection, and the uniform jump class is used as the start page parameter for jump. Specifically:

[0139] The corresponding Activity class name is obtained through AndroidName, and then the corresponding class class is obtained through reflection, which is used as the parameter of intent for jump;

[0140] Exemplary, in step S502, the corresponding page path information is obtained through the page parameter concatenator in the path string, and the key value pair of the corresponding parameter is obtained and stored in a uniform page jump protocol set. Specifically:

[0141] The parameters in the path string are concatenated by the "&" symbol, and the corresponding page path information Url is obtained through the page parameter concatenator "&", and the key value pair of the corresponding parameter is obtained and stored in a Map set;

[0142] Exemplary, in step S503, a Bundle object is created, and the corresponding field is taken out from the uniform page jump protocol set to put the key value of the corresponding parameter into the Bundle object. Specifically:

[0143] A Bundle object is created, and the corresponding field is taken out from the Map set to put the corresponding parameter into the Bundle object through the put method of the Bundle object;

[0144] For example, the packaged Bundle object is put into the start page parameter in step S504 to complete the page jump, specifically:

[0145] The packaged Bundle object is put into the Intent, and the context.startActivity is called to pass in the corresponding class and the Intent object to complete the page jump.

[0146] It should be noted that, as shown in Figure 6 The page jump request sent by the client is received in step S103, and the page jump request includes a pseudo-protocol jump link; in step S104, the target page is jumped according to the pseudo-protocol jump link, specifically including

[0147] In step S601, the page jump request sent by the application is listened to;

[0148] It should be understood that the application is various applications, also known as APP, which can run in Android, IOS or other similar systems, such as WeChat, Weibo, etc. The page jump request is a request for page jump, which can be triggered by opening a home page when starting the application to jump to the home page or clicking a key in a certain page to jump to the target page. The way to listen to the page jump request of the first application can be customized, and in an embodiment, a unified class can be provided, which is a unified jump class. The onclick method in the application program is implemented by listening to the class, which means that the element is clicked, that is, a certain button is clicked to perform the corresponding operation. Listening to the page jump request of the application program means listening to whether the page jump request of the application program occurs. In an embodiment, the system's built-in listening method is used to listen to the page jump request of the application program.

[0149] In step S602, when the page jump request is listened to, the pseudo-protocol jump link included in the current page jump request is recognized and extracted;

[0150] It should be understood that when the page jump request is monitored, that is, when the onclick method needs to be executed, that is, when the current page jump request is monitored. The pseudo-protocol jump link is the pseudo-protocol jump link of the corresponding target page obtained by the pseudo-link routing protocol in step S102. Through the pseudo-protocol jump link, the entry of each technology stack can be unified. For example, the current page includes three virtual keys, and the three virtual keys correspond to three page jump requests, and each page jump request corresponds to a pseudo-protocol jump link. For example, the three virtual keys can jump to A page, B page and C page respectively, and the target pages corresponding to the pseudo-protocol jump links of the three virtual keys are A page, B page and C page respectively. The pseudo-protocol jump link corresponding to each virtual key can be found through the page jump request.

[0151] In step S603, the target page parameters are obtained by analyzing the pseudo-protocol jump link.

[0152] It should be understood that the target page parameters refer to the page type and page path information related to the target page, that is, the protocol string and the path string are obtained through the pseudo-protocol jump link, the page type of the target page is obtained by reading the protocol string, and the page path information of the target page is obtained by reading the path string. When the path string needs to pass parameters, the page jump parameters also include page parameter splicing symbols.

[0153] In step S604, the corresponding target page jump method is obtained according to the target page parameters.

[0154] It should be noted that the corresponding target page jump method can be obtained according to the target page jump parameters. The target page jump method is a specific method for implementing target page jump. The target page jump method can generate a corresponding target page resource acquisition request. The target page resource acquisition request is a request for obtaining target page resources. The target page resource acquisition request is sent to the server to obtain the target page resources. The target page resources include the display file corresponding to the target page, so that the target page resources can be parsed to jump and display the target page.

[0155] In step S605, the target page jump method is used to jump to the target page.

[0156] It should be understood that when the target page resource acquisition request corresponds to the target page resource in the local, the target page resource can also be obtained from the local to quickly jump to and display the target page.

[0157] It should be noted that, as shown in Figure 7 The steps of the target page jump method in step S605 include:

[0158] Step S701, obtaining the start byte and the end byte of the target page parameter from the pseudo link routing protocol by searching for a preset string;

[0159] It should be understood that the preset string is a string pre-set by the terminal, and the start byte and the end byte of the target page parameter are obtained according to the preset string, and the start byte and the end byte are used to obtain the protocol string;

[0160] Step S702, obtaining the target page parameter by obtaining the characters between the start byte and the end byte;

[0161] It should be understood that, taking the pseudo protocol jump link https: / / esales-local / ask_bob#visit?jumpUrl=native: / / iOSName=KDEAISellGroundViewController&androidName=xxxx of the second native page as an example, the preset string is jumpUrl=, the start byte is =, and the end byte is / / .

[0162] Step S703, obtaining the path string from the pseudo link routing protocol according to the end byte;

[0163] It should be understood that the path string is iOSName=KDEAISellGroundViewController&androidName=xxxx after / / in the pseudo protocol jump link.

[0164] Step S704, reading a plurality of page splicing parameters from the path string according to a page splicing parameter connector.

[0165] It should be noted that the page splicing parameter connector is & in the path string, and for the processing of parameters that need to be carried, the present embodiment uses & to splice in the path string of the pseudo protocol jump link, and for complex parameters (for example, containing special characters), a _coparams special parameter value field is used to wrap JSON format, for example, _coparams={"webUrl":"https: / / www.baidu.com"}. For some special characters (such as parameters containing "#" or "&"), urlEncode can be used for encoding and transmission.

[0166] It should be understood that the present embodiment realizes the jump between multiple pages through the pseudo protocol jump link, unifies the entrance and exit of multiple technology stacks, facilitates unified maintenance and management in the development process, and ensures the unity and consistency in the version iteration process.

[0167] It should be understood that although each step in the flowchart involved in the above embodiments is shown in sequence according to the arrow, the steps are not necessarily executed in the order indicated by the arrow. Unless otherwise specified herein, the execution of the steps is not strictly limited in sequence, and the steps can be executed in other orders. Moreover, at least part of the steps in the flowchart involved in the above embodiments can include multiple steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution order of the steps or stages is not necessarily sequential, but can be alternately executed with other steps or steps or stages in other steps.

[0168] The method embodiments provided by the present application are described above, and the device embodiments provided by the present application will be described below. It should be understood that the description of the device embodiments corresponds to the description of the method embodiments, and therefore, the content not described in detail can be referred to the above method embodiments.

[0169] Reference Figure 8 As shown in the figure, the protocol-based routing jump device is an embodiment of the present application, which can implement the above-mentioned protocol-based routing jump method. The device comprises a routing protocol module 801, a pseudo link acquisition module 802, a receiving module 803 and a page jump module 804.

[0170] The routing protocol module 801 is configured to predefine a pseudo link routing protocol, which is used to indicate the correspondence between the target page parameters and the pseudo protocol jump link.

[0171] The pseudo link acquisition module 802 is configured to extract the target page parameters from the target page based on the pseudo link routing protocol, and acquire the corresponding pseudo protocol jump link according to the target page parameters.

[0172] The receiving module 803 is configured to receive the page jump request sent by the client, and the page jump request comprises the pseudo protocol jump link.

[0173] The page jump module 804 is configured to jump to the target page according to the pseudo protocol jump link.

[0174] The protocol-based routing jump device of the embodiment of the present application is used to execute the protocol-based routing jump method in the above-mentioned embodiments, and the specific processing process is the same as the protocol-based routing jump method in the above-mentioned embodiments, which will not be described here.

[0175] The electronic device of another embodiment is illustrated in the hardware structure, and the electronic device includes:

[0176] Please refer to Figure 9 , Figure 9 The electronic device of another embodiment is illustrated in the hardware structure, and the electronic device includes:

[0177] The processor 901 can be implemented in a general-purpose CPU (Central Processing Unit), a microprocessor, an ASIC (Application Specific Integrated Circuit), or one or more integrated circuits, and is configured to execute related programs to implement the technical solutions provided by the embodiments of the present application.

[0178] The memory 902 can be implemented in the form of a ROM (Read Only Memory), a static storage device, a dynamic storage device, or a RAM (Random Access Memory). The memory 902 can store an operating system and other application programs. When the technical solutions provided by the embodiments of the present application are implemented by software or firmware, the related program codes are stored in the memory 902 and are called and executed by the processor 901 to implement the protocol-based routing hopping method of the embodiments of the present application.

[0179] The input / output interface 903 is configured to implement information input and output.

[0180] The communication interface 904 is configured to implement the communication interaction between the device and other devices. The communication can be implemented in a wired manner (for example, USB, network cable, etc.) or in a wireless manner (for example, mobile network, WIFI, Bluetooth, etc.).

[0181] The bus 905 is configured to transmit information between various components (for example, the processor 901, the memory 902, the input / output interface 903, and the communication interface 904) of the device.

[0182] The processor 901, the memory 902, the input / output interface 903, and the communication interface 904 are connected to each other in the device through the bus 905.

[0183] The embodiment of the present application further provides a storage medium, which is a computer readable storage medium, and is used for computer readable storage. The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the protocol-based routing and hopping method.

[0184] The memory, as a non-transitory computer readable storage medium, can be used to store non-transitory software programs and non-transitory computer executable programs. In addition, the memory can include a high-speed random access memory, and can also include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state memory device. In some embodiments, the memory can optionally include a memory remotely arranged relative to the processor, and these remote memories can be connected to the processor through a network. Examples of the above network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0185] The recommendation method, the recommendation device, the electronic equipment and the storage medium provided by the embodiment of the present application are provided. The recommendation method, the recommendation device, the electronic equipment and the storage medium provided by the embodiment of the present application are provided. The pseudo-link routing protocol is used to indicate the correspondence between the target page parameter and the pseudo-protocol jump link; the target page parameter is extracted from the target page based on the pseudo-link routing protocol, and the corresponding pseudo-protocol jump link is obtained according to the target page parameter; receiving the page jump request sent by the client, the page jump request includes the pseudo-protocol jump link; and the target page is jumped according to the pseudo-protocol jump link. The embodiment of the present application realizes the jump between multiple pages through the pseudo-protocol jump link, unifies the entrance and exit of multiple technology stacks, facilitates unified maintenance and management in the development process, and ensures the unity and consistency in the version iteration process.

[0186] The embodiments described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, with the evolution of technology and the appearance of new application scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0187] Those skilled in the art can understand that, Figures 1-7 The technical solutions shown in the foregoing embodiments are not a limitation on the embodiments of the present application, and can include more or fewer steps than those shown in the drawings, or combine certain steps, or different steps.

[0188] The device embodiments described above are only schematic, and the units described as separate components can or can not be physically separate, that is, can be located in one place, or can be distributed on multiple network units. Part or all of the modules can be selected according to actual needs to achieve the purpose of the embodiment solutions.

[0189] Those skilled in the art can understand that all or some of the steps in the method disclosed above, the function modules / units in the system and the device can be implemented as software, firmware, hardware and appropriate combinations thereof.

[0190] The terms "first", "second", "third", "fourth" and the like in the description of the application and in the claims hereof, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the use of the terms so termed is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of orderly or chronological permutations. Moreover, the terms "comprise", "have" and any variations thereof are intended to cover a non-exclusive inclusion, for example, a process, method, article, or apparatus that comprises a list of steps or units can not necessarily be limited to those steps or units, but can include additional steps or units not expressly listed or inherent to such process, method, article, or apparatus.

[0191] It should be understood that, in the present application, "at least one" means one or more, and "multiple" means two or more. "And / or" is used to describe the relationship between associated objects, which means that there can be three relationships, for example, "A and / or B" can mean that there are three cases: only A, only B, and A and B at the same time, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects. "At least one of the following" or similar expressions means any combination of these items, including any combination of single or multiple items. For example, at least one of a, b or c can mean a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0192] In several embodiments provided by the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above-mentioned units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be omitted or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed objects can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0193] The units described as separate components above can or can not be physically separate, and the components shown as units can or can not be physical units, i.e., can be located in one place, or can be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0194] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present alone, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0195] The integrated unit, if realized in the form of a software functional unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application, essentially or the part that contributes to the prior art, or all or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes multiple instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods of the embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program storage media.

[0196] The preferred embodiments of the embodiments of the present application are described above with reference to the accompanying drawings, and the scope of the rights of the embodiments of the present application is not limited thereto. Any modifications, equivalent replacements and improvements made by those skilled in the art without departing from the scope and essence of the embodiments of the present application shall be within the scope of the rights of the embodiments of the present application.

Claims

1. A protocol-based routing hop method, characterized by, The method comprises: predefining a pseudo-link routing protocol, the pseudo-link routing protocol being used to indicate a corresponding relationship between a target page parameter and a pseudo-protocol jump link; extracting the target page parameter from the target page based on the pseudo-link routing protocol, and obtaining the corresponding pseudo-protocol jump link according to the target page parameter; obtaining a page jump request, the page jump request comprising a pseudo-protocol jump link; and jumping to the target page according to the pseudo-protocol jump link; the pseudo-link routing protocol comprises a general jump pseudo-protocol identification string, a preset string, a protocol string and a path string; the jumping to the target page according to the pseudo-protocol jump link comprises: determining the identity of the pseudo-protocol jump link according to the general jump pseudo-protocol identification string; determining an adaptive protocol according to the preset string; determining the page type of the target page according to the protocol string; determining the page path information of the target page according to the path string; obtaining the target page parameter by parsing the pseudo-protocol jump link; obtaining the corresponding target page jump method according to the target page parameter; jumping to the target page according to the identity of the pseudo-protocol jump link, the adaptive protocol, the page type of the target page, the page path information of the target page and the target page jump method.

2. The protocol-based route hopping method of claim 1, wherein, the page type comprises a native page type, the native page type comprising a first native page type and a second native page type, the first native page type being defined as a native page carrying a page number, and the second native page type being defined as a native page not carrying a page number, if the page type is the native page type, the jumping to the target page according to the pseudo-protocol jump link comprises: determining whether the native page type of the target page is the first native page type or the second native page type; if the native page type of the target page is the second native page type, obtaining the target page parameter from the pseudo-protocol jump link and jumping to the target page by a backdoor protocol jump mode.

3. The protocol-based route hopping method of claim 2, wherein, the jumping to the target page according to the pseudo-protocol jump link further comprises: if the native page type of the target page is the first native page type, jumping to the target page by the page number.

4. The protocol-based route hopping method of claim 3, wherein, the specific steps of the backdoor protocol jump mode are: obtaining the corresponding activity class name through the target page parameter, and then obtaining the corresponding uniform jump class through reflection, and taking the uniform jump class as a start page parameter for jump; obtaining the corresponding page path information through a page parameter concatenator in the path string, obtaining the key-value pair of the corresponding parameter, and storing it in a uniform page jump protocol set; creating a Bundle object, taking out the corresponding field from the uniform page jump protocol set, and putting the key-value of the corresponding parameter into the Bundle object; putting the encapsulated Bundle object into the start page parameter to complete the jump of the page.

5. The protocol-based route hopping method of claim 1, wherein, the page jump request further comprises: listening to the page jump request sent by the application program; When a page jump request is monitored, a pseudo-protocol jump link included in the page jump request is identified and extracted.

6. The protocol-based route hopping method of claim 1, wherein, The parsing of the pseudo-protocol jump link obtains the target page parameter, and a corresponding target page jump method is obtained according to the target page parameter, including: The start byte and the end byte of the target page parameter are obtained from the pseudo-link routing protocol by searching for a preset character string; The target page parameter is obtained by reading the characters between the start byte and the end byte; The path string is obtained from the pseudo-link routing protocol according to the end byte; A plurality of page splicing parameters are read from the path string according to a page splicing parameter connector.

7. A protocol-based routing hop device, characterized by The device includes: A routing protocol module, configured to predefine a pseudo-link routing protocol, the pseudo-link routing protocol being used to indicate a corresponding relationship between a target page parameter and a pseudo-protocol jump link; A pseudo-link obtaining module, configured to extract a target page parameter from a target page based on a pseudo-link routing protocol, and obtain a corresponding pseudo-protocol jump link according to the target page parameter; A receiving module, configured to obtain a page jump request, the page jump request including a pseudo-protocol jump link; A page jump module, configured to jump to a target page according to the pseudo-protocol jump link; The pseudo-link routing protocol includes a general jump pseudo-protocol identification string, a preset character string, a protocol string, and a path string. The jumping to the target page according to the pseudo-protocol jump link includes: Determining the identity of the pseudo-protocol jump link according to the general jump pseudo-protocol identification string; Determining an adaptive protocol according to the preset character string; Determining the page type of the target page according to the protocol string; Determining the page path information of the target page according to the path string; Parsing the pseudo-protocol jump link to obtain the target page parameter; Obtaining a corresponding target page jump method according to the target page parameter; Jumping to the target page according to the identity of the pseudo-protocol jump link, the adaptive protocol, the page type of the target page, the page path information of the target page, and the target page jump method.

8. An electronic device, comprising: The electronic device includes a memory, a processor, a program stored on the memory and executable on the processor, and a data bus for realizing connection communication between the processor and the memory, and the program is executed by the processor to realize the steps of the protocol-based routing jump method according to any one of claims 1 to 6.

9. A storage medium, the storage medium being a computer-readable storage medium for computer-readable storage, characterized in that, The storage medium stores one or more programs, which can be executed by one or more processors to realize the steps of the protocol-based routing jump method according to any one of claims 1 to 6.

Images