Multi-scene entry jump method and device, computer equipment and storage medium

Abstract

The invention relates to the technical field of computers, and discloses a multi-scene entry jump method and device, computer equipment and a storage medium. The method comprises the following steps: receiving a function request sent by any entrance for a target function of an application program, and obtaining a request parameter corresponding to the function request; determining a target jump strategy matched with the entry based on the request parameter; and skipping to a target session page corresponding to the target function from the entry according to the target skipping strategy. By implementing the technical scheme of the invention, the skipping from each entry to the target function does not need the original service function to perform request forwarding to the new target function, so that the forwarding logic of the function request does not need to be set, and the flexible skipping from multiple scene entries to the target function is realized.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a method, device, computer equipment and storage medium for entry jump in multiple scenarios. Background Art

[0002] The application client has a variety of functions, such as manual service functions. As the application's business develops, some of the original underlying business functions on the application client may not be able to meet the user's requirements for problem-solving efficiency. At this time, the original business functions may need to be migrated or upgraded. Accordingly, the application client will also be released to meet the new business functions. However, the adjustment of the original business functions depends on the modification and release of the application client code. Users cannot access the new business functions without upgrading.

[0003] The commonly used solution to this problem is to forward requests on the original underlying business functions to achieve compatibility between the original underlying business functions and the new business functions. However, for business functions with diverse usage scenarios, there will be multiple entrances, and there are often some special logics such as grayscale judgment and parameter mapping that need to be processed during the forwarding process, making it difficult to achieve flexible jumps to all entrances, thus affecting the user experience of the application client. Summary of the invention

[0004] In view of this, the embodiments of the present disclosure provide a multi-scenario entry jump method, apparatus, computer equipment and storage medium to solve the problem that it is difficult to flexibly jump all entries to business functions after the business function is upgraded.

[0005] In the first aspect, the embodiments of the present disclosure provide a multi-scenario entry jump method, including: receiving a function request issued by any entry for a target function of an application, and obtaining request parameters corresponding to the function request; based on the request parameters, determining a target jump strategy that matches the entry; and jumping from the entry to a target session page corresponding to the target function according to the target jump strategy.

[0006] The multi-scenario entry jump method provided by the disclosed embodiment obtains the function request initiated by any entry and parses the request parameters carried by the function request to determine the target jump strategy that matches the current entry, and directly jumps to the target function according to the target jump strategy, thereby avoiding the forwarding logic of the function request, and thus there is no need to deal with the logical problems existing in the request forwarding process. Entering the target session page corresponding to the target function through the corresponding target jump strategy can thus be compatible with the flexible jump from multiple scene entries to the target function, thereby improving the user experience of the application.

[0007] In the second aspect, the embodiment of the present disclosure provides a multi-scenario entry jump device, including: a parameter acquisition module, used to receive a function request issued by any entry for a target function of an application, and obtain request parameters corresponding to the function request; a policy determination module, used to determine a target jump strategy that matches the entry based on the request parameters; a jump module, used to jump from the entry to a target session page corresponding to the target function according to the target jump strategy.

[0008] In a third aspect, an embodiment of the present disclosure provides a computer device, comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, computer instructions being stored in the memory, and the processor executing the multi-scenario entry jump method of the above-mentioned first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0009] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the multi-scenario entry jump method of the above-mentioned first aspect or any corresponding implementation manner thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In order to more clearly illustrate the specific embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the specific embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0011] Figure 1 It is a jump diagram after the customer service system is upgraded in the related technology;

[0012] Figure 2 is a flowchart of an entry jump method for multiple scenarios according to some embodiments of the present disclosure;

[0013] Figure 3 is a schematic diagram of an entrance of multiple scenarios according to some embodiments of the present disclosure;

[0014] Figure 4 is a flowchart of another multi-scenario entry jump method according to some embodiments of the present disclosure;

[0015] Figure 5 is a schematic diagram of traffic diversion for customer service according to some embodiments of the present disclosure;

[0016] Figure 6 is a schematic diagram of web page jump according to some embodiments of the present disclosure;

[0017] Figure 7is a flowchart of another multi-scenario entry jump method according to some embodiments of the present disclosure;

[0018] Figure 8 is a schematic diagram of upgrading a customer service system according to some embodiments of the present disclosure;

[0019] Fig. 9 is a schematic diagram of multi-scenario entrance jump after the customer service system is upgraded according to some embodiments of the present disclosure;

[0020] Fig.10 is a structural block diagram of an entry jump device for multiple scenarios according to an embodiment of the present disclosure;

[0021] Fig.11 It is a schematic diagram of the hardware structure of the computer device of the embodiment of the present disclosure. DETAILED DESCRIPTION

[0022] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, rather than all the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present disclosure.

[0023] As the business of the application develops, some of the original underlying business functions on the application client may not be able to meet the user's requirements for problem solving efficiency. At this time, the original business functions may need to be migrated or upgraded. Correspondingly, the application client will also be released to meet the new business functions. Take the customer system as an example. Figure 1 As shown, adjustments to the original client system rely on changes and releases to the application client code, and users cannot access the new client system without upgrading.

[0024] The current solution is to forward requests on the original underlying business functions to achieve compatibility between the original underlying business functions and the new business functions. However, in the forwarding process, there are often some special logics of grayscale judgment and parameter mapping that need to be processed.

[0025] like Figure 1As shown in the figure, after grayscale judgment, customer service system A finds that the current request should be handled by customer service system B. Customer service system B needs an "entry" information, but the Applink used by customer service system A only supports carrying "scenario" information. In order to reuse the original link, scene a is mapped to entry information b required by customer service system B in customer service system A, and then passed to customer service system B. This requires customer service system A to be compatible with the logic of both the new and old systems, and it cannot be offline, which is a high risk; part of the business logic of customer system B is coupled in customer service system A, the boundary is not clear, and subsequent related changes will affect the two systems; customer service system A needs to maintain the parameter mapping between the two systems, and the configuration cost is high.

[0026] Based on this, the disclosed technical solution matches the corresponding target jump strategy for each entrance so that each entrance can flexibly jump to the target function, thereby being compatible with the flexible jump from multiple scene entrances to new business functions. And the jump process does not require the original business system to forward requests to the new business system, and the jump from each entrance to the new business function no longer depends on the original business system, so the original business system does not need to be compatible with the new and old system logics, and can be offline after the new business system is online, reducing risks. At the same time, the original business system does not need to maintain the parameter mapping between the two systems, reducing configuration costs. In addition, since the jump from each entrance to the new business function no longer depends on the original business system, the new business system and the original business system are fully decoupled and independent of each other, and subsequent related changes will not affect their respective systems.

[0027] According to an embodiment of the present disclosure, an embodiment of an entry jump method for multiple scenarios is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0028] In this embodiment, a multi-scenario entry jump method is provided, which can be used for computer devices such as mobile phones, tablet computers, computers, etc. Figure 2 is a flow chart of a method for redirecting an entry to multiple scenarios according to an embodiment of the present disclosure. Figure 2 As shown, the process includes the following steps:

[0029] Step S101, receiving a function request sent by any entry for a target function of an application, and obtaining request parameters corresponding to the function request.

[0030] Applications are deployed in computer devices to complete various tasks, such as document processing applications, audio and video applications, game applications, instant messaging applications, etc. Target functions are functions that applications can support, such as manual customer service functions, intelligent dialogue functions, etc. Function requests are requests triggered when the user of an application enters the target function through the target function's entrance. Request parameters are parameters carried in the function request, which may include request source, request entrance type, requested service, etc.

[0031] The target function of the application has corresponding entrances in multiple application scenarios, such as the function tag entrance set in the client, the tag entrance in the web program, the view entrance provided by the client, etc. Taking manual customer service as an example, Figure 3 As shown, a function label entry "Help and Customer Service" is provided in the client; an icon label entry is provided in the web page program corresponding to the application; a customer service view entry is provided in the communication bar in the client, etc.

[0032] Any entry can enter the target function to use the services provided by the target function. Specifically, when a user requests the target function through any entry, the application can receive the function request for the target function triggered by the user and obtain the request parameters carried in the function request.

[0033] Step S102: Determine a target jump strategy that matches the entry based on the request parameters.

[0034] The target jump strategy is the jump strategy required to enter the target function from the current entry. In order to ensure that different entries can jump to the target function smoothly, corresponding jump strategies are set for different entries. The request parameters corresponding to the entry carry relevant information of the entry. After obtaining the request parameters, by analyzing the request parameters of the entry, the relevant information of the current entry can be determined, thereby determining the target jump strategy that matches the entry.

[0035] Step S103: Jump from the entrance to the target session page corresponding to the target function according to the target jump strategy.

[0036] The target session page is the session page provided by the target function. After determining the target jump strategy, a jump link from the current entrance to the target function is assembled according to the target jump strategy, so as to directly enter the target session page corresponding to the target function according to the jump link.

[0037] The multi-scenario entry jump method provided in this embodiment obtains the function request initiated by any entry and parses the request parameters carried by the function request to determine the target jump strategy that matches the current entry, and directly jumps to the target function according to the target jump strategy, avoiding the forwarding logic of the function request, so there is no need to deal with the logical problems existing in the request forwarding process. Entering the target session page corresponding to the target function through the corresponding target jump strategy can be compatible with the flexible jump from multiple scene entries to the target function, thereby improving the user experience of the application.

[0038] In this embodiment, a multi-scenario entry jump method is provided, which can be used for computer devices such as mobile phones, tablet computers, computers, etc. Figure 4 is a flowchart of a computer device method according to an embodiment of the present disclosure, such as Figure 4 As shown, the process includes the following steps:

[0039] Step S201, receiving a function request issued by any entry for a target function of an application, and obtaining request parameters corresponding to the function request. For detailed description, please refer to the relevant description corresponding to the above embodiment, which will not be repeated here.

[0040] Step S202: Determine a target jump strategy that matches the entry based on the request parameters.

[0041] Specifically, the above step S202 may include:

[0042] Step S2021, parse the request parameters to determine the request source carried by the request parameters.

[0043] The request source is used to characterize the entry source that initiates the function request. The request parameter carries the identification information of the request source. The identification information corresponding to different request sources is unique, that is, the entry that initiates the function request is characterized by the unique identification information. For example, if the function request is initiated through the web page entry, the request parameter carries the unique identification A corresponding to the web page entry; if the function request is initiated through the client entry, the request parameter carries the unique identification C corresponding to the client entry.

[0044] After obtaining the request parameters, the parameter content carried by the request parameters is parsed to parse out the identification information for the request source carried in the request parameters. Based on the correspondence between the identification information and the request source, the request source carried in the current request parameters can be determined.

[0045] Step S2022, determining a target jump strategy that matches the entry according to the request source.

[0046] Different entries correspond to different jump strategies. Combined with the determined request source, the target entry that initiates the function request can be determined from the multiple entries corresponding to the target function. Therefore, according to the correspondence between the entry and the jump strategy, the target jump strategy that matches the current entry can be determined.

[0047] In some optional implementation methods, the target jump strategy may specifically include a direct jump strategy and a diversion jump strategy. The direct jump strategy is to jump directly from the entrance to the session page of the target function, and the diversion jump strategy means entering the intermediate page corresponding to the target function from the current entrance, and then jumping to the session page of the target function through the intermediate page.

[0048] Specifically, the above step S2022 may include:

[0049] Step a1: When the request source is the client entry, detect whether the client version is lower than the version supported by the target function.

[0050] Step a2: When the version of the client is equal to or higher than the version supported by the target function, the target jump strategy matching the entry is determined to be a direct jump strategy.

[0051] Step a3, when the client version is lower than the version supported by the target function, determine that the target jump strategy matching the entrance is the diversion jump strategy, and the diversion jump strategy is used to jump to the intermediate page of the target session page to enter the target session page through the intermediate page.

[0052] The client entry means entering from the tag entry set in the client, such as Figure 3 As shown, the customer service of the client is entered through the label "Help and Customer Service". The version supported by the target function is used to represent the version of the client that can directly jump to the target function through the entrance.

[0053] Since the client will iterate, the client version usually has low version and high version. For the high version client, since the target function is added after the new client is released, there is no compatibility issue for the high version client. You can jump directly to the target function through the registered application link Applink.

[0054] When determining to enter the target function through the client entry, it is necessary to detect whether the client version is lower than the version supported by the target function. When it is determined that the client version is equal to or higher than the version supported by the target function, it means that the client version is the version supported by the target function. At this time, it can be determined that the target jump strategy matching the client entry is the direct jump strategy, that is, after receiving the function request initiated by the client entry, it can directly jump to the corresponding target function through the registered application link Applink.

[0055] When it is determined that the client version is lower than the version supported by the target function, it means that the client version is not a version supported by the target function. At this time, in order to ensure that the lower version client can use the target function, you can first jump to the middle page of the target session page (the middle page can be generated based on the front-end SDK), and display the prompt information for entering the target session page in the middle page, so that the user can trigger the page jump according to the prompt information, thereby jumping from the middle page to the target session page corresponding to the target function.

[0056] like Figure 5 As shown, taking the customer service function as an example, when entering the customer service function through a lower version of the client, the original customer service function session page will be entered, and a prompt message "The function entrance has been moved, click here to jump to the new entrance" will be generated on the original customer service function session page. The user can click "here" in the prompt message to enter the middle page, and the entrance information of the new customer service function will be displayed on the middle page. Through the entrance information, the target session page corresponding to the new customer service function can be entered. In this way, the service is rejected through the original customer service function to guide the function request to the new customer service function.

[0057] In the above implementation, when requesting the target function through the client entrance, if the client version is equal to or higher than the version supported by the target function, a direct jump is made; if the client version is lower than the version supported by the target function, a jump is made through an intermediate page. Thus, the target function is interacted with through an independent intermediate page, and the jump from the client entrance to the target function is achieved without upgrading the client or modifying the original business function.

[0058] In some optional embodiments, the above step S2022 may also include: when the request source is an in-end entry and the client version is lower than the version supported by the target function, in response to the session information generated on the client's session page, generating a diversion jump strategy based on the session information.

[0059] The in-terminal entrance is the view entrance displayed in the client. The session information is the information entered by the user through the view entrance of the low-version client to enter the session page of the original business function, that is, the original business function is the function corresponding to the target function, which can provide services consistent with the target function in the low-version client.

[0060] Specifically, for the same business function, users can request the original business function through the view entrance displayed in the low-version client in the past. When the original business function is updated to the target function, the client version will be upgraded, and the user can update the client version to use the new target function.

[0061] If the user has not updated the client, when the user sends session information again through the session page of the original business function, the lower version client will respond to the session information initiated by the user, generate a corresponding diversion jump strategy based on the session information, and divert the session information to the target function through the diversion jump strategy. Figure 7 As shown, after the session page of the low-version client receives the session information, it will trigger the generation of corresponding prompt information, which is used to remind the user that the relevant business functions have been migrated and display the new entrance of the target function so that the user can jump from the new entrance to the target session page corresponding to the target function.

[0062] In the above implementation, when a target function is requested from an in-terminal entrance, corresponding prompt information is generated on the client's session page to direct the function request to the target function through the prompt information, thereby achieving forced diversion of the function request, ensuring that the target function can be jumped to through the in-terminal entrance, and avoiding the original business function being unable to go offline due to the continued provision of services at the in-terminal entrance.

[0063] In some optional implementation modes, the target jump strategy may specifically include a web page jump strategy. Accordingly, the above step S2022 may further include: when the request source is a web page portal, determining a web page jump strategy that matches the web page portal.

[0064] The web page jump strategy is used to jump to the middle page of the target session page. The middle page of the web page refers to a prompt page that pops up in the application web page for entering the target function, such as Figure 6 As shown, the user can enter the target session page through the middle page of the web page. Among them, the web page entrance can be an H5 page, a web page, or other pages, which are not specifically limited here.

[0065] When a target function is requested from a web page entrance, a web page middle page corresponding to the web page entrance is displayed in combination with the function request initiated by the web page entrance, and a link redirection is performed through the web page middle page to jump from the web page middle page to the target session page corresponding to the target function.

[0066] In the above implementation, by providing a corresponding web page jump strategy for the web page entrance, it is convenient to jump from the web page entrance to the target function, thereby realizing flexible jumping from the web page entrance to the target function.

[0067] Step S203: Jump from the entrance to the target session page corresponding to the target function according to the target jump strategy. For detailed description, please refer to the relevant description of the above embodiment, which will not be repeated here.

[0068] The multi-scenario entry jump method provided in this embodiment configures different jump strategies for different entries, and is compatible with various entries of low-version clients and entry of high-version clients, so that multiple scene entries can flexibly jump to the target function. There is no need to configure conversion logic between the original business function of the low-version client and the target function of the high-version client, which reduces the configuration cost. Therefore, the jump from each entry to the target function can be achieved without being restricted by the client version, which greatly improves the jump flexibility of multiple scene entries.

[0069] In this embodiment, a multi-scenario entry jump method is provided, which can be used for computer devices such as mobile phones, tablet computers, computers, etc. Figure 7 is a flow chart of a method for redirecting an entry to multiple scenarios according to an embodiment of the present disclosure. Figure 7 As shown, the process includes the following steps:

[0070] Step S301, receiving a function request issued by any entry for a target function of an application, and obtaining request parameters corresponding to the function request. For detailed description, please refer to the relevant description corresponding to the above embodiment, which will not be repeated here.

[0071] Step S302: Determine a target jump strategy that matches the entry based on the request parameters. For detailed description, please refer to the corresponding description of the above embodiment, which will not be repeated here.

[0072] Step S303: Jump from the entrance to the target session page corresponding to the target function according to the target jump strategy.

[0073] Specifically, the above step S303 may include:

[0074] Step S3031, based on the account information corresponding to the entry, determine the session identifier that matches the entry.

[0075] The account information is used to represent the login information of the application client, and the session identifier is the identifier information used to construct the target session page corresponding to the target function. For the same account information, when entering the target function through any entrance, the session identifiers corresponding to each entrance are the same, that is, the session identifiers assigned to each entrance of the same account information are consistent.

[0076] After determining the target jump strategy for the entry, the account information of the current entry is determined by retrieving the login information of the application client, and then the session identifier matching the account information of the current entry can be pulled from the target function in combination with the target jump strategy.

[0077] Step S3032: Determine session link information for the target function according to the session identifier.

[0078] The session link information is a jump link generated when jumping from the current entry to the target function. Specifically, after determining the session identifier that matches the entry, the session link information is assembled through the session identifier in combination with the protocol supported by the application client.

[0079] The session link information may be application link information Applink, web page link information (such as H5link), or in-terminal link information (such as H5Applink), etc., which is not specifically limited here.

[0080] Step S3033: jump to the target session page corresponding to the target function according to the target jump strategy and the session link information.

[0081] The session link information points to the target session page corresponding to the target function. Combined with the target jump strategy, according to the session link information, you can jump directly from the current entrance to the target session page, or jump to the intermediate page first, and then jump from the intermediate page to the target session page according to the session link information.

[0082] For example, the target jump strategy corresponding to the web page entrance is the web page jump strategy. When a function request is initiated through the web page entrance, an intermediate page corresponding to the target function will pop up on the web page according to the web page jump strategy. Then, according to the web page entrance, the entry link of the web page entrance and the session identifier of the target function returned to the web page entrance are assembled into session link information, that is, a redirection request link for the target function is constructed. Then, the user can switch from the intermediate page to the target session page corresponding to the target function through the session link information.

[0083] In some optional embodiments, the above method may further include:

[0084] Step b1, detecting whether the session link information is established for the first time.

[0085] Step b2: when the session link information is constructed for the first time, the session link information is created based on the session identifier.

[0086] Step b3: when the session link information is not constructed for the first time, the session link information matching the session identifier is retrieved from the historical session link information.

[0087] As mentioned above, the session identifiers corresponding to the various entries of the same account information are the same. Although the session link information corresponding to the various entries may be different due to the communication protocols of the various entries, the session identifiers contained in the session connection information corresponding to the various entries are the same. As long as the session identifier remains unchanged, the session link information corresponding to the various entries of the same account information remains unchanged, that is, after the session link information is constructed for the first time, when entering the target session page corresponding to the target function again, it is sufficient to retrieve the corresponding session link information without repeated construction.

[0088] After obtaining the session identifier that matches the current entry, it is possible to detect whether there is session link information corresponding to the current entry based on the session identifier, that is, to detect whether the session link information is constructed for the first time. When there is no session link information containing the session identifier, it means that the session link information is constructed for the first time, and the session link information for the target function is assembled according to the session identifier. When there is session link information containing the session identifier, it means that the session link information is not constructed for the first time, and the historical session link information containing the session identifier can be retrieved to determine the session link information corresponding to the current entry from the historical session link information.

[0089] In the above implementation, since the session identifier is globally unique for the account information, by detecting whether the session link information is constructed for the first time, repeated construction of the session link information for the same account information is avoided, ensuring that the same account information can enter the same target session page, thereby improving the user experience of the target function.

[0090] In some optional implementation modes, the above method may further include: based on the entry position corresponding to the entry, displaying recommendation information matching the entry on the target session page.

[0091] The entry position is used to characterize the application function unit corresponding to the current entry. Specifically, an application usually has multiple function units, and each of the multiple function units can be provided with an entry for accessing the target function, so that each function unit can use the service provided by the target function according to actual needs.

[0092] The recommended information is the commonly used consulting information for each functional unit pre-built into the target function. Specifically, different functional units are used to provide different services, and the recommended information matches the functional unit where the current entry is located, that is, for different entry positions, after entering the target session page, the recommended information corresponding to the functional unit where the entry position is located will be displayed.

[0093] In the above implementation, corresponding recommendation information is displayed on the target session page in combination with the functional unit where the entrance is located, so that the content displayed on the target session page is more matched with the functional unit, which greatly improves the user experience.

[0094] The multi-scenario portal jump method provided by this embodiment determines the session identifier corresponding to the portal through account information, and constructs the session link information of the current portal for the target function in combination with the session identifier, thereby ensuring the uniqueness of the session link information corresponding to the same account information. By combining the session link information and the target jump strategy, the user jumps from the current portal to the target session page corresponding to the target function, thereby avoiding page jump errors and ensuring the accuracy of the jump from the current portal to the target function.

[0095] This embodiment takes the customer service function of the application client as an example to explain in detail the entrance jump method of the above multiple scenarios. The communication application client is pre-installed with a customer service system A in the early stage of release to realize the customer service function. In multiple scene entrances (such as H5 consultation entrance, client consultation entrance, and webview consultation entrance in the terminal), you can directly jump to the conversation page of the customer service system A through the URL link (Applink) supported by the communication application client.

[0096] like Figure 8 As shown in the figure, when the underlying customer service system A is migrated to the customer service system B in order to meet the efficiency of customer service problem solving, Applink needs to be adjusted due to the change of the underlying receiving system. The adjustment of Applink depends on the modification and release of the communication application client code. If the communication application client is not upgraded, it cannot enter the customer service system B to consult problems.

[0097] For the upgraded high-version client, since customer service system B is added with the release of the new client, there is no compatibility issue for the high-version client. At this time, a new Applink can be registered in the high-version client. By clicking the Applink, the high-version client can directly call customer service system B to obtain the customer service session ID and jump to the customer service session page corresponding to customer service system B, achieving the same effect as the original customer service system A. Fig. 9 shown.

[0098] For low-version clients, H5, and webview in the terminal, in order to avoid changes in various entrances of low-version clients, the front-end SDK or H5 intermediate page is set here to jump to the intermediate page of customer service system B, and each entrance can be connected to the target intermediate page. Therefore, the intermediate page is responsible for interacting with customer service system B to obtain the customer service session identification ID, and assembles the session link information containing the customer service session identification ID according to the protocol supported by the low-version client, and jumps to the Applink corresponding to customer service system B through the session link information, thereby entering the customer service session page corresponding to customer service system B.

[0099] like Fig. 9 As shown, for the H5 consultation entrance of the low-version client, the intermediate page parses the parameters carried by the H5 consultation entrance to obtain the customer service session identification ID corresponding to the H5 consultation entrance from the customer service system B, and combines the H5 link corresponding to the H5 consultation entrance with the customer service session identification ID to splice it into the session link information that jumps to the customer service system B, enters the customer service session page corresponding to the customer service system B through the session link information, and closes the intermediate page at the same time.

[0100] For the client consultation entrance and the in-end webview consultation entrance of the low-version client, the intermediate page parses the parameters carried by the client consultation entrance / in-end webview consultation entrance to obtain the customer service session identification ID corresponding to the client entrance / in-end webview consultation entrance from customer service system B, and combines the H5 Applink corresponding to the client entrance with the customer service session identification ID to splice it into the session link information that jumps to the customer service system B. Enter the customer service session page corresponding to the customer service system B through the session link information, and close the intermediate page at the same time.

[0101] It should be noted that the customer service session identification ID is globally unique for the same account, that is, for the same account, the customer service session identification IDs of various entrances are the same.

[0102] In this embodiment, a multi-scenario entry jump device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0103] This embodiment provides a multi-scenario entry jump device, such as Fig.10 As shown, including:

[0104] The parameter acquisition module 401 is used to receive a function request sent by any entry for a target function of an application program, and acquire request parameters corresponding to the function request.

[0105] The strategy determination module 402 is used to determine a target jump strategy that matches the entry based on the request parameters.

[0106] The jump module 403 is used to jump from the entrance to the target session page corresponding to the target function according to the target jump strategy.

[0107] In some optional implementation modes, the above-mentioned policy determination module 402 may include:

[0108] The parsing unit is used to parse the request parameters and determine the request source carried by the request parameters.

[0109] The matching unit is used to determine a target jump strategy that matches the entry according to the request source.

[0110] In some optional implementation modes, the target jump strategy includes a direct jump strategy and a diversion jump strategy. Accordingly, the matching unit may include:

[0111] The detection subunit is used to detect whether the version of the client is lower than the version supported by the target function when the request source is the client entry.

[0112] The first matching subunit is used to determine that the target jump strategy matched by the entry is a direct jump strategy when the version of the client is equal to or higher than the version supported by the target function.

[0113] The second matching sub-unit is used to determine that the target jump strategy matching the entrance is a diversion jump strategy when the client version is lower than the version supported by the target function. The diversion jump strategy is used to jump to the middle page of the target session page to enter the target session page through the middle page.

[0114] In some optional embodiments, the matching unit may further include:

[0115] The strategy generation subunit is used to generate a diversion jump strategy based on the session information in response to the session information generated on the client's session page when the request source is an in-end entrance and the client version is lower than the version supported by the target function.

[0116] In some optional implementation modes, the target jump strategy may further include a web page jump strategy. Accordingly, the matching unit may further include:

[0117] The third matching subunit is used to determine the target jump strategy matching the web page entrance as the web page jump strategy when the request source is a web page entrance. The web page jump strategy is used to jump to the web page middle page of the target session page to enter the target session page through the web page middle page.

[0118] In some optional implementation modes, the jump module 403 may include:

[0119] The identification acquisition unit is used to determine the session identification matching the entry based on the account information corresponding to the entry.

[0120] The link generation unit is used to determine session link information for a target function according to the session identifier.

[0121] The page jump unit is used to jump to the target session page corresponding to the target function according to the target jump strategy and session link information.

[0122] In some optional embodiments, the above device may further include:

[0123] The link detection unit is used to detect whether the session link information is established for the first time.

[0124] The link creation unit is used to create the session link information based on the session identifier when the session link information is constructed for the first time.

[0125] The link retrieving unit is used to retrieve the session link information matching the session identifier from the historical session link information when the session link information is not constructed for the first time.

[0126] In some optional embodiments, the above device may further include:

[0127] The recommendation information display module is used to display the recommendation information matching the entrance on the target session page based on the entrance position corresponding to the entrance.

[0128] The further functional description of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0129] The multi-scenario entry jump device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0130] The multi-scenario entry jump device provided in this embodiment obtains the function request initiated by any entry and parses the request parameters carried by the function request to determine the target jump strategy that matches the current entry, and directly jumps to the target function according to the target jump strategy, avoiding the forwarding logic of the function request, so there is no need to deal with the logical problems existing in the request forwarding process. Entering the target session page corresponding to the target function through the corresponding target jump strategy can be compatible with the flexible jump from multiple scene entries to the target function, thereby improving the user experience of the application.

[0131] The present disclosure also provides a computer device having the above Fig.10 The entry jump device of multiple scenes is shown.

[0132] See also Fig.11 , Fig.11 is a schematic diagram of a computer device provided by an optional embodiment of the present disclosure, such as Fig.11 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Fig.11 A processor 10 is taken as an example.

[0133] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0134] The memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0135] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0136] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0137] The computer device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Fig.11 The example of connecting through bus is taken in the following.

[0138] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0139] The computer device also includes a communication interface, which is used for the computer device to communicate with other devices or a communication network.

[0140] The embodiments of the present disclosure also provide a computer-readable storage medium. The above-mentioned method according to the embodiments of the present disclosure can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium and downloaded through a network, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0141] Although the embodiments of the present disclosure have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present disclosure, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A multi-scenario entry jump method, It is characterized in that The method comprises: Receive a function request issued by any entry for a target function of an application, and obtain request parameters corresponding to the function request; Based on the request parameters, determining a target jump strategy that matches the entry; Jump from the entrance to the target session page corresponding to the target function according to the target jump strategy.

2. The method according to claim 1, It is characterized in that The determining, based on the request parameter, a target jump strategy matching the entry, comprises: Parsing the request parameters to determine the request source carried by the request parameters; A target jump strategy matching the entry is determined according to the request source.

3. The method according to claim 2, It is characterized in that The target jump strategy includes a direct jump strategy and a diversion jump strategy. The target jump strategy that matches the entry is determined according to the request source, including: When the request source is a client entry, detecting whether the client version is lower than the version supported by the target function; When the version of the client is equal to or higher than the version supported by the target function, determining that the target jump strategy matching the entry is a direct jump strategy; When the version of the client is lower than the version supported by the target function, the target jump strategy matching the entry is determined to be a diversion jump strategy, and the diversion jump strategy is used to jump to the intermediate page of the target session page to enter the target session page through the intermediate page.

4. The method according to claim 3, It is characterized in that Also includes: When the request source is an in-end entry and the version of the client is lower than the version supported by the target function, the traffic redirection strategy is generated based on the session information generated on the session page of the client.

5. The method according to claim 3, It is characterized in that The target jump strategy also includes a web page jump strategy, and the target jump strategy that matches the target entry is determined according to the request source, and further includes: When the request source is a web page entrance, the target jump strategy matching the web page entrance is determined as the web page jump strategy, and the web page jump strategy is used to jump to the web page middle page of the target session page to enter the target session page through the web page middle page.

6. The method according to claim 1, It is characterized in that The step of jumping from the entrance to a target session page corresponding to the target function according to the target jump strategy includes: Determining a session identifier that matches the entry based on the account information corresponding to the entry; Determining session link information for the target function according to the session identifier; Jump to the target session page corresponding to the target function according to the target jump strategy and the session link information.

7. The method according to claim 6, It is characterized in that Also includes: Detecting whether the session link information is established for the first time; When the session link information is constructed for the first time, creating the session link information based on the session identifier; When the session link information is not constructed for the first time, the session link information matching the session identifier is retrieved from the historical session link information.

8. The method according to claim 6, It is characterized in that After jumping from the entrance to the target session page corresponding to the target function according to the target jump strategy, the method further includes: Based on the entry position corresponding to the entry, recommendation information matching the entry is displayed on the target session page.

9. A multi-scene entry jump device, It is characterized in that The device comprises: A parameter acquisition module, used to receive a function request issued by any entry for a target function of an application, and obtain request parameters corresponding to the function request; A strategy determination module, used to determine a target jump strategy matching the entry based on the request parameters; A jump module is used to jump from the entrance to a target session page corresponding to the target function according to the target jump strategy.

10. A computer device, It is characterized in that include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the multi-scenario entry jump method according to any one of claims 1 to 8 by executing the computer instructions.

11. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the multi-scenario entry jump method according to any one of claims 1 to 8.

Images