Content Centric Mobile Social Networks
We propose the content centric mechanism as an efficient solution for mobile content delivery in MSNs in 5G for the following reasons.
Community with Common Interest versus Interest Based Content In MSNs, the community consists of users with common interests. As the content in CCNs is also delivered based on the interest, it is natural that multiple users can be satisfied with one interest. As shown in Fig. 6.3, when users in the community subscribe to content with the same interest, the original server only needs to send the content once to the small cell. Then the small cell will distribute this content to these multiple users who have interest in this content. That is to say: as multiple users in the community may have the same interest in the content, content centric delivery of one content can satisfy the interest of multiple users, and the total traffic of content delivery between the original server and the small cell can be reduced.
User ID versus Interest Based Content ID In MSNs, the content is produced by a user who has a social ID. The content ID can be a hierarchical name containing the mobile user ID. If multiple replicas of this content are delivered over different communities by using the content ID, these replicas can be recognized as the replicas of the same content. When a user wants to update content or publish some new information related to this content, the existing networks manage the replicas in
Fig. 6.3 Community with common interest versus interest based content
different IP addresses as different content and update these replicas with a high overhead. However, these replicas can be recognized as the replicas of the same content as shown in Fig. 6.4, with content ID these replicas can be recognized as the replicas of the same content. When the original content is updated, different replicas of this content in the same small cell can be updated on time by the command from the small cell, with a reduction of overhead.
Mobility versus Content Store A user may keep moving during the request of one content. If this user can only get the interested content from the original server, when he leaves the coverage area of one small cell, the connection between the original server and the small cell may be interrupted. Then, the content store in the CCNs nodes in small cells keeps some replicas of content. If the interested content is available in the content store, this replica can be provided to the user, as shown in Fig. 6.5. Therefore, if the user keeps moving through different small cells, he can get the interested content in the small cell without contacting to the original server, resulting in a reduction of delay.
Fig. 6.4 User ID versus interest based content ID