CN116366528A - Routing data generating method, electronic device, and computer-readable storage medium - Google Patents

Abstract

The embodiment of the present disclosure discloses a method for generating route data, an electronic device and a computer-readable storage medium. The method includes: in response to the fact that the routing data to be generated has a first routing identifier and a first routing group identifier, from the stored routing information, obtain the first shared routing attribute information corresponding to the first routing group identifier, and the first routing identifier corresponding to The first private routing attribute information; performing information assembly on the first shared routing attribute information and the first private routing attribute information to generate routing data to be generated. The embodiments of the present disclosure can reduce the storage of redundant information, thereby reducing waste of resources.

Description

Routing data generating method, electronic device, and computer-readable storage medium

technical field

The present disclosure relates to the technical field of communication, and in particular, to a method for generating routing data, electronic equipment, and a computer-readable storage medium.

Background technique

Routing data is the core data for gateway devices to provide gateway services, therefore, the management of routing data is very important.

Generally speaking, gateway data is managed by the gateway configuration background. Specifically, all routing configuration information can be stored in the gateway configuration background. The gateway configuration background can perform routing according to the routing configuration information stored by itself at regular or irregular intervals. Data generation, and provide the generated routing data to the gateway device.

It should be noted that, with the above method, a large amount of redundant information will be stored in the gateway configuration background, which will cause waste of resources.

Contents of the invention

In order to solve the above-mentioned technical problems, the present disclosure is proposed. Embodiments of the present disclosure provide a method for generating routing data, electronic equipment, and a computer-readable storage medium.

According to an aspect of an embodiment of the present disclosure, a method for generating routing data is provided, including:

In response to the fact that the routing data to be generated has a first routing identifier and a first routing group identifier, from the stored routing information, obtain first shared routing attribute information corresponding to the first routing group identifier, and the first routing identifier corresponding to The attribute information of the first private route;

Information assembly is performed on the first shared routing attribute information and the first private routing attribute information to generate the to-be-generated routing data.

According to another aspect of the embodiments of the present disclosure, a routing data generation device is provided, including:

An acquisition module, configured to respond to the fact that the routing data to be generated has a first routing identifier and a first routing group identifier, from stored routing information, acquire the first shared routing attribute information corresponding to the first routing group identifier, and the First private route attribute information corresponding to the first route identifier;

A generating module, configured to perform information assembly on the first shared routing attribute information and the first private routing attribute information to generate the to-be-generated routing data.

According to another aspect of the embodiments of the present disclosure, an electronic device is provided, including:

memory for storing computer program products;

The processor is configured to execute the computer program product stored in the memory, and when the computer program product is executed, realize the above method for generating routing data.

According to still another aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium on which computer program instructions are stored, wherein, when the computer program instructions are executed by a processor, the above method for generating routing data is implemented.

According to yet another aspect of the embodiments of the present disclosure, a computer program product is provided, including computer program instructions, and when the computer program instructions are executed by a processor, the above method for generating routing data is implemented.

In the embodiment of the present disclosure, when the routing data to be generated has a first routing identifier and a first routing group identifier, the first shared routing attribute information corresponding to the first routing group identifier can be obtained from the stored routing information, As well as the first private routing attribute information corresponding to the first routing identifier, the routing data to be generated can be generated by assembling the information of the first shared routing attribute information and the first private routing attribute information. In this way, by grouping routing data, the same attributes of all routing data in the same routing data group can be extracted and stored as shared routing attribute information, and private routing attribute information can be stored for the unique attributes of each routing data , therefore, there will not be a large amount of redundant information in the stored routing information, and the information stored in the stored routing information is very concise, thereby helping to reduce waste of resources.

The technical solution of the present disclosure will be described in further detail below with reference to the drawings and embodiments.

Description of drawings

The above and other objects, features and advantages of the present disclosure will become more apparent by describing the embodiments of the present disclosure in more detail with reference to the accompanying drawings. The accompanying drawings are used to provide a further understanding of the embodiments of the present disclosure, and constitute a part of the specification, and are used together with the embodiments of the present disclosure to explain the present disclosure, and do not constitute limitations to the present disclosure. In the drawings, the same reference numerals generally represent the same components or steps.

Fig. 1 is a schematic flowchart of a method for generating routing data provided by an exemplary embodiment of the present disclosure.

Fig. 2 is a schematic flowchart of a method for generating routing data provided by another exemplary embodiment of the present disclosure.

Fig. 3 is a schematic flowchart of a method for generating routing data provided by yet another exemplary embodiment of the present disclosure.

Fig. 4 is a schematic flowchart of a method for generating routing data provided by another exemplary embodiment of the present disclosure.

Fig. 5 is a schematic diagram of a user inputting selected parameters in a routing data generation method provided by another exemplary embodiment of the present disclosure.

Fig. 6 is a schematic flowchart of a method for generating routing data provided by another exemplary embodiment of the present disclosure.

Fig. 7 is a schematic structural diagram of a routing data generation device provided by an exemplary embodiment of the present disclosure.

Fig. 8 is a structural diagram of an electronic device provided by an exemplary embodiment of the present disclosure.

Detailed ways

Hereinafter, exemplary embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. Apparently, the described embodiments are only some of the embodiments of the present disclosure, rather than all the embodiments of the present disclosure, and it should be understood that the present disclosure is not limited by the exemplary embodiments described here.

It should be noted that relative arrangements of components and steps, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless specifically stated otherwise.

Those skilled in the art can understand that terms such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different steps, devices or modules, etc., and do not represent specific technical meanings, nor do they represent a necessary logical order.

It should also be understood that in the embodiments of the present disclosure, "plurality" may refer to two or more than two, and "at least one" may refer to one, two or more than two.

It should also be understood that any component, data or structure mentioned in the embodiments of the present disclosure can generally be understood as one or more unless there is a clear limitation or a contrary suggestion is given in the context.

In addition, the term "and/or" in the present disclosure is only an association relationship describing associated objects, indicating that there may be three relationships, for example, A and/or B may indicate: A exists alone, and A and B exist at the same time , there are three cases of B alone. In addition, the character "/" in the present disclosure generally indicates that the contextual objects are an "or" relationship.

It should also be understood that the description of the various embodiments in the present disclosure emphasizes the differences between the various embodiments, and the same or similar points can be referred to each other, and for the sake of brevity, details are not repeated here.

At the same time, it should be understood that, for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

The following description of at least one exemplary embodiment is merely illustrative in nature and in no way intended as any limitation of the disclosure, its application or uses.

Techniques, methods and devices known to those of ordinary skill in the relevant art may not be discussed in detail, but where appropriate, such techniques, methods and devices should be considered part of the description.

It should be noted that like numerals and letters denote like items in the following figures, therefore, once an item is defined in one figure, it does not require further discussion in subsequent figures.

Embodiments of the present disclosure may be applied to electronic devices such as terminal devices, computer systems, servers, etc., which may operate with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known terminal devices, computing systems, environments and/or configurations suitable for use with electronic devices such as terminal devices, computer systems, servers include, but are not limited to: personal computer systems, server computer systems, thin clients, thick client computers, handheld or laptop devices, microprocessor-based systems, set-top boxes, programmable consumer electronics, networked personal computers, minicomputer systems, mainframe computer systems, and distributed cloud computing technology environments including any of the foregoing, among others.

Electronic devices such as terminal devices, computer systems, servers, etc. may be described in the general context of computer system-executable instructions, such as program modules, being executed by the computer system. Program modules may include routines, programs, objects, components, logic, data structures, etc., that perform particular tasks or implement particular abstract data types. The computer system/server can be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computing system storage media including storage devices.

exemplary method

Fig. 1 is a schematic flowchart of a method for generating routing data provided by an exemplary embodiment of the present disclosure. The method shown in FIG. 1 can be applied to electronic devices such as a gateway configuration background, and the method shown in FIG. 1 can include step 110 and step 120, and each step will be described separately below.

Step 110, in response to the fact that the routing data to be generated has the first routing identifier and the first routing group identifier, from the stored routing information, obtain the first shared routing attribute information corresponding to the first routing group identifier, and the first shared routing attribute information corresponding to the first routing identifier. Attribute information of the first private route.

It should be noted that any routing data involved in the embodiments of the present disclosure may have a routing identifier, such as a routing id, and the routing identifier can be used to distinguish different routing data; at least part of the routing data involved in the embodiments of the present disclosure There may be a routing group identifier, for example, a routing group id, and the routing group identifier can be used to distinguish different routing data groups.

Optionally, the stored routing information may include information necessary to generate any routing data, and the stored routing information may be stored in the form of a data table. For a clear layout, the composition of the stored routing information will be described in detail later .

Optionally, the first shared routing attribute information corresponding to the first routing group identifier may refer to: routing attribute information shared by all routing data in the routing data group with the first routing group identifier.

Optionally, the first private routing attribute information corresponding to the first routing identifier may refer to routing attribute information that is unique to the routing data to be generated but not possessed by the rest of the routing data in the routing data group with the first routing group identifier .

Step 120, information assembly is performed on the first shared routing attribute information and the first private routing attribute information to generate routing data to be generated.

In step 120, by assembling information on the first shared routing attribute information and the first private routing attribute information, routing data in JSON format (which is a lightweight data exchange format) can be generated, and the routing data can be used as Routing data to be generated.

It should be noted that by executing the above steps 110 to 120, one piece of routing data to be processed can be obtained, and by executing the above steps 110 to 120 multiple times, a large amount of routing data can be obtained, and the gateway configuration background can convert these routing data All are provided to the gateway device, so that the gateway device can provide reliable gateway services by using the routing data provided by the gateway configuration background.

In the embodiment of the present disclosure, when the routing data to be generated has a first routing identifier and a first routing group identifier, the first shared routing attribute information corresponding to the first routing group identifier can be obtained from the stored routing information, As well as the first private routing attribute information corresponding to the first routing identifier, the routing data to be generated can be generated by assembling the information of the first shared routing attribute information and the first private routing attribute information. In this way, by grouping routing data, the same attributes of all routing data in the same routing data group can be extracted and stored as shared routing attribute information, and private routing attribute information can be stored for the unique attributes of each routing data , therefore, there will not be a large amount of redundant information in the stored routing information, and the information stored in the stored routing information is very concise, thereby helping to reduce waste of resources.

In an optional example, the stored routing information includes: a first information set, a second information set, and a third information set, the first information set records the correspondence between the routing group identifier and the path prefix of the shared route definition, A plurality of routing rule information is recorded in the second information set, each routing rule information in the second information set corresponds to a routing identifier or a routing group identifier, and a plurality of routing basic information is recorded in the third information set, each basic The routing basic information corresponds to a routing identifier or a routing group identifier;

On the basis of the embodiment shown in Figure 1, as shown in Figure 2, step 110 includes:

Step 1101, based on the first information set, determine the first shared routing definition path prefix corresponding to the first routing group identifier;

Step 1103, based on the second information set, determine the first shared routing rule information corresponding to the first routing group identifier, and the first private routing rule information corresponding to the first routing identifier;

Step 1105, based on the third information set, determine the first routing basic information corresponding to the first routing identifier, and obtain the first private route definition path suffix corresponding to the first routing identifier from the first routing basic information;

Wherein, the first shared route attribute information includes: first shared route definition path prefix and first shared route rule information, and the first private route attribute information includes: first private route definition path suffix and first private route rule information.

Optionally, the first information set, the second information set, and the third information set may all be in the form of data tables.

Optionally, the number of the second information sets may be two, wherein one second information set is used to record multiple asserters, and the other second information set is used to record multiple filters, and each of the multiple asserters An asserter can be used as a routing rule information, and each filter in multiple filters can also be used as a routing rule information.

It should be noted that, if the two second information sets are both in the form of data tables, the two second information sets may be called an asserter table and a filter table respectively. In addition, the number of the second information set may be only one, and multiple asserters and multiple filters may be recorded in this second information set at the same time.

Optionally, each routing basic information in the third information set may include at least one of the following: information identifier (such as a sequence number used to characterize the sorting position of the routing basic information in the third information set), creation time, creation Person, modification time, modification person, a field used to indicate whether the routing basic information corresponds to routing data or routing data group. If the basic routing information corresponds to a routing data group, the basic routing information may also include a routing group identifier of the routing data group. If the routing basic information corresponds to routing data, the routing basic information may also include the routing identifier of the routing data, and if the routing data also belongs to a certain routing data group, the routing basic information may also include the route of the routing data group Group identifier, and the sub-identification of the routing data under the routing data group, so that through the routing identifier, the routing group identifier and the sub-identification, the association between the routing data and the routing data group can be better represented , thus efficiently and reliably identifying routing data that has both routing identifiers and routing group identifiers.

In an example, the information shown in Table 1 may be recorded in the first information set:

Routing group ID shared routing definition path prefix Z1 /console/marketing/authorization Z2 /console/after-sale serving/authorization

Table 1

The quantity of the second information set can be two, and one of the second information sets can record the information shown in Table 2, and the other second information set can record the information shown in Table 3:

routing rule information logo asserter a Z1 Assertor b Z1 asserter m r1 assertor f r2

Table 2

routing rule information logo filter c Z1 filter g r1 filter n r2

table 3

The information shown in Table 4 may be recorded in the third information set:

logo Routing basic information Z1 Routing Basic Information 1 r1 Routing Basic Information 2 r2 Routing Basic Information 3

Table 4

Assuming that the first routing ID is r1 and the first routing group ID is Z1, it can be seen from Table 1 above that the first shared routing definition path prefix corresponding to Z1 is /console/marketing/authorization; from the above Table 2 and Table 3, it can be seen that the first shared routing rule information corresponding to Z1 may include asserter a, asserter b, and filter c, and the first private routing rule information corresponding to r1 may include asserter m and filter g; from the above Table 4 shows that the first routing basic information corresponding to r1 is routing basic information 2, and routing basic information 2 may include a private routing definition path suffix, and the private routing definition path suffix can be used as the first private routing definition path suffix. So far, the path prefix of the first shared routing definition, the first shared routing rule information, the first private routing rule information, and the first private routing definition path suffix have all been successfully obtained, and then the routing data corresponding to r1 can be generated through information assembly (that is, to be generate routing data).

In the embodiments of the present disclosure, referring to the first information set, the second information set and the third information set, it is possible to efficiently and reliably determine the first shared routing definition path prefix, the first shared routing rule information, the first private routing rule information, The first private route defines a path suffix, so as to realize the generation of routing data to be generated accordingly, and, by using the first information set to store the shared route definition path prefix, use the second information set to store routing rule information, and use the third information set Storing the routing basic information can make the storage of routing-related information more regular, facilitate information search, and help ensure the generation speed of routing data.

On the basis of the embodiment shown in FIG. 2 , as shown in FIG. 3 , the method further includes step 130 , step 140 , step 150 , step 160 and step 170 .

Step 130, receiving a user's operation request on the second information set or the third information set.

Optionally, the user can initiate an operation request for the second information set or the third information set through touch input, keyboard input, mouse input, voice input, etc.; where the operation request can be used to request the second information set Or the third information set is added, deleted, modified, checked, etc.

Step 140, receiving verification information input by the user.

Optionally, the user may input verification information through keyboard input, mouse input, voice input, etc.; the verification information may include the user's identification information, for example, the user's UCID (Universal Call Identifier).

Step 150, determining the first microservice selected by the user.

Optionally, the user can select a microservice from multiple microservices through keyboard input, mouse input, voice input, etc., and the microservice selected by the user can be used as the first microservice.

Optionally, in the housing rental and sales scenario, the new house can be used as a microservice, the second-hand house can be used as another microservice, and the factory building can be used as another microservice.

It should be noted that any routing data involved in the embodiments of the present disclosure can belong to a microservice, and the microservice to which the routing data belongs can be represented by the application_id field in the corresponding routing basic information.

Step 160, based on the verification information, determine the user's authority information corresponding to the first microservice.

Optionally, a list of administrators corresponding to the first microservice may be stored in advance, and the list of administrators may include the respective UCIDs of at least one administrator; where at least one administrator may include at least one of the following: ordinary administrators, super administrators .

The verification information may include the user's UCID. If the user's UCID is in the administrator list, it can be determined that the user does not have the operation authority corresponding to the first microservice. If the user's UCID is in the administrator list, it can be determined that the user has the first microservice. The operation authority corresponding to the microservice, and further, it can also be determined what kind of operation authority the user has corresponding to the first microservice, so that the authority information of the user corresponding to the first microservice can be obtained.

Step 170, process the operation request based on the authority information.

In an alternative embodiment,

Before step 170, the method also includes:

Obtaining the public information of the first service corresponding to the first microservice;

Step 170, including at least one of the following:

Responding to the authority information indicating that the user does not have the operation authority corresponding to the first microservice, does not respond to the operation request, and displays the public information of the first service and a list of administrators corresponding to the first microservice;

Responding to the authority information indicating that the user has the first type of operation authority corresponding to the first microservice, responding to the operation request, and displaying the first service public information;

In response to the permission information indicating that the user has the second type of operation permission corresponding to the first microservice, respond to the operation request, and display the public information of the first service and a preset configuration page corresponding to the first microservice.

Optionally, a fourth information set may be preset, and the fourth information set may record the correspondence between microservices and service public information, and the service public information may include at least one of the following: service identifier, forwarding address; wherein, Service identifiers include but are not limited to service IDs, service names, and so on.

Optionally, the fourth information set may be located in the stored routing information, or located outside the stored routing information.

Optionally, the first type of operation authority may be the operation authority corresponding to the ordinary administrator, and the second type of operation authority may be the operation authority corresponding to the super administrator.

In this implementation manner, according to the corresponding relationship recorded in the fourth information set, the first service public information corresponding to the first microservice can be determined efficiently and reliably.

If the authority information of the user corresponding to the first microservice indicates that the user does not have the operation authority corresponding to the first microservice, the user may not respond to the operation request, for example, assuming that the application_id field in a certain routing basic information in the third information set indicates The routing data corresponding to the current basic routing information belongs to the first microservice, so users are not allowed to add, delete, modify, and check the basic routing information. In addition, the public information of the first service and the first microservice can also be presented to the user The administrator list corresponding to the service is convenient for the user to view the public information of the first service, and the user can contact the administrator of the first microservice to enable the operation authority corresponding to the first microservice.

If the permission information of the user corresponding to the first microservice indicates that the user has the first operation permission corresponding to the first microservice, the user can respond to the operation request, that is, allow the user to add, delete, and delete the second information set or the third information set. In addition, the public information of the first service can also be presented to the user.

If the authority information of the user corresponding to the first microservice indicates that the user has the second type of operation authority corresponding to the first microservice, in addition to responding to the operation request and presenting the public information of the first service to the user, it is also possible to present the second service authority to the user. A preset configuration page corresponding to a microservice. The preset configuration page can be the advanced configuration page of the first microservice. Users can operate on the advanced configuration page according to actual needs, so as to perform operations on the second information set or the third information set. For advanced configuration, for example, under the first type of operation authority, the user may only modify a certain value in the third information set within a certain value range, while under the second type of operation authority, through the advanced configuration page, the user can modify the first The value in the three information sets is modified to any value required by itself.

In the embodiment of the present disclosure, when receiving the user's operation request for the second information set or the third information set, it can be determined that the user corresponds to the first microservice to which the routing data to be generated belongs by referring to the verification information input by the user. Authority information, in order to refer to the determined authority information, and process the operation request in an appropriate way. In this way, through authority control, it can be ensured that only authorized personnel can operate the routing information under the corresponding service in the stored routing information. Therefore, it is beneficial to ensure the security and reliability of the stored routing information. In addition, each routing data belongs to the corresponding microservice, which is conducive to the isolation of routing data between different businesses, thereby avoiding mutual influence between different businesses.

On the basis of the embodiment shown in FIG. 2 , as shown in FIG. 4 , the method further includes step 175 , step 180 , step 185 and step 190 .

Step 175, display multiple routing attribute options.

Optionally, as shown in FIG. 5 , the multiple route attribute options may include an interface Uniform Resource Identifier (UniformResource Identifier, URI) option, a login option, an authority point option, and the like.

Step 180, receiving a routing configuration operation input by the user; wherein, the routing configuration operation is used to respectively input selected parameters for multiple routing attribute options.

Optionally, users can perform routing configuration operations through keyboard input, mouse input, voice input, etc. For example, users can fill in a certain interface URI in the rectangular box behind "Interface Uri" in Figure 5, and select the "Yes" or "No" behind "Do you need to log in", select the required permission point from the drop-down menu in the rectangular box behind "Permission Point" in Figure 5, and the interface URI filled in by the user can be used as an option for the interface URI The selected parameter input, "Yes" or "No" selected by the user may be used as the selected parameter input for the login option, and the permission point selected by the user may be used as the selected parameter input for the permission point option.

Step 185, corresponding to the route configuration operation, determine the second route identifier.

In step 185, it is possible to traverse all the identifiers in the third information set, and generate another identifier different from all the identifiers in the third information set according to preset rules, and the generated identifier can be used as the second route logo.

Assuming that all the identifiers in the third information set are in the form of numerical IDs, the ID with the largest numerical value in the third information set may be determined, and the sum of the ID with the largest numerical value and 1 is used as the second routing identifier.

Step 190: Add corresponding information to the second information set and the third information set respectively based on the selected parameters corresponding to the plurality of routing attribute options and the second routing identifier.

Continuing the above example for Figure 5, assuming that the interface URI filled in by the user is "/api/v1/frame", and the user selects "Yes", a new piece of basic routing information can be added to the third information set. The basic routing information Corresponding to the second routing identifier, and "/api/v1/frame" is placed in a certain position in the routing basic information, and a new routing rule information can be added to the second information set, and the routing rule information is the same as The second routing identifier corresponds, and the routing rule information is used to indicate that login is required.

In the embodiment of the present disclosure, by presenting multiple routing attribute options to the user in a visual manner, the user can input selected parameters for multiple routing attribute options according to actual needs, and through a simple input operation, it can automatically send to the second Corresponding information is added to the information set and the third information set, and complex routing data in JSON format can be automatically generated subsequently based on the added information.

In an optional example, the first shared route attribute information includes: the first shared route definition path prefix and the first shared route rule information, and the first private route attribute information includes: the first private route definition path suffix and the first private route rule information;

Information assembly is performed on the first shared routing attribute information and the first private routing attribute information to generate routing data to be generated, including:

In response to the conflict between the first routing rule information in the first shared routing rule information and the second routing rule information in the first private routing rule information, define a path prefix for the first shared route, except the first shared routing rule information in the first shared routing rule information Routing rule information other than the routing rule information, the first private routing definition path suffix, and the first private routing rule information are assembled to generate routing data to be generated.

It should be noted that the determination method of the first shared route definition path prefix, the first shared route rule information, the first private route definition path suffix and the first private route rule information can refer to the relevant introduction above, and will not be repeated here. repeat.

Assuming that there is first routing rule information in the first shared routing rule information, the first routing rule information indicates that login is required, the first private routing rule information contains second routing rule information, and the second routing rule information indicates that login is not required, Then it can be considered that the first routing rule information conflicts with the second routing rule information. At this time, the first routing rule information in the first shared routing rule information can be discarded, and the remaining information of the first shared routing rule information can be used to generate The generation of routing data is beneficial to avoid conflicting routing rule information in the generated routing data, thereby ensuring the correctness of the generated routing data.

On the basis of the embodiment shown in Figure 1, as shown in Figure 6, before step 120, the method also includes:

Step 112, determining the second microservice to which the routing data to be generated belongs.

In step 112, the application_id field in the basic routing information corresponding to the routing data to be generated may be referred to to determine the second microservice to which the routing data to be generated belongs.

Step 114, acquiring public information of the second service corresponding to the second microservice.

It should be noted that, for the specific implementation process of step 114 , please refer to the related introduction of the manner of obtaining the public information of the first service above, and details will not be repeated here.

Step 120 includes step 1201 .

Step 1201, information assembly is performed on the first shared route attribute information, the first private route attribute information and the second service public information, so as to generate routing data to be generated.

In an optional implementation manner, the first shared route attribute information includes: the first shared route definition path prefix and the first shared route rule information, and the first private route attribute information includes: the first private route definition path suffix and the first A private routing rule information, the second service public information includes: the first service identifier and the first forwarding address;

Step 1201, including:

performing information assembly on the first service identifier, the first shared route definition path prefix, and the first private route definition path suffix to generate the first target data;

performing information assembly on the first forwarding address, the first shared route definition path prefix, and the first private route definition path suffix to generate second target data;

performing information assembly on the first shared routing rule information and the first private routing rule information to generate third target data;

The routing data to be generated including the first target data, the second target data and the third target data is generated.

Suppose the path prefix of the first shared route definition is console/marketing/authorization, the first shared route rule information includes asserter a, asserter b, and filter c, the path suffix of the first private route definition is /update, and the first private route rule The information includes asserter m, filter g, the first service identifier is serviceId, and the first forwarding address is lb://xxx.com, then the first target data can be represented as follows: serviceId/console/marketing/authorization/update , the second target data can be represented as follows: lb://xxx.com/console/marketing/authorization/update, the third target data can include two parts, one of which is asserter a, asserter b, asserter m , the other part is filter c and filter g, from which the routing data to be generated including the first target data, the second target data and the third target data can be obtained. The routing data to be generated specifically includes four parts, which are:

1. The path requested by the front end (corresponding to the first target data)

2. The target service address to be forwarded to (corresponding to the second target data)

3. Assertor (corresponding to a part of the third target data)

4. Filter (corresponding to another part in the third target data).

In this embodiment, by assembling the first shared routing definition path prefix, the first shared routing rule information, the first private routing definition path suffix, the first private routing rule information, the first service identifier and the first forwarding address, The generation of routing data can be realized efficiently and reliably, and after the generated routing data is provided to the gateway device, effective guidance can be provided for processing and forwarding of corresponding data requests.

In an example, suppose there are two routing data, namely routing data 1 and routing data 2, wherein routing data 1 includes asserter a, asserter b, asserter m, filter c, filter g, and routing Data 2 includes asserter a, asserter b, asserter f, filter c, and filter n, and the routing definition path in routing data 1 is lb://xxx.com/console/marketing/authorization/update, The routing definition route in routing data 2 is lb://xxx.com/console/marketing/authorization/copy, and in related technologies, in order to realize the generation of routing data 1 and routing data 2, the gateway configuration background needs to target routing The routing identifier of data 1 stores asserter a, asserter b, asserter m, filter c, filter g, and lb://xxx.com/console/marketing/authorization/update, and for the route of routing data 2 Identify and store asserter a, asserter b, asserter f, filter c, filter n, and lb://xxx.com/console/marketing/authorization/copy. Obviously, the information stored in the background of the gateway configuration is more Much redundancy.

In view of this, in the embodiments of the present disclosure, the concept of routing data group can be introduced, specifically, routing data 1 and routing data 2 can be classified into the same routing data group, and for the routing group identifier of the routing data group, you can Store asserter a, asserter b, filter c, /console/marketing/authorization for the routing identifier of routing data 1, and additionally store assertor m, filter g, and /update for routing identifier of routing data 2 , can additionally store assertor f, filter n, and /copy. In this way, when actually generating routing data such as routing data 1 and routing data 2, you can first scan the private filter, assertor, routing definition path suffix, etc. of the routing data, and then scan the routing data group to which this routing data belongs Shared assertors, routers, route definition path prefixes, etc., through information assembly, can eventually become a route data that can be provided to the gateway device. Compared with related technologies, in order to realize the generation of routing data, the amount of information required to be stored in the gateway configuration background is greatly reduced, thereby avoiding waste of resources.

Any routing data generation method provided by the embodiments of the present disclosure may be executed by any appropriate device with data processing capabilities, including but not limited to: terminal devices, servers, and the like. Alternatively, any routing data generating method provided in the embodiments of the present disclosure may be executed by a processor, for example, the processor executes any routing data generating method mentioned in the embodiments of the present disclosure by calling a corresponding instruction stored in a memory. I won't go into details below.

Exemplary device

FIG. 7 is a schematic structural diagram of an apparatus for generating routing data provided by an exemplary embodiment of the present disclosure. The apparatus shown in FIG. 7 includes a first obtaining module 710 and a generating module 720 .

The first obtaining module 710 is configured to obtain the first shared routing attribute information corresponding to the first routing group identifier from the stored routing information in response to the routing data to be generated having the first routing identifier and the first routing group identifier, and the second First private route attribute information corresponding to a route identifier;

The generating module 720 is configured to perform information assembly on the first shared routing attribute information and the first private routing attribute information, so as to generate routing data to be generated.

In an optional example, the stored routing information includes: a first information set, a second information set, and a third information set, the first information set records the correspondence between the routing group identifier and the path prefix of the shared route definition, A plurality of routing rule information is recorded in the second information set, each routing rule information in the second information set corresponds to a routing identifier or a routing group identifier, and a plurality of routing basic information is recorded in the third information set, each basic The routing basic information corresponds to a routing identifier or a routing group identifier;

The first acquiring module 710 includes:

The first determination submodule is configured to determine the first shared routing definition path prefix corresponding to the first routing group identifier based on the first information set;

The second determining submodule is configured to determine the first shared routing rule information corresponding to the first routing group identifier and the first private routing rule information corresponding to the first routing identifier based on the second information set;

The obtaining submodule is configured to determine the first routing basic information corresponding to the first routing identifier based on the third information set, and obtain the first private route definition path suffix corresponding to the first routing identifier from the first routing basic information;

Wherein, the first shared route attribute information includes: first shared route definition path prefix and first shared route rule information, and the first private route attribute information includes: first private route definition path suffix and first private route rule information.

In an optional example, the device also includes:

The first receiving module is configured to receive a user's operation request for the second information set or the third information set;

The second receiving module is configured to receive verification information input by the user;

A first determining module, configured to determine the first microservice selected by the user;

The second determination module is used to determine the permission information of the user corresponding to the first microservice based on the verification information;

The processing module is configured to process the operation request based on the permission information.

In an optional example,

The unit also includes:

The second obtaining module is used to obtain the public information of the first service corresponding to the first microservice before processing the operation request based on the authority information;

processing modules, including at least one of the following:

The first processing submodule is configured to respond to the authority information indicating that the user does not have the operation authority corresponding to the first microservice, does not respond to the operation request, and displays the public information of the first service and a list of administrators corresponding to the first microservice;

The second processing submodule is used to respond to the operation request and display the public information of the first service in response to the authority information indicating that the user has the first type of operation authority corresponding to the first microservice;

The third processing sub-module is configured to respond to the operation request in response to the permission information indicating that the user has the second type of operation permission corresponding to the first microservice, and display the public information of the first service and a preset configuration page corresponding to the first microservice.

In an optional example, the device also includes:

A display module for displaying multiple route attribute options;

The third receiving module is used to receive the routing configuration operation input by the user; wherein, the routing configuration operation is used to respectively input selected parameters for multiple routing attribute options;

A third determining module, configured to determine the second routing identifier corresponding to the routing configuration operation;

The adding module is configured to add corresponding information to the second information set and the third information set respectively based on the selected parameters corresponding to the multiple routing attribute options and the second routing identifier.

In an optional example, the first shared route attribute information includes: the first shared route definition path prefix and the first shared route rule information, and the first private route attribute information includes: the first private route definition path suffix and the first private route rule information;

The generation module 720 is specifically used for:

In response to the conflict between the first routing rule information in the first shared routing rule information and the second routing rule information in the first private routing rule information, define a path prefix for the first shared route, except the first shared routing rule information in the first shared routing rule information Routing rule information other than the routing rule information, the first private routing definition path suffix, and the first private routing rule information are assembled to generate routing data to be generated.

In an optional example,

The unit also includes:

The fourth determination module is used to determine the second microservice to which the routing data to be generated belongs before performing information assembly on the first shared routing attribute information and the first private routing attribute information to generate the routing data to be generated;

A third acquisition module, configured to acquire the public information of the second service corresponding to the second microservice;

The generation module 720 is specifically used for:

Information assembly is performed on the first shared routing attribute information, the first private routing attribute information, and the second service public information to generate routing data to be generated.

In an optional example, the first shared route attribute information includes: the first shared route definition path prefix and the first shared route rule information, and the first private route attribute information includes: the first private route definition path suffix and the first private route Rule information, the second service public information includes: the first service identifier and the first forwarding address;

Generate module 720, comprising:

The first generation sub-module is used to assemble information on the first service identifier, the first shared route definition path prefix, and the first private route definition path suffix, so as to generate the first target data;

The second generation submodule is used to assemble information on the first forwarding address, the first shared route definition path prefix, and the first private route definition path suffix, so as to generate the second target data;

A third generating submodule, configured to assemble the first shared routing rule information and the first private routing rule information to generate third target data;

The fourth generating submodule is configured to generate routing data to be generated including first target data, second target data and third target data.

Exemplary electronic device

Hereinafter, an electronic device according to an embodiment of the present disclosure is described with reference to FIG. 8 . The electronic device may be either or both of the first device and the second device, or a stand-alone device independent of them, and the stand-alone device may communicate with the first device and the second device to receive collected data from them. input signal.

FIG. 8 illustrates a block diagram of an electronic device 800 according to an embodiment of the disclosure.

As shown in FIG. 8 , electronic device 800 includes one or more processors 810 and memory 820 .

The processor 810 may be a central processing unit (CPU) or other form of processing unit having data processing capabilities and/or instruction execution capabilities, and may control other components in the electronic device 800 to perform desired functions.

The memory 820 may store one or more computer program products, and the memory 820 may include various forms of computer-readable storage media, such as volatile memory and/or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and/or cache memory (cache). The non-volatile memory may include, for example, a read-only memory (ROM), a hard disk, a flash memory, and the like. One or more computer program products may be stored on the computer-readable storage medium, and the processor 810 may run the computer program products to implement the routing data generation method and/or the above-mentioned various embodiments of the present disclosure or other desired functionality. Various contents such as input signal, signal component, noise component, etc. may also be stored in the computer-readable storage medium.

In an example, the electronic device 800 may further include: an input device 830 and an output device 840, and these components are interconnected through a bus system and/or other forms of connection mechanisms (not shown).

For example, when the electronic device 800 is the first device or the second device, the input device 830 may be a microphone or a microphone array. When the electronic device 800 is a stand-alone device, the input device 830 may be a communication network connector for receiving collected input signals from the first device and the second device.

In addition, the input device 830 may also include, for example, a keyboard, a mouse, and the like.

The output device 840 can output various information to the outside. The output device 840 may include, for example, a display, a speaker, a printer, a communication network and its connected remote output devices, and the like.

Of course, for simplicity, only some components related to the present disclosure in the electronic device 800 are shown in FIG. 8 , and components such as bus, input/output interface, etc. are omitted. In addition, according to specific application conditions, the electronic device 800 may further include any other appropriate components.

Exemplary computer program product and computer readable storage medium

In addition to the above-mentioned methods and devices, embodiments of the present disclosure may also be computer program products, which include computer program instructions that, when executed by a processor, cause the processor to perform the above-mentioned "exemplary method" of this specification. The steps in the routing data generating method according to various embodiments of the present disclosure described in the section.

The computer program product can be written in any combination of one or more programming languages to execute the program codes for performing the operations of the embodiments of the present disclosure, and the programming languages include object-oriented programming languages, such as Java, C++, etc. , also includes conventional procedural programming languages, such as the "C" language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server to execute.

In addition, the embodiments of the present disclosure may also be a computer-readable storage medium, on which computer program instructions are stored, and the computer program instructions, when executed by a processor, cause the processor to execute the above-mentioned "Exemplary Method" section of this specification. The steps in the method for generating routing data according to various embodiments of the present disclosure described in .

The computer readable storage medium may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may include, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination thereof, for example. More specific examples (non-exhaustive list) of readable storage media include: electrical connection with one or more conductors, portable disk, hard disk, random access memory (RAM), read only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

The basic principles of the present disclosure have been described above in conjunction with specific embodiments, but it should be pointed out that the advantages, advantages, effects, etc. mentioned in the present disclosure are only examples rather than limitations, and these advantages, advantages, effects, etc. Various embodiments of the present disclosure must have. In addition, the specific details disclosed above are only for the purpose of illustration and understanding, rather than limitation, and the above details do not limit the present disclosure to be implemented by using the above specific details.

Each embodiment in this specification is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same or similar parts of each embodiment can be referred to each other. As for the system embodiment, since it basically corresponds to the method embodiment, the description is relatively simple, and for the related parts, please refer to the part of the description of the method embodiment.

The block diagrams of devices, devices, devices, and systems involved in the present disclosure are only illustrative examples and are not intended to require or imply that they must be connected, arranged, and configured in the manner shown in the block diagrams. As will be appreciated by those skilled in the art, these devices, devices, devices, systems may be connected, arranged, configured in any manner. Words such as "including", "comprising", "having" and the like are open-ended words meaning "including but not limited to" and may be used interchangeably therewith. As used herein, the words "or" and "and" refer to the word "and/or" and are used interchangeably therewith, unless the context clearly dictates otherwise. As used herein, the word "such as" refers to the phrase "such as but not limited to" and can be used interchangeably therewith.

The methods and apparatus of the present disclosure may be implemented in many ways. For example, the methods and apparatuses of the present disclosure may be implemented by software, hardware, firmware or any combination of software, hardware, and firmware. The above sequence of steps for the method is for illustration only, and the steps of the method of the present disclosure are not limited to the sequence specifically described above unless specifically stated otherwise. Furthermore, in some embodiments, the present disclosure can also be implemented as programs recorded in recording media, the programs including machine-readable instructions for realizing the method according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

It should also be pointed out that, in the devices, equipment and methods of the present disclosure, each component or each step can be decomposed and/or reassembled. These decompositions and/or recombinations should be considered equivalents of the present disclosure.

The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects without departing from the scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the aspects shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

The foregoing description has been presented for purposes of illustration and description. Furthermore, this description is not intended to limit the disclosed embodiments to the forms disclosed herein. Although a number of example aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, changes, additions and sub-combinations thereof.

Claims (10)

1. A routing data generation method, characterized in that, comprising: In response to the fact that the routing data to be generated has a first routing identifier and a first routing group identifier, from the stored routing information, obtain first shared routing attribute information corresponding to the first routing group identifier, and the first routing identifier corresponding to The attribute information of the first private route; Information assembly is performed on the first shared routing attribute information and the first private routing attribute information to generate the to-be-generated routing data. 2. The method according to claim 1, wherein the stored routing information includes: a first information set, a second information set, and a third information set, and the routing group identifier is recorded in the first information set The corresponding relationship with the shared routing definition path prefix, the second information set records a plurality of routing rule information, and each routing rule information in the second information set corresponds to a routing identifier or a routing group identifier, A plurality of routing basic information is recorded in the third information set, and each basic routing basic information corresponds to a routing identifier or a routing group identifier; The acquiring the first shared routing attribute information corresponding to the first routing group identifier and the first private routing attribute information corresponding to the first routing identifier from the stored routing information includes: Based on the first information set, determine a first shared routing definition path prefix corresponding to the first routing group identifier; Based on the second information set, determine first shared routing rule information corresponding to the first routing group identifier, and first private routing rule information corresponding to the first routing identifier; Based on the third information set, determine the first routing basic information corresponding to the first routing identifier, and obtain the first private route definition path suffix corresponding to the first routing identifier from the first routing basic information ; Wherein, the first shared routing attribute information includes: the first shared routing definition path prefix and the first shared routing rule information, and the first private routing attribute information includes: the first private routing definition path suffix and the first private routing rule information. 3. The method according to claim 2, wherein the method further comprises: receiving a user's operation request on the second information set or the third information set; receiving verification information input by the user; determining the first microservice selected by the user; Based on the verification information, determine the authority information of the user corresponding to the first microservice; Based on the authority information, the operation request is processed. 4. The method of claim 3, wherein, Before processing the operation request based on the authority information, the method further includes: Obtaining first service public information corresponding to the first microservice; The processing of the operation request based on the permission information includes at least one of the following: Responding to the authority information indicating that the user does not have the operation authority corresponding to the first microservice, not responding to the operation request, and displaying the public information of the first service and the administrator corresponding to the first microservice list; Responding to the authority information indicating that the user has the first type of operation authority corresponding to the first microservice, responding to the operation request, and displaying the first service public information; Responding to the authority information indicating that the user has the second type of operation authority corresponding to the first microservice, responding to the operation request, and displaying the public information of the first service and the preset information corresponding to the first microservice Set configuration page. 5. The method according to claim 2, characterized in that the method further comprises: Show multiple routing attribute options; A routing configuration operation that receives user input; wherein, the routing configuration operation is used to respectively input selected parameters for the plurality of routing attribute options; determining a second routing identifier corresponding to the routing configuration operation; Adding corresponding information to the second information set and the third information set respectively based on the selected parameters corresponding to the plurality of routing attribute options and the second routing identifier. 6. The method according to claim 1, wherein the first shared route attribute information includes: first shared route definition path prefix and first shared route rule information, and the first private route attribute information includes: The first private route defines path suffix and first private route rule information; The information assembling of the first shared routing attribute information and the first private routing attribute information to generate the routing data to be generated includes: In response to the conflict between the first routing rule information in the first shared routing rule information and the second routing rule information in the first private routing rule information, define a path prefix for the first shared route, the first In the shared routing rule information, routing rule information other than the first routing rule information, the first private route definition path suffix, and the first private routing rule information are assembled to generate the route to be generated data. 7. The method of claim 1, wherein, Before performing information assembly on the first shared routing attribute information and the first private routing attribute information to generate the routing data to be generated, the method further includes: determining the second microservice to which the routing data to be generated belongs; Acquire second service public information corresponding to the second microservice; The information assembling of the first shared routing attribute information and the first private routing attribute information to generate the routing data to be generated includes: Information assembly is performed on the first shared routing attribute information, the first private routing attribute information, and the second service public information to generate the to-be-generated routing data. 8. The method according to claim 7, wherein the first shared routing attribute information includes: the first shared routing definition path prefix and first shared routing rule information, and the first private routing attribute information includes: The first private route defines a path suffix and first private route rule information, and the second service public information includes: the first service identifier and the first forwarding address; The information assembling of the first shared routing attribute information and the first private routing attribute information to generate the routing data to be generated includes: performing information assembly on the first service identifier, the first shared route definition path prefix, and the first private route definition path suffix to generate first target data; performing information assembly on the first forwarding address, the first shared route definition path prefix, and the first private route definition path suffix to generate second target data; performing information assembly on the first shared routing rule information and the first private routing rule information to generate third target data; generating the to-be-generated routing data including the first target data, the second target data and the third target data. 9. An electronic device, characterized in that it comprises: memory for storing computer program products; The processor is configured to execute the computer program product stored in the memory, and when the computer program product is executed, implement the method for generating route data according to any one of claims 1 to 8 above. 10. A computer-readable storage medium, on which computer program instructions are stored, characterized in that, when the computer program instructions are executed by a processor, the generation of routing data according to any one of claims 1 to 8 is realized method.

Images