## 3 Architecture
### IPCRSA Overview
#### 3.1.1 Scheduling Node
It is important to note that the resolution hierarchy and resolution domains of this hierarchical name resolution system correspond one-to-one with the scheduling hierarchy and scheduling domains in IPCRSA. Each scheduling domain in IPCRSA is also a resolution domain of the hierarchical name resolution system. The RN provides name resolution services within each scheduling domain, as illustrated in Figure 1.  
The ID Management Module is responsible for interacting with the RN in its scheduling domain, completing the registration, deregistration, and query of the mapping relationship between the SN's RSS_ID_L\({}_{x}\) and IP. Topology Construction Module utilizes the ID Management Module and ICN name resolution system to build a semi-distributed structured tree-like topology and structured connections among SNs within each scheduling domain at the L\({}_{3}\) and L\({}_{2}\) levels sequentially. The SN with the minimum average communication delay to other SNs within the domain is selected as the root node, and the root node of the lower-level scheduling domain also belongs to the scheduling domain at the upper level, with the corresponding resource scheduling service identifier (L\({}_{3}\) is the lowest level). Subsequently, within the scheduling domain at the L\({}_{1}\) level, the module establishes a fully distributed unstructured topology and unstructured connections among SNs. Ultimately, the hierarchical topology structure depicted in Figure 1 is constructed. It should be additionally noted that the Topology Construction Module, through the ID Management Module, queries the address information of other SNs within its scheduling domain from the RN and measures the communication delay with other SNs. The construction of tree-like topologies and structured connections among SNs within the L\({}_{3}\) and L\({}_{2}\) level scheduling domains primarily aims to reduce the overhead associated with the flooding of subsequent computing resource status information among SNs, akin to the method discussed in reference [51]. The establishment of unstructured topology  
Figure 3: Hierarchical name resolution system in IPCRSA. and connections within the L1 level scheduling domain primarily aims at load balancing among SNs. The construction process of the hierarchical topology is as follows:  
1. When a new SN comes online, its ID Management Module registers the mapping relationship between RSS_ID_L3 and IP with the RN within its L3 level scheduling domain. 2. Within each scheduling domain at the L3 level, the Topology Construction Module of each SN queries the IP address information of other SNs within its scheduling domain from the RN via the ID Management Module and measures the communication delay with other SNs. 3. The SN with the smallest average communication delay to other SNs within the domain is selected as the root SN for the corresponding L3 level scheduling domain, with other SNs serving as leaf nodes. 4. Adjacency relationships are established between the root SN and all leaf SNs to form a tree-structured logical topology. 5. The ID Management Module of the root SN of each scheduling domain at the L3 level registers the mapping relationship between RSS_ID_L2 and IP with the RN within its L2 level scheduling domain. 6. Similarly, within each scheduling domain at the L2 level, the Topology Construction Module of each SN sequentially completes the tasks of measuring the communication delay between SNs, selecting the root SN, and constructing the tree-structured logical topology. 7. The ID Management Module of the root SN of each scheduling domain at the L2 level registers the mapping relationship between RSS_ID_L1 and IP with the RN within its L1 level scheduling domain. 8. Within the scheduling domain at the L1 level, each SN establishes adjacency relationships with each other, forming a fully distributed, unstructured topology. Ultimately, the construction of the hierarchical logical topology is completed.