## 3 Enhanced Name Resolution System
### Partitioning-Based Registration and Resolution
#### 3.2.2 Name Registration and Name Resolution Schemes
1: Initialization: \(T_{cost}=0\), \(T_{trans}=0\), \(S_{f}=\varnothing\)
2:\(T_{cost}=T_{recv}-T_{send}\)
3:\(T_{remain}=T_{remain}-T_{cos.t}\)
4:\(T_{trans}=T_{d}-T_{remain}\)
5: if \(T_{remain}>0\) then:
6: for each \(HM_{ip}\) in the \(\left\{HM_{ip}\right\}\) do:
7: if there exist \(HM_{ip}\) whose latency to \(HM_{ik}\), that is \(T_{p}\) satisfies \(T_{remain}\geq 2*T_{p}+T_{trans}\) then:
8: Add \(HM_{ip}\) into \(S_{f}\). 9: end if
10: else:
11: \(S_{f}=\varnothing\)
12: end if
13: end for
14: end if
15: if \(T_{remain}=0\) or \(S_{f}=\varnothing\) then:
16: return query failure response to \(HM_{ik}\). 17: end if
18: else:
19: \(HM_{ik}\) writes the updated \(T_{remain}\) and \(T_{send}\) in the QUERY message. 20: \(HM_{ik}\) forwards the QUERY message to the node(s) in \(S_{f}\). 21: end if
```  
**Algorithm 2**. **Tolerable Latency-Based Peer HM Forwarding**  
As shown in Figure 2(b)-d, we demonstrate different situations of providers and subscribers that are located in the same HEAs of different levels in ENRS. Based on our name resolution schemes, if the providers and subscribers are in the same network domain, the resolution path can also be contained in that domain. Thus, local resolution at different granularity and the forwarding locality can be achieved; as a consequence, the inter-domain traffic will be minimized. In Case 2 and Case 3, if the scope of latency to the peer HMs is tolerable, the query request will be forwarded to the peer links of HMs, which can effectively manage the spreading scopes of the messages. What is more, ENRS can avoid frequent updating of name bindings in the same HEA when UEs move within a HEA, which is beneficial for reducing the update traffic and decreasing the maintenance overhead. Mobility has become a basic requirement of communication networks because of the explosive growth of wireless and mobile devices. Mobility objectives can be divided into two types in ICN: producer mobility and consumer mobility. In our system, both the producer and consumer mobility can be primarily handled by the ENRS by supporting late-binding technology [49]. To support mobility \begin{table}
\begin{tabular}{l l l l} \hline \hline
**Symbol** & **Meaning** & **Symbol** & **Meaning** \\ \hline \(S_{f}\) & the peer resolver set to forward message & \(T_{cost}\) & the time cost for single hop \\ \(T_{recv}\) & the time receiving the request & \(HM_{ik}\) & current resolver \\ \(T_{trans}\) & the total delay from requestor to current node & \(HM_{ip}\) & the peer neighboring resolver of \(HM_{ik}\) \\ \(T_{p}\) & the delay between \(HM_{ip}\) and \(HM_{ik}\) & \(\left\{HM_{ip}\right\}\) & the node set in the DNHT of \(HM_{ik}\) \\ \hline \hline \end{tabular}
\end{table} 
Table 2: The meaning of symbols in Algorithm 2.  
if an entity (e.g., UE, IoT device, data entity) is moved and attached to a new Point of Access (PoA), it has to re-register in ENRS with its new NA(s) and must be updated in time to make itself accessible for other entities in the ENRS. From a new aspect, ENRS is a local NRS. Thus, different levels of HMs represent different control traffic offloading capabilities from the global NRS. If a name query request is satisfied by ENRS, then the query load is offloaded by ENRS from the global NRS. The offloading rate is equal to the hit ratio and the merit of ENRS is that it is more intuitive when thinking about the traffic load.