CN113691455A - Routing scheduling method, device, equipment and readable storage medium - Google Patents

Routing scheduling method, device, equipment and readable storage medium Download PDF

Info

Publication number
CN113691455A
CN113691455A CN202111251918.XA CN202111251918A CN113691455A CN 113691455 A CN113691455 A CN 113691455A CN 202111251918 A CN202111251918 A CN 202111251918A CN 113691455 A CN113691455 A CN 113691455A
Authority
CN
China
Prior art keywords
sub
application
routing
routing information
route
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
Application number
CN202111251918.XA
Other languages
Chinese (zh)
Other versions
CN113691455B (en
Inventor
廖宏军
刘小双
欧馨
周雷
王宗强
许琦枫
赵一波
陈军
冯建设
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Xinrun Fulian Digital Technology Co Ltd
Original Assignee
Shenzhen Xinrun Fulian Digital Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shenzhen Xinrun Fulian Digital Technology Co Ltd filed Critical Shenzhen Xinrun Fulian Digital Technology Co Ltd
Priority to CN202111251918.XA priority Critical patent/CN113691455B/en
Publication of CN113691455A publication Critical patent/CN113691455A/en
Application granted granted Critical
Publication of CN113691455B publication Critical patent/CN113691455B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/02Topology update or discovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00Routing or path finding of packets in data switching networks
    • H04L45/14Routing performance; Theoretical aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/02Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The application discloses a method, a device, equipment and a readable storage medium for routing scheduling, wherein the method comprises the following steps: monitoring current routing information and acquiring sub-routing information corresponding to routing information change; determining a sub-routing identification string corresponding to the sub-routing information according to a preset identification string relation table; according to the sub-route information and the sub-route identification string, changing the route of the main application to obtain a main route; determining a target sub-application corresponding to the main route, and jumping to the target sub-application; by the method, the sub-routing information which generates the routing information change is monitored in real time, the sub-routing information is analyzed, the sub-routing identification string of the sub-routing is obtained, the main routing can be changed according to the respective sub-routing information and the sub-routing identification string, the accurate target sub-application is obtained, the target sub-application is opened by scheduling the sub-routing information independent identification string, the independence of the sub-application routing scheduling is realized, and the routing conflict problem is avoided.

Description

Routing scheduling method, device, equipment and readable storage medium
Technical Field
The present application relates to the field of computer network technologies, and in particular, to a method, an apparatus, a device, and a readable storage medium for routing scheduling.
Background
In the current web platform website system of medium and small enterprises, when one web platform website integrates a plurality of different small micro front-end service applications, a plurality of front-end teams develop the web platform website by adopting a main application which does not process the route at all (the main application does not schedule sub-routes according to the route, and the internal state change of the sub-applications is reflected to the main routing system as the original state). The main application does not process the route, and the main application does not generate an effect when the route is carried into the page, but enters an initial state, so that when the interior of the sub-application is changed, the system cannot locate the route belonging to which micro task, and further when the main application jumps to the sub-application according to the route, other sub-applications corresponding to the same route can be opened, and therefore, the problem of route conflict is generated during route scheduling.
Disclosure of Invention
The present application mainly aims to provide a method, an apparatus, a device and a readable storage medium for routing scheduling, and aims to solve the technical problem of routing scheduling conflict in micro front-end development.
In order to achieve the above object, the present application provides a routing scheduling method, including:
monitoring current routing information and acquiring sub-routing information corresponding to routing information change;
determining a sub-routing identification string corresponding to the sub-routing information according to a preset identification string relation table;
according to the sub-route information and the sub-route identification string, changing the route of the main application to obtain a main route;
and determining a target sub-application corresponding to the main route, and jumping to the target sub-application, wherein the main application comprises at least one sub-application.
Optionally, the step of monitoring the current routing information and obtaining the sub-routing information corresponding to the change of the routing information includes:
monitoring current routing information according to a preset function, and notifying the routing information change and sub-routing information corresponding to the routing information change to a main application when the current routing information is monitored to have the routing information change;
such that the primary application receives the routing information change and the sub-routing information.
Optionally, before the step of determining the sub-routing identifier string corresponding to the sub-routing information according to the preset identifier string relationship table, the method includes:
acquiring original sub-routing information of the sub-application, and marking an original service identification string corresponding to the original sub-routing information;
and creating an identification string relation table according to the sub-application name corresponding to at least one sub-application, the original sub-routing information and the original service identification string.
Optionally, the step of determining, according to a preset identifier string relationship table, a sub-route identifier string corresponding to the sub-route information includes:
acquiring an identification string relation table;
and determining a sub-routing identification string corresponding to the sub-routing information according to the sub-routing information and the identification string relation table.
Optionally, the step of determining a target sub-application corresponding to the main route and jumping to the target sub-application includes:
determining the target sub-application corresponding to the main route according to the identification string relation table;
judging whether the current running sub-application is consistent with the target sub-application;
if not, the main route is scheduled to open the interface of the target sub-application.
Optionally, after the step of determining whether the currently running current sub-application is consistent with the target sub-application, the method includes:
if so, after the current sub application is closed, jumping to the interface of the target sub application.
Optionally, after the step of determining a target sub-application corresponding to the main route and jumping to the target sub-application, the method includes:
and acquiring a target storage space corresponding to a target sub-application, wherein the internal state change of the target sub-application is stored in the target storage space.
In order to achieve the above object, the present invention provides a routing scheduling apparatus, including:
the monitoring module monitors the current routing information and acquires sub-routing information corresponding to the routing information change;
the determining module is used for determining a sub-routing identification string corresponding to the sub-routing information according to a preset identification string relation table;
the change module is used for changing the route of the main application according to the sub-route information and the sub-route identification string to obtain a main route;
and the skipping module is used for determining a target sub-application corresponding to the main route and skipping to the target sub-application, wherein the main application comprises at least one sub-application.
In addition, to achieve the above object, the present application also provides a routing scheduling apparatus, which includes a memory, a processor, and a routing scheduler stored in the memory and operable on the processor, and when executed by the processor, the routing scheduler implements the steps of the routing scheduling method as described above.
In addition, to achieve the above object, the present application also provides a computer readable storage medium, which stores a routing scheduler program, and when the routing scheduler program is executed by a processor, the routing scheduler program implements the steps of the routing scheduling method as described above.
Compared with the routing scheduling conflict in the micro front-end development in the prior art, the method and the system have the advantages that the sub-routing information corresponding to the routing information change is obtained by monitoring the current routing information; determining a sub-routing identification string corresponding to the sub-routing information according to a preset identification string relation table; according to the sub-route information and the sub-route identification string, changing the route of the main application to obtain a main route; determining a target sub-application corresponding to the main route, and jumping to the target sub-application, wherein the main application comprises at least one sub-application; by the method, the sub-routing information which generates the routing information change is monitored in real time, the sub-routing information is analyzed, the sub-routing identification string of the sub-routing is obtained, the main routing can be changed according to the respective sub-routing information and the sub-routing identification string, the accurate target sub-application is obtained, the target sub-application is opened by scheduling the sub-routing information independent identification string, the independence of the sub-application routing scheduling is realized, and the routing conflict problem is avoided.
Drawings
Fig. 1 is a schematic flow chart of a first embodiment of a routing scheduling method according to the present application;
FIG. 2 is a functional block diagram of a preferred embodiment of the routing scheduler of the present application;
fig. 3 is a schematic structural diagram of a hardware operating environment according to an embodiment of the present application.
The implementation, functional features and advantages of the objectives of the present application will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
Referring to fig. 1, fig. 1 is a schematic flowchart of a first embodiment of a routing scheduling method according to the present application.
The present application provides an embodiment of a routing scheduling method, and it should be noted that although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in an order different from that here. The route scheduling method can be applied to a program module for route scheduling of an application server. For convenience of description, the execution of the body to describe each step of the route scheduling method is omitted below. The routing scheduling method comprises the following steps:
step S10, monitoring the current route information, and obtaining the sub-route information corresponding to the route information change;
step S20, determining a sub-route identification string corresponding to the sub-route information according to a preset identification string relation table;
step S30, according to the sub-route information and the sub-route identification string, changing the route of the main application to obtain the main route;
step S40, determining a target sub-application corresponding to the main route, and jumping to the target sub-application, wherein the main application includes at least one sub-application.
The method comprises the following specific steps:
step S10, monitoring the current route information, and obtaining the sub-route information corresponding to the route information change;
in this embodiment, it should be noted that the route scheduling method may be applied to a route scheduling apparatus, where the route scheduling apparatus belongs to a route scheduling system, and the route scheduling system belongs to a route scheduling device.
In this embodiment, the specific application scenarios may be: in the current web platform website system of medium and small enterprises, when one web platform website integrates a plurality of different small micro front-end service applications, a plurality of front-end teams develop the web platform website by adopting a main application which does not process the route at all (the main application does not schedule sub-routes according to the route, and the internal state change of the sub-applications is reflected to the main routing system as the original state). The main application does not process the route, and the main application does not generate an effect when the route is carried into the page, but enters an initial state, so that when the interior of the sub-application is changed, the system cannot locate the route belonging to which micro task, and further when the main application jumps to the sub-application according to the route, other sub-applications corresponding to the same route can be opened, and therefore, the problem of route conflict is generated during route scheduling.
In this embodiment, it should be noted that the micro front end refers to that an application program is designed into a series of loosely-coupled fine-grained services, and is organized through a lightweight communication protocol, that is, an application is constructed into a group of small services, and the micro front end belongs to a front end architecture. A web platform comprises a plurality of micro front ends, the micro front ends correspond to micro front end applications, namely main applications, and the main applications comprise at least one sub application. Jumping or opening the main application and the sub-application requires routing scheduling, which is implemented by a routing configuration module in the system.
In some scenarios, the main sub-application (main application and sub-application) is developed and designed by different personnel, so that names of the sub-applications in the main application may be consistent, and therefore, when the main sub-application (main application and sub-application) is opened according to a website, routing information in the website which may be recognized is consistent, so that a wrong sub-application is opened, and therefore, a certain identifier needs to be set for different sub-applications, and the problem of routing conflict is avoided.
In this embodiment, current routing information of the system is monitored, where the current routing information refers to real-time routing information in routing scheduling of the current system, and when the current routing information changes, corresponding sub-routing information that causes the routing to change is obtained, and the sub-routing information is analyzed, where the sub-routing information includes a sub-application name, and a corresponding sub-application is determined according to the sub-routing information. It can be understood that when a user clicks a certain sub-application or inputs a website of a certain sub-application, that is, when the micro service interface is operated, a sub-route and information corresponding to the sub-route are generated, and in a process of changing from current routing information to sub-route information, that is, a process of changing routing information, a current system has changed routing information. At this time, the route configuration module analyzes the sub-route information to obtain the sub-application route, so that the main application opens the sub-application according to the sub-application route.
Wherein, monitoring the current routing information and obtaining the sub-routing information corresponding to the routing information change, comprising the following steps of S11-S12:
step S11, monitoring the current routing information according to the preset function, and when the current routing information is monitored to have the routing information change, notifying the routing information change and the sub-routing information corresponding to the routing information change to the main application;
step S12, so that the master application receives the routing information change and the sub-routing information.
In this embodiment, the sub-application currently running in the system monitors the current routing information, and checks whether the current routing information changes through the core function isTurnChild and some functions of the current application. If the current routing information has the routing information change, notifying the main application of the routing information change, wherein the routing information change can be signal information, and when the current routing information changes, sending the routing information change to the main application; the change of the routing information may also be a change operation, which changes the current routing information into the sub-routing information. And sending the micro service interface operation information (routing information change and sub-routing information corresponding to the routing information change) to the main application through API frame. The code that implements this process is, for example:
Figure 282325DEST_PATH_IMAGE001
the main application side receives the routing information change and the sub-routing information and acquires the message from the micro-service through the cross-window communication API frame. And the subsequent main application changes the route thereof according to the sub-route information and schedules the route of the target sub-application. The code that implements this process is, for example:
Figure 901525DEST_PATH_IMAGE002
further, before listening to the current routing information, the following step S13 is included:
step S13, changing the global event state, and patching the main application route;
in this embodiment, the global event state is changed, and the host application route is patched, so that the route monitoring states of some browsers are manually taken over, and accurate monitoring, operation and distribution of sub-routes are facilitated. In the patching process, a custom event is created, the default event of the browser is taken over, error abnormity is prevented, and routing information change is completely controlled by an engineer and is far away from the default control of the browser. The code that implements this process is, for example:
Figure 230876DEST_PATH_IMAGE003
step S20, determining a sub-route identification string corresponding to the sub-route information according to a preset identification string relation table;
in this embodiment, the preset identifier string relationship table includes sub-routing information and a sub-routing identifier string, a uniquely corresponding sub-routing identifier string may be obtained from the identifier string relationship table according to the sub-routing information, and a key operation of a sub-application corresponding to the sub-routing information is identified when the sub-routing identifier string is executed. It can be understood that one main application corresponds to at least one sub-application, the sub-application routes in one sub-application are set differently during development, but since different sub-applications may be developed by different persons, the name settings of the sub-application routes may be the same, and when identifying the sub-route information, a jump may be made to the wrong sub-application. Therefore, different sub-routing identification strings need to be set for the sub-routing information in the sub-application, so that the sub-routing information and the sub-routing identification strings are unique in the main application, and the problem of routing conflict is avoided.
Wherein, according to the preset identification string relation table, before determining the sub-route identification string corresponding to the sub-route information, the following steps S21-S22 are included:
step S21, obtaining the original sub-route information of the sub-application, and marking the original service identification string corresponding to the original sub-route information;
step S22, creating an identifier string relation table according to the sub-application name, the original sub-routing information, and the original service identifier string corresponding to at least one of the sub-applications.
In this embodiment, the original sub-routing information refers to all routing information of at least one sub-application in the main application, and the sub-routing information includes a name of the sub-application. The developed sub-applications and all the corresponding routing information of the sub-applications are marked with unique original service identification strings, and the independent original service identification strings can distinguish different sub-routing information. It should be noted that different sub-routing information corresponds to a unique original service identification string, and different sub-applications correspond to respective sub-routing information, so that an identification string relation table is established according to the name of the sub-application, the original sub-routing information, and the original service identification string. In the identification string relation table, an original service identification string uniquely corresponding to the original sub-routing information can be searched/matched according to the original sub-routing information, and a corresponding sub-application name can be searched/matched according to the original service identification string and the original sub-routing information. The code that implements this procedure is for example (APP _ NAME sets the service identification string of the microservice):
Figure 757672DEST_PATH_IMAGE004
further, determining a sub-route identification string corresponding to the sub-route information according to a preset identification string relation table, including the following steps S23-S24:
step S23, obtaining an identification string relation table;
step S24, determining a sub-routing identification string corresponding to the sub-routing information according to the sub-routing information and the identification string relation table.
In this embodiment, the identification string relationship table is obtained, the sub-routing information is input, the first original sub-routing information corresponding to the sub-routing information is obtained in the identification string relationship table, and the uniquely determined first original service identification string is obtained according to the first original sub-routing information, where the first original service identification string is also the sub-routing identification string corresponding to the sub-routing information.
Step S30, according to the sub-route information and the sub-route identification string, changing the route of the main application to obtain the main route;
in this embodiment, when the main application receives the route information change and acquires the sub-route information, the route of the main application is modified according to the route function and the sub-route information, so as to obtain the main route. The routing function is used for processing and changing the route and collecting route related data, and the current routing information in the route of the main application and the identification string corresponding to the current routing information are changed into the sub-routing information and the corresponding sub-routing identification string through the routing function, so that the main route is obtained.
The code that implements this process is, for example:
Figure 715964DEST_PATH_IMAGE005
step S40, determining a target sub-application corresponding to the main route, and jumping to the target sub-application, wherein the main application includes at least one sub-application.
In this embodiment, a target sub-application corresponding to a main route is found and determined according to the main route or the name, and the main application jumps to the target sub-application through micro-service.
The code that implements this process is, for example:
Figure 709328DEST_PATH_IMAGE006
wherein, determining a target sub-application corresponding to the main route, and jumping to the target sub-application, comprises the following steps S41-S43:
step S41, determining the target sub-application corresponding to the main route according to the identification string relation table;
step S42, judging whether the current running sub-application is consistent with the target sub-application;
and step S43, if not, scheduling the main route to open the interface of the target sub-application.
In this embodiment, since the sub-routing information includes the name of the sub-application, the target sub-application corresponding to the sub-routing information can be determined according to the identifier string relation table, that is, the target sub-application is a sub-application scheduled according to the changed main route. And if the target sub-application is not the current sub-application, opening/jumping to an interface of the target sub-application according to the scheduling sub-route by the route configuration module. It should be noted that, in the process of jumping to the target sub-application, the current sub-application is closed, and the system deletes the current sub-application, so as to avoid that memory data is leaked when the current sub-application is not deleted, which may cause a browser or an operating platform to crash due to excessive data for a long time.
Further, if the target sub-application is the current sub-application, no change to the main route is required.
The code that implements this process is, for example:
Figure 791553DEST_PATH_IMAGE007
the routing scheduling method of the embodiment comprises the following steps: monitoring current routing information and acquiring sub-routing information corresponding to routing information change; determining a sub-routing identification string corresponding to the sub-routing information according to a preset identification string relation table; according to the sub-route information and the sub-route identification string, changing the route of the main application to obtain a main route; determining a target sub-application corresponding to the main route, and jumping to the target sub-application, wherein the main application comprises at least one sub-application; by the method, the sub-routing information which generates the routing information change is monitored in real time, the sub-routing information is analyzed, the sub-routing identification string of the sub-routing is obtained, the main routing can be changed according to the respective sub-routing information and the sub-routing identification string, the accurate target sub-application is obtained, the target sub-application is opened by scheduling the sub-routing information independent identification string, the independence of the sub-application routing scheduling is realized, and the routing conflict problem is avoided.
In some embodiments, if the sub-application is cow, when a user clicks a home page defining a route name/home, a link click event is intercepted by default, a route matching function is triggered, and a pushState is matched. When the child application cow/home interface is matched, the pushState is modified to be/home, the iframe URL is modified to be/home, the current child application URL is notified to be/home, the URL of the main application is updated, at the moment, the URL becomes/cow/home, and the system returns to the home page of the cow application.
Second embodiment
Based on the first implementation, a second embodiment of the routing scheduling method of the present application is provided. In this embodiment, the routing scheduling method further includes:
step S50, obtaining a target storage space corresponding to a target sub-application, where the internal state change of the target sub-application is stored in the target storage space.
In this embodiment, the main application corresponds to a plurality of sub-applications, and in order to facilitate the main application to issue data or the sub-applications to store data, respective storage spaces need to be set for the sub-applications. And the main application schedules the target sub-application according to the main route and simultaneously obtains a target storage space corresponding to the target sub-application, and the internal state change of the target sub-application is stored in the storage space, so that the data of each sub-application are not interfered with each other, and the side effect on the global context is isolated when the sub-application generates the route.
Further, before obtaining the target storage space corresponding to the target sub-application, the method includes the following steps S51:
step S51, obtaining the sub-application name in the sub-routing information, establishing the storage space corresponding to the sub-application name,
in this embodiment, a corresponding storage space is created according to the name of the sub-application, data related to the sub-application is stored in the storage space, and when the sub-application searches for the data, the data is only searched in the corresponding storage space. It should be noted that the storage space may be a sandbox of each sub-application, and it can be understood that the main application schedules the sub-applications according to the routing, and state changes inside the sub-applications are reflected in the respective sandboxes without interfering with each other.
Third embodiment
The present application further provides a routing scheduling apparatus, referring to fig. 2, the routing scheduling apparatus includes:
the monitoring module 10 monitors the current routing information to obtain sub-routing information corresponding to the routing information change;
the determining module 20 determines a sub-routing identifier string corresponding to the sub-routing information according to a preset identifier string relation table;
a change module 30, changing the route of the main application according to the sub-route information and the sub-route identification string to obtain a main route;
and the skipping module 40 determines a target sub-application corresponding to the main route, and skips to the target sub-application, wherein the main application comprises at least one sub-application.
Optionally, the listening module 10 includes:
the monitoring submodule monitors current routing information according to a preset function, and when the current routing information is monitored to have routing information change, the monitoring submodule informs the routing information change and sub-routing information corresponding to the routing information change to a main application;
a receiving submodule, such that the primary application receives the routing information change and the sub-routing information.
Optionally, the routing scheduling apparatus further includes:
the marking module is used for acquiring original sub-routing information of the sub-application and marking an original service identification string corresponding to the original sub-routing information;
and the creating module is used for creating an identification string relation table according to the sub-application name corresponding to at least one sub-application, the original sub-routing information and the original service identification string.
Optionally, the determining module 20 includes:
the obtaining submodule obtains an identification string relation table;
and the first determining submodule determines the sub-routing identification string corresponding to the sub-routing information according to the sub-routing information and the identification string relation table.
Optionally, the skip module 40 includes:
the second determining sub-module determines the target sub-application corresponding to the main route according to the identification string relation table;
the judgment submodule judges whether the current running sub-application is consistent with the target sub-application or not;
and if not, scheduling the main route to open the interface of the target sub-application.
Optionally, the skip module 40 further includes:
and if so, turning to the interface of the target sub application after closing the current sub application.
Optionally, the routing scheduling apparatus further includes:
the storage module is used for acquiring a target storage space corresponding to a target sub-application, and the internal state change of the target sub-application is stored in the target storage space.
In addition, the application also provides a routing scheduling device. As shown in fig. 3, fig. 3 is a schematic structural diagram of a hardware operating environment according to an embodiment of the present application.
It should be noted that fig. 3 is a schematic structural diagram of a hardware operating environment of the routing scheduling apparatus.
As shown in fig. 3, the route scheduling apparatus may include: a processor 1001, such as a CPU, a memory 1005, a user interface 1003, a network interface 1004, a communication bus 1002. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a storage device separate from the processor 1001.
Optionally, the routing scheduling device may further include an RF (Radio Frequency) circuit, a sensor, an audio circuit, a WiFi module, and the like.
Those skilled in the art will appreciate that the routing scheduling device architecture shown in fig. 3 does not constitute a limitation of the routing scheduling device and may include more or fewer components than shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 3, a memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a routing scheduler. The operating system is a program for managing and controlling the hardware and software resources of the routing scheduling device, and supports the operation of the routing scheduling program and other software or programs.
In the routing scheduling apparatus shown in fig. 3, the user interface 1003 is mainly used for connecting a terminal and performing data communication with the terminal, such as receiving user signaling data sent by the terminal; the network interface 1004 is mainly used for the background server and performs data communication with the background server; the processor 1001 may be configured to invoke a routing scheduler stored in the memory 1005 and perform the steps of the routing scheduling method as described above.
The specific implementation of the route scheduling device of the present application is substantially the same as that of each embodiment of the route scheduling method, and is not described herein again.
Furthermore, an embodiment of the present application also provides a computer-readable storage medium, where a routing scheduler is stored on the computer-readable storage medium, and the routing scheduler, when being executed by a processor, implements the steps of the routing scheduling method as described above.
The specific implementation manner of the computer-readable storage medium of the present application is substantially the same as that of each embodiment of the routing scheduling method, and is not described herein again.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, a device, or a network device) to execute the method according to the embodiments of the present application.
The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application, or which are directly or indirectly applied to other related technical fields, are included in the scope of the present application.

Claims (10)

1. A route scheduling method, characterized in that the route scheduling method comprises the following steps:
monitoring current routing information and acquiring sub-routing information corresponding to routing information change;
determining a sub-routing identification string corresponding to the sub-routing information according to a preset identification string relation table;
according to the sub-route information and the sub-route identification string, changing the route of the main application to obtain a main route;
and determining a target sub-application corresponding to the main route, and jumping to the target sub-application, wherein the main application comprises at least one sub-application.
2. The routing scheduling method of claim 1, wherein the step of monitoring the current routing information and obtaining the sub-routing information corresponding to the routing information change comprises:
monitoring current routing information according to a preset function, and notifying the routing information change and sub-routing information corresponding to the routing information change to a main application when the current routing information is monitored to have the routing information change;
such that the primary application receives the routing information change and the sub-routing information.
3. The routing scheduling method of claim 1, wherein before the step of determining the sub-routing identifier string corresponding to the sub-routing information according to a preset identifier string relationship table, the method comprises:
acquiring original sub-routing information of the sub-application, and marking an original service identification string corresponding to the original sub-routing information;
and creating an identification string relation table according to the sub-application name corresponding to at least one sub-application, the original sub-routing information and the original service identification string.
4. The routing scheduling method of claim 1, wherein the step of determining the sub-routing identifier string corresponding to the sub-routing information according to a preset identifier string relationship table comprises:
acquiring an identification string relation table;
and determining a sub-routing identification string corresponding to the sub-routing information according to the sub-routing information and the identification string relation table.
5. The routing scheduling method of claim 1, wherein the step of determining a target sub-application corresponding to the main route and jumping to the target sub-application comprises:
determining the target sub-application corresponding to the main route according to the identification string relation table;
judging whether the current running sub-application is consistent with the target sub-application;
if not, the main route is scheduled to open the interface of the target sub-application.
6. The route scheduling method according to claim 5, wherein after the step of determining whether the currently running current sub-application is consistent with the target sub-application, the method comprises:
if so, after the current sub application is closed, jumping to the interface of the target sub application.
7. The routing scheduling method according to claim 1, wherein after the step of determining the target sub-application corresponding to the main route and jumping to the target sub-application, the method comprises:
and acquiring a target storage space corresponding to a target sub-application, wherein the internal state change of the target sub-application is stored in the target storage space.
8. An apparatus for routing, the apparatus comprising:
the monitoring module monitors the current routing information and acquires sub-routing information corresponding to the routing information change;
the determining module is used for determining a sub-routing identification string corresponding to the sub-routing information according to a preset identification string relation table;
the change module is used for changing the route of the main application according to the sub-route information and the sub-route identification string to obtain a main route;
and the skipping module is used for determining a target sub-application corresponding to the main route and skipping to the target sub-application, wherein the main application comprises at least one sub-application.
9. A route scheduling device, characterized in that the route scheduling device comprises a memory, a processor and a route scheduler stored on the memory and operable on the processor, which when executed by the processor implements the steps of the route scheduling method according to any of claims 1 to 7.
10. A computer-readable storage medium, characterized in that a routing scheduler is stored on the computer-readable storage medium, which when executed by a processor implements the steps of the routing scheduling method according to any of claims 1 to 7.
CN202111251918.XA 2021-10-27 2021-10-27 Routing scheduling method, device, equipment and readable storage medium Active CN113691455B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111251918.XA CN113691455B (en) 2021-10-27 2021-10-27 Routing scheduling method, device, equipment and readable storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111251918.XA CN113691455B (en) 2021-10-27 2021-10-27 Routing scheduling method, device, equipment and readable storage medium

Publications (2)

Publication Number Publication Date
CN113691455A true CN113691455A (en) 2021-11-23
CN113691455B CN113691455B (en) 2022-02-15

Family

ID=78588250

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111251918.XA Active CN113691455B (en) 2021-10-27 2021-10-27 Routing scheduling method, device, equipment and readable storage medium

Country Status (1)

Country Link
CN (1) CN113691455B (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114401320A (en) * 2021-12-14 2022-04-26 杭州趣链科技有限公司 Sub-application access method, system, block chain platform, gateway and storage medium
CN114661375A (en) * 2022-03-24 2022-06-24 阿里云计算有限公司 Application integration method and device
CN114844820A (en) * 2022-04-28 2022-08-02 四川虹魔方网络科技有限公司 Route data processing and skipping implementation method based on heaven and earth micro front end

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100318679A1 (en) * 2009-06-16 2010-12-16 Lavoie Jason Dana Method and system for content-based routing of network traffic
WO2017050146A1 (en) * 2015-09-21 2017-03-30 阿里巴巴集团控股有限公司 Loading method and device for terminal application (app)
US20190281189A1 (en) * 2014-06-24 2019-09-12 Ec Data Systems Inc. Audit logging for a secure, scalable and flexible internet fax architecture
CN110650091A (en) * 2019-08-14 2020-01-03 平安普惠企业管理有限公司 Routing configuration information processing method and device, computer equipment and storage medium
CN112217731A (en) * 2020-10-16 2021-01-12 青岛海尔科技有限公司 Target application generation method and device and storage medium
CN112748962A (en) * 2021-01-22 2021-05-04 北京五八信息技术有限公司 Application loading method and device, electronic equipment and computer readable medium
CN112948035A (en) * 2021-01-29 2021-06-11 北京高途云集教育科技有限公司 Method and device for controlling micro front-end page, terminal equipment and storage medium
CN113419817A (en) * 2021-06-22 2021-09-21 康键信息技术(深圳)有限公司 Front-end application nesting method, device, equipment and storage medium

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100318679A1 (en) * 2009-06-16 2010-12-16 Lavoie Jason Dana Method and system for content-based routing of network traffic
US20190281189A1 (en) * 2014-06-24 2019-09-12 Ec Data Systems Inc. Audit logging for a secure, scalable and flexible internet fax architecture
WO2017050146A1 (en) * 2015-09-21 2017-03-30 阿里巴巴集团控股有限公司 Loading method and device for terminal application (app)
CN110650091A (en) * 2019-08-14 2020-01-03 平安普惠企业管理有限公司 Routing configuration information processing method and device, computer equipment and storage medium
CN112217731A (en) * 2020-10-16 2021-01-12 青岛海尔科技有限公司 Target application generation method and device and storage medium
CN112748962A (en) * 2021-01-22 2021-05-04 北京五八信息技术有限公司 Application loading method and device, electronic equipment and computer readable medium
CN112948035A (en) * 2021-01-29 2021-06-11 北京高途云集教育科技有限公司 Method and device for controlling micro front-end page, terminal equipment and storage medium
CN113419817A (en) * 2021-06-22 2021-09-21 康键信息技术(深圳)有限公司 Front-end application nesting method, device, equipment and storage medium

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114401320A (en) * 2021-12-14 2022-04-26 杭州趣链科技有限公司 Sub-application access method, system, block chain platform, gateway and storage medium
CN114661375A (en) * 2022-03-24 2022-06-24 阿里云计算有限公司 Application integration method and device
CN114844820A (en) * 2022-04-28 2022-08-02 四川虹魔方网络科技有限公司 Route data processing and skipping implementation method based on heaven and earth micro front end
CN114844820B (en) * 2022-04-28 2023-11-21 四川虹魔方网络科技有限公司 Method for processing route data and implementing skip based on heaven and earth micro front end

Also Published As

Publication number Publication date
CN113691455B (en) 2022-02-15

Similar Documents

Publication Publication Date Title
CN113691455B (en) Routing scheduling method, device, equipment and readable storage medium
CN106815276B (en) Page skipping method and device
CN110221872B (en) Page jump method and device, electronic equipment and storage medium
JP4890794B2 (en) System and method for auditing a network
US20170242783A1 (en) System and Method for Data Collection and Analysis of Information Relating to Mobile Applications
CN1620039A (en) Context-aware automatic service discovery and execution engine in mobile AD-HOC networks
JP2005285118A (en) Remote software support agent system
CN107729014B (en) Page jump method and structure based on Android
CN110457154B (en) Abnormal service processing method and device, storage medium and communication terminal
US8990929B2 (en) Auditing application activities
CN110543428B (en) Application system testing method and device
KR20160061306A (en) Method and apparatus for firmware virtualization
JP2015082149A (en) Communication system, communication method, and communication program
CN105094921A (en) Method and device for calling peripheral in cross-browser mode
AU2015201637A1 (en) Device management system, relay apparatus, relay method, and program
CN114040024A (en) Gateway-based micro-service gray level publishing method, device, equipment and storage medium
CN113760278A (en) Page management method and device
JP2014142872A (en) Testing device
JP2021033316A (en) Scenario providing system, scenario providing apparatus, scenario information providing method, and program
CN112416739A (en) Test method and device and electronic equipment
KR20040008189A (en) Requests in a communication system
CN107707433A (en) A kind of method and computer equipment from network platform test operation flow
EP2053504A1 (en) System and method for managing processing resources
CN114253441A (en) Target function starting method and device, storage medium and electronic device
US20100293258A1 (en) Dynamic optimization of mobile services

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