## 2 Related Work
### Icn, Icn-Based Computing Network, and SDN  
The ICN is a new network architecture focusing on content rather than addresses to enhance reliability, flexibility, and security. At present, the representative research includes DONA [50], NDN [51], PURSUIT [52], Mobility First [53], SEANET [54] etc. The ICN is categorized into evolutionary types, which integrate with the current TCP/IP network (e.g., SEANET), and revolutionary types, which redesign the network architecture and key technologies (e.g., NDN, PURSUIT). Considering their feasibility [55; 56], this paper adopts the evolutionary type. The ICN uses a content-centric model where each network entity has a unique identifier, enabling routing based on this identifier. This mechanism is very suitable for service scheduling. A large number of service instances have unique identifiers, which can be managed uniformly and implement routing based on identifiers, i.e., at the service level. Currently, the ICN has two naming methods [57]: hierarchical (similar to URLs) and flat (using irregular characters). Flat naming shows advantages in security, flexibility, and scalability. Thus, this paper chooses the flat naming method. Although ICN routes are based on content names, the content itself is stored at specific locations within content providers. Consequently, a name resolution system [58] (NRS) is required to manage the mapping between names and \begin{table}
\begin{tabular}{p{142.3 pt} p{142.3 pt}} \hline \hline
**Institutions** & **White Papers 1/Drafts/Recommendations** \\ \hline \multirow{2}{*}{China Mobile} & White Paper of Computing-Aware Networking \\  & (2021) [44] \\ \hline \multirow{2}{*}{China Unicom} & White paper of computing power network \\  & (2019) [45] \\ \hline \multirow{2}{*}{China Telecom} & Cloud and network convergence 2030 \\  & Technical White Paper (2020) [46] \\ \hline \multirow{2}{*}{CCSA (China Communications Standards Association)} & Network 5.0 Technology White Paper \\  & (2019) [47] \\ \hline \multirow{2}{*}{COINRG (Computing in the Network Research Group, IRTF)} & Requirement of Computing in network \\  & (2021) [48] \\ \hline \multirow{2}{*}{ITU-T (International Telecommunication Union’s Framework and Architecture of Computing Telecommunication Standardization Sector)} & \multirow{2}{*}{Only a selection of representative documents is included in the table; for more documents, please refer to [[https://github.com/WeiRanRan0/whitergapers](https://github.com/WeiRanRan0/whitergapers)]([https://github.com/WeiRanRan0/whitergapers](https://github.com/WeiRanRan0/whitergapers)) (accessed on 27 October 2024).} \\  & \\ \end{tabular}
\end{table} 
Table 1: Representative documents on Computing Networks. their corresponding locations. During routing, the system first determines the location based on the content name and then performs routing according to this location. As for the ICN-Based Computing Network, the authors in [59] have designed an integration of the ICN with the Computing Network, providing detailed descriptions of various mechanisms. The authors in [60] proposed a centralized ICN-Based Computing Network architecture and developed a scheduling algorithm. However, both architectures are based on a revolutionary ICN framework, which presents significant challenges for practical deployment. The SDN can greatly assist in deploying the ICN [61]. By providing centralized control and flexible network management, the SDN can optimize content routing and resource allocation in the ICN, simplify policy implementation, and enhance scalability and flexibility. Therefore, integration of the SDN and ICN holds significant potential for improving network architecture and efficiency. In traditional SDNs, network nodes cannot proactively monitor traffic, causing delays due to frequent data-control plane interactions. The stateful programmable data plane [62] addresses this by retaining state information within the data plane. The state is defined as the data stored in network devices for future packet processing, such as in stateful firewalls.