Routing update control method and its device, equipment and medium

Abstract

The present application discloses a method for controlling routing updates and its apparatus, device and medium, the method comprising: responding to a routing maintenance page pull request, parsing the request to determine the online service it points to; implementing a traversal of the functional components owned by the online service according to the component dependency information pre-configured by the online service; for the traversed functional components, if the corresponding routing configuration file is updated, merging the routing configuration information contained in the routing configuration file with the corresponding cached routing configuration information in the gateway to construct the latest routing configuration file; constructing a visual navigation structure according to the component dependency information, pushing a routing maintenance page containing the visual navigation structure to respond to the pull request, the visual navigation structure containing a functional component list to list the functional components, and each functional component can display its routing configuration information. The application of the present application can dynamically collect routes and provide a visual routing retrieval service, which can improve the efficiency of routing screening.

Description

Technical Field

[0001] The present application relates to network routing control technology, and in particular to a routing update control method, and also to corresponding devices, equipment and non-volatile storage media of the method. Background Art

[0002] Online services or applications have various types of functional components and pages to provide various types of services or functions. As the functional requirements of online services increase, developers add more and more functional components and pages to the project to meet various requirements. As a result, it is necessary to configure various types of routes for each functional component and page to achieve interaction and jump scenarios between the functional components and pages.

[0003] However, as more and more routes are configured for each functional component and page in an online service or application, developers need to further configure each functional component and page route to optimize the routes in the online service or application, or check whether the configuration of each route is reasonable to prevent redundancy caused by repeated definition of routes, which affects the smoothness of jumps between functional components and pages. However, developers can only search for routes through the route project files of each functional component and page. The search work is very cumbersome and makes it impossible for developers to comprehensively optimize the route configuration, making the route configuration of each functional component and page difficult, resulting in frequent misconfiguration, which greatly affects the user experience of online services or applications.

[0004] In view of the fact that various existing technologies cannot meet the routing retrieval needs of developers, the applicant has made corresponding explorations based on this demand. Summary of the invention

[0005] The purpose of the present application is to meet the needs of the prior art or overcome at least some of the deficiencies of the prior art and to provide a routing update control method and its corresponding device, electronic device, and non-volatile storage medium.

[0006] In order to achieve the purpose of this application, the following technical solutions are adopted:

[0007] A routing update control method proposed for the purpose of this application includes the following steps:

[0008] Respond to pull requests for the routing maintenance page and parse the request to determine the online service it points to;

[0009] According to the component dependency information pre-configured by the online service, traverse the functional components owned by the online service;

[0010] For the traversed functional component, if its corresponding routing configuration file is updated, the routing configuration information contained in the routing configuration file is merged with the corresponding cached routing configuration information in the gateway to construct the latest routing configuration file, otherwise the cached routing configuration information is retained in the latest routing configuration file;

[0011] A visual navigation structure is constructed according to the component dependency information, the visual navigation structure is included in a routing maintenance page, and the routing maintenance page is pushed in response to the pull request, wherein the visual navigation structure includes a functional component list, the list lists the functional components, and each functional component is configured to display the routing configuration information in its latest routing configuration file in response to a touch event.

[0012] In a further embodiment, the step of traversing the functional components owned by the online service according to the component dependency information pre-configured by the online service includes:

[0013] Constructing a component dependency graph representing routing dependency relationships between all functional components included in the online service according to the component dependency information of the online service;

[0014] According to the routing dependency relationship between the functional components represented by the component dependency graph, traverse and search whether there is new routing configuration information in the routing configuration files of each functional component;

[0015] If there is new routing configuration information in the routing configuration file, it will be determined as an updated routing configuration file.

[0016] In a further embodiment, according to the dependency relationship between the components represented by the component dependency graph, the step of traversing and searching whether the routing configuration file of each functional component has been updated includes:

[0017] Querying the field information with the routing identifier in the functional component, wherein the field information refers to the class field or method field in the functional component;

[0018] Determine whether the current routing identifiers of the field information are the same as the old routing identifiers cached in the gateway, and merge the new routing identifiers of the different field information with the old routing identifiers to construct the latest routing configuration information of the functional component;

[0019] The latest routing configuration information is stored in the routing configuration file corresponding to the functional component.

[0020] In a further embodiment, for the traversed functional component, if its corresponding routing configuration file is updated, the routing configuration information contained in the routing configuration file is merged with the corresponding cached routing configuration information in the gateway to construct the latest routing configuration file; otherwise, in the step of retaining the cached routing configuration information in the latest routing configuration file, the routing configuration information has a routing version identifier, and the routing configuration file is used to perform version classification according to the routing version identifier of each routing configuration information.

[0021] In a further embodiment, the visual navigation structure includes a functional component list, the list lists the functional components, and each functional component is configured to display the routing configuration information in its latest routing configuration file in response to a touch event, including:

[0022] The routing maintenance page responds to a selection instruction acting on any one of the functional components in the functional component list, and determines the functional component pointed to by the selected instruction;

[0023] Load the routing configuration file corresponding to the functional component into the current page to visually display the routing configuration information in the routing configuration file.

[0024] In a further embodiment, the routing update control method includes the following post-processing steps:

[0025] Responding to the route screening instruction of the route maintenance page, determining the route identifier pointed to by the instruction;

[0026] Query the routing configuration files of each functional component of the online service in the routing maintenance page, and obtain field information corresponding to the routing identifier pointed to by the routing screening instruction in the routing configuration files;

[0027] The field information corresponding to the routing identifier is pushed to the routing maintenance page for loading and display.

[0028] In a further embodiment, the routing update control method includes the following post-processing steps:

[0029] Receiving a version filtering instruction acting on a routing configuration file displayed in the routing maintenance page;

[0030] In response to the version filtering instruction, determine the routing version identifier pointed to by the version filtering instruction;

[0031] The routing configuration information identified by the routing version in the routing configuration file is queried, and the routing configuration information is pushed to the routing maintenance page for loading and display.

[0032] A routing update control device proposed for the purpose of this application includes:

[0033] A pull request response module is used to respond to the pull request of the routing maintenance page and parse the request to determine the online service it points to;

[0034] A functional component traversal module, used to implement traversal of the functional components owned by the online service according to the component dependency information pre-configured by the online service;

[0035] A file update module is used to merge the routing configuration information contained in the routing configuration file with the corresponding routing configuration information cached in the gateway to construct the latest routing configuration file if the corresponding routing configuration file of the traversed functional component is updated, otherwise the cached routing configuration information is retained in the latest routing configuration file;

[0036] A structure visualization module is used to construct a visual navigation structure according to the component dependency information, include the visual navigation structure in a routing maintenance page, and push the routing maintenance page in response to the pull request. The visual navigation structure includes a functional component list, which lists the functional components, and each functional component is configured to display the routing configuration information in its latest routing configuration file in response to a touch event.

[0037] In a further embodiment, the functional component traversal module includes:

[0038] A relationship graph construction submodule, used to construct a component dependency relationship graph representing the routing dependency relationship between all functional components included in the online service according to the component dependency information of the online service;

[0039] An information traversal submodule, used to traverse and search whether there is new routing configuration information in the routing configuration files of each functional component according to the routing dependency relationship between the functional components represented by the component dependency graph;

[0040] The update determination submodule is used to determine that if there is new routing configuration information in the routing configuration file, it will be determined as an updated routing configuration file.

[0041] In a further embodiment, the structure visualization module comprises:

[0042] A selected instruction response submodule, used for the routing maintenance page to respond to a selected instruction acting on any one of the functional components in the functional component list, and to determine the functional component pointed to by the selected instruction;

[0043] The information visualization submodule is used to load the routing configuration file corresponding to the functional component into the current page to visually display the routing configuration information in the routing configuration file.

[0044] An electronic device proposed to meet the purpose of the present application includes a central processing unit and a memory, wherein the central processing unit is used to call and run a computer program stored in the memory to execute the steps of the routing update control method.

[0045] A non-volatile storage medium is proposed to meet the purpose of the present application, which stores a computer program implemented according to the routing update control method. When the computer program is called and executed by a computer, the steps included in the corresponding method are executed.

[0046] Compared with the prior art, the advantages of this application are as follows:

[0047] This application dynamically collects the routing configuration of each functional component in the online service in real time, constructs it into a visual routing maintenance page and pushes it to the developer's development end, so that the developer can perform routing retrieval through the routing maintenance page and intuitively understand the current routing configuration of each functional component in the online service, so as to improve the routing screening efficiency of the developer, and facilitate the developer to optimize the routing configuration of each functional component according to the routing configuration displayed on the page, so that the functional interaction and page jump display between the routing components in the online service can be smoothly executed, and the routing redundancy caused by repeated routing definition is prevented, which causes the online service to fail to run smoothly and affects the user experience.

[0048] First, the present application dynamically collects routing configuration files between various functions in the online service. When the routing configuration file of a functional component is updated, the routing configuration file of the functional component will be updated by merging the routing configuration information of the old and new versions to ensure that the routing configuration file loaded and displayed in the routing maintenance page is the latest version, and the routing configuration information of the old and new versions is provided for developers to refer to, so that developers can understand the differences between the new and old versions of routing, and then optimize the routing configuration of the functional component to ensure the smoothness of page jumps and functional interactions in online services and improve the user experience.

[0049] Secondly, this application caches the collected routing configuration information in the gateway. When the routing configuration information is not updated, it can quickly respond to the page pull instructions from the development side, directly obtain the routing configuration information from the gateway to construct and push the routing maintenance page, so that the developer can quickly obtain the page for routing screening, effectively improving the routing optimization efficiency of developers.

[0050] In addition, the routing maintenance page constructed in the present application has a routing filtering function. Developers can optimize the routing of online services by triggering corresponding filtering events in the page. For example, by triggering routing filtering events, the page can display the field information of the routing configured in the corresponding online service, thereby preventing repeated routing definitions and causing routing redundancy, so as to avoid errors in page jumps or functional interactions in online services, which will affect the user experience.

[0051] Additional aspects and advantages of the present application will be partially given in the following description, which will become apparent from the following description, or will be understood through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0053] Figure 1 A schematic diagram of a typical network deployment architecture related to implementing the technical solution of this application;

[0054] Figure 2 A flowchart of a typical embodiment of the routing update control method of the present application;

[0055] Figure 3 A schematic diagram of a graphical user interface of a routing maintenance page of the present application;

[0056] Figure 4 for Figure 2 A flow chart of the specific steps of the embodiment of step S12;

[0057] Figure 5 for Figure 4 A flow chart of the specific steps of the embodiment of step S122;

[0058] Figure 6 for Figure 2 A flow chart of the specific steps of the embodiment of step S14;

[0059] Figure 7 A schematic diagram of the display style of the routing configuration file in the page when the routing maintenance page of the present application outputs the routing configuration file to the graphical user interface;

[0060] Figure 8 This is a flow chart of an embodiment of the routing update control method of the present application, which relatively adds a post-step;

[0061] Fig. 9 A schematic diagram of the display style of the field information on the page when the field information fed back by the route filtering instruction is pushed to the route maintenance page of this application;

[0062] Fig.10 This is a flow chart of another embodiment of the routing update control method of the present application, which relatively adds a post-step;

[0063] Fig.11 A schematic diagram of the display style of the routing configuration information on the page when the routing configuration information fed back by the version screening instruction is pushed to the routing maintenance page of this application;

[0064] Fig.12 A principle block diagram of a typical embodiment of the routing update control device of the present application;

[0065] Fig.13 This is a basic structural block diagram of a computer device according to an embodiment of the present application. DETAILED DESCRIPTION

[0066] The embodiments of the present application are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and cannot be interpreted as limiting the present application.

[0067] It will be understood by those skilled in the art that, unless expressly stated, the singular forms "one", "said", and "the" used herein may also include plural forms. It should be further understood that the term "comprising" used in the specification of the present application refers to the presence of the features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof. It should be understood that when we refer to an element as being "connected" or "coupled" to another element, it may be directly connected or coupled to the other element, or there may be an intermediate element. In addition, the "connection" or "coupling" used herein may include wireless connection or wireless coupling. The term "and / or" used herein includes all or any unit and all combinations of one or more associated listed items.

[0068] It will be understood by those skilled in the art that, unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as those generally understood by those skilled in the art to which this application belongs. It should also be understood that terms such as those defined in general dictionaries should be understood to have meanings consistent with those in the context of the prior art, and will not be interpreted with idealized or overly formal meanings unless specifically defined as here.

[0069] It will be understood by those skilled in the art that the "client", "terminal" and "terminal device" used herein include both devices with wireless signal receivers, which are devices with only wireless signal receivers without transmission capabilities, and devices with receiving and transmitting hardware, which are devices with receiving and transmitting hardware capable of two-way communication on a two-way communication link. Such devices may include: cellular or other communication devices such as personal computers, tablet computers, which have single-line displays or multi-line displays or cellular or other communication devices without multi-line displays; PCS (Personal Communications Service, personal communication system), which can combine voice, data processing, fax and / or data communication capabilities; PDA (Personal Digital Assistant, personal digital assistant), which may include a radio frequency receiver, pager, Internet / intranet access, web browser, notepad, calendar and / or GPS (Global Positioning System, global positioning system) receiver; conventional laptop and / or palmtop computers or other devices, which have and / or include a conventional laptop and / or palmtop computer or other device with and / or including a radio frequency receiver. The "client", "terminal" and "terminal device" used herein may be portable, transportable, installed in a vehicle (air, sea and / or land), or suitable for and / or configured to run locally, and / or in a distributed form, at any other location on the earth and / or in space. The "client", "terminal" and "terminal device" used herein may also be a communication terminal, an Internet terminal, a music / video playing terminal, for example, a PDA, a MID (Mobile Internet Device) and / or a mobile phone with a music / video playing function, or a smart TV, a set-top box and other devices.

[0070] The hardware referred to by the names such as "server", "client", and "service node" in this application is essentially an electronic device with the equivalent capabilities of a personal computer. It is a hardware device with the necessary components revealed by the von Neumann principle, such as a central processing unit (including an arithmetic unit and a controller), a memory, an input device, and an output device. The computer program is stored in its memory, and the central processing unit calls the program stored in the external memory into the internal memory for execution, executes the instructions in the program, and interacts with the input and output devices to complete specific functions.

[0071] It should be pointed out that the concept of "server" referred to in this application can also be extended to the case of server clusters. According to the network deployment principle understood by those skilled in the art, the servers should be logically divided. In physical space, these servers can be independent of each other but can be called through interfaces, or integrated into a physical computer or a set of computer clusters. Those skilled in the art should understand this flexibility, and should not use it to restrict the implementation of the network deployment method of this application.

[0072] See also Figure 1 , the hardware foundation required for the implementation of the relevant technical solutions of this application can be deployed according to the architecture shown in the figure. The server 80 referred to in this application is deployed in the cloud. As a business server, it can be responsible for further connecting relevant data servers and other servers that provide relevant support, etc., so as to form a logically related service cluster to provide services for relevant terminal devices such as the smartphone 81 and personal computer 82 shown in the figure or a third-party server (not shown). The smartphone and personal computer can access the Internet through a well-known network access method and establish a data communication link with the server 80 in the cloud to run terminal applications related to the services provided by the server.

[0073] For the server, the application is usually constructed as a service process, opening the corresponding program interface for remote calls by applications running on various terminal devices. The relevant technical solutions in this application that are suitable for running on the server can be implemented in the server in this way.

[0074] For the server, the application is usually constructed as a service process, opening the corresponding program interface for remote calls by applications running on various terminal devices. The relevant technical solutions in this application that are suitable for running on the server can be implemented in the server in this way.

[0075] The live broadcast room referred to in this application refers to a video chat room implemented by Internet technology, which usually has audio and video broadcast control functions, including anchor users and audience users. Audience users can include registered users who have registered on the platform, or unregistered visitor users; they can be registered users who follow anchor users, or registered or unregistered users who do not follow anchor users. The anchor user and the audience user can interact through well-known online interactive methods such as voice, video, and text. Generally, the anchor user performs programs for the audience users in the form of audio and video streams, and economic transactions can also be generated during the interaction. Of course, the application form of the live broadcast room is not limited to online entertainment, but can also be extended to other related scenarios, such as education and training scenarios, video conferencing scenarios, product promotion and sales scenarios, and any other scenarios that require similar interactions.

[0076] The online service referred to in this application refers to an application or web page running on a server or terminal device, whose program code can be stored in a non-volatile storage medium recognizable by a computer in the form of computer executable instructions, and loaded into the memory by the central processing unit for execution. The relevant device of this application is constructed through the operation of the online service on the computer.

[0077] Those skilled in the art should be aware that, although the various methods of the present application are described based on the same concept and thus present commonality to each other, unless otherwise specified, these methods can be independently executed. Similarly, for each embodiment disclosed in the present application, they are all proposed based on the same inventive concept, therefore, concepts with the same expression, and concepts that are appropriately changed for convenience despite different expressions, should be understood as equivalent.

[0078] See also Figure 2 , a routing update control method of the present application, in its typical embodiment, comprises the following steps:

[0079] Step S11, responding to the route maintenance page pull request, parsing the request to determine the online service it points to:

[0080] The server responds to the routing maintenance page pull request and parses the pull request to determine the online service to which the request points.

[0081] The routing maintenance page pull request is generally pushed by a terminal device that establishes a data communication link with the server. The terminal device generates a push by entering the corresponding network link address in its own browser, or responding to the routing maintenance page pull event in the corresponding page of the browser or application. The network link address and the page pull event are used to specify the corresponding online service, so that the terminal device generates the pull request pointing to the online service according to the online service specified by it, so that the server can determine the online service pointed to by responding to the pull request, and push the routing maintenance page containing the visual navigation structure of the online service to the terminal device.

[0082] The online service generally refers to a network online page or application that provides users with corresponding functions and services. The online service generally includes multiple types of functional components to provide users with a variety of services and functions. There is a dependency relationship between the functional components to construct the online service with corresponding services and functions. By pre-configuring a corresponding routing configuration file for each functional component, corresponding page jumps and functional interactions can be performed between these functional components. For example, a functional component with a live room browsing function generally has a dependency relationship with a functional component with a live room playback function. The routing configuration files pre-configured by both parties are generally configured with a route for jumping to the other party's page, so that the function of jumping to the other party's page can be realized through the corresponding controls constructed by the functional components of both parties.

[0083] Please refer to Figure 3 , Figure 3 The page shown is a graphical user interface of the routing maintenance page. The online service summary 301 is generally used to display the name of the online service pointed to by the pull request. The functional component list 302 is used to display the functional components in the online service pointed to by the pull request. By selecting any functional component displayed in the functional component list 302, the routing configuration information in the routing configuration file corresponding to the selected functional component will be displayed in the routing configuration information display window 303; the routing maintenance page dynamically collects the routing configuration files of each functional component in the online service, so that the developer can determine the routing configuration information of each functional component in the online service in real time through the routing maintenance page, understand the routing configuration between each functional component in the current online service, and perform routing maintenance to optimize the routing of the online service, prevent the redefinition of the routing configuration, and affect the functional interaction and page jump between the functional components, for example, affecting the data transmission and jump response between the functional components.

[0084] Step S12: According to the component dependency information pre-configured by the online service, the functional components owned by the online service are traversed:

[0085] After the server responds to the pull request and determines the online service to which the request points, it will obtain the component dependency information pre-configured by the online service, determine the functional components owned by the online service and determine the routing dependencies between the functional components, and then implement a traversal of these functional components to determine whether there are any updates to the routing configuration files of each functional component.

[0086] The component dependency information represents the routing dependency relationship between the functional components in the online service, which is generally pre-stored in the corresponding database of the server, so that after the server determines the online service pointed to by the pull request, it queries the database to obtain the component dependency information of the online service, determines the functional components of the online service and determines the routing dependency relationship between the functional components, so as to perform traversal retrieval on the routing configuration files of the component functions according to the routing dependency relationship between the functional components, and determines the functional components whose routing configuration files are to be updated among the functional components.

[0087] The routing configuration file of each functional component stores the routing configuration information of its current latest configuration. When the developer updates the routing configuration information of a functional component, the latest routing configuration information of the functional component is pushed to the routing configuration file corresponding to the functional component for storage, so that the server can determine whether the routing configuration information of the functional component is updated by retrieving the routing configuration file of the functional component, so as to merge the routing configuration information.

[0088] The routing configuration information is used to characterize the routing configured by the functional component. The routing configuration information of each functional component stores field information with routing identifiers and their corresponding routing identifiers. The field information refers to class fields or method fields. The server compares and analyzes the routing identifiers of the classes and methods stored in the routing configuration information of the functional component with the routing identifiers of the classes and methods stored in the routing configuration information of the functional component in the gateway to determine whether the routing configuration information is updated.

[0089] Please refer to Figure 4 Regarding the implementation method of the server implementing the traversal of the functional components owned by the online service according to the component dependency information of the online service, the specific implementation steps are as follows:

[0090] Step S121: construct a component dependency graph representing the routing dependency relationships between all functional components included in the online service according to the component dependency information of the online service:

[0091] The server constructs the component dependency graph representing the dependency relationships among all functional components included in the online service according to the component dependency information of the online service pointed to by the pull request, so as to determine the routing dependency relationships among the functional components.

[0092] The component dependency graph is used to characterize the routing dependencies between all functions included in the online service. The routing dependencies of the functional components represented in the component dependency graph are the interaction and jump logic between the functional components in the online service. For example, when the online service is a live online service, there is generally a routing dependency between its virtual gift functional component and the online payment functional component, so that when a user selects and gives a virtual gift through the virtual gift functional component, it will trigger the graphical user interface to display the virtual gift payment page of the online feedback functional component, allowing the user to pay for the virtual gift on this page to give the anchor the virtual gift selected in the virtual gift functional component, and there is generally a routing dependency between the virtual gift functional component and the live stream playback functional component, so that the online service can visualize the virtual gift selected in the virtual gift functional component in the live stream playback window of the live stream playback functional component.

[0093] Step S122: according to the routing dependency relationship between the functional components represented by the component dependency graph, traverse and search whether there is new routing configuration information in the routing configuration files of the functional components:

[0094] The server traverses and searches the routing configuration files of the functional components according to the routing dependency relationships between the functional components represented by the component dependency graph to determine the functional components with updated routing configuration information as the updated functional components.

[0095] The routing configuration information in the routing configuration file of the functional component is generally collected in advance by the server. The server establishes a data communication link with the development device to monitor the routing configuration information of the functional components in the development device in real time or periodically. When the routing configuration information of a functional component in the development device is monitored to be modified, the server will collect the modified routing configuration information and store the routing configuration information in the routing configuration file of the functional component.

[0096] Please refer to Figure 5 Regarding the implementation method of the routing configuration information stored in the routing configuration file of the server collection function component, the specific implementation steps are as follows:

[0097] Step S1221, querying the field information with the routing identifier in the functional component, wherein the field information refers to the class field or method field in the functional component:

[0098] The server establishes a data communication link with the implementation development end device, and queries the field information with routing identifier in the implementation functional component through the link. The field information refers to the class field or method field in the functional component, which is used to implement the corresponding function or service of the functional component. For example, the title field is used to implement the page title or application title in the online service.

[0099] The field information with the routing identifier has a routing function, and each type of the routing identifier is used to implement different types of routing functions. For example, the routing identifier of the jump page is used to implement the routing function of the page jump, and the routing identifier of the image and text loading is used to implement the routing function of obtaining the image and text for output display, etc.

[0100] Step S1222, determine whether the current routing identifier of the field information is the same as the old routing identifier cached in the gateway, and merge the new routing identifier of the different field information with the old routing identifier to construct the latest routing configuration information of the functional component:

[0101] After the server determines all the field information with the routing identifier in the functional component, it will determine whether the current routing identifier of these field information is the same as the old version of the routing identifier cached in the gateway. If they are the same, the routing configuration information of the routing component will not be updated. If they are not the same, the newly added new version of the routing identifier of the routing component will be merged with the old version of the routing identifier to construct the latest routing configuration information of the functional component.

[0102] Step S1223, storing the latest routing configuration information in the routing configuration file corresponding to the functional component:

[0103] The server stores the latest routing configuration information constructed by synthesis into the routing configuration file corresponding to the functional component to complete the update of the routing configuration information of the functional component.

[0104] Step S123: If there is new routing configuration information in the routing configuration file, it will be determined as an updated routing configuration file:

[0105] When the server retrieves that there is new routing configuration information in the routing configuration file of any of the functional components, it is determined that the routing configuration file of the functional component is updated.

[0106] The server generally determines whether the routing configuration information stored in the routing configuration file is updated by querying the modification time of the routing configuration information stored in the routing configuration file, or by comparing the routing configuration information in the routing configuration file of the functional component with the routing configuration information cached by the functional component in the gateway to determine whether the routing configuration information is updated.

[0107] Step S13: For the traversed functional component, if its corresponding routing configuration file is updated, the routing configuration information contained in the routing configuration file is merged with the corresponding cached routing configuration information in the gateway to construct the latest routing configuration file; otherwise, the cached routing configuration information is retained in the latest routing configuration file:

[0108] The server traverses the routing configuration information stored in the routing configuration file of each functional component of the online service, and determines whether the routing configuration file is updated by querying the modification time of the routing configuration information or comparing the routing configuration information with the corresponding routing configuration information cached in the gateway.

[0109] When the server retrieves that the routing configuration file of any functional component in the online service is updated, the routing configuration information contained in the routing configuration information of the functional component is merged with the routing configuration information cached in the gateway of the functional component to construct the latest routing configuration file of the functional component.

[0110] When the server retrieves that the routing configuration file of any functional component in the online service has not been updated, the routing configuration information of the routing configuration file of the functional component is not modified.

[0111] Specifically, regarding the implementation method of merging the routing configuration information by the server, it is generally achieved by storing the latest routing configuration information contained in the routing configuration file of the functional component and the old version of the routing configuration information in the gateway into the routing configuration file to construct the latest routing configuration file of the functional component, and based on the version identifier of the old version of the routing configuration information, creating a version identifier for the latest routing configuration information with a version number higher than the version identifier, the version identifier is used to characterize the version number of the routing configuration information, so that the server can classify the versions of the routing configuration information through the corresponding version identifiers of each routing configuration information in the routing configuration information.

[0112] The routing configuration information cached in the gateway is historically collected and cached by the server. After the server completes the merging of the routing configuration information of any functional component, it caches the routing configuration information in the gateway to update the routing configuration information cached in the gateway by the functional component.

[0113] Step S14, constructing a visual navigation structure according to the component dependency information, including the visual navigation structure in a routing maintenance page, pushing the routing maintenance page in response to the pull request, the visual navigation structure including a functional component list, the list listing the functional components, each functional component being configured to display routing configuration information in its latest routing configuration file in response to a touch event:

[0114] The server constructs the visual navigation structure according to the dependency relationship between the functional components in the online service represented by the component dependency information, and pushes the routing maintenance page containing the visual navigation structure to the sender of the pull request. After the sender receives the routing maintenance page, its application or browser loads the routing maintenance page, which lists the functional components contained in its own visual navigation structure. The functional component list lists the functional components of the online service, so that the user of the sender can generate the touch event by touching any functional component in the functional component list, so that the routing maintenance page responds to the touch event and displays the routing configuration information in the latest routing configuration file of the functional component pointed to by the event on the page.

[0115] The visual navigation structure is used to visually navigate the routing configuration information of each functional component of the online service in the routing maintenance page of the online service, guide the user to query the corresponding functional component through the visual navigation structure, and perform visual output of the routing configuration information of the functional component. For example, please refer to Figure 3 , Figure 3 The functional component list 302 is a functional component list of the visual navigation structure. The component name of each functional component is visually output in the functional component list 302 so that the user can select the corresponding functional component through the functional component list 302 and output the routing configuration information of the functional component to the routing configuration information display window 303.

[0116] Please refer to Figure 3 , 6 And 7, regarding the implementation method of the touch event of the routing maintenance page response function component list, the specific implementation steps are as follows:

[0117] Step S141, the routing maintenance page responds to a selection instruction acting on any one of the functional components in the functional component list, and determines the functional component pointed to by the selection instruction:

[0118] The routing maintenance page responds to the selected instruction acting on any one of the functional components in the functional component list to determine the functional component pointed to by the selected instruction.

[0119] Please refer to Figure 3 The user touches the C functional component 304 in the functional component list 302 to generate the selected instruction pointing to the C functional component 304, so that the routing maintenance page responds to the selected instruction and determines that the functional component pointed to by the selected instruction is the C functional component 304.

[0120] Step S142, loading the routing configuration file corresponding to the functional component into the current page to visually display the routing configuration information in the routing configuration file:

[0121] After the routing maintenance page determines the functional component pointed to by the selected instruction, it will load the routing configuration file corresponding to the functional component into the current page, and visualize the routing configuration information in the routing configuration file to display the routing configuration information in the graphical user interface of the current page.

[0122] Please refer to Figure 3 and Figure 7 After the routing maintenance page responds to the selected instruction directed to the C functional component 304, each routing configuration information contained in the routing configuration file of the C functional component 304 is loaded into the routing configuration information display window 303 for output display. The routing information display window 303 will output the following Figure 7 The routing configuration information shown is visualized so that the user can determine the current routing configuration of the C functional component 304 through the routing information display window 303 to perform routing optimization configuration for the C functional component.

[0123] The above typical embodiments and their variant embodiments fully disclose the implementation scheme of the routing update control method of the present application. However, various variant embodiments of the method can still be derived by changing and expanding some technical means. Other embodiments are briefly described as follows:

[0124] In one embodiment, see Figure 8 , the method further comprises the following post-processing steps:

[0125] Step S15, responding to the route screening instruction of the route maintenance page, determining the route identifier pointed to by the instruction:

[0126] The server responds to the routing screening instruction of the routing maintenance page and determines the routing identifier pointed to by the instruction.

[0127] The routing filtering instruction is generally generated and pushed by the routing maintenance page in response to a routing filtering event. The routing filtering event refers to an event triggered by a user specifying a corresponding routing identifier through the routing maintenance page, so that the routing maintenance page displays the field information corresponding to the routing identifier in the current online service.

[0128] Step S16, querying the routing configuration files of each functional component of the online service in the routing maintenance page, and obtaining field information corresponding to the routing identifier pointed to by the routing screening instruction in these routing configuration files:

[0129] The server queries the routing configuration file of each functional component of the online service in the routing maintenance page for the routing identifier pointed to by the routing screening instruction, and obtains the field information corresponding to the routing identifier.

[0130] Step S17, pushing the field information corresponding to the routing identifier to the routing maintenance page for loading and display:

[0131] After acquiring the field information corresponding to the routing identifier from each routing configuration file, the server pushes the field information to the routing maintenance page so that the field information is displayed on the routing maintenance page.

[0132] Please refer to Figure 3 and Fig. 9 After the routing maintenance page receives the field information pushed by the server for visualization, please Figure 3 The routing configuration information display window 303 will output Fig. 9 The visual information shown allows users to Fig. 9 The visualization information shown can help you understand whether there are repeated definitions of routes in the current online service, so that users can Fig. 9 Visualize information, reconfigure the routing of the corresponding functional components in the online service, optimize the routing of the online service, and prevent routing redundancy caused by redefinition of routing.

[0133] In another embodiment, please refer to Fig.10 , the method further comprises the following post-processing steps:

[0134] Step S15', receiving a version filtering instruction acting on the routing configuration file displayed in the routing maintenance page:

[0135] The server receives the version filtering instruction of the routing configuration file currently displayed in the routing maintenance page.

[0136] The version filtering instruction is generally generated and pushed by the routing maintenance page in response to a version filtering event. The routing filtering event refers to an event triggered by the user specifying a corresponding routing version identifier through the routing maintenance page, so that the routing maintenance page displays the routing configuration information corresponding to the routing version identifier in the current routing configuration file.

[0137] Step S16', responding to the version screening instruction, determining the routing version identifier pointed to by the version screening instruction:

[0138] The server responds to the version filtering instruction and determines the routing version identifier pointed to by the version filtering instruction, so as to query the routing configuration information of the routing version identifier from the routing configuration file currently displayed in the routing maintenance page.

[0139] Step S17', query the routing configuration information for the routing version identifier in the routing configuration file, and push the routing configuration information to the routing maintenance page for loading and display:

[0140] The server queries the routing configuration information of the routing version identifier pointed to by the version filtering instruction in the routing configuration file, obtains the routing configuration information, and pushes the routing configuration information to the routing maintenance page so that the routing maintenance page loads the routing configuration information for visual output display.

[0141] Please refer to Figure 7 and 11 When the version screening instruction is for the C functional component, and the routing version identified by the instruction is the A routing version, the routing configuration information displayed in the routing maintenance page will be Figure 7 Convert to Fig.11 The displayed routing configuration information allows users to Fig.11 The routing configuration information shown is used to understand the routing configuration of the A routing version in the C functional component, so as to optimize the routing configuration of the C functional component, make the interaction or jump of each service or function in the C functional component smoother, and then optimize the routing configuration of the online service and improve the user experience.

[0142] Furthermore, by functionalizing each step in the method disclosed in the above embodiments, a routing update control device of the present application can be constructed. Fig.12 In a typical embodiment, the device includes: a pull request response module 11, which is used to respond to a pull request from a routing maintenance page and parse the request to determine the online service to which it points; a functional component traversal module 12, which is used to implement a traversal of the functional components owned by the online service according to the component dependency information pre-configured by the online service; a file update module 13, which is used to merge the routing configuration information contained in the routing configuration file with the corresponding cached routing configuration information in the gateway to construct the latest routing configuration file if the corresponding routing configuration file of the traversed functional component is updated, otherwise the cached routing configuration information is retained in the latest routing configuration file; a structure visualization module 14, which is used to construct a visual navigation structure according to the component dependency information, include the visual navigation structure in the routing maintenance page, and push the routing maintenance page to respond to the pull request, wherein the visual navigation structure includes a functional component list, the list lists the functional components, and each functional component is configured to display the routing configuration information in its latest routing configuration file in response to a touch event.

[0143] In one embodiment, the functional component traversal module 12 includes: a relationship graph construction submodule, which is used to construct a component dependency graph representing the routing dependency relationships between all functional components included in the online service based on the component dependency information of the online service; an information traversal submodule, which is used to traverse and retrieve whether there is new routing configuration information in the routing configuration files of each functional component according to the routing dependency relationships between the functional components represented by the component dependency graph; and an update determination submodule, which is used to determine that if there is new routing configuration information in the routing configuration file, it will be determined as an updated routing configuration file.

[0144] In one embodiment, the structure visualization module 14 includes: a selected instruction response submodule, which is used for the routing maintenance page to respond to a selected instruction acting on any functional component in the functional component list, and determine the functional component pointed to by the selected instruction; an information visualization submodule, which is used to load the routing configuration file corresponding to the functional component into the current page to visually display the routing configuration information in the routing configuration file.

[0145] In order to solve the above technical problems, the embodiment of the present application also provides a computer device for running a computer program implemented according to the routing update control method. Fig.13 , Fig.13 This is a basic structural block diagram of the computer device in this embodiment.

[0146] like Fig.13 As shown, a schematic diagram of the internal structure of a computer device. The computer device includes a processor, a non-volatile storage medium, a memory, and a network interface connected via a system bus. Among them, the non-volatile storage medium of the computer device stores an operating system, a database, and computer-readable instructions. The database may store a control information sequence. When the computer-readable instructions are executed by the processor, the processor can implement a routing update control method. The processor of the computer device is used to provide computing and control capabilities to support the operation of the entire computer device. The memory of the computer device may store computer-readable instructions. When the computer-readable instructions are executed by the processor, the processor can execute a routing update control method. The network interface of the computer device is used to connect and communicate with a terminal. Those skilled in the art can understand that Fig.13 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0147] In this embodiment, the processor is used to execute the specific functions of each module / submodule in the routing update control device of the present invention, and the memory stores the program code and various data required to execute the above modules. The network interface is used to transmit data between user terminals or servers. The memory in this embodiment stores the program code and data required to execute all modules / submodules in the routing update control device, and the server can call the program code and data of the server to execute the functions of all submodules.

[0148] The present application also provides a non-volatile storage medium, wherein the routing update control method is written into a computer program and stored in the storage medium in the form of computer-readable instructions. When the computer-readable instructions are executed by one or more processors, it means that the program is run in the computer, thereby enabling one or more processors to execute the steps of the routing update control method of any of the above embodiments.

[0149] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, the aforementioned storage medium can be a non-volatile storage medium such as a disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0150] In summary, the present application dynamically collects the routing configuration of each functional component in the online service in real time, constructs it into a visual routing maintenance page and pushes it to the developer's development end, so that the developer can perform routing retrieval through the routing maintenance page and intuitively understand the current routing configuration of each functional component in the online service, so as to improve the routing screening efficiency of the developer, and facilitate the developer to optimize the routing configuration of each functional component according to the routing configuration displayed on the page, so that the functional interaction and page jump display between the routing components in the online service can be smoothly executed, and the routing redundancy caused by repeated routing definition is prevented, which causes the online service to fail to run smoothly and affects the user experience.

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

[0152] Those skilled in the art will appreciate that the various operations, methods, steps, measures, and schemes in the processes discussed in this application may be alternated, altered, combined, or deleted. Further, other steps, measures, and schemes in the various operations, methods, and processes discussed in this application may also be alternated, altered, rearranged, decomposed, combined, or deleted. Further, the steps, measures, and schemes in the prior art that are similar to those disclosed in this application may also be alternated, altered, rearranged, decomposed, combined, or deleted.

[0153] The above description is only a partial implementation method of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A routing update control method, characterized in that: The steps include: Respond to pull requests for the routing maintenance page and parse the request to determine the online service it points to; According to the component dependency information pre-configured by the online service, the functional components owned by the online service are traversed, including: constructing a component dependency graph representing the routing dependency relationships between all functional components included in the online service according to the component dependency information of the online service; traversing and searching whether there is new routing configuration information in the routing configuration files of each functional component according to the routing dependency relationships between the functional components represented by the component dependency graph, including: querying the field information with routing identifiers in the functional component, the field information refers to the class field or method field in the functional component, judging whether the current routing identifiers of the field information are the same as the old routing identifiers cached in the gateway, merging the new routing identifiers of the different field information with the old routing identifiers to construct the latest routing configuration information of the functional component, and storing the latest routing configuration information in the routing configuration file corresponding to the functional component; if the routing configuration file has new routing configuration information, it will be determined as an updated routing configuration file; For the traversed functional component, if its corresponding routing configuration file is updated, the routing configuration information contained in the routing configuration file is merged with the corresponding cached routing configuration information in the gateway to construct the latest routing configuration file, otherwise the cached routing configuration information is retained in the latest routing configuration file, the routing configuration information has a routing version identifier, and the routing configuration file is classified according to the routing version identifier of each routing configuration information; A visual navigation structure is constructed according to the component dependency information, the visual navigation structure is included in a routing maintenance page, and the routing maintenance page is pushed in response to the pull request, wherein the visual navigation structure includes a functional component list, the list lists the functional components, and each functional component is configured to display the routing configuration information in its latest routing configuration file in response to a touch event.

2. The method according to claim 1, characterized in that The visual navigation structure includes a functional component list, which lists the functional components, and each functional component is configured to display the routing configuration information in its latest routing configuration file in response to a touch event, including: The routing maintenance page responds to a selection instruction acting on any one of the functional components in the functional component list, and determines the functional component pointed to by the selected instruction; Load the routing configuration file corresponding to the functional component into the current page to visually display the routing configuration information in the routing configuration file.

3. The method according to claim 1 or 2, characterized in that: The following post-processing steps are included: Responding to the route screening instruction of the route maintenance page, determining the route identifier pointed to by the instruction; Query the routing configuration files of each functional component of the online service in the routing maintenance page, and obtain field information corresponding to the routing identifier pointed to by the routing screening instruction in the routing configuration files; The field information corresponding to the routing identifier is pushed to the routing maintenance page for loading and display.

4. The method according to claim 1 or 2, characterized in that: The following post-processing steps are included: Receiving a version filtering instruction acting on a routing configuration file displayed in the routing maintenance page; In response to the version filtering instruction, determine the routing version identifier pointed to by the version filtering instruction; The routing configuration information identified by the routing version in the routing configuration file is queried, and the routing configuration information is pushed to the routing maintenance page for loading and display.

5. A routing update control device, characterized in that: It includes: A pull request response module is used to respond to the pull request of the routing maintenance page and parse the request to determine the online service it points to; The function component traversal module is used to implement traversal of the function components owned by the online service according to the component dependency information pre-configured by the online service, including: constructing a component dependency graph representing the routing dependency relationship between all the function components included in the online service according to the component dependency information of the online service; traversing and searching whether there is new routing configuration information in the routing configuration files of each function component according to the routing dependency relationship between each function component represented by the component dependency graph, including: querying the field information with routing identifiers in the function component, the field information refers to the class field or method field in the function component, judging whether the current routing identifiers of the field information are the same as the old routing identifiers cached in the gateway, merging the new routing identifiers of the different field information with the old routing identifiers to construct the latest routing configuration information of the function component, and storing the latest routing configuration information in the routing configuration file corresponding to the function component; if there is new routing configuration information in the routing configuration file, it will be determined as an updated routing configuration file; A file update module, for traversing a functional component, if its corresponding routing configuration file is updated, merging the routing configuration information contained in the routing configuration file with the corresponding routing configuration information cached in the gateway to construct a latest routing configuration file, otherwise retaining the cached routing configuration information in the latest routing configuration file, the routing configuration information having a routing version identifier, and the routing configuration file is classified by the routing version identifier of each routing configuration information; A structure visualization module is used to construct a visual navigation structure according to the component dependency information, include the visual navigation structure in a routing maintenance page, and push the routing maintenance page in response to the pull request. The visual navigation structure includes a functional component list, which lists the functional components, and each functional component is configured to display the routing configuration information in its latest routing configuration file in response to a touch event.

6. The device according to claim 5, characterized in that The structure visualization module includes: A selected instruction response submodule, used for the routing maintenance page to respond to a selected instruction acting on any one of the functional components in the functional component list, and to determine the functional component pointed to by the selected instruction; The information visualization submodule is used to load the routing configuration file corresponding to the functional component into the current page to visually display the routing configuration information in the routing configuration file.

7. An electronic device, comprising a central processing unit and a memory, characterized in that: The central processing unit is used to call and run a computer program stored in the memory to execute the steps of the method according to any one of claims 1 to 4.

8. A non-volatile storage medium, characterized in that: The computer program implemented according to the method described in any one of claims 1 to 4 is stored in the form of computer-readable instructions, and when the computer program is called and executed by a computer, the steps included in the method are executed.

Images