CN113641940A - Page jumping method, device, system, device and storage medium - Google Patents
Page jumping method, device, system, device and storage medium Download PDFInfo
- Publication number
- CN113641940A CN113641940A CN202111194299.5A CN202111194299A CN113641940A CN 113641940 A CN113641940 A CN 113641940A CN 202111194299 A CN202111194299 A CN 202111194299A CN 113641940 A CN113641940 A CN 113641940A
- Authority
- CN
- China
- Prior art keywords
- page
- parameter
- link
- client
- parameters
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9558—Details of hyperlinks; Management of linked annotations
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
本申请提出一种页面跳转方法、装置、系统、设备及存储介质，该方法包括：服务器根据客户端地址和链接参数，生成待跳转的页面链接，发送该页面链接给目标用户；接收客户端基于页面链接发送的回传参数和链接参数；确定回传参数和链接参数对应的页面导航地址；发送页面导航地址给客户端，使客户端跳转至页面导航地址对应的页面。本申请中客户端获取当前的回传参数，将页面链接透传的链接参数及获取的回传参数发送给服务器，服务器依据回传参数和连接参数确定最终的页面导航地址，实现根据当前的状态确定最终的页面导航地址，大大减少了页面跳转失败的情况，规避了页面跳转的安全风险，降低了客户端因页面跳转失败而崩溃的次数。
The present application proposes a page jumping method, device, system, device and storage medium. The method includes: a server generates a page link to be jumped according to a client address and link parameters, and sends the page link to a target user; Based on the return parameters and link parameters sent by the page link; determine the page navigation address corresponding to the return parameters and link parameters; send the page navigation address to the client, so that the client can jump to the page corresponding to the page navigation address. In this application, the client obtains the current postback parameters, and sends the link parameters of the page link transparent transmission and the acquired postback parameters to the server. The server determines the final page navigation address according to the postback parameters and connection parameters, and realizes that according to the current state Determining the final page navigation address greatly reduces the failure of page jumps, avoids the security risks of page jumps, and reduces the number of client crashes due to page jump failures.
Description
Technical Field
The present application belongs to the technical field of network communication, and in particular, relates to a page jump method, apparatus, system, device, and storage medium.
Background
With the popularization of mobile terminals such as mobile phones and tablet computers, APPs (application programs) running on the mobile terminals are also widely used. The APP often sends some short messages, APP reminding messages or webpage messages and other push messages to the user according to different services, the push messages may include page links, and the user clicks the page links to open corresponding pages in the APP.
In the related art, all page links in the push message are written fixed jump links, and clicking the page links can open fixed pages in the APP. However, the application state, the system state, the user role, and the like corresponding to the fixed page to which the page link in the push message is directed may be different from the current application state, the system state, the user role, and the like of the APP in the mobile terminal, for example, the APP version corresponding to the page link in the push message is different from the APP version on the current mobile terminal. When these disagreements occur, the page link in the push message cannot jump to the corresponding fixed page, and even the APP may crash.
Disclosure of Invention
The application provides a page jump method, a device, a system, equipment and a storage medium, wherein link parameters are carried in a page link pushed to a user, current return parameters and link parameters are obtained from a client, a final page navigation address is determined according to the current state, the page jump failure condition is greatly reduced, the page jump safety risk is avoided, and the collapse frequency of the client due to the page jump failure is reduced.
An embodiment of a first aspect of the present application provides a page jump method, including:
generating a page link to be jumped according to the client address and the link parameter, and sending the page link to a target user;
receiving a return parameter and the link parameter sent by the client based on the page link;
determining a page navigation address corresponding to the return parameter and the link parameter;
and sending the page navigation address to the client so as to enable the client to jump to a page corresponding to the page navigation address.
In some embodiments of the present application, the generating a page link to be skipped according to a client address and a link parameter includes:
determining that a target user currently accords with a preset link pushing condition corresponding to a target service;
acquiring a current scene state parameter and a service parameter of the target service corresponding to the scene state parameter, and taking the scene state parameter and the service parameter as link parameters;
and packaging the client address corresponding to the client to which the target service belongs and the link parameter into a page link to be jumped.
In some embodiments of the present application, the method further comprises:
Acquiring a preset transfer route;
and packaging the preset transfer route, the client address and the link parameter into a page link to be jumped.
In some embodiments of the present application, the determining the page navigation address corresponding to the return parameter and the link parameter includes:
acquiring corresponding routing information according to the return parameters and the link parameters;
and generating a final page navigation address according to the routing information.
In some embodiments of the present application, the obtaining the corresponding routing information according to the backhaul parameter and the link parameter includes:
determining whether a record corresponding to the scene state parameter and the return parameter exists in a mapping relation of the pre-configured scene state parameter, the return parameter and the routing information;
if yes, obtaining the scene state parameter and the routing information corresponding to the return parameter from the record;
and if not, acquiring a preset backing route.
In some embodiments of the present application, the routing information obtained from the record includes a routing address and a parameter key, and the link parameter further includes a service parameter;
Generating a final page navigation address according to the routing information, wherein the generating of the final page navigation address comprises:
acquiring a parameter value corresponding to the parameter key from the service parameter;
and splicing the routing address and the parameter value into a final page navigation address.
In some embodiments of the present application, the context state parameters include context values, and the backhaul parameters include system type and client version number;
the obtaining of the corresponding routing information according to the backhaul parameter and the link parameter includes:
determining whether a record containing the scene value and the system type exists in a mapping relation among a preset scene state parameter, a return parameter and routing information;
if so, acquiring a preset version number from the record, and comparing whether the client version number is consistent with the preset version number;
if the two routing information are consistent, acquiring first routing information from the record, and if the two routing information are not consistent, acquiring second routing information from the record;
and if the record does not exist in the mapping relation or the version comparison process is in error, acquiring a preset bottoming route.
In some embodiments of the present application, the scene state parameter further includes a process type or user identification information, and the obtaining, according to the backhaul parameter and the link parameter, corresponding routing information includes:
Acquiring a user role parameter and/or a service state parameter corresponding to the user identification information;
and acquiring corresponding routing information according to the return parameters, the link parameters, the user role parameters and/or the service state parameters.
An embodiment of a second aspect of the present application provides a page jump method, applied to a client, including:
receiving a page jump request of a target user, wherein the page jump request comprises a link parameter;
acquiring current return parameters, and sending the return parameters and the link parameters to a server;
receiving a page navigation address returned by the server according to the return parameter and the link parameter;
and displaying the page corresponding to the page navigation address.
In some embodiments of the present application, the page jump request further includes a preset relay route; the method further comprises the following steps:
displaying a transfer page according to the preset transfer route;
acquiring the return parameters through the transfer page;
and after receiving the page navigation address, jumping from the transfer page to a page corresponding to the page navigation address.
An embodiment of a third aspect of the present application provides a page jump system, including: a server and a client;
The server is used for generating a page link to be jumped according to the client address and the link parameter and sending the page link to a target user; receiving a return parameter and the link parameter sent by the client based on the page link; determining a page navigation address corresponding to the return parameter and the link parameter; sending the page navigation address to the client;
the client is used for receiving a page jump request of a target user, and the page jump request comprises the link parameter; acquiring current return parameters, and sending the return parameters and the link parameters to a server; receiving a page navigation address returned by the server; and displaying the page corresponding to the page navigation address.
An embodiment of a fourth aspect of the present application provides a page jump apparatus, which is applied to a server, and includes:
the generating module is used for generating a page link to be jumped according to the client address and the link parameter;
the first sending module is used for sending the page link to a target user;
the first receiving module is used for receiving the return parameters and the link parameters sent by the client based on the page link;
The determining module is used for determining the page navigation address corresponding to the return parameter and the link parameter;
the first sending module is configured to send the page navigation address to the client, so that the client jumps to a page corresponding to the page navigation address.
An embodiment of a fifth aspect of the present application provides a page jump apparatus, which is applied to a client, and includes:
the second receiving module is used for receiving a page jump request of a target user, wherein the page jump request comprises a link parameter;
the acquisition module is used for acquiring the current return parameters;
the second sending module is used for sending the return parameter and the link parameter to a server;
the second receiving module is used for receiving the page navigation address returned by the server according to the return parameter and the link parameter;
and the display module is used for displaying the page corresponding to the page navigation address.
An embodiment of a sixth aspect of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor executes the computer program to implement the method of the first aspect or the second aspect.
An embodiment of a seventh aspect of the present application provides a computer-readable storage medium having a computer program stored thereon, the program being executed by a processor to implement the method of the first or second aspect.
The technical scheme provided in the embodiment of the application at least has the following technical effects or advantages:
in the embodiment of the application, the link parameters are carried in the page link pushed to the user, when the user clicks the pushed page link, the corresponding client is opened, the client acquires the current return parameters, and the link parameters transparently transmitted by the pushed page link and the acquired return parameters are sent to the server. And the server determines a final page navigation address according to the link parameter and the return parameter and feeds the final page navigation address back to the client. And the client displays a final target page according to the page navigation address. The method and the device realize page jump according to the current state, so that the client displays the page matched with the current state, the condition of page jump failure is greatly reduced, the safety risk of page jump is avoided, and the times of collapse of the client due to page jump failure are reduced.
Furthermore, by designing the link parameters and the return parameters to include different parameter combinations, the client can also jump to the correct page when the terminal system, the client version, the process type, the user role or the service state and the like change, and the condition that the jump fails due to the change of various states is avoided.
Additional aspects and advantages of the present application will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the present application.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the application. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 illustrates a schematic structural diagram of a page jump system according to an embodiment of the present application;
fig. 2 shows a signaling interaction diagram of a page jump method according to an embodiment of the present application;
FIG. 3 is a flowchart illustrating a page jump method applied to a server according to an embodiment of the present application;
FIG. 4 is a flowchart illustrating a page jump method applied to a client according to an embodiment of the present application;
FIG. 5 is a schematic structural diagram illustrating a page jump apparatus applied to a server according to an embodiment of the present application;
FIG. 6 is a schematic structural diagram illustrating a page jump apparatus applied to a client according to an embodiment of the present application;
Fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application;
fig. 8 is a schematic diagram of a storage medium provided in an embodiment of the present application.
Detailed Description
Exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present application are shown in the drawings, it should be understood that the present application may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
It is to be noted that, unless otherwise specified, technical or scientific terms used herein shall have the ordinary meaning as understood by those skilled in the art to which this application belongs.
A page jump method, an apparatus, a system, a device and a storage medium according to embodiments of the present application are described below with reference to the accompanying drawings.
At present, the APP often sends some short messages, APP alert messages, web messages, and other push messages to the user according to different services, where the push messages may include a page link, and the user clicks the page link to open a corresponding page in the APP. In the related art, all page links in the push message are written fixed links, and clicking the links opens the fixed pages in the APP. However, the application state, the system state, the user role, and the like corresponding to the fixed page to which the page link in the push message is directed may be different from the current application state, the system state, the user role, and the like of the APP in the mobile terminal, for example, the APP version corresponding to the page link in the push message is different from the APP version on the current mobile terminal. When these disagreements occur, the page link in the push message cannot jump to the corresponding fixed page, and even the APP may crash.
For example, if the version of the APP is upgraded, the page corresponding to the fixed jump link is offline, and at this time, the jump may report an error because the page cannot be found, or even the APP may crash seriously.
Alternatively, the logged-in user is replaced and then jumps to a page designated by a fixed link, which may result in unauthorized operation. For example, originally, the link to be jumped is pushed to the VIP user, and the link is some content which only allows the VIP user to watch or some charging operation. Then, after the user switches the account of an ordinary user in the APP, the user directly jumps to a page that has no authority to access by clicking the link again. If the page has no verification measure, some uncontrollable consequences can be caused. If the link is spread across a community of users, it is likely to cause immeasurable losses.
Still alternatively, some operations of the user repeatedly clicking on the pushed fixed link may also confuse the data. For example, after a user clicks a fixed link and uploads one piece of data, the user clicks the fixed link again and uploads another piece of data, so that two pieces of data associated with the same fixed link exist, and the system cannot determine which piece of data is used for subsequent processing, so that dirty data is formed.
The current industry approach is to allow the operations in the above examples to recognize the consequences of a user clicking a failed link, and add some verification to the page at most when there is user feedback, so as to prevent some economic loss, but still cause bad experience for the user.
Based on this, the embodiment of the application provides a page jump method, in which a page link pushed to a user carries link parameters, and when the user clicks the pushed page link, opens a corresponding client of an APP, and the client acquires current return parameters and sends the link parameters passed through by the pushed page link and the acquired return parameters to a server. And the server determines a final page navigation address according to the link parameter and the return parameter and feeds the final page navigation address back to the client. And the client jumps to a final target page according to the page navigation address.
The final page navigation address is determined according to the current state of the client, and the client jumps to the page corresponding to the page navigation address, so that the client displays the page matched with the current state, thereby greatly reducing the page jump failure, avoiding the safety risk of page jump, and reducing the times of collapse of the client due to the page jump failure.
Referring to fig. 1, a system architecture based on the method includes a server and a client, and the client is installed on a terminal such as a mobile phone or a tablet computer. The server is in communication connection with the client through a network.
The server is pre-configured with the mapping relation among the scene state parameters, the return parameters and the routing information. The scene state parameters are used for representing scenes, states and the like when the server pushes the page link to the user, and the scene state parameters may include scene values, process types, user states and the like. The scene value is used to identify a scene corresponding to a page that the user is accessing when pushing the page link, the flow type is used to identify a type of a flow corresponding to a page that the user is accessing when pushing the page link, and the flow type may include a new flow (stream _ new), an old flow (stream _ old), a general flow (public), or the like. The user state is used for identifying the role or behavior state of the user when the page link is pushed, and the role state of the user may include a vip user or a common user. The behavior state of the user is used for identifying the progress state of the user currently accessing the business service, such as the state of a user payment order, the state of a merchant for order delivery of the user, the state of a user submitting a beautification appeal, the state of a doctor submitting a shaping scheme according to the beautification appeal of the user, and the like.
And the return parameter is used for representing the current state of the client when the user clicks the pushed page link to open the client of the APP. The backhaul parameters may include system type, client version number, etc. The system type may include android or IOS, etc. The routing information comprises a routing address and a parameter key of a service parameter corresponding to the routing address. A set of scene state parameters and backhaul parameters in the preconfigured mapping relationship may correspond to one or more pieces of routing information, and in the case of corresponding to a plurality of pieces of routing information, matching routing information may be selected from the corresponding plurality of pieces of routing information according to the scene state parameters and backhaul parameters.
In the embodiment of the present application, a preset bottoming route is also preconfigured in the server. The preset backing route is used for enabling the client to display the corresponding backing page according to the preset backing route when the final page navigation address corresponding to the current state cannot be determined, and therefore the problem of page jump failure is avoided.
Based on the system architecture shown in fig. 1, and after the configuration operation on the server is completed, as shown in fig. 2, the page jump is implemented through the following steps, which specifically include:
step 101: and the server generates a page link to be jumped according to the client address and the link parameter, and sends the page link to a target user.
The server can provide a plurality of business services for the user through the client, and can monitor whether the current business of the user meets the preset link pushing condition corresponding to the business in real time in the process that the user accesses the server through the client. The preset link pushing condition is set according to the service requirement. For example, when the server detects a user payment order, it is determined that the user currently meets a preset link pushing condition; or if the user submits the beautifying appeal information, determining that the user currently meets the preset link pushing condition, and the like.
When the server detects a target user meeting a preset link pushing condition, firstly, a page link to be jumped is generated according to the address link parameter of the client. Specifically, when the server determines that the target user currently meets a preset link pushing condition corresponding to the target service according to the service requirement, the server obtains a current scene state parameter and a service parameter of the target service corresponding to the scene state parameter, and takes the scene state parameter and the service parameter as link parameters.
The scene state parameters at least comprise scene values, and besides the scene values, the scene state parameters can also comprise one or more of parameters such as flow types and user states. The server determines a current scene value according to the current state of the target user accessing the target service, such as determining the scene value according to the state of the current payment order of the target user. The server obtains the current flow type of the target service accessed by the target user, or the server obtains the current user role or user behavior and other user states of the target user.
After determining the current scene value, the server determines all routing information corresponding to the scene value from the mapping relation among the pre-configured scene state parameters, the return parameters and the routing information, acquires parameter keys of service parameters included in all the determined routing information, then determines the parameter value corresponding to each parameter key according to the current state of the target service accessed by the target user, and combines each parameter key and the corresponding parameter value into a parameter key value pair. And taking all the parameter key value pairs as service parameters under the scene corresponding to the scene value. And taking the acquired scene state parameters and the acquired service parameters as link parameters. And then packaging the link parameter of the client address corresponding to the client to which the target service belongs into a page link to be jumped.
Wherein the client address is used for specifying the client needing to be opened. And the server packages the client address and the link parameter according to a packaging rule corresponding to the current client to obtain the page link to be jumped. Specifically, the client address and the link parameter can be spliced together sequentially from left to right through the connector to obtain the page link to be jumped.
In other embodiments of the present application, a preset relay route may be further configured in advance in the server, where the preset relay route is a page route written in advance, and is used for enabling the client to display the relay page according to the preset relay route. In the process of generating the page link to be skipped, the server may further obtain a preset relay route configured in advance, and encapsulate the preset relay route, the client address and the link parameter into the page link to be skipped according to an encapsulation rule corresponding to the client. Specifically, the client address, the preset transfer route and the link parameter can be spliced together through the connector from left to right to obtain the page link to be skipped.
Because the page links spliced together in the mode are longer, after one link is obtained through splicing, the link can be identified through a plurality of shorter character strings to obtain the page link to be finally jumped, so that errors of the longer page link in the transmission process or the display at a user side are avoided.
For example, the link formed by encapsulating the client address, the preset relay route and the link parameter may be app.abc:// html & url = https:// m.abc.com/appm/syacn/wechat/smsLink & route _ key = is _ grab _2& otherUID { $ p _ uid }. The longer link may be denoted http://. abc. com/defg/.
After the spliced links are identified by the short character strings in the mode to obtain the page links to be jumped, the corresponding relation between the page links and the spliced links can be stored. The server also sends the correspondence to the domain name server. The domain name server stores the correspondence.
After the server generates the page link to be jumped through the method, the server sends a push message containing the page link to the target user. The push message may be a short message, a web page message, a client-side reminder message, or an instant messaging message sent through instant messaging software, etc. Besides the page link, the push message may also include document information. For example, the push message may be "Congratulations you successfully place an order, please click on http://. abc. com/defg/, knowing the order completion progress".
And the server sends the push message to a terminal of a target user, and the terminal displays the push message. After seeing the displayed push message, the user can click a page link included in the push message. When the terminal detects that the user clicks the page link, a domain name resolution request is sent to a domain name server, and the domain name resolution request carries the page link. And if the domain name resolution request carries the page link of the shorter character string, the domain name server acquires the corresponding splicing link from the corresponding relation between the page link and the splicing link, and returns the splicing link to the terminal.
After the terminal receives the splicing address, the outermost layer of the splicing address is analyzed, namely, the outermost layer of the splicing address is analyzed from the leftmost side of the splicing address, the client address included by the splicing address is determined, the corresponding client installed on the terminal is opened according to the client address, and the webview component of the client is opened. And then sending a page jump request to the client, wherein the page jump request comprises the link parameter in the splicing address.
Step 102: the client receives a page jump request of a target user, wherein the page jump request comprises a link parameter.
And if the splicing address also comprises a preset transfer route, the page jump request comprises the preset transfer route and the link parameter.
And if the page jump request comprises the preset transfer route, the client displays the transfer page according to the preset transfer route comprised by the page jump request.
And the client displays the transfer page by using the webview component according to the preset transfer route included in the page jump request.
In the embodiment of the application, the preset transit route comprises three parts, wherein the first part is used for starting a transit page by using a webview component in a client to acquire a return parameter and a link parameter of page link pass-through. The second part is used for building a transit interface to connect the transit page and the server. The third part is used for calling a page jump function to jump from the transfer page to the final target page.
Step 103: the client acquires the current return parameters and sends the return parameters and the link parameters to the server.
And if the client displays the transfer page, acquiring the current return parameters through the transfer page. And if the client does not display the transfer page, the client acquires the return parameters through a preset program for acquiring the return parameters.
The backhaul parameter may include a system type to which an operating system of the terminal belongs, such as android or IOS. The backhaul parameters may also include the client's current client version number. In addition to the system type and client version number, the backhaul parameters may include any other parameter capable of indicating the status of the end system or client.
The client also obtains the link parameters transparently transmitted from the page links contained in the push message. And the client sends the link parameter and the acquired return parameter to the server.
Step 104: and the server receives the return parameters and the link parameters sent by the client based on the page link, and determines the page navigation addresses corresponding to the return parameters and the link parameters.
The link parameters comprise scene state parameters and service parameters, and the service parameters comprise a plurality of parameter key value pairs. The server stores the service parameters in a parameter pool. And acquiring corresponding routing information according to the received return parameters and the link parameters. And generating a final page navigation address according to the acquired routing information.
Firstly, the server determines whether a record corresponding to a scene state parameter and a return parameter exists in a mapping relation of the scene state parameter, the return parameter and routing information which are configured in advance. If yes, the routing information corresponding to the scene state parameter and the return parameter is obtained from the record. And generating a final page navigation address according to the routing information. Wherein the routing information includes a routing address and a parameter key of a service parameter.
And respectively acquiring the parameter value corresponding to each parameter key included in the routing information from a plurality of parameter key value pairs included in the service parameters stored in the parameter pool according to the parameter key of the service parameter included in the routing information. And then splicing the routing address included by the routing information and the acquired parameter value corresponding to each parameter key into a final page navigation address.
If it is determined that the preset mapping relation does not have records corresponding to the scene state parameters and the return parameters received by the server, a preset backing route is obtained, and the preset backing route is determined as a final navigation address. The preset underlying route can be the address of the home page of the client or the address of the home page of the user, and the like.
Step 105: the server sends the page navigation address to the client.
Step 106: and the client receives the returned page navigation address and displays the page corresponding to the page navigation address.
And if the client displays the transit page, after receiving the page navigation address, jumping from the transit page to a page corresponding to the page navigation address.
In the embodiment of the application, page skipping under different application scenes can be realized through different environment state parameters and return parameters. The following illustrates the page jump process in several application scenarios.
Application scenario one
The scene state parameters comprise scene values and process types, and the return parameters comprise system types and client version numbers. The server determines the final page navigation address through step 105, and specifically determines whether a record containing the scene value, the flow type, and the system type exists from a mapping relationship between a pre-configured scene state parameter, a return parameter, and the routing information. If so, acquiring a preset version number from the record, and comparing whether the client version number included in the return parameter is consistent with the preset version number; and if so, acquiring first routing information from the record, and generating a final page navigation address according to the first routing information. And if not, acquiring second routing information from the record, and generating a final page navigation address according to the second routing information. If the mapping relation does not have a record containing the scene state parameter and the return parameter, or the version comparison process reports an error, acquiring a preset backing route, and taking the backing route as a final page navigation address.
For example, the mapping relationship between the scene state parameter, the backhaul parameter, and the routing information, which are configured in advance in the server, is shown in table 1, and in the mapping relationship, in addition to scene 1, many records corresponding to other scene values are stored, and the description is given by taking scene 1 as an example. Assume that the scene state parameter in the link parameters received by the server includes a scene value of "scene 1" and a flow type of "new flow". The system type in the received backhaul parameters is android, and the client version number is 3.0. And determining that the corresponding preset client version number is 3.0 according to the scene value 'scene 1', the process type 'new process' and the system type 'android'. The server compares the client version number '3.0' preset in the mapping relation with the client version number '3.0' in the received return parameter, determines that the comparison result is True (True), and then acquires the routing information from the mapping relation: "True-route 1" and "True-parameter key 1". And subsequently, according to the "True-parameter key 1", acquiring a parameter value corresponding to the "True-parameter key 1" from the service parameter in the link parameter received by the server. And splicing the 'True-route 1' and the acquired parameter values into a final page navigation address. And returning the page navigation address to the client, and jumping to a page corresponding to the page navigation address from the currently displayed transfer page by the client.
TABLE 1
In practical applications, when a user clicks a page link in a push message, a system of a user terminal, a version of a client, a flow type, and the like may have changed, which is different from when a server pushes the page link to the user. In the first application scenario, a final page navigation address is determined according to a scenario value, a flow type, a system type and a client version number. Therefore, even if a user replaces a terminal such as a mobile phone or a tablet computer, the system type of the terminal is changed. Alternatively, the user upgrades the version of the client. Alternatively, the flow type is changed. Even if the changes occur, the final page navigation address can be accurately determined, so that the client jumps to the correct page, and page jump failure is avoided.
Application scenario two
The scene state parameters comprise scene values and user identification information, and the return parameters comprise system types and client version numbers. The user identification information may be a user account, a contact address, and the like. After receiving the user identification information, the server obtains a user role parameter corresponding to the user identification information, where the user role parameter may include a VIP user or a general user. And the server determines whether a record containing the scene value, the user role parameter and the system type exists in a mapping relation of a pre-configured scene state parameter, a return parameter and the routing information. If so, acquiring a preset version number from the record, and comparing whether the client version number included in the return parameter is consistent with the preset version number; and if so, acquiring first routing information from the record, and generating a final page navigation address according to the first routing information. And if not, acquiring second routing information from the record, and generating a final page navigation address according to the second routing information. If the mapping relation does not have a record containing the scene state parameter and the return parameter, or the version comparison process reports an error, acquiring a preset backing route, and taking the backing route as a final page navigation address.
For example, the mapping relationship between the pre-configured scene state parameter, the backhaul parameter, and the routing information in the server is as shown in table 2, and it is assumed that the scene value included in the scene state parameter in the link parameters received by the server is "scene 1", the user identification information is "user 1", and the user role parameter corresponding to "user 1" is determined to be "normal user". The system type in the received backhaul parameters is "iOS", and the client version number is "1.0". And determining that the corresponding preset client version number is 2.0 according to the scene value 'scene 1', the user role parameter 'common user' and the system type 'iOS'. The server compares the client version number "2.0" preset in the mapping relationship with the client version number "1.0" in the received backhaul parameter, determines that the comparison result is False (False), and then obtains the routing information from the mapping relationship: "False-route 2" and "False-parameter key 2". And subsequently, according to the 'False-parameter key 2', acquiring a parameter value corresponding to the 'False-parameter key 2' from the service parameter in the link parameter received by the server. And splicing the 'False-route 2' and the acquired parameter value into a final page navigation address. And returning the page navigation address to the client, and jumping to a page corresponding to the page navigation address from the currently displayed transfer page by the client.
TABLE 2
When the user clicks the page link in the push message in the actual application, the VIP validity period of the user may be passed, and the VIP user is recovered to be a normal user. At this time, the user cannot be shown the page corresponding to the VIP when clicking the page link. In the second application scenario, the final page navigation address is determined according to the scenario value, the user role parameter, the system type and the client version number. Therefore, even if a user replaces a terminal such as a mobile phone or a tablet computer, the system type of the terminal is changed. Alternatively, the user upgrades the version of the client. Alternatively, the user role parameters have changed. Even if the changes occur, the final page navigation address can be accurately determined, so that the client jumps to the correct page, and page jump failure is avoided.
Application scenario three
The scene state parameters comprise scene values and user identification information, and the return parameters comprise system types and client version numbers. The user identification information may be a user account, a contact address, and the like. And after receiving the user identification information, the server acquires a service state parameter corresponding to the user identification information, wherein the service state parameter is used for representing the service progress state of the user, such as the state of a paid order, the state of a merchant having delivered goods and the like. And the server determines whether a record containing the scene value, the service state parameter and the system type exists in a mapping relation of a pre-configured scene state parameter, a return parameter and the routing information. If so, acquiring a preset version number from the record, and comparing whether the client version number included in the return parameter is consistent with the preset version number; and if so, acquiring first routing information from the record, and generating a final page navigation address according to the first routing information. And if not, acquiring second routing information from the record, and generating a final page navigation address according to the second routing information. If the mapping relation does not have a record containing the scene state parameter and the return parameter, or the version comparison process reports an error, acquiring a preset backing route, and taking the backing route as a final page navigation address.
For example, the mapping relationship between the pre-configured scene state parameter, the backhaul parameter, and the routing information in the server is as shown in table 3, and it is assumed that the scene value included in the scene state parameter in the link parameter received by the server is "scene 1", the user identification information is "user 1", and the service state parameter corresponding to "user 1" is determined to be "state of paid order". The system type in the received backhaul parameters is "iOS", and the client version number is "1.0". And determining that the corresponding preset client version number is 2.0 according to the scene value 'scene 1', the service state parameter as 'the state of the paid order' and the system type 'iOS'. The server compares the client version number "2.0" preset in the mapping relationship with the client version number "1.0" in the received backhaul parameter, determines that the comparison result is False (False), and then obtains the routing information from the mapping relationship: "False-route 2" and "False-parameter key 2". And subsequently, according to the 'False-parameter key 2', acquiring a parameter value corresponding to the 'False-parameter key 2' from the service parameter in the link parameter received by the server. And splicing the 'False-route 2' and the acquired parameter value into a final page navigation address. And returning the page navigation address to the client, and jumping to a page corresponding to the page navigation address from the currently displayed transfer page by the client.
TABLE 3
When the user clicks the page link in the push message in actual application, the state corresponding to the service of the user may have changed, for example, the state of the user is "paid order" when the user just paid the order, and the state of the user is "merchant shipped" after the merchant ships. For the "paid order" state, the order detail page needs to be presented to the user, and for the "merchant shipped" state, the logistics page needs to be presented to the user. In the third application scenario, the final page navigation address is determined according to the scenario value, the service state parameter, the system type and the client version number. Therefore, even if a user replaces a terminal such as a mobile phone or a tablet computer, the system type of the terminal is changed. Alternatively, the user upgrades the version of the client. Or, the state corresponding to the service of the user is changed. Even if the changes occur, the final page navigation address can be accurately determined, so that the client jumps to the correct page, and page jump failure is avoided.
Application scenario four
The scene state parameters comprise scene values, process types and user identification information, and the return parameters comprise system types and client version numbers. The user identification information may be a user account, a contact address, and the like. After receiving the user identification information, the server obtains a user role parameter and a service state parameter corresponding to the user identification information, where the user role parameter may include a VIP user or a general user. The business status parameter is used for indicating the business process status of the user, such as the status of paid orders, the status of shipped by merchants and the like. And the server determines whether a record containing the scene value, the process type, the user role parameter, the service state parameter and the system type exists in a mapping relation of a pre-configured scene state parameter, a return parameter and the routing information. If so, acquiring a preset version number from the record, and comparing whether the client version number included in the return parameter is consistent with the preset version number; and if so, acquiring first routing information from the record, and generating a final page navigation address according to the first routing information. And if not, acquiring second routing information from the record, and generating a final page navigation address according to the second routing information. If the mapping relation does not have a record containing the scene state parameter and the return parameter, or the version comparison process reports an error, acquiring a preset backing route, and taking the backing route as a final page navigation address.
For example, the mapping relationship between the pre-configured scene state parameter, the backhaul parameter, and the routing information in the server is as shown in table 4, and it is assumed that the scene value included in the scene state parameter in the link parameters received by the server is "scene 1", the flow type is "new flow", the user identification information is "user 1", and the user role parameter corresponding to "user 1" is determined to be "normal user". And determining that the service state parameter corresponding to the user1 is the state of the paid order. The system type in the received backhaul parameters is "iOS", and the client version number is "1.0". And determining that the corresponding preset client version number is 2.0 according to the scene value 'scene 1', the flow type is 'new flow', the user role parameter is 'ordinary user', the service state parameter is 'state of paid order' and the system type 'iOS'. The server compares the client version number "2.0" preset in the mapping relationship with the client version number "1.0" in the received backhaul parameter, determines that the comparison result is False (False), and then obtains the routing information from the mapping relationship: "False-route 2" and "False-parameter key 2". And subsequently, according to the 'False-parameter key 2', acquiring a parameter value corresponding to the 'False-parameter key 2' from the service parameter in the link parameter received by the server. And splicing the 'False-route 2' and the acquired parameter value into a final page navigation address. And returning the page navigation address to the client, and jumping to a page corresponding to the page navigation address from the currently displayed transfer page by the client.
TABLE 4
When a user clicks a page link in a push message in actual application, one or more of various states such as a role of the user, a service state, a flow type, a system type of a terminal or a version of a client may be changed. In the fourth application scenario, the final page navigation address is determined according to the scenario value, the process type, the user role parameter, the service state parameter, the system type and the client version number. Therefore, even if a user replaces a terminal such as a mobile phone or a tablet computer, the system type of the terminal is changed. Alternatively, the user upgrades the version of the client. Or, the state corresponding to the service of the user is changed. Or the user's role has changed, etc. Even if the changes occur, the final page navigation address can be accurately determined, so that the client jumps to the correct page, and page jump failure is avoided.
In this embodiment of the present application, the environment state parameter includes a scene value, and the environment state parameter may further include a flow type or user identification information, and the like, in addition to the scene value. The backhaul parameters include the system type and the client version number, etc. Different page jump schemes can be realized by designing that the environment state parameters and the return parameters respectively comprise different parameters. In addition to the above four application scenarios, the embodiment of the present application can also be applied to any application scenario in which page link pushing is required due to business requirements and page skipping is performed based on the pushed page link, and therefore, description is not repeated one by one here.
In the embodiment of the application, the link parameters are carried in the page link pushed to the user, when the user clicks the pushed page link, the corresponding client is opened, the client acquires the current return parameters, and the link parameters transparently transmitted by the pushed page link and the acquired return parameters are sent to the server. And the server determines a final page navigation address according to the link parameter and the return parameter and feeds the final page navigation address back to the client. And the client displays a final target page according to the page navigation address. The method and the device realize page jump according to the current state, so that the client displays the page matched with the current state, the condition of page jump failure is greatly reduced, the safety risk of page jump is avoided, and the times of collapse of the client due to page jump failure are reduced.
The embodiment of the application also provides a page jump method, and the execution main body of the method is the server. As shown in fig. 3, includes:
step 201: and the server generates a page link to be jumped according to the address link parameter of the client, and sends the page link to be jumped to a target user.
And the server generates a page link to be jumped according to the client address and the link parameter. Specifically, the server determines that the target user currently meets a preset link pushing condition corresponding to the target service; acquiring a current scene state parameter and a service parameter of a target service corresponding to the scene state parameter, and taking the scene state parameter and the service parameter as link parameters; and packaging the client address and the link parameter corresponding to the client to which the target service belongs into a page link to be jumped. The server then sends a push message containing the link to the page to the target user.
In another implementation manner, the server further obtains a preset relay route, and encapsulates the preset relay route, the client address and the link parameter into a page link to be skipped.
Step 202: and the server receives the return parameters and the link parameters sent by the client based on the page link.
Step 203: and the server determines the page navigation address corresponding to the return parameter and the link parameter.
And the server acquires corresponding routing information according to the return parameters and the link parameters. And generating a final page navigation address according to the routing information.
The method comprises the steps that a link parameter comprises a scene state parameter, and specifically, a server determines whether a record corresponding to the scene state parameter and a return parameter exists in a mapping relation of the pre-configured scene state parameter, the return parameter and routing information; if yes, obtaining the scene state parameter and the routing information corresponding to the return parameter from the record; and if not, acquiring a preset backing route.
If the record corresponding to the scene state parameter and the return parameter exists, the routing information obtained from the record comprises a routing address and a parameter key, and the link parameter further comprises a service parameter. The server acquires a parameter value corresponding to the parameter key from the service parameter; and splicing the routing address included by the routing information and the acquired parameter value into a final page navigation address.
In the embodiment of the present application, the scene state parameter includes a scene value, and the backhaul parameter includes a system type and a client version number. Correspondingly, the server determines whether a record containing a scene value and a system type exists in a mapping relation among the pre-configured scene state parameter, the return parameter and the routing information; if so, acquiring a preset version number from the record, and comparing whether the version number of the client side is consistent with the preset version number; if the two routing information are consistent, acquiring first routing information from the record, and if the two routing information are not consistent, acquiring second routing information from the record; if no record exists in the mapping relation or the version comparison process is in error, a preset bottoming route is obtained.
In other embodiments of the present application, the scene state parameters further include a process type or user identification information, and the server obtains a user role parameter and/or a service state parameter corresponding to the user identification information; and acquiring corresponding routing information according to the return parameters, the link parameters and the user role parameters and/or the service state parameters.
Step 204: and the server sends the generated page navigation address to the client so that the client jumps to a page corresponding to the page navigation address.
The page jump method applied to the server according to the above-mentioned embodiment of the present application and the page jump method according to any of the above-mentioned embodiments of the present application have the same inventive concept and have the same beneficial effects as the method adopted, run, or implemented by the application program stored in the page jump method.
The embodiment of the application also provides a page jump method, and the execution main body of the method is a client. As shown in fig. 4, includes:
step 301: the client receives a page jump request of a target user, wherein the page jump request comprises a link parameter.
Step 302: the client acquires the current return parameters and sends the return parameters and the link parameters to the server.
Step 303: and the client receives the page navigation address returned by the server according to the return parameter and the link parameter, and displays the page corresponding to the page navigation address.
In another implementation manner, the page jump request further includes a preset transit route. When the client receives the page jump request, the client displays a transfer page according to a preset transfer route; acquiring a return parameter through a transfer page; and after receiving the page navigation address, jumping from the transfer page to a page corresponding to the page navigation address.
The page jump method applied to the client provided by the above embodiment of the present application and the page jump method provided by any of the above embodiments of the present application have the same inventive concept and have the same beneficial effects as the method adopted, run or implemented by the application program stored in the page jump method.
The embodiment of the application also provides a page jump system, which is used for executing the page jump method provided by any one of the embodiments. As shown in fig. 1, the system includes: a server and a client;
the server is used for generating a page link to be jumped according to the client address and the link parameter and sending the page link to be jumped to a target user; receiving a return parameter and a link parameter sent by a client based on a page link; determining a page navigation address corresponding to the return parameter and the link parameter; sending a page navigation address to a client;
the client is used for receiving a page jump request of a target user, and the page jump request comprises a link parameter; acquiring current return parameters, and sending the return parameters and the link parameters to a server; receiving a page navigation address returned by the server; and displaying the page corresponding to the page navigation address.
The page jump system provided by the above embodiment of the present application and the page jump method provided by the embodiment of the present application have the same inventive concept and have the same beneficial effects as the method adopted, operated or implemented by the application program stored in the page jump system.
The embodiment of the present application further provides a page jump device, where the page jump device is configured to execute an operation executed by a server in the page jump method provided in any of the above embodiments. As shown in fig. 5, the apparatus includes:
a generating module 401, configured to generate a page link to be skipped according to the client address and the link parameter;
a first sending module 402, configured to send a page link to be skipped to a target user;
a first receiving module 403, configured to receive a backhaul parameter and a link parameter sent by a client based on a page link;
a determining module 404, configured to determine a page navigation address corresponding to the return parameter and the link parameter;
a first sending module 402, configured to send the page navigation address to the client, so that the client jumps to a page corresponding to the page navigation address.
A generating module 401, configured to determine that a target user currently meets a preset link pushing condition corresponding to a target service; acquiring a current scene state parameter and a service parameter of a target service corresponding to the scene state parameter, and taking the scene state parameter and the service parameter as link parameters; and packaging the client address and the link parameter corresponding to the client to which the target service belongs into a page link to be jumped.
A generating module 401, configured to obtain a preset transit route; and packaging the preset transfer route, the client address and the link parameter into a page link to be jumped.
A determining module 404, configured to obtain corresponding routing information according to the backhaul parameter and the link parameter; and generating a final page navigation address according to the routing information.
The link parameter includes a scene state parameter, and the determining module 404 is configured to determine whether a record corresponding to the scene state parameter and the backhaul parameter exists in a mapping relationship between a preconfigured scene state parameter, the backhaul parameter, and the routing information; if yes, obtaining the scene state parameter and the routing information corresponding to the return parameter from the record; and if not, acquiring a preset backing route.
The routing information obtained from the method comprises a routing address and a parameter key, and the link parameter also comprises a service parameter;
a determining module 404, configured to obtain a parameter value corresponding to the parameter key from the service parameter; and splicing the routing address and the parameter value into a final page navigation address.
The scene state parameter comprises a scene value, and the return parameter comprises a system type and a client version number;
a determining module 404, configured to determine whether a record including a scene value and a system type exists in a mapping relationship between a preconfigured scene state parameter, a backhaul parameter, and routing information; if so, acquiring a preset version number from the record, and comparing whether the version number of the client side is consistent with the preset version number; if the two routing information are consistent, acquiring first routing information from the record, and if the two routing information are not consistent, acquiring second routing information from the record; and if no record exists in the mapping relation or the version comparison process is in error, acquiring a preset bottoming route.
The scene state parameters further include a process type or user identification information, and the determining module 404 is configured to obtain a user role parameter and/or a service state parameter corresponding to the user identification information; and acquiring corresponding routing information according to the return parameters, the link parameters and the user role parameters and/or the service state parameters.
The page jump device provided by the above embodiment of the present application and the page jump method provided by the embodiment of the present application have the same inventive concept and have the same beneficial effects as the method adopted, operated or implemented by the application program stored in the page jump device.
The embodiment of the present application further provides a page jump apparatus, where the apparatus is configured to execute an operation executed by a client in the page jump method provided in any of the above embodiments. As shown in fig. 6, the apparatus includes:
a second receiving module 501, configured to receive a page jump request of a target user, where the page jump request includes a link parameter;
an obtaining module 502, configured to obtain a current backhaul parameter;
a second sending module 503, configured to send the backhaul parameter and the link parameter to the server;
a second receiving module 501, configured to receive a page navigation address returned by the server according to the return parameter and the link parameter;
And the display module 504 is configured to display a page corresponding to the page navigation address.
In another implementation manner, the page jump request further includes a preset transit route. When the second receiving module 501 receives the page jump request, the displaying module 504 is further configured to display a transit page according to a preset transit route; the obtaining module 502 is further configured to obtain a return parameter through a transit page; after the second receiving module 501 receives the page navigation address, the displaying module 504 is further configured to jump from the transfer page to a page corresponding to the page navigation address.
The page jump device provided by the above embodiment of the present application and the page jump method provided by the embodiment of the present application have the same inventive concept and have the same beneficial effects as the method adopted, operated or implemented by the application program stored in the page jump device.
The embodiment of the application also provides electronic equipment for executing the page jump method. Please refer to fig. 7, which illustrates a schematic diagram of an electronic device according to some embodiments of the present application. As shown in fig. 7, the electronic device 8 includes: a processor 800, a memory 801, a bus 802 and a communication interface 803, the processor 800, the communication interface 803 and the memory 801 being connected by the bus 802; the memory 801 stores a computer program that can be executed on the processor 800, and the processor 800 executes the page jump method provided in any of the foregoing embodiments when executing the computer program.
The Memory 801 may include a high-speed Random Access Memory (RAM) and may also include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The communication connection between the network element of the apparatus and at least one other network element is realized through at least one communication interface 803 (which may be wired or wireless), and the internet, a wide area network, a local network, a metropolitan area network, etc. may be used.
The processor 800 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 800. The Processor 800 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; but may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 801, and the processor 800 reads the information in the memory 801 and completes the steps of the method in combination with the hardware thereof.
The electronic device provided by the embodiment of the application and the page jump method provided by the embodiment of the application have the same inventive concept and have the same beneficial effects as the method adopted, operated or realized by the electronic device.
Referring to fig. 8, the computer-readable storage medium is an optical disc 30, and a computer program (i.e., a program product) is stored thereon, and when being executed by a processor, the computer program executes the page jump method provided by any of the foregoing embodiments.
It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, a phase change memory (PRAM), a Static Random Access Memory (SRAM), a Dynamic Random Access Memory (DRAM), other types of Random Access Memories (RAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a flash memory, or other optical and magnetic storage media, which are not described in detail herein.
The computer-readable storage medium provided by the above-mentioned embodiment of the present application and the page jump method provided by the embodiment of the present application have the same beneficial effects as the method adopted, run or implemented by the application program stored in the computer-readable storage medium.
It should be noted that:
in the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the application may be practiced without these specific details. In some instances, well-known structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the application, various features of the application are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the application and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted to reflect the following schematic: this application is intended to cover such departures from the present disclosure as come within known or customary practice in the art to which this invention pertains. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this application.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the application and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
The above description is only for the preferred embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application should be covered within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (15)
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111194299.5A CN113641940B (en) | 2021-10-13 | 2021-10-13 | Page jumping method, device, system, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111194299.5A CN113641940B (en) | 2021-10-13 | 2021-10-13 | Page jumping method, device, system, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113641940A true CN113641940A (en) | 2021-11-12 |
| CN113641940B CN113641940B (en) | 2022-01-25 |
Family
ID=78426653
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111194299.5A Active CN113641940B (en) | 2021-10-13 | 2021-10-13 | Page jumping method, device, system, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113641940B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114189718A (en) * | 2021-11-23 | 2022-03-15 | 贵阳朗玛视讯科技有限公司 | Method and device for optimizing IPTV (Internet protocol television) starting |
| CN114254220A (en) * | 2021-12-22 | 2022-03-29 | 云南腾云信息产业有限公司 | Webpage view processing method and device and electronic equipment |
| CN114553477A (en) * | 2022-01-12 | 2022-05-27 | 青岛海尔科技有限公司 | Page jump method, device, equipment and storage medium |
| CN115065945A (en) * | 2022-06-28 | 2022-09-16 | 飞鸟鱼信息科技有限公司 | Short message link generation method and device, electronic equipment and storage medium |
| CN115186274A (en) * | 2022-09-14 | 2022-10-14 | 深圳开源互联网安全技术有限公司 | IAST-based security test method and device |
| CN115221435A (en) * | 2022-07-12 | 2022-10-21 | 上海蒜芽信息科技有限公司 | Method, system, device and medium for processing sharing path of pages in applet |
| CN115277821A (en) * | 2022-08-02 | 2022-11-01 | 中国银行股份有限公司 | Processing method and device for accessing APP |
| CN115733879A (en) * | 2022-09-27 | 2023-03-03 | 海尔优家智能科技（北京）有限公司 | Target page pushing method and device, storage medium and electronic device |
| CN118474029A (en) * | 2024-05-30 | 2024-08-09 | 北京希望在线线上学科培训学校 | A method for implementing client redirection |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107844324A (en) * | 2017-10-23 | 2018-03-27 | 北京京东尚科信息技术有限公司 | Customer terminal webpage redirects treating method and apparatus |
| US20190095541A1 (en) * | 2016-05-11 | 2019-03-28 | Alibaba Group Holding Limited | Method and system for starting application |
| US20190220159A1 (en) * | 2017-01-22 | 2019-07-18 | Tencent Technology (Shenzhen) Company Limited | Page display method, apparatus, terminal, and server, and storage medium |
| CN110221872A (en) * | 2019-04-22 | 2019-09-10 | 五八有限公司 | Method for page jump, device, electronic equipment and storage medium |
| CN110750741A (en) * | 2019-10-18 | 2020-02-04 | 深圳市比量科技传媒有限公司 | Webpage link skipping processing method, computer device and storage medium |
| CN112579264A (en) * | 2019-09-30 | 2021-03-30 | 上海游昆信息技术有限公司 | Application program jumping method, terminal and computer storage medium |
| CN113221048A (en) * | 2021-04-20 | 2021-08-06 | 武汉联影医疗科技有限公司 | Page jump method, device, computer equipment and storage medium |
-
2021
- 2021-10-13 CN CN202111194299.5A patent/CN113641940B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190095541A1 (en) * | 2016-05-11 | 2019-03-28 | Alibaba Group Holding Limited | Method and system for starting application |
| US20190220159A1 (en) * | 2017-01-22 | 2019-07-18 | Tencent Technology (Shenzhen) Company Limited | Page display method, apparatus, terminal, and server, and storage medium |
| CN107844324A (en) * | 2017-10-23 | 2018-03-27 | 北京京东尚科信息技术有限公司 | Customer terminal webpage redirects treating method and apparatus |
| CN110221872A (en) * | 2019-04-22 | 2019-09-10 | 五八有限公司 | Method for page jump, device, electronic equipment and storage medium |
| CN112579264A (en) * | 2019-09-30 | 2021-03-30 | 上海游昆信息技术有限公司 | Application program jumping method, terminal and computer storage medium |
| CN110750741A (en) * | 2019-10-18 | 2020-02-04 | 深圳市比量科技传媒有限公司 | Webpage link skipping processing method, computer device and storage medium |
| CN113221048A (en) * | 2021-04-20 | 2021-08-06 | 武汉联影医疗科技有限公司 | Page jump method, device, computer equipment and storage medium |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114189718A (en) * | 2021-11-23 | 2022-03-15 | 贵阳朗玛视讯科技有限公司 | Method and device for optimizing IPTV (Internet protocol television) starting |
| CN114254220A (en) * | 2021-12-22 | 2022-03-29 | 云南腾云信息产业有限公司 | Webpage view processing method and device and electronic equipment |
| CN114553477A (en) * | 2022-01-12 | 2022-05-27 | 青岛海尔科技有限公司 | Page jump method, device, equipment and storage medium |
| CN114553477B (en) * | 2022-01-12 | 2024-03-22 | 青岛海尔科技有限公司 | Page jump method, device, equipment and storage medium |
| CN115065945A (en) * | 2022-06-28 | 2022-09-16 | 飞鸟鱼信息科技有限公司 | Short message link generation method and device, electronic equipment and storage medium |
| CN115065945B (en) * | 2022-06-28 | 2023-08-29 | 飞鸟鱼信息科技有限公司 | Short message link generation method and device, electronic equipment and storage medium |
| CN115221435A (en) * | 2022-07-12 | 2022-10-21 | 上海蒜芽信息科技有限公司 | Method, system, device and medium for processing sharing path of pages in applet |
| CN115221435B (en) * | 2022-07-12 | 2026-01-23 | 上海蒜芽信息科技有限公司 | Method, system, equipment and medium for processing sharing path of page in applet |
| CN115277821A (en) * | 2022-08-02 | 2022-11-01 | 中国银行股份有限公司 | Processing method and device for accessing APP |
| CN115186274A (en) * | 2022-09-14 | 2022-10-14 | 深圳开源互联网安全技术有限公司 | IAST-based security test method and device |
| CN115733879A (en) * | 2022-09-27 | 2023-03-03 | 海尔优家智能科技（北京）有限公司 | Target page pushing method and device, storage medium and electronic device |
| CN118474029A (en) * | 2024-05-30 | 2024-08-09 | 北京希望在线线上学科培训学校 | A method for implementing client redirection |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113641940B (en) | 2022-01-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113641940B (en) | Page jumping method, device, system, device and storage medium | |
| CN104461491B (en) | The operation method and system of a kind of Hybrid components | |
| CN113014475B (en) | Message pushing integration method and device | |
| CN107070858B (en) | Service processing method and device | |
| US8060414B1 (en) | Encoding and decoding of product properties in a uniform resource locator | |
| CN105931107B (en) | Sharing method and device | |
| CN104134145A (en) | Receiving address error correction method and system | |
| CN112818270B (en) | Data cross-domain transfer method and device and computer equipment | |
| US11362929B2 (en) | System and method for remote management of sale transaction data | |
| US9292613B2 (en) | Generation of generic universal resource indicators | |
| CN104580112A (en) | Service authentication method and system, and server | |
| CN104965690A (en) | Method and apparatus for processing data | |
| US20160162984A1 (en) | Processing unstructured messages | |
| CN111209028B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN110324361A (en) | The method, apparatus of authentification of message calculates equipment and medium | |
| CN117807157A (en) | Transaction execution method, apparatus, program product, device and medium for blockchain | |
| CN114640506B (en) | Vulnerability detection method, device, equipment and medium | |
| CN108021593B (en) | Information transfer method and device and browser | |
| CN117880008A (en) | Gateway-based service request processing method, device, equipment and storage medium | |
| CN110427745B (en) | Verification code obtaining method and device, electronic equipment and computer readable medium | |
| CN112667447B (en) | Data restoration method and device | |
| CN108874390A (en) | A kind of data processing method and device, equipment, storage medium | |
| CN121365969A (en) | Resource transfer method, device, equipment and storage medium | |
| CN121071921A (en) | Data processing method, device, equipment and medium | |
| CN121478559A (en) | Database disaster recovery method and device, storage medium, product and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |