# Data Naming Mechanism of LEO Satellite Mega-Constellations for the Internet of Things
## 3 Design of Data Naming Mechanism
### Data Naming Mechanism
Therefore, the content distribution process occurs at any time. During information publishing, some content is divided into several equal-sized blocks, and the block information is stored in each content block. The Publish information  
Figure 11: Multilayer multicomponent names designed for ICN-HMcH. name pattern is '/Publish/Data/Prefix/Version/Timestamp/Number/Host-B/'. The field \"Publish\" is the flag for publishing information, which is used to inform the forwarding node that this type of request is published push information. The \"Data\" field is the data flag. 'Prefix' is the name prefix, and \"Version\" is the data-type information, such as video, voice or data. \"Timestamp\" is a timestamp. The file block serial number information \"Number\" is included in the back, \"Host-B\" is the node information of the content publisher, and the ID of the information publisher is only a named name. Therefore, ID is location-independent and used to observe how many hops of ISL the communication between the content provider and consumer will go through. The ID will be used as a basis for simulation latency. After receiving the content request, the forwarding node first parses the name, determines that the content is the type of posted information, and detects the second field. If it is a local node, node directly resolves and processes. The data name, content block number, and source node information are obtained by parsing, and this information is sorted and cached in the content storage structure, as shown in Table 4. If it is not a local node, the node will perform routing and forwarding according to the content matching forwarding interface of the forwarding interest database FIB. If a node in the network has new content, the data will be released via this process. When some data sources leave the service range of the central node due to problems such as movement or the data are deleted due to the cache replacement strategy, the content provider node sends the deletion information of the corresponding data, thereby updating the forwarding node information quickly. In Step 2 (obtaining content source information), the LEO mega constellation for the IoT has multiple sources for data transmission due to the high dynamics of satellites. If the requester node wants to obtain the data response in a block request through a multisource method, it should generate a multisource information request name pattern as '/Multihoming/Data/Prefix/Version/Timestamp/Number1/Number2/'. The field \"Multihoming\" is a special flag bit that indicates that the interest request is multisource information. Ordinary interest request packets are distributed to various nodes in the network by broadcasting, and the forwarding node of the multisource information request only performs the forwarding function until the request reaches the content requester node. The structure of the data content name part is similar to that of the published information name mode. The difference is that the last part of the information request name pattern is a locally stored content block, which is used to inform the content provider node not to send related information. In Step 3 (request to download data in blocks), the content provider node parses the data name after receiving the content request and searches for related items in the summary information. After the search is completed, the content blocks stored by the requesting node are discharged, and the sequence numbers of other content blocks are packaged with the corresponding content publisher information and block information as a data packet to respond. After the requester node obtains the corresponding file block information of the reply to the data packet, it integrates the data content name and