Methods, apparatus, equipment, and storage media for constructing cross-domain resource service grids
By registering sub-routing services and resource services using public IP addresses as the main routing service in the cross-domain resource service mesh, the challenges of constructing and managing the cross-domain resource service mesh are solved, enabling low-cost and efficient cross-domain resource invocation and collaboration.
Patent Information
- Application Number
- CN202311192057.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-09-14
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2043-09-14
AI Technical Summary
How to quickly and cost-effectively build a cross-domain resource service mesh to solve network interconnection limitations and management challenges between different domains, especially to enable resource access and collaboration across multiple domains.
A main routing service with a public IP address is adopted. Each sub-routing service is registered to the cross-domain resource service mesh through the main routing service, and the resource services are registered to the mesh through the first intermediate routing service. The resource service lists of each routing service and the main routing service are updated to complete the construction of the cross-domain resource service mesh.
It reduces the construction and maintenance costs of cross-domain resource service meshes, expands network scale, simplifies cross-domain call collaboration of resource services, supports the rapid construction of cross-domain storage and computing services, and is not limited by network connectivity.
Smart Images

Figure CN117424844B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of network communication technology, and in particular to a method, apparatus, device and storage medium for constructing a cross-domain resource service grid. Background Technology
[0002] Computing infrastructure, represented by artificial intelligence computing centers, supercomputing centers, and integrated big data centers, has become an important component of the nation's new infrastructure, with computing power development shifting from a decentralized to a centralized approach. As computing centers and infrastructure are gradually completed across the country, artificial intelligence computing power will also gradually move from a single computing center model to a computing network model. In particular, the construction of the national supercomputing internet and its service platform will further optimize the distribution and application of supercomputing power within China, thus forming a "highway" supporting the construction of Digital China.
[0003] Against this backdrop, it is particularly important to quickly build a dynamic resource service mesh that supports collaborative management and invocation of cross-domain resource services. In particular, how to break through the limitations of local area networks between different domains and realize cross-domain resource invocation and collaboration is also a key problem that needs to be solved.
[0004] To address the issue of interconnecting networks across multiple domains, one approach is to establish dedicated, bidirectional interconnection lines between each pair of domains. However, this method is costly to build and difficult to implement. Another approach is to utilize existing VPN technology, deploying and configuring the same VPN across multiple domains to connect them. However, this method is prone to causing local area network address conflicts between domains and is also difficult to deploy and manage. Summary of the Invention
[0005] The main objective of this application is to provide a method, apparatus, device, and storage medium for constructing a cross-domain resource service grid, aiming to solve the technical problem of how to quickly construct a cross-domain dynamic resource service grid in a low-cost, easy-to-deploy, and manageable manner.
[0006] To achieve the above objectives, this application provides a method for constructing a cross-domain resource service grid, the method comprising:
[0007] Start the main routing service deployed in the cross-domain resource service mesh;
[0008] Based on the main routing service, each sub-routing service is registered to the cross-domain resource service mesh;
[0009] Determine the first intermediate routing service corresponding to each resource service in each of the sub-routing services and the main routing service, and register each resource service to the cross-domain resource service mesh through each of the first intermediate routing services;
[0010] The resource service lists of each sub-routing service and the main routing service are updated based on the resource registration information of each resource service to complete the construction of the cross-domain resource service mesh.
[0011] Optionally, in one feasible embodiment, the step of registering each sub-routing service to the cross-domain resource service mesh based on the main routing service includes:
[0012] Determine the target sub-routing service currently registering in each of the sub-routing services, and the second intermediate routing service corresponding to the target sub-routing service, wherein the second intermediate routing service is the main routing service or a sub-routing service that has completed registration;
[0013] The routing registration information of the target sub-routing service is added to the cross-domain resource service mesh through the second intermediate routing service.
[0014] Optionally, in one feasible embodiment, after the step of adding the routing registration information of the target sub-routing service to the cross-domain resource service mesh via the second intermediate routing service, the method further includes:
[0015] Based on the routing registration information, update the network topology information and routing table information of each of the sub-routing services and the main routing service in the cross-domain resource service mesh.
[0016] Optionally, in a feasible embodiment, the step of updating the network topology information and routing table information of each of the sub-routing services and the main routing service in the cross-domain resource service mesh based on the routing registration information includes:
[0017] The target sub-routing service outputs the route registration information to the first routing service adjacent to the target sub-routing service.
[0018] Update the network topology information and routing table information of the first routing service according to the routing registration information;
[0019] The routing registration information is output to the second routing service adjacent to the first routing service through the first routing service;
[0020] The second routing service is used as the first routing service, and the process returns to the step of updating the network topology information and routing table information of the first routing service according to the routing registration information, until the network topology information and routing table information of each sub-routing service and the main routing service in the cross-domain resource service mesh are updated.
[0021] Optionally, in a feasible embodiment, the step of updating the network topology information and routing table information of the first routing service according to the registration information includes:
[0022] The target connection method between the first routing service and the target sub-routing service in the network topology information of the first routing service is updated according to the routing registration information, wherein the target connection method includes: routing relay mode;
[0023] When the target connection mode is a route relay mode, the routing table information of the first route service is updated according to the route registration information.
[0024] Optionally, in one feasible embodiment, the step of updating the resource service lists of each of the sub-routing services and the main routing service based on the resource registration information of each of the resource services includes:
[0025] Determine the target resource service currently registered in each of the resource services, and the target routing service corresponding to the target resource service in each of the first intermediate routing services;
[0026] The resource registration information of the resource service is output to the third routing service adjacent to the target routing service through the target routing service;
[0027] Update the resource service list of the third routing service according to the resource registration information;
[0028] The resource registration information is output to the fourth routing service adjacent to the third routing service through the third routing service;
[0029] The fourth routing service is used as the third routing service, and the process returns to the step of updating the resource service list of the third routing service according to the resource registration information, until the resource service lists of each sub-routing service and the main routing service in the cross-domain resource service mesh are updated.
[0030] Optionally, in a feasible embodiment, the step of updating the resource service lists of each of the sub-routing services and the main routing service based on the resource registration information of each of the resource services further includes:
[0031] Each resource service generates its own proxy address based on its unique identifier, and adds each proxy address to the resource service list.
[0032] Furthermore, to achieve the above objectives, this application also provides a cross-domain resource service grid construction apparatus, wherein the cross-domain resource service grid construction apparatus is a virtual apparatus, and the cross-domain resource service grid construction apparatus includes:
[0033] The main route deployment module is used to start the main route service deployed in the cross-domain resource service mesh;
[0034] The sub-route registration module is used to register each sub-route service to the cross-domain resource service mesh based on the main route service;
[0035] The resource service registration module is used to determine the first intermediate routing service corresponding to each resource service in each of the sub-routing services and the main routing service, and register each resource service to the cross-domain resource service mesh through each of the first intermediate routing services;
[0036] The grid construction module is used to update the resource service lists of each sub-routing service and the main routing service based on the resource registration information of each resource service, so as to complete the construction of the cross-domain resource service grid.
[0037] In addition, to achieve the above objectives, this application also provides a cross-domain resource service mesh construction device, which includes: a memory, a processor, and a cross-domain resource service mesh construction program stored in the memory and executable on the processor. When the cross-domain resource service mesh construction program is executed by the processor, it implements the steps of the cross-domain resource service mesh construction method described above.
[0038] This application also provides a computer storage medium storing a cross-domain resource service grid construction program, which, when executed by a processor, implements the steps of the cross-domain resource service grid construction method described above.
[0039] This application provides a method, apparatus, device, and storage medium for constructing a cross-domain resource service mesh. The method for constructing the cross-domain resource service mesh includes: starting a main routing service deployed in the cross-domain resource service mesh; registering each sub-routing service to the cross-domain resource service mesh based on the main routing service; determining the first intermediate routing service corresponding to each resource service in each sub-routing service and the main routing service, and registering each resource service to the cross-domain resource service mesh through each first intermediate routing service; and updating the resource service lists of each sub-routing service and the main routing service based on the resource registration information of each resource service, thereby completing the construction of the cross-domain resource service mesh.
[0040] Compared to existing technologies that use dedicated networks or VPNs for cross-domain network interconnection, the cross-domain resource service mesh construction method of this application constructs the cross-domain resource service mesh by using a main routing service with a public IP address. Multiple sub-routes that are directly or indirectly connected to the main route are registered in the cross-domain resource service. When adding a resource service, the resource service is registered to the cross-domain resource service through a sub-route within the same domain. When resources in different domains need to be accessed, cross-domain access to resource services can be achieved simply by connecting the routing services.
[0041] Therefore, the method of constructing a cross-domain resource service network based on the aforementioned main routing service with a public IP address, compared with the traditional method of using leased networks or configuring VPNs for cross-domain network interconnection, offers lower construction and maintenance costs. Furthermore, it allows for network expansion by registering sub-routing services, and resource services can collaborate across domains without considering network connectivity, greatly simplifying the implementation of upper-layer services. Moreover, the constructed dynamic resource service mesh does not restrict the type of resource service; cross-domain storage and computing services can be quickly built upon the resource service mesh. Attached Figure Description
[0042] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0043] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, those skilled in the art can obtain other drawings based on these drawings without creative effort.
[0044] Figure 1 This is a schematic diagram of the device structure for constructing a cross-domain resource service mesh in the hardware operating environment of the device involved in the embodiments of this application.
[0045] Figure 2 This is a schematic diagram illustrating the implementation process of an embodiment of the method for constructing a cross-domain resource service grid according to this application;
[0046] Figure 3 This is a schematic diagram of the cross-domain resource service grid structure, representing an embodiment of the cross-domain resource service grid construction method of this application.
[0047] Figure 4 This document illustrates three network connection establishment modes in one embodiment of the method for constructing a cross-domain resource service grid according to this application.
[0048] Figure 5 This is a schematic diagram of the process for cross-domain resource service call handling in one embodiment of the method for constructing a cross-domain resource service mesh according to this application;
[0049] Figure 6 This is a schematic diagram of the functional modules of the device for constructing a cross-domain resource service grid according to the embodiments of this application.
[0050] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation
[0051] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.
[0052] It should be noted that computing infrastructure, represented by artificial intelligence computing centers, supercomputing centers, and integrated big data centers, has become an important component of the country's new infrastructure, and computing power construction is shifting from a decentralized to a centralized approach. As computing centers and infrastructure are gradually completed across the country, artificial intelligence computing power will also gradually move from a single computing center model to a computing network model. In particular, the construction of the national supercomputing internet and its service platform will further optimize the distribution and application of supercomputing power within China, thus forming a "highway" supporting the construction of Digital China.
[0053] Against this backdrop, it is particularly important to quickly build a dynamic resource service mesh that supports collaborative management and invocation of cross-domain resource services. In particular, how to break through the limitations of local area networks between different domains and realize cross-domain resource invocation and collaboration is also a key problem that needs to be solved.
[0054] To address the issue of interconnecting networks across multiple domains, one approach is to establish dedicated, bidirectional interconnection lines between each pair of domains. However, this method is costly to build and difficult to implement. Another approach is to utilize existing VPN technology, deploying and configuring the same VPN across multiple domains to connect them. However, this method is prone to causing local area network address conflicts between domains and is also difficult to deploy and manage.
[0055] To address the aforementioned issues, this application provides a method, apparatus, device, and storage medium for constructing a cross-domain resource service mesh. The method for constructing the cross-domain resource service mesh includes: starting a main routing service deployed in the cross-domain resource service mesh; registering each sub-routing service to the cross-domain resource service mesh based on the main routing service; determining the first intermediate routing service corresponding to each resource service in each sub-routing service and the main routing service, and registering each resource service to the cross-domain resource service mesh through each first intermediate routing service; and updating the resource service lists of each sub-routing service and the main routing service based on the resource registration information of each resource service, thereby completing the construction of the cross-domain resource service mesh.
[0056] Compared to existing technologies that use dedicated networks or VPNs for cross-domain network interconnection, the cross-domain resource service mesh construction method of this application constructs the cross-domain resource service mesh by using a main routing service with a public IP address. Multiple sub-routes that are directly or indirectly connected to the main route are registered in the cross-domain resource service. When adding a resource service, the resource service is registered to the cross-domain resource service through a sub-route within the same domain. When resources in different domains need to be accessed, cross-domain access to resource services can be achieved simply by connecting the routing services.
[0057] Therefore, the method of constructing a cross-domain resource service network based on the aforementioned main routing service with a public IP address, compared with the traditional method of using leased networks or configuring VPNs for cross-domain network interconnection, offers lower construction and maintenance costs. Furthermore, it allows for network expansion by registering sub-routing services, and resource services can collaborate across domains without considering network connectivity, greatly simplifying the implementation of upper-layer services. Moreover, the constructed dynamic resource service mesh does not restrict the type of resource service; cross-domain storage and computing services can be quickly built upon the resource service mesh.
[0058] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.
[0059] Please refer to Figure 1 , Figure 1 This is a schematic diagram of the device structure for constructing a cross-domain resource service mesh in the hardware operating environment of the device involved in the embodiments of this application.
[0060] like Figure 1As shown, the construction device for this cross-domain resource service mesh may include: a processor 1001, such as a CPU, a memory 1005, and a communication bus 1002. The communication bus 1002 is used to establish communication between the processor 1001 and the memory 1005. The memory 1005 may be high-speed RAM or stable non-volatile memory, such as disk storage. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.
[0061] Optionally, the equipment for constructing this cross-domain resource service mesh may also include a user interface 1003, a network interface 1004, a camera, RF (Radio Frequency) circuitry, sensors, audio circuitry, a WiFi module, etc. The user interface may include a display screen and an input submodule such as a keyboard. Optionally, the user interface may also include standard wired or wireless interfaces. The network interface may optionally include standard wired or wireless interfaces (such as a WiFi interface).
[0062] Those skilled in the art will understand that Figure 1 The construction device structure of the cross-domain resource service mesh shown does not constitute a limitation on the construction device of the cross-domain resource service mesh, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0063] like Figure 1 As shown, the memory 1005, which serves as a computer storage medium, may include an operating system, a network communication module, and a cross-domain resource service grid (CRPG) construction program. The operating system is a program that manages and controls the hardware and software resources of the CRPG construction device, supporting the operation of the CRPG construction program and other software and / or programs. The network communication module is used to enable communication between the various components within the memory 1005, as well as communication with other hardware and software in the CRPG construction device.
[0064] exist Figure 1 In the cross-domain resource service mesh construction device shown, processor 1001 is used to execute the cross-domain resource service mesh construction program stored in memory 1005, and perform the following operations:
[0065] Start the main routing service deployed in the cross-domain resource service mesh;
[0066] Based on the main routing service, each sub-routing service is registered to the cross-domain resource service mesh;
[0067] Determine the first intermediate routing service corresponding to each resource service in each of the sub-routing services and the main routing service, and register each resource service to the cross-domain resource service mesh through each of the first intermediate routing services;
[0068] The resource service lists of each sub-routing service and the main routing service are updated based on the resource registration information of each resource service to complete the construction of the cross-domain resource service mesh.
[0069] Furthermore, the processor 1001 can call the cross-domain resource service mesh builder stored in the memory 1005 and also perform the following operations:
[0070] Determine the target sub-routing service currently registering in each of the sub-routing services, and the second intermediate routing service corresponding to the target sub-routing service, wherein the second intermediate routing service is the main routing service or a sub-routing service that has completed registration;
[0071] The routing registration information of the target sub-routing service is added to the cross-domain resource service mesh through the second intermediate routing service.
[0072] Furthermore, the processor 1001 can call the cross-domain resource service mesh builder stored in the memory 1005 and also perform the following operations:
[0073] Based on the routing registration information, update the network topology information and routing table information of each of the sub-routing services and the main routing service in the cross-domain resource service mesh.
[0074] Furthermore, the processor 1001 can call the cross-domain resource service mesh builder stored in the memory 1005 and also perform the following operations:
[0075] The target sub-routing service outputs the route registration information to the first routing service adjacent to the target sub-routing service.
[0076] Update the network topology information and routing table information of the first routing service according to the routing registration information;
[0077] The routing registration information is output to the second routing service adjacent to the first routing service through the first routing service;
[0078] The second routing service is used as the first routing service, and the process returns to the step of updating the network topology information and routing table information of the first routing service according to the routing registration information, until the network topology information and routing table information of each sub-routing service and the main routing service in the cross-domain resource service mesh are updated.
[0079] Furthermore, the processor 1001 can call the cross-domain resource service mesh builder stored in the memory 1005 and also perform the following operations:
[0080] The target connection method between the first routing service and the target sub-routing service in the network topology information of the first routing service is updated according to the routing registration information, wherein the target connection method includes: routing relay mode;
[0081] When the target connection mode is a route relay mode, the routing table information of the first route service is updated according to the route registration information.
[0082] Furthermore, the processor 1001 can call the cross-domain resource service mesh builder stored in the memory 1005 and also perform the following operations:
[0083] Determine the target resource service currently registered in each of the resource services, and the target routing service corresponding to the target resource service in each of the first intermediate routing services;
[0084] The resource registration information of the resource service is output to the third routing service adjacent to the target routing service through the target routing service;
[0085] Update the resource service list of the third routing service according to the resource registration information;
[0086] The resource registration information is output to the fourth routing service adjacent to the third routing service through the third routing service;
[0087] The fourth routing service is used as the third routing service, and the process returns to the step of updating the resource service list of the third routing service according to the resource registration information, until the resource service lists of each sub-routing service and the main routing service in the cross-domain resource service mesh are updated.
[0088] Furthermore, the processor 1001 can call the cross-domain resource service mesh builder stored in the memory 1005 and also perform the following operations:
[0089] Each resource service generates its own proxy address based on its unique identifier, and adds each proxy address to the resource service list.
[0090] This application provides a method for constructing a cross-domain resource service mesh. In the first embodiment of this method, please refer to... Figure 2 The method for constructing the cross-domain resource service mesh includes:
[0091] Step S10: Start the main routing service deployed in the cross-domain resource service mesh;
[0092] It should be noted that, in this embodiment, the cross-domain resource service mesh is a star network formed by interconnecting multiple resource services and routing services, providing cross-domain access and collaboration of resources.
[0093] It should be noted that in this embodiment, the routing service is used to establish network connections between various resource services. It also provides service registration and discovery functions, as well as DNS resolution functions to resolve the unique identifiers of resource services into routing service proxy addresses. The routing service is also divided into primary routing services and secondary routing services. The primary routing service needs to have a public IP address and serves as the initial node of the resource service mesh. Each routing service contains a routing service identifier, which is text information that uniquely identifies the routing service and has no special format requirements.
[0094] It should be noted that in this embodiment, resources refer to the hardware and software resources on a computer or server, such as storage resources, computing resources, and software resources.
[0095] Resource services refer to services that encapsulate the hardware and software resources on a computer or server, providing a unified interface for resource access. A service can only provide one type of resource, but it can provide multiple instances of that resource. Resource services are divided into main services and sub-services. Sub-services provide access to specific resources, while the main service implements unified management and scheduling of all resources.
[0096] Each resource service has a unique resource service identifier, which is a textual information that uniquely identifies the resource service. It consists of multiple layers of information, and the specific format is "domain identifier-resource type-resource service unique number". For example, the identifier for a storage resource service is "AreaA-Storage-Service1" (the first storage resource service in domain A), and the identifier for a compute resource service is "AreaB-Compute-Service2" (the second compute resource service in domain B).
[0097] Service registration refers to a service (including resource services and routing services) registering its relevant information with the resource service mesh, thus making itself a part of the resource service mesh.
[0098] Service discovery refers to the process where, when a new service is registered in the resource service mesh, all existing services of the same type in the resource service mesh will receive the registration information of the new service.
[0099] In this embodiment, when building a cross-domain resource service network, the main routing service is first deployed and started through the launcher.
[0100] It should be noted that in this embodiment, the service launcher is used to start and run the control program of the resource service. Through the relevant functions provided by the operating system kernel, the way the resource service establishes a network connection can be modified, so that when the resource service makes cross-domain calls to each other, it only needs to know the other party's unique service identifier to establish a network connection and make resource calls.
[0101] Step S20: Register each sub-routing service to the cross-domain resource service mesh based on the main routing service;
[0102] In this embodiment, after the main routing service is started, when it is necessary to add a new sub-routing service to the cross-domain resource service mesh to expand the mesh, the sub-routing network to be added is started through the starter. If only the main routing service exists in the mesh, the sub-routing service is registered to the cross-domain resource service mesh through the main routing service. If there is a registered sub-routing service in the mesh, the new sub-routing service can be registered to the cross-domain resource service mesh through the registered sub-routing service or the main routing service.
[0103] Step S30: Determine the first intermediate routing service corresponding to each resource service in each of the sub-routing services and the main routing service, and register each resource service to the cross-domain resource service mesh through each of the first intermediate routing services;
[0104] Step S40: Update the resource service lists of each sub-routing service and the main routing service based on the resource registration information of each resource service to complete the construction of the cross-domain resource service mesh.
[0105] In this embodiment, after adding all sub-routing services to the cross-domain resource service mesh, the resource services need to be deployed and started. First, the first intermediate routing service corresponding to each resource service in each sub-routing service and the main routing service is determined. The first intermediate routing service can be a sub-routing service in the same domain as the corresponding resource service, or it can be a main routing service that does not belong to any domain, just like the corresponding resource service. The resource service is registered to the cross-domain resource service mesh through the first intermediate routing service. Then, the registration information of the resource service is broadcast to the adjacent routing services through the first intermediate routing service. The adjacent routing services will then update their resource service lists according to the registration information of the resource services. After all the routing services have updated their resource service lists, new resource services can be registered. When the registration of all resource services is completed, the cross-domain resource service mesh is built.
[0106] For details, please refer to Figure 3 , Figure 3 This is a schematic diagram of a cross-domain resource service grid structure, representing an embodiment of the cross-domain resource service grid construction method of this application. Figure 3 As shown, when building a cross-domain resource service mesh, the main routing service is deployed and started first. Then, the sub-routing services A1, B1, C1, and D1 in domain AD can be connected to the main routing service to register in the cross-domain resource service mesh. Then, they are connected to multiple sub-routing services in each domain. For example, in domain A, sub-routing services A2 and A3 are registered to the cross-domain resource service mesh by connecting to sub-routing service A1. The same applies to other sub-routing services. After all sub-routing services have completed registration, when registering resource services, the corresponding routing service is selected based on the domain to which the resource service belongs. For example, if the primary storage service M-S1 does not belong to domains A, B, C, or D, it will directly register with the cross-domain resource service network through the primary routing service. Then, the primary routing service will broadcast the registration information to the sub-routing services A1-D1. After the sub-routing services A1-D1 update their resource service lists, they will broadcast the registration information to their sub-routing services A2, A3, B2, B3, C2, C3, D2, and D3, until the resource service lists of all sub-routing services are updated.
[0107] Additionally, when registering the sub-storage service A-S2, since A-S2 belongs to domain A, the sub-routing service A2 in domain A can be selected as the corresponding routing service for registration. Then, the registration information of A-S2 is broadcast to sub-routing service A1 through sub-routing service A2 to update the resource service list of sub-routing service A1. Then, the registration information is broadcast to sub-routing service A3 and the main routing service through sub-routing service A1. The above steps are repeated until the resource service lists of all routing services are updated.
[0108] After registering all routing and resource services, the cross-domain resource service mesh can be built.
[0109] Compared to existing technologies that use dedicated networks or VPNs for cross-domain network interconnection, the cross-domain resource service mesh construction method of this application constructs the cross-domain resource service mesh by using a main routing service with a public IP address. Multiple sub-routes that are directly or indirectly connected to the main route are registered in the cross-domain resource service. When adding a resource service, the resource service is registered to the cross-domain resource service through a sub-route within the same domain. When resources in different domains need to be accessed, cross-domain access to resource services can be achieved simply by connecting the routing services.
[0110] Therefore, the method of constructing a cross-domain resource service network based on the aforementioned main routing service with a public IP address, compared with the traditional method of using leased networks or configuring VPNs for cross-domain network interconnection, offers lower construction and maintenance costs. Furthermore, it allows for network expansion by registering sub-routing services, and resource services can collaborate across domains without considering network connectivity, greatly simplifying the implementation of upper-layer services. Moreover, the constructed dynamic resource service mesh does not restrict the type of resource service; cross-domain storage and computing services can be quickly built upon the resource service mesh.
[0111] Furthermore, based on the first embodiment of the cross-domain resource service grid construction method of this application described above, a second embodiment of the cross-domain resource service grid construction method of this application is proposed.
[0112] In the second embodiment of the cross-domain resource service mesh construction method of this application, step S20 above, the step of registering each sub-routing service to the cross-domain resource service mesh based on the main routing service, includes:
[0113] Step S201: Determine the target sub-routing service currently registering in each of the sub-routing services, and the second intermediate routing service corresponding to the target sub-routing service, wherein the second intermediate routing service is the main routing service or a sub-routing service that has completed registration;
[0114] Step S202: Add the routing registration information of the target sub-routing service to the cross-domain resource service mesh through the second intermediate routing service.
[0115] It should be noted that, in this embodiment, the service registration information is the information that needs to be provided when registering a service, specifically including key information such as the service address, the service domain, and the service type. The unique identifier of the service itself is automatically generated and its uniqueness is guaranteed by the service resource grid.
[0116] In this embodiment, when registering a new sub-routing service, it is necessary to select an existing main routing service or sub-routing service in the resource service mesh. When the new sub-routing service can actively establish a network connection with the selected routing service, it can actively register its own information. Otherwise, it is necessary to manually call the interface of the selected routing service to add the information of the new sub-routing service into the resource service mesh. After determining the second intermediate routing service, the registration information of the newly registered target sub-routing service is transferred to the cross-domain resource service mesh through the second intermediate routing service.
[0117] Furthermore, in a feasible embodiment, after step S202 above, where the routing registration information of the target sub-routing service is added to the cross-domain resource service mesh via the second intermediate routing service, the method further includes:
[0118] Step S203: Update the network topology information and routing table information of each of the sub-routing services and the main routing service in the cross-domain resource service mesh based on the routing registration information.
[0119] In this embodiment, similar to the registration of resource services, when registering a new sub-routing service, it is necessary to update the network topology information and routing table information of each sub-routing service and the main routing service in the cross-domain resource service mesh according to the routing registration information of the new sub-routing service.
[0120] It should be noted that in this embodiment, network topology information refers to the way each routing service establishes network connections with other routing services. Network connection establishment refers to the current routing service establishing a new network connection with the target routing service through active or passive mode. Active and passive modes can indirectly transform a unidirectional network into a bidirectional network. Routing relay mode can indirectly transform a network that is not bidirectionally connectable into a bidirectional network. Besides active and passive modes, routing relay mode can also indirectly establish network connections between routing services.
[0121] For details, please refer to Figure 4 , Figure 4 This diagram illustrates three network connection establishment modes in one embodiment of the cross-domain resource service grid construction method of this application.
[0122] like Figure 4 As shown, active mode refers to the network connection establishment mode adopted when a routing service can actively initiate a network connection to another routing service on the physical network. Routing services can directly establish network connections with each other through active mode.
[0123] Passive mode refers to the network connection establishment mode used when a routing service cannot proactively initiate a network connection to another routing service on the physical network, but conversely, the target routing service can proactively initiate a network connection to the current routing service. In this mode, the target routing service will proactively initiate a network connection to the control address of the current routing service during initialization and accept the control of the current routing service. When the current routing service needs to establish a new network connection with the target routing service, it controls the target routing service to initiate a new connection to the data address of the current routing service, thereby indirectly realizing the function of the current routing service proactively establishing a new network connection with the target routing service.
[0124] Routing relay mode is a network connection establishment mode used when a routing service cannot initiate a network connection with another routing service through active or passive modes. In this case, the current routing service needs to establish a network connection with the target routing service through one or more other routing services, such as... Figure 4 As shown, in the routing relay mode, the connection method with other routing services can be either passive or active, and the current routing service and the target routing service are connected through a virtual network.
[0125] Furthermore, in a feasible embodiment, step S203 above, the step of updating the network topology information and routing table information of each of the sub-routing services and the main routing service in the cross-domain resource service mesh based on the routing registration information, includes:
[0126] Step S2031: The route registration information is output to the first route service adjacent to the target sub-route service through the target sub-route service;
[0127] Step S2032: Update the network topology information and routing table information of the first routing service according to the routing registration information;
[0128] Step S2033: The routing registration information is output to the second routing service adjacent to the first routing service through the first routing service;
[0129] Step S2034: The second routing service is used as the first routing service, and the process returns to the step of updating the network topology information and routing table information of the first routing service according to the routing registration information, until the network topology information and routing table information of each sub-routing service and the main routing service in the cross-domain resource service mesh are updated.
[0130] It should be noted that, in this embodiment, the routing table information refers to the table information that records the best transit path in the routing transit mode.
[0131] In this embodiment, after selecting the second intermediate routing service, the routing registration information of the newly registered target sub-routing service is first output to the adjacent first routing service through the target sub-routing service. There can be one or more first routing services. Then, the connection method between the first routing service and the target sub-routing service can be obtained, and the connection method is added to the network topology information to complete the update of the network topology information of the first routing service. If the connection method is active mode or passive mode, there is no need to update the routing table information. If the connection method is routing relay mode, it is also necessary to record the best relay path between the first routing service and the target sub-routing service, and then add the best relay path to the routing table information of the first routing service to complete the update of the routing table information.
[0132] Furthermore, in a feasible embodiment, step S2032 above, the step of updating the network topology information and routing table information of the first routing service according to the routing registration information, includes:
[0133] Step S20321: Update the target connection mode between the first routing service and the target sub-routing service in the network topology information of the first routing service according to the routing registration information, wherein the target connection mode includes: routing relay mode;
[0134] Step S20322: When the target connection mode is a route relay mode, update the routing table information of the first route service according to the route registration information.
[0135] In this embodiment, the connection method between the first routing service and the target sub-routing service can be obtained based on the routing registration information. The connection method is added to the network topology information to update the network topology information of the first routing service. If the connection method is a routing relay mode, the best relay path between the first routing service and the target sub-routing service also needs to be recorded. Then, the best relay path is added to the routing table information of the first routing service to update the routing table information.
[0136] Specifically, after the selected second intermediate routing service broadcasts the registration information of the new target sub-routing service to the adjacent first routing service, the receiving routing service compares and updates its own network topology information and routing table information. When the network topology information changes, it continues to broadcast the received routing service registration information to adjacent routing services, repeating the above steps until no new routing service registration broadcast information appears in the entire resource service mesh. At this point, all routing services in the entire resource service mesh possess the topology information of the entire network and the key information of all routing services. Each routing service will calculate and update the optimal connection method (active mode, passive mode, or routing relay mode) when establishing network connections with other routing services based on the information of other routing services. When the optimal connection method is routing relay mode, it calculates and updates the optimal relay path (routing table information).
[0137] In this way, all routing services in the mesh can be connected through the above service discovery method. When resource services make cross-domain calls and collaborate, they do not need to consider the network connectivity between each other, which greatly simplifies the implementation of upper-layer services.
[0138] Furthermore, based on the first and second embodiments of the cross-domain resource service grid construction method of this application described above, a third embodiment of the cross-domain resource service grid construction method of this application is proposed.
[0139] In the third embodiment of the method for constructing a cross-domain resource service mesh, step S40 above, which involves updating the resource service lists of each sub-routing service and the main routing service based on the resource registration information of each resource service, includes:
[0140] Step S401: Determine the target resource service currently being registered in each of the resource services, and the target routing service corresponding to the target resource service in each of the first intermediate routing services;
[0141] Step S402: Output the resource registration information of the resource service to the third routing service adjacent to the target routing service through the target routing service;
[0142] Step S403: Update the resource service list of the third routing service according to the resource registration information;
[0143] Step S404: The resource registration information is output to the fourth routing service adjacent to the third routing service through the third routing service;
[0144] Step S405: The fourth routing service is used as the third routing service, and the process returns to the step of updating the resource service list of the third routing service according to the resource registration information, until the resource service lists of each sub-routing service and the main routing service in the cross-domain resource service mesh are updated.
[0145] In this embodiment, when registering a new target resource service, a target routing service in the same domain as the target resource service is selected. The service information of the target resource service is then output to a third routing service adjacent to the target routing service. There can be one or more third routing services. The registration information of the resource service is then added to the resource service list of the third routing service. The resource registration information is then output to a fourth routing service adjacent to the third routing service, and so on, until the resource service lists of all routing services are updated.
[0146] Furthermore, in step S40 above, the step of updating the resource service lists of each sub-routing service and the main routing service based on the resource registration information of each resource service further includes:
[0147] Step S406: Generate a proxy address for each resource service based on the unique identifier corresponding to each resource service, and add each proxy address to the resource service list.
[0148] In this embodiment, the registration information of the resource service includes the address of the resource service. The routing service can resolve the unique identifier of the resource service to its own proxy address through DNS resolution, so as to generate the proxy address of the resource service and add it to the resource service list.
[0149] Specifically, after a new target resource service is registered, the selected target routing service broadcasts the resource service's registration information to neighboring routing services. Routing services receiving this broadcast compare and update their own resource service lists, adding the target resource service's registration information to their lists. When the resource service list changes, the received resource service registration information is broadcast to neighboring routing services again. This process is repeated until no new resource service registration broadcasts appear in the entire resource service mesh. All sub-routing services then prepare new proxy addresses for the newly added resource services and add the proxy address information to their resource service lists. This completes the construction of the cross-domain resource service mesh.
[0150] When cross-domain resource access is required, please refer to [the relevant documentation / reference]. Figure 5 , Figure 5 This is a schematic diagram of the process for cross-domain resource service call handling in one embodiment of the method for constructing a cross-domain resource service mesh according to this application.
[0151] like Figure 5 As shown, when a sub-resource service in domain B needs to make a cross-domain call to a sub-resource service in domain A, it first starts the called resource service through the service launcher, then listens for cross-domain call requests from the resource service through the service launcher, then queries the DNS resolution of the sub-routing service through the sub-resource service to obtain the proxy address number of the sub-routing service, and then modifies the proxy service address number to the actual proxy service address through the service launcher. After that, the sub-resource service can access the actual proxy service address of the sub-routing service. Then, through the virtual network connection established between the sub-routing service in domain A and the sub-routing service in domain B through the routing relay mode, the sub-resource service in domain B can forward resource call requests to the sub-routing service in domain A through the sub-routing service in domain B.
[0152] Therefore, the method of constructing a cross-domain resource service network based on the aforementioned main routing service with a public IP address, compared with the traditional method of using leased networks or configuring VPNs for cross-domain network interconnection, offers lower construction and maintenance costs. Furthermore, it allows for network expansion by registering sub-routing services, and resource services can collaborate across domains without considering network connectivity, greatly simplifying the implementation of upper-layer services. Moreover, the constructed dynamic resource service mesh does not restrict the type of resource service; cross-domain storage and computing services can be quickly built upon the resource service mesh.
[0153] In addition, please refer to Figure 6 , Figure 6 This application provides a functional module diagram of the cross-domain resource service grid construction apparatus. The apparatus further includes:
[0154] The main route deployment module is used to start the main route service deployed in the cross-domain resource service mesh;
[0155] The sub-route registration module is used to register each sub-route service to the cross-domain resource service mesh based on the main route service;
[0156] The resource service registration module is used to determine the first intermediate routing service corresponding to each resource service in each of the sub-routing services and the main routing service, and register each resource service to the cross-domain resource service mesh through each of the first intermediate routing services;
[0157] The grid construction module is used to update the resource service lists of each sub-routing service and the main routing service based on the resource registration information of each resource service, so as to complete the construction of the cross-domain resource service grid.
[0158] Optional, the sub-route registration module includes:
[0159] An information registration unit is used to determine the target sub-routing service currently registering among the sub-routing services, and the second intermediate routing service corresponding to the target sub-routing service, wherein the second intermediate routing service is the main routing service or a sub-routing service that has completed registration; and to add the routing registration information of the target sub-routing service to the cross-domain resource service mesh through the intermediate routing service.
[0160] Optionally, the apparatus for building a cross-domain resource service grid also includes:
[0161] The routing information update module is used to update the network topology information and routing table information of each of the sub-routing services and the main routing service in the cross-domain resource service mesh based on the routing registration information.
[0162] Optionally, the routing information update module includes:
[0163] The routing information broadcast update unit is configured to: output the routing registration information to a first routing service adjacent to the target sub-routing service through the target sub-routing service; update the network topology information and routing table information of the first routing service according to the routing registration information; output the routing registration information to a second routing service adjacent to the first routing service through the first routing service; use the second routing service as the first routing service, and return to execute the step of updating the network topology information and routing table information of the first routing service according to the routing registration information, until the network topology information and routing table information of each sub-routing service and the main routing service in the cross-domain resource service mesh are updated.
[0164] Optionally, the routing information broadcast update unit includes:
[0165] The information update subunit is used to update the target connection mode between the first routing service and the target sub-routing service in the network topology information of the first routing service according to the routing registration information, wherein the target connection mode includes: routing relay mode; when the target connection mode is routing relay mode, the routing table information of the first routing service is updated according to the routing registration information.
[0166] Optionally, the mesh building module includes:
[0167] The resource information update unit is used to determine the target resource service currently registered in each of the resource services, and the target routing service corresponding to the target resource service in each of the first intermediate routing services; output the resource registration information of the resource service to the third routing service adjacent to the target routing service through the target routing service; update the resource service list of the third routing service according to the resource registration information; output the resource registration information to the fourth routing service adjacent to the third routing service through the third routing service; use the fourth routing service as the third routing service, and return to execute the step of updating the resource service list of the third routing service according to the resource registration information, until the resource service lists of each of the sub-routing services and the main routing service in the cross-domain resource service mesh are updated.
[0168] Optionally, the mesh building module also includes:
[0169] The address update unit is used to generate a proxy address for each resource service based on the unique identifier corresponding to each resource service, and add each proxy address to the resource service list.
[0170] The specific implementation of the cross-domain resource service grid construction apparatus of this application is basically the same as the embodiments of the cross-domain resource service grid construction method described above, and will not be repeated here.
[0171] Furthermore, this application also proposes a computer storage medium storing a program for constructing a cross-domain resource service grid, which, when executed by a processor, implements the steps of the cross-domain resource service grid construction method of this application as described above.
[0172] The specific embodiments of the computer storage medium in this application are basically the same as the embodiments of the cross-domain resource service grid construction method described above, and will not be repeated here.
[0173] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.
[0174] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0175] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.
[0176] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.
Claims
1. A method for constructing a cross-domain resource service grid, characterized in that, The method for constructing the cross-domain resource service grid includes: Starting a main routing service deployed in a cross-domain resource service mesh includes starting and running resource services through a service launcher, wherein the service launcher is also used to run a control program, the control program is used to establish network connections for cross-domain resource invocation, and the main routing service has a public IP address; Based on the main routing service, each sub-routing service is registered to the cross-domain resource service mesh; Determine the first intermediate routing service corresponding to each resource service in each of the sub-routing services and the main routing service, and register each resource service to the cross-domain resource service mesh through each of the first intermediate routing services; The resource service lists of each sub-routing service and the main routing service are updated based on the resource registration information of each resource service to complete the construction of the cross-domain resource service mesh; The step of registering each sub-routing service to the cross-domain resource service mesh based on the main routing service includes: Determine the target sub-routing service currently registering in each of the sub-routing services, and the second intermediate routing service corresponding to the target sub-routing service, wherein the second intermediate routing service is the main routing service or a sub-routing service that has completed registration; The routing registration information of the target sub-routing service is added to the cross-domain resource service mesh through the second intermediate routing service; After the step of adding the routing registration information of the target sub-routing service to the cross-domain resource service mesh via the second intermediate routing service, the method further includes: Based on the routing registration information, update the network topology information and routing table information of each of the sub-routing services and the main routing service in the cross-domain resource service mesh; The step of updating the network topology information and routing table information of each sub-routing service and the main routing service in the cross-domain resource service mesh based on the routing registration information includes: The target sub-routing service outputs the route registration information to the first routing service adjacent to the target sub-routing service. Update the network topology information and routing table information of the first routing service according to the routing registration information; The routing registration information is output to the second routing service adjacent to the first routing service through the first routing service; The second routing service is used as the first routing service, and the process returns to the step of updating the network topology information and routing table information of the first routing service according to the routing registration information, until the network topology information and routing table information of each of the sub-routing services and the main routing service in the cross-domain resource service mesh are updated. The step of updating the network topology information and routing table information of the first routing service according to the routing registration information includes: The target connection method between the first routing service and the target sub-routing service is updated in the network topology information of the first routing service according to the routing registration information. The target connection method includes: routing relay mode, active mode and passive mode. The passive mode refers to the target sub-routing service initiating a connection to the data address of the first routing service. The routing relay mode is the network connection establishment mode adopted when the routing service cannot initiate a network connection through active mode and passive mode. In the routing relay mode, the first routing service and the target sub-routing service are connected through a virtual network connection. When the target connection mode is a route relay mode, the routing table information of the first route service is updated according to the route registration information; The step of updating the resource service lists of each sub-routing service and the main routing service based on the resource registration information of each resource service includes: Each resource service generates its own proxy address based on its unique identifier, and adds each proxy address to the resource service list.
2. The method of claim 1, wherein, The step of updating the resource service lists of each sub-routing service and the main routing service based on the resource registration information of each resource service further includes: Determine the target resource service currently registered in each of the resource services, and the target routing service corresponding to the target resource service in each of the first intermediate routing services; The resource registration information of the resource service is output to the third routing service adjacent to the target routing service through the target routing service; Update the resource service list of the third routing service according to the resource registration information; The resource registration information is output to the fourth routing service adjacent to the third routing service through the third routing service; The fourth routing service is used as the third routing service, and the process returns to the step of updating the resource service list of the third routing service according to the resource registration information, until the resource service lists of each sub-routing service and the main routing service in the cross-domain resource service mesh are updated.
3. A constructing device of a cross-domain resource service mesh, characterized in that, The apparatus for constructing the cross-domain resource service grid includes: The main routing deployment module is used to start the main routing service deployed in the cross-domain resource service mesh, wherein the main routing service has a public network address; The sub-route registration module is used to register each sub-route service to the cross-domain resource service mesh based on the main route service; The resource service registration module is used to determine the first intermediate routing service corresponding to each resource service in each of the sub-routing services and the main routing service, and register each resource service to the cross-domain resource service mesh through each of the first intermediate routing services; The grid construction module is used to update the resource service lists of each sub-routing service and the main routing service based on the resource registration information of each resource service, so as to complete the construction of the cross-domain resource service grid; The sub-route registration module is further configured to determine the target sub-route service currently registering in each of the sub-route services, and the second intermediate route service corresponding to the target sub-route service, wherein the second intermediate route service is the main route service or a sub-route service that has completed registration; add the route registration information of the target sub-route service to the cross-domain resource service mesh through the second intermediate route service; the cross-domain resource service mesh construction device is further configured to update the network topology information and routing table information of each of the sub-route services and the main route service in the cross-domain resource service mesh based on the route registration information; output the route registration information to a first route service adjacent to the target sub-route service through the target sub-route service; update the network topology information and routing table information of the first route service according to the route registration information; output the route registration information to a second route service adjacent to the first route service through the first route service; and use the second route service as the first... The routing service returns to the step of updating the network topology information and routing table information of the first routing service according to the routing registration information, until the network topology information and routing table information of each of the sub-routing services and the main routing service in the cross-domain resource service mesh are updated; the target connection mode between the first routing service and the target sub-routing service in the network topology information of the first routing service according to the routing registration information is updated, wherein the target connection mode includes: routing relay mode, active mode and passive mode, wherein the passive mode refers to the target sub-routing service initiating a connection to the data address of the first routing service, the routing relay mode is the network connection establishment mode adopted when the routing service cannot initiate a network connection through active mode and passive mode, and the first routing service and the target sub-routing service are connected through a virtual network connection in the routing relay mode; when the target connection mode is routing relay mode, the routing table information of the first routing service is updated according to the routing registration information; The grid construction module is further configured to generate a proxy address for each resource service based on the unique identifier corresponding to each resource service, and add each proxy address to the resource service list.
4. A fabric device for a cross-domain resource service mesh, the fabric device comprising: The cross-domain resource service grid construction device includes a memory and a processor, wherein the memory stores a cross-domain resource service grid construction program, and when the cross-domain resource service grid construction program is executed by the processor, it implements the steps of the cross-domain resource service grid construction method as described in any one of claims 1 to 2.
5. A computer storage medium, characterized in that The computer storage medium stores a cross-domain resource service grid construction program, which, when executed by a processor, implements the steps of the cross-domain resource service grid construction method as described in any one of claims 1 to 2.
Citation Information
Patent Citations
Method and system for processing node registration notice
CN106453539A
