CN103415047B - Mobile support method in a kind of content center network - Google Patents
Mobile support method in a kind of content center network Download PDFInfo
- Publication number
- CN103415047B CN103415047B CN201310315590.2A CN201310315590A CN103415047B CN 103415047 B CN103415047 B CN 103415047B CN 201310315590 A CN201310315590 A CN 201310315590A CN 103415047 B CN103415047 B CN 103415047B
- Authority
- CN
- China
- Prior art keywords
- content
- user
- content source
- mobile
- request message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Abstract
The present invention discloses the mobile support method in a kind of content center network, comprises user's mobility support mechanism and content source mobility support mechanism. In user's mobility support mechanism: when user's mobile handoff is about to start, transmission types is that the request message of " user moves beginning " is to its primary access router; In user's mobile handoff process, its primary access router buffer memory mails to the data-message of user's original position; After user's mobile handoff completes, its primary access router upgrades the new location of data-message to user of also forwarding cache. In content source mobility support mechanism: when content source mobile handoff is about to start, transmission types is that the request message of " content source moves beginning " is to its primary access router; In content source mobile handoff process, its primary access router buffer memory mails to the request message of content source original position; After content source mobile handoff completes, its primary access router upgrades and forwards the request message mailing to content source original position to the new location of content source.
Description
Technical field
The present invention relates to technical field of the computer network, particularly relate to the mobile support method in a kind of content center network.
Background technology
Being different from the conventional internet centered by main frame, what the content center network centered by content was paid close attention to is content itself, and content is identified by it by content name, also by content name, it is achieved content is separated with content location. In the content in heart network, user without the need to by the request forward of content to the specific main frame having this content, only adopt content-based routing forwarding mechanism, can from providing the contiguous node of this content fetch corresponding content. In addition, content center network also by node to the buffer memory of content, accelerate the time of response of other user's access cache content in network, it is to increase the utilization ratio of network resource. At present, in content center network research, the network architecture of main flow is NDN(NamedDataNetworking).
NDN adopts the communication pattern of " user's driving ". User to the available link being attached thereto, forwards the request message (mainly comprise 3 options: content name, to the selection condition of content and randomized number) being used for request content; NDN network receives arbitrarily this request message and the NDN node of this request message institute request content can be provided, all by the forwarding path along request message, oppositely forward a data-message (mainly comprising 4 options: content name, signature, signature information and requested content) comprising requested content to the user asking this content; Meanwhile, data-message forwards the NDN node on path, also by according to self cache policy and cache resources, and its data-message received of buffer memory.
As an emerging network architecture, there is comparatively serious mobility support problem in NDN. On the one hand, owing to the primary access router of user cannot know the mobile state that user is current, so the loss of data-message that the mobile handoff of user will cause this access router to mail to user's original position; Owing to user's mobile handoff process remaining open state with network, so the loss of request message that the mobile handoff of user will cause user to mail to network; Owing to the forwarding information storehouse renewal of node each in network needs the regular hour, user's mobile handoff cannot effectively utilize the content of contiguous nodal cache after completing, so the mobile handoff of user will introduce longer mobile handoff time delay, user's mobile handoff is experienced poor. On the other hand, owing to the primary access router of content source cannot know the mobile state that content source is current, so the loss of request message that the mobile handoff of content source will cause this access router to mail to content source original position; Owing to the forwarding information storehouse renewal of node each in network needs the regular hour, the content that user provides after cannot obtaining content source mobile handoff immediately, so the mobile handoff of content source will introduce longer mobile handoff time delay, user's mobile handoff is experienced poor.
For solving user's mobility support problem that existing NDN network exists, JihoonLee etc. propose a kind of mobile management based on agency mechanism, and by introducing subscriber proxy server, content user asked before mobile handoff carries out buffer memory. This mechanism can effectively avoid the loss of the data-message that user's mobile handoff causes, and can shorten the mobile handoff time delay that user's mobile handoff is introduced to a certain extent, it is to increase the mobile handoff of user is experienced. But, on the one hand, this mechanism cannot avoid the loss of the request message that user's mobile handoff causes; On the other hand, this mechanism still need to by traditional IP network, just can mobile control message between completing user proxy server mutual.
For solving the content source mobility support problem that existing NDN network exists, FrederikHermans etc. propose the mobility support mechanism that a kind of position is separated with mark, by introducing HR(HomeRepository by name) mobile agency, content source can provide the name prefix of content and the positional information of correspondence thereof carry out buffer memory. This mechanism can effectively avoid the loss of the request message that content source mobile handoff causes, and can shorten the mobile handoff time delay that content source mobile handoff is introduced to a certain extent, it is to increase the mobile handoff of user is experienced. But, owing to the request message of user need to be forwarded to, by mobile agency, the content source that can provide requested content, so when mobile agency is not on the shortest path of user with content source, this mechanism will increase the content acquisition times of user to a certain extent, wastes the bandwidth resources of network.
Summary of the invention
It is an object of the invention to provide the mobile support method in a kind of content center network.
In order to solve prior art problem, the present invention discloses the mobile support method in a kind of content center network, comprises user's mobility support mechanism and content source mobility support mechanism.
User's mobility support mechanism comprises the following steps:
When user's mobile handoff is about to start, user's transmission types be the request message of " user moves beginning " to its primary access router, impel its primary access router to upgrade this user and asked but the request table clause undetermined that do not obtain content; Meanwhile, user stops the network that the request message that transmission types is " common " is about to leave to user, avoids user's mobile handoff to cause the loss that type is the request message of " common ";
In user's mobile handoff process, its primary access router is according to the request table clause undetermined after renewal, and buffer memory mails to the data-message that the type of user's original position is " common ", avoids user's mobile handoff to cause the loss of data-message;
After user's mobile handoff completes, transmission types is that the request message of " mobile retransmit " is to its primary access router, impel its primary access router that the data-message that the type of buffer memory is " common " is updated to the data-message of type for " mobile re-transmission ", and it is forwarded to the new location after user's mobile handoff.
Further, as preferably, also comprising:
Hereafter, user's transmission types is that the request message of " common " is to providing the content source of requested content; It is the data-message of " common " new location to user's mobile handoff that content source forwards the type comprising requested content.
Content source mobility support mechanism comprises the following steps:
When content source mobile handoff is about to start, transmission types be the request message of " content source moves beginning " to its primary access router, impel its primary access router to upgrade forwarding information storehouse entry that this content source can provide content;
In content source mobile handoff process, its primary access router is according to the forwarding information storehouse entry after renewal, and buffer memory mails to the request message that the type of content source original position is " common ", avoids content source mobile handoff to cause the loss of request message;
After content source mobile handoff completes, the request message that transmission types is " content source has moved " is to its primary access router, impel its primary access router that the request message that the type mailing to content source original position is " common " is updated to the request message of type for " mobile re-transmission ", and it is forwarded to the new location after content source mobile handoff;
Content source receives the request message that type is " mobile forward ", forwards data-message that the type comprising requested content be " mobile forwarding " to the user asking this content.
Further, as preferably, also comprising:
Hereafter, user's transmission types is the request message of " common " new location to content source mobile handoff; It is that the data-message of " common " is to the user asking this content that content source forwards the type comprising requested content.
The present invention is by adopting user and content source mobility support mechanism, it is possible to reduce user or the mobile handoff time delay of content source mobile handoff introducing, saves the bandwidth resources of network, and the mobile handoff promoting user is experienced.
Accompanying drawing explanation
When considered in conjunction with the accompanying drawings, by referring to detailed description below, it is possible to more complete understand the present invention and advantage thereof better. Accompanying drawing described herein is used to provide a further understanding of the present invention, forms the part of the present invention, and the schematic description and description of the present invention, for explaining the present invention, does not form inappropriate limitation of the present invention, wherein:
Fig. 1 is embodiment of the present invention user's mobility support mechanism schema.
Fig. 2 is embodiment of the present invention content source mobility support mechanism schema.
Fig. 3 is embodiment of the present invention user's mobility support schematic diagram of mechanism.
Fig. 4 is embodiment of the present invention content source mobility support schematic diagram of mechanism.
Fig. 5 (a) is embodiment of the present invention request message format schematic diagram.
Fig. 5 (b) is embodiment of the present invention data message format schematic diagram.
Fig. 6 (a) is embodiment of the present invention content memorizer form schematic diagram.
Fig. 6 (b) is embodiment of the present invention request sheet format schematic diagram undetermined.
Fig. 6 (c) is embodiment of the present invention forwarding information storehouse form schematic diagram.
Fig. 7 (a) is embodiment of the present invention request message treatment scheme schematic diagram.
Fig. 7 (b) is embodiment of the present invention data-message treatment scheme schematic diagram.
Fig. 8 (a) is the interacting message schematic flow sheet of embodiment of the present invention user's mobile context.
Fig. 8 (b) is the interacting message schematic flow sheet of embodiment of the present invention content source mobile context. Fig. 9 is the embodiment of the present invention one user's mobile context schematic diagram.
Figure 10 is the embodiment of the present invention two content source mobile context schematic diagram.
Embodiment
With reference to Fig. 1-10, embodiments of the invention are described.
For enabling above-mentioned purpose, feature and advantage more become apparent, below in conjunction with the drawings and specific embodiments, the present invention is further detailed explanation.
The present invention provides the mobile support method in a kind of content center network, can solve the user's mobility support problem in existing content center network and content source mobility support problem. Described method is made up of user's mobility support mechanism and content source mobility support mechanism two portions.
As shown in Figure 1, a kind of user's mobility support mechanism, this mechanism comprises the following steps:
S11, user's mobile handoff are about to start step: user's transmission types be the request message of " user moves beginning " to its primary access router, impel its primary access router to upgrade this user and asked but the request table clause undetermined that do not obtain content; Meanwhile, user stops the network that the request message that transmission types is " common " is about to leave to user, avoids user's mobile handoff to cause the loss that type is the request message of " common ";
Step in S12, user's mobile handoff process: the primary access router of user is according to the request table clause undetermined after renewal, and buffer memory mails to the data-message that the type of user's original position is " common ", avoids user's mobile handoff to cause the loss of data-message;
S13, user's mobile handoff complete after step: user's transmission types is that the request message of " mobile retransmit " is to its primary access router, impel its primary access router that the data-message that the type of buffer memory is " common " is updated to the data-message of type for " mobile re-transmission ", and it is forwarded to the new location after user's mobile handoff.
Hereafter, user's transmission types is that the request message of " common " is to providing the content source of requested content; It is the data-message of " common " new location to user's mobile handoff that content source forwards the type comprising requested content.
As shown in Figure 2, a kind of content source mobility support mechanism, this mechanism comprises the following steps:
S21, content source mobile handoff are about to start step: content source transmission types be the request message of " content source moves beginning " to its primary access router, impel its primary access router to upgrade forwarding information storehouse entry that this content source can provide content;
Step in S22, content source mobile handoff process: the primary access router of content source is according to the forwarding information storehouse entry after renewal, buffer memory mails to the request message that the type of content source original position is " common ", avoids content source mobile handoff to cause the loss of request message;
S23, content source mobile handoff complete after step: content source transmission types is that the request message of " content source has moved " is to its primary access router, impel its primary access router that the request message that the type mailing to content source original position is " common " is updated to the request message of type for " mobile re-transmission ", and it is forwarded to the new location after content source mobile handoff;
Content source receives the request message that type is " mobile forward ", forwards data-message that the type comprising requested content be " mobile forwarding " to the user asking this content.
Hereafter, user's transmission types is the request message of " common " new location to content source mobile handoff; It is that the data-message of " common " is to the user asking this content that content source forwards the type comprising requested content.
User's mobility support schematic diagram of mechanism is as shown in Figure 3, specific as follows:
Step 301, when user's mobile handoff is about to start, send a request message (type is " user moves beginning "), to its primary access router, impels its primary access router to upgrade relevant request table undetermined; Meanwhile, user stops the network that (type is " common ") be about to leave that sends a request message to it, avoids user's mobile handoff to cause the loss of request message;
Step 302, in user's mobile handoff process, its primary access router is according to the request table undetermined after renewal, and buffer memory mails to the data-message (type is " common ") of user's original position, avoids user's mobile handoff to cause the loss of data-message;
Step 303-304, after user's mobile handoff completes, send a request message (type is " mobile re-transmission ") to its primary access router, its primary access router is impelled to upgrade and the new location of the data-message of forwarding cache (type be " mobile re-transmission ") to user's mobile handoff, and shortening the mobile handoff time delay that user's mobile handoff is introduced whereby, the mobile handoff promoting user is experienced;
Step 305-306, hereafter, user sends a request message (type is " common ") to the content source that can provide requested content; Content source forwards the new location of the data-message (type is " common ") comprising requested content to user's mobile handoff. So, user and content source by the interactive communication of common request message and data-message, content requests before the user's mobile handoff that continues further and acquisition.
Content source mobility support schematic diagram of mechanism is as shown in Figure 4, specific as follows:
Step 401, when content source mobile handoff is about to start, send a request message (type is " content source moves beginning "), to its primary access router, impels its primary access router to upgrade relevant forwarding information storehouse;
Step 402, in content source mobile handoff process, its primary access router is according to the forwarding information storehouse after renewal, and buffer memory mails to the request message (type is " common ") of content source original position, avoids content source mobile handoff to cause the loss of request message;
Step 403, after content source mobile handoff completes, content source sends a request message (type is " content source has moved ") to its primary access router, impels its new access router add to primary access router or upgrade relevant forwarding information storehouse;
Step 404, the primary access router of content source receives the request message of step 403, upgrades and forwards the new location of the request message (type is " mobile forwarding ") mailing to content source original position to content source mobile handoff;
Step 405, content source receives the request message of step 404, forwards the data-message (type is " mobile forwarding ") comprising requested content to the user asking this content. User has upgraded in the whole network forwarding information storehouse without the need to waiting, the content provided after can obtaining content source mobile handoff, whereby, can shorten the mobile handoff time delay that content source mobile handoff is introduced to a certain extent, and the mobile handoff promoting user is experienced;
Step 406-407, hereafter, user sends a request message (type is " common ") new location to content source mobile handoff; Content source forwards the data-message (type is " common ") comprising requested content to the user asking this content. So, user and content source by the interactive communication of common request message and data-message, content requests before the content source mobile handoff that continues further and acquisition.
Type of message, data structure, Message Processing flow process and interacting message flow process that mobile support method in the network of foregoing center relates to are specific as follows.
Type of message
Mobile support method in the content center network that the embodiment of the present invention provides comprises the message of 2 types: request message and data-message, such as accompanying drawing 5(a), 5(b) shown in.
Request message mainly comprises 4 options: content name, selection condition, randomized number with can option, as shown in Fig. 5 (a). Wherein, the requested content of content name Option, selection condition option indicates the content choice conditions such as priority ordering, content source filtration, content choice scope, for avoiding, the circulation of request message forwards randomized number option, can provide the expansion information according to actual demand interpolation such as type, application message by option.
In the present invention, when the type of request message is " common ", " mobile re-transmission " or " mobile forwarding ", application message is " station location marker that requested content is current "; When the type of request message is for " user moves beginning ", application message be " station location marker of the primary access router of user " and " user asked but fail the content name of content of acquisition "; When the type of request message is for " content source moves beginning ", application message is " station location marker of the primary access router of content source " and " content name of the available content of content source "; When the type of request message is for " content source has moved ", application message is " station location marker of the primary access router of content source ", " content name of the available content of content source " and " station location marker of the new access router of content source ".
Data-message mainly comprises 5 options: content name, signature, signature information, content with can option, as shown in Fig. 5 (b). Wherein, the requested content of content name Option, signature option is for realizing the source certification of content, signature information option provides the content signature information such as content source mark, key location, expired time, content options comprises requested content, can provide the expansion information according to actual demand interpolation such as type, application message by option.
In the present invention, when the type of data-message is " common ", " mobile re-transmission " or " mobile forwarding ", application message is " station location marker that requested content is current ".
Data structure
Mobile support method in the content center network that the embodiment of the present invention provides comprises the data structure of 3 types: content memorizer, request table undetermined and forwarding information storehouse, such as accompanying drawing 6(a)-6(c) shown in.
Content memorizer stores the available content of this node, mainly comprises 3 options: content name, content and survival time, as shown in Fig. 6 (a). What the node in content center network can be received comprises the content memorizer of data-message buffer memory to this node of requested content, to reduce the time of response of other this content of node visit in content center network, it is to increase the content distribution efficiency of content center network.
Request token this node of record undetermined receives but the request message state also failing to be consumed, mainly comprises 3 options: content name, entrance list and survival time, as shown in Fig. 6 (b). When the mobile state flag bit that in entrance list, interface is corresponding is " 0 ", the user of this entry corresponding content and this node is asked to be in connection state; When the mobile state flag bit that in entrance list, interface is corresponding is " 1 ", the user of this entry corresponding content and this node is asked to be in disconnection state; The mobile state flag bit that in entrance list, interface is corresponding is defaulted as " 0 ". The data-message comprising requested content can be forwarded to the node of this content of request by content center network according to request table undetermined.
Forwarding information storehouse records the request message that this node receives and optionally forwards path, mainly comprises 3 options: content name or station location marker, outlet list and survival time, as shown in Fig. 6 (c). When the mobile state flag bit that in outlet list, interface is corresponding is " 0 ", content source and the network of this entry corresponding content are in connection state; When the mobile state flag bit that in outlet list, interface is corresponding is " 1 ", the content source of this entry corresponding content and network are in disconnection state; The mobile state flag bit that in outlet list, interface is corresponding is defaulted as " 0 ". The request message being used for request content can be forwarded to the node that can provide this content by content center network according to forwarding information storehouse.
Message Processing flow process
Mobile support method in the content center network that the embodiment of the present invention provides comprises the Message Processing flow process of 2 types: request message treatment scheme and data-message treatment scheme, such as Fig. 7 (a), 7(b) shown in.
Request message treatment scheme is as shown in Fig. 7 (a).
1. type is the request message treatment scheme of " common ", " mobile re-transmission " or " mobile forwarding ":
Whether step 11, exist the entry of coupling according to the content memorizer of the longest prefix match principle decision node of content name. If performing step 12; If not, perform step 13.
Step 12, it is to construct comprise the data-message of requested content, and the data-message of new construction is forwarded by receiving the interface of request message, abandon the request message received simultaneously.
Whether step 13, exist the entry of coupling according to the request table undetermined of the longest prefix match principle decision node of content name. If performing step 14; If not, perform step 15.
Step 14, upgrades request table undetermined coupling entry (the mobile state flag bit of the interface and correspondence thereof that receive request message is added into the entrance list of request table undetermined coupling entry), and abandons the request message received.
Step 15, successively according to whether station location marker (" station location marker that requested content is current " that request message comprises) exists, with the forwarding information storehouse of the longest prefix match principle decision node of content name, the entry mated. If performing step 16; If not, perform step 17.
Step 16, judges whether forwarding information storehouse coupling entry exists mobile state flag bit. If performing step 18; If not, perform step 19.
Step 17, node thinks that the object of request message can not reach, and abandons the request message received.
Step 18, judges whether the mobile state flag bit of forwarding information storehouse coupling entry is 0. If performing step 110; If not, perform step 111.
Step 19, upgrade request table undetermined (adding the undetermined request table clause corresponding with requested content), and forward, according to the forwarding strategy (being defaulted as Best-Route strategy, namely select outlet that priority is the highest and the request message that receives along the path forward node of optimum) of the coupling outlet list of entry of forwarding information storehouse and this node, the request message received.
Step 110, judges that whether " station location marker that requested content is current " that the station location marker of forwarding information storehouse coupling entry comprises with request message be consistent. If performing step 112; If not, perform step 113.
Step 111, node is thought provides the content source of requested content and network to be in disconnection state, the request message that buffer memory receives.
Step 112, upgrade request table undetermined (adding the undetermined request table clause corresponding with requested content), and forward, according to the forwarding strategy (being defaulted as Best-Route strategy, namely select outlet that priority is the highest and the request message that receives along the path forward node of optimum) of the coupling outlet list of entry of forwarding information storehouse and this node, the request message received.
Step 113, upgrades the request message received and (type is set to " mobile forwarding "; Application message is set to " station location marker that requested content is current " the i.e. station location marker of forwarding information storehouse coupling entry) entry (interface receiving request message is added into the entrance list of request table undetermined coupling entry) is mated with request table undetermined, and forward the request message after upgrading according to the forwarding strategy (being defaulted as Best-Route strategy, namely select outlet that priority is the highest and the request message that receives along the path forward node of optimum) of the coupling outlet list of entry of forwarding information storehouse and this node.
2. type is the request message treatment scheme of " user moves beginning ":
Step 21, " station location marker of the primary access router of user " that the station location marker of comparison node and request message comprise, judges that whether this node is the primary access router of user. If performing step 22; If not, perform step 23.
Step 22, " user asked but fail the content name of content that obtains " comprised according to request message, upgrade this user to have asked but the request table clause undetermined (being set to mobile state flag bit corresponding to interface receiving this request message " 1 ") that do not obtain content, and abandon the request message received.
Step 23, it is wrong that node thinks that this request message forwards, and abandons the request message received.
3. type is the request message treatment scheme of " content source moves beginning ":
Step 31, " station location marker of the primary access router of content source " that the station location marker of comparison node and request message comprise, judges that whether this node is the primary access router of content source. If performing step 32; If not, perform step 33.
Step 32, " content name of the available content of content source " comprised according to request message, upgrade forwarding information storehouse entry corresponding to content available with content source (being set to " 1 " by the mobile state flag bit corresponding with the interface receiving this request message), and abandon the request message received.
Step 33, it is wrong that node thinks that this request message forwards, and abandons the request message received.
4. type is the request message treatment scheme of " content source has moved ":
Step 41, " station location marker of the primary access router of content source " that the station location marker of comparison node and request message comprise, judges that whether this node is the primary access router of content source. If performing step 42; If not, perform step 43.
Step 42, " content name of the available content of content source " comprised according to request message, outlet (is set to " interface receiving this request message " by the forwarding information storehouse entry upgrading content available with content source corresponding; Movement state flag bit is set to " 0 "; Station location marker is set to " station location marker of the new access router of content source "), and abandon the request message received; Perform step 44.
Step 43, " station location marker of the new access router of content source " that the station location marker of comparison node and request message comprise, judges that whether this node is the new access router of content source. If performing step 46; If not, perform step 47.
Step 44, upgrades the request message mailing to content source original position and (type is set to " mobile forwarding "; Application message is set to the station location marker of " station location marker that requested content is current " the i.e. new access router of content source); Perform step 45.
Step 45, forwards the request message after upgrading (being the request message treatment scheme of " common ", " mobile re-transmission " or " move and forward " with reference to above-mentioned 1. type).
Step 46, " content name of the available content of content source " comprised according to request message, adds the forwarding information storehouse entry that content available with content source is corresponding; Perform step 47.
Whether step 47, exist the entry of coupling according to the forwarding information storehouse of the longest prefix match principle decision node of station location marker (" station location marker of the primary access router of content source " that request message comprises). If performing step 48; If not, perform step 49.
Step 48, the request message received is forwarded according to the forwarding strategy (being defaulted as Best-Route strategy, namely select outlet that priority is the highest and the request message that receives along the path forward node of optimum) of the coupling outlet list of entry of forwarding information storehouse and this node.
Step 49, node thinks that the object of request message can not reach, and abandons the request message received.
Data-message treatment scheme is as shown in Fig. 7 (b).
Type is the data-message treatment scheme of " common ", " mobile re-transmission " or " mobile forwarding ":
Whether step 51, exist the entry of coupling according to the content memorizer of the longest prefix match principle decision node of content name. If performing step 52; If not, perform step 53.
Step 52, node is thought and is received the content that this data-message comprises, and abandons the data-message received.
Whether step 53, exist the entry of coupling according to the request table undetermined of the longest prefix match principle decision node of content name. If performing step 54; If not, perform step 55.
Step 54, judges whether the mobile state flag bit of request table undetermined coupling entry is 0. If performing step 56; If not, perform step 57.
Step 55, node think non-request receiving to the content that comprises of data-message, abandon the data-message received.
Step 56, the data-message that buffer memory receives is to the content memorizer of node, and forwards, according to the entrance list of request table undetermined coupling entry, the data-message received, and deletes request table undetermined coupling entry simultaneously.
Step 57, node thinks that the user of the content that requested data message comprises and this node are in disconnection state, and the data-message that buffer memory receives, to the content memorizer of node, deletes request table undetermined coupling entry simultaneously.
Interacting message flow process
Mobile support method in the content center network that the embodiment of the present invention provides comprises the interacting message flow process of 2 types: the interacting message flow process of user's mobile context and the interacting message flow process of content source mobile context, such as Fig. 8 (a), 8(b) shown in.
The interacting message flow process of user's mobile context is as shown in Fig. 8 (a).
5. when user's mobile handoff is about to start:
Step 81, user sends a request message, and (type is " user moves beginning "; Application message is " station location marker of the primary access router of user " and " user asked but fail the content name of content that obtains ") to its primary access router, impel its primary access router to upgrade this user and asked but the request table clause undetermined (the mobile state flag bit corresponding with the interface receiving this request message is set to " 1 ") that do not obtain content; Meanwhile, user's stopping sends a request message, and (type is " common "; Application message is the station location marker of " station location marker that requested content is current " the i.e. access router of content source) network that leaves it is about to it.
6. in user's mobile handoff process:
Step 82, the primary access router of user is according to the request table clause undetermined (mobile state flag bit be " 1 ") after upgrading, and buffer memory mails to the data-message of user's original position, and (type is " common "; Application message is the station location marker of " station location marker that requested content is current " the i.e. access router of content source).
7. after user's mobile handoff completes:
Step 83, user sends a request message, and (type is " mobile re-transmission "; Application message is " station location marker that requested content is current " the i.e. station location marker of the primary access router of user) to its primary access router.
Step 84, the primary access router of user receives the request message of step 83, and type (is set to " mobile re-transmission " by the data-message upgrading buffer memory; Application message is set to " station location marker that requested content is current " the i.e. station location marker of the primary access router of user), and further the data-message after renewal is forwarded to the new location after user's mobile handoff.
Step 85-86, hereafter, user sends a request message, and (type is " common "; The station location marker that application message is " station location marker that requested content is current " the i.e. access router of content source) to the content source that can provide requested content; Content source forwards the data-message that comprises requested content, and (type is for " common "; Application message is the station location marker of " station location marker that requested content is current " the i.e. access router of content source) new location to user's mobile handoff.
The interacting message flow process of content source mobile context is as shown in Fig. 8 (b).
8. when content source mobile handoff is about to start:
Step 91, content source sends a request message, and (type is " content source moves beginning "; Application message is " station location marker of the primary access router of content source " and " content name of the available content of content source ") to its primary access router, impel its primary access router to upgrade forwarding information storehouse entry (being set to " 1 " by the mobile state flag bit corresponding with the interface receiving this request message) corresponding to content available with content source.
9. in content source mobile handoff process:
Step 92, the primary access router of content source is according to the forwarding information storehouse entry (mobile state flag bit be " 1 ") after upgrading, and buffer memory mails to the request message of content source original position, and (type is " common "; Application message is " station location marker that requested content is current " the i.e. station location marker of the primary access router of content source).
10. after content source mobile handoff completes:
Step 93, content source sends a request message, and (type is " content source has moved "; Application message is " station location marker of the primary access router of content source ", " content name of the available content of content source " and " station location marker of the new access router of content source ") to its primary access router. During the new access router of this request message approach content source, this access router is impelled to add forwarding information storehouse entry corresponding to content available with content source; When this request message is forwarded to the primary access router of content source, outlet (is set to " interface receiving this request message " by the forwarding information storehouse entry impelling this access router to upgrade content available with content source corresponding; Movement state flag bit is set to " 0 "; Station location marker is set to " station location marker of the new access router of content source ").
Step 94, the primary access router of content source receives the request message of step 93, upgrades the request message mailing to content source original position and (type is set to " mobile forwarding "; Application message is set to the station location marker of " station location marker that requested content is current " the i.e. new access router of content source), and further the request message after renewal is forwarded to the new location after content source mobile handoff.
Step 95, content source receives the request message of step 94, and (type is " mobile forward " to forward the data-message that comprises requested content; The station location marker that application message is " station location marker that requested content is current " the i.e. new access router of content source) to the user asking this content.
Step 96-97, hereafter, user sends a request message, and (type is " common "; Application message is the station location marker of " station location marker that requested content is current " the i.e. new access router of content source) new location to content source mobile handoff; Content source forwards the data-message that comprises requested content, and (type is for " common "; The station location marker that application message is " station location marker that requested content is current " the i.e. new access router of content source) to the user asking this content.
Embodiment one
Embodiments provide the mechanism of the user's mobility support in a kind of content center network, user's mobile handoff can be effectively avoided to cause the loss of request message and data-message, and the mobile handoff time delay that user's mobile handoff is introduced can be shortened to a certain extent, it is to increase the mobile handoff of user is experienced.
User's mobile context schematic diagram under this mechanism is as shown in Figure 9, see table 1, in the process of video/as3/ar3/iplab/toalice.avi/v1 that user ALICE provides at view content source IPLAB, from the primary access router of access router-A R1(user, station location marker is /as1/ar1) mobile handoff is to the new access router accessing router-A R2(user, station location marker is /as2/ar2).
The communication process of this mechanism user's mobile context is specific as follows:
Step 301, when user's ALICE mobile handoff is about to start, sending a request message, (content name is "/as1/ar1/mobilitycontroller "; Type is " user moves beginning "; Application message be "/as1/ar1 " with "/as3/ar3/iplab/toalice.avi/v1/sn; n=43; ...; 62 ", n is the sequence number of video content block) to the primary access router AR1 of ALICE, impel AR1 to upgrade ALICE and asked but the request table clause undetermined (the mobile state flag bit corresponding with the interface " 0 " receiving this request message is set to " 1 ") that do not obtain content; Meanwhile, ALICE stop sending a request message (content name for "/as3/ar3/iplab/toalice.avi/v1/sn ", n=63,64, Type is " common "; Application message is " as3/ar3 ") to AR1, avoid ALICE mobile handoff to cause the loss of request message.
Step 302, in ALICE mobile handoff process, AR1 is according to the request table clause undetermined (mobile state flag bit is " 1 ") after renewal, buffer memory mails to the data-message of ALICE original position, and (content name is for "/as3/ar3/iplab/toalice.avi/v1/sn ", n=43 ..., 62; Type is " common "; Application message is " as3/ar3 "). So, the data-message comprising requested content is no longer forwarded to the position at the front place of ALICE mobile handoff by AR1, whereby, ALICE mobile handoff can be avoided to cause the loss of data-message.
Step 303, after ALICE mobile handoff completes, send a request message (content name is "/as3/ar3/iplab/toalice.avi/v1/sn ", n=43 ..., 62; Type is " mobile re-transmission "; Application message is "/as1/ar1 ") to AR1.
Step 304, AR1 receives the request message of step 303, and type (is set to " mobile re-transmission " by the data-message upgrading buffer memory; Application message is set to "/as1/ar1 "), and further by upgrade after data-message (content name is "/as3/ar3/iplab/toalice.avi/v1/sn ", n=43 ..., 62; Type is " mobile re-transmission "; Application message is " as1/ar1 ") it is forwarded to the new location after ALICE mobile handoff. So, ALICE has upgraded in the whole network forwarding information storehouse without the need to waiting, can fetch the content failing mobile handoff process to obtain from contiguous AR1, whereby, can shortening the mobile handoff time delay that ALICE mobile handoff is introduced to a certain extent, the mobile handoff promoting ALICE is experienced.
Step 305, hereafter, ALICE start to send a request message (content name is "/as3/ar3/iplab/toalice.avi/v1/sn ", n=63,64, Type is " common "; Application message is " as3/ar3 ") to the content source IPLAB that can provide requested content.
Step 306, IPLAB receives the request message of step 305, it is to construct and forward comprise requested content data-message (content name for "/as3/ar3/iplab/toalice.avi/v1/sn ", n=63,64, Type is " common "; Application message is " as3/ar3 ") new location to ALICE mobile handoff. So, ALICE and IPLAB by the interactive communication of common request message and data-message, content requests before the ALICE mobile handoff that continues further and acquisition.
In table 1 step 301 AR1 upgrade after request table clause undetermined
Embodiment two
Embodiments provide the mechanism of the content source mobility support in a kind of content center network, content source mobile handoff can be effectively avoided to cause the loss of request message, and the mobile handoff time delay that content source mobile handoff is introduced can be shortened to a certain extent, it is to increase the mobile handoff of user is experienced.
Content source mobile context schematic diagram under this mechanism is as shown in Figure 10, see table 2-4, content source NGIID is in the process for user BOB offer video/as1/ar1/ngiid/tobob.avi/v1, from the primary access router of access router-A R1(content source, station location marker is /as1/ar1) mobile handoff is to the new access router accessing router-A R2(content source, station location marker is /as2/ar2).
The communication process of this contents of mechanism source mobile context is specific as follows:
Step 401, when content source NGIID mobile handoff is about to start, sending a request message, (content name is "/as1/ar1/mobilitycontroller "; Type is " content source moves beginning "; Application message is "/as1/ar1 " and "/as1/ar1/ngiid/tobob.avi/v1 ") to the primary access router AR1 of NGIID, impel AR1 to upgrade forwarding information storehouse entry (being set to " 1 " by the mobile state flag bit corresponding with the interface " 0 " receiving this request message) corresponding to content available with NGIID.
Step 402, in NGIID mobile handoff process, AR1 is according to the forwarding information storehouse entry (mobile state flag bit is " 1 ") after renewal, buffer memory mails to the request message of NGIID original position, and (content name is for "/as1/ar1/ngiid/tobob.avi/v1/sn ", n=43 ..., 62; Type is " common "; Application message is "/as1/ar1 "). So, the request message received no longer is forwarded to the position at the front place of NGIID mobile handoff by AR1; Whereby, the loss of the request message that NGIID mobile handoff causes can be avoided.
Step 403, after NGIID mobile handoff completes, sending a request message, (content name is "/as1/ar1/mobilitycontroller "; Type is " content source has moved ", and application message is "/as1/ar1 ", "/as1/ar1/ngiid/tobob.avi/v1 " and "/as2/ar2 ") to AR1. During this request message approach AR2, AR2 is impelled to add forwarding information storehouse entry corresponding to content available with content source; When this request message is forwarded to AR1, AR1 is impelled to upgrade forwarding information storehouse entry (outlet be set to " 1 ", be set to " 0 " by movement state flag bit, be set to "/as2/ar2 " by station location marker) corresponding to content available with content source.
Step 404, AR1 receives the request message of step 403, (type is set to upgrading the request message mailing to NGIID original position " mobile forwarding "; Application message is set to "/as2/ar2 "), and further by upgrade after request message (content name is "/as1/ar1/ngiid/tobob.avi/v1/sn ", n=43 ..., 62; Type is " mobile forwarding "; Application message is "/as2/ar2 ") it is forwarded to the new location after NGIID mobile handoff.
Step 405, NGIID receives the request message of step 4, by forward comprise requested content data-message (content name for "/as1/ar1/ngiid/tobob.avi/v1/sn ", n=43 ..., 62; Type is " mobile forwarding "; Application message is "/as2/ar2 ") to the user BOB asking this content. So, BOB has upgraded in the whole network forwarding information storehouse without the need to waiting, the content provided after can obtaining NGIID mobile handoff, whereby, can shorten the mobile handoff time delay that NGIID mobile handoff is introduced to a certain extent, and the mobile handoff promoting BOB is experienced.
Step 406, hereafter, BOB send a request message (content name for "/as1/ar1/ngiid/tobob.avi/v1/sn ", n=63,64, Type is " common "; Application message is " as2/ar2 ") new location to NGIID mobile handoff.
Step 407, NGIID receives the request message of step 406, it is to construct and forward comprise requested content data-message (content name for "/as1/ar1/ngiid/tobob.avi/v1/sn ", n=63,64, Type is " common "; Application message is " as2/ar2 ") to BOB. So, BOB and NGIID by the interactive communication of common request message and data-message, content requests before the NGIID mobile handoff that continues further and acquisition.
In table 2 step 401 AR1 upgrade after forwarding information storehouse entry
In table 3 step 403 AR1 upgrade after forwarding information storehouse entry
The forwarding information storehouse entry that in table 4 step 403, AR2 adds
Although the foregoing describing the specific embodiment of the present invention, but the technician of this area is to be understood that, these embodiments are only illustrate, the technician of this area is not when departing from principle and the essence of the present invention, it is possible to the details of aforesaid method and system is carried out various omission, replacement and change. Such as, merge aforesaid method step, thus perform the identical function of essence to realize the scope that the identical result of essence then belongs to the present invention according to the method that essence is identical. Therefore, the scope of the present invention is only defined by the appended claims.
Claims (3)
1. the mobile support method in a content center network, it is characterised in that, comprise user's mobility support mechanism, described user's mobility support mechanism comprises the following steps:
When user's mobile handoff is about to start, transmission types be the request message of " user moves beginning " to its primary access router, impel its primary access router to upgrade this user and asked but the request table clause undetermined that do not obtain content; Meanwhile, user stops the network that the request message that transmission types is " common " is about to leave to it, avoids user's mobile handoff to cause the loss that type is the request message of " common ";
In user's mobile handoff process, its primary access router is according to the request table clause undetermined after renewal, and buffer memory mails to the data-message that the type of user's original position is " common ", avoids user's mobile handoff to cause the loss of data-message;
After user's mobile handoff completes, transmission types is that the request message of " mobile retransmit " is to its primary access router, impel its primary access router that the data-message that the type of buffer memory is " common " is updated to the data-message of type for " mobile re-transmission ", and it is forwarded to the new location after user's mobile handoff;
Comprising content source mobility support mechanism further, described content source mobility support mechanism comprises the following steps:
When content source mobile handoff is about to start, transmission types be the request message of " content source moves beginning " to its primary access router, impel its primary access router to upgrade forwarding information storehouse entry that this content source can provide content;
In content source mobile handoff process, its primary access router is according to the forwarding information storehouse entry after renewal, and buffer memory mails to the request message that the type of content source original position is " common ", avoids content source mobile handoff to cause the loss of request message;
After content source mobile handoff completes, the request message that transmission types is " content source has moved " is to its primary access router, impel its primary access router that the request message that the type mailing to content source original position is " common " is updated to the request message of type for " mobile re-transmission ", and it is forwarded to the new location after content source mobile handoff;
Content source receives the request message that type is " mobile forward ", forwards data-message that the type comprising requested content be " mobile forwarding " to the user asking this content.
2. the mobile support method in content center network according to claim 1, it is characterised in that, comprise further:
Hereafter, user's transmission types is that the request message of " common " is to providing the content source of requested content; It is the data-message of " common " new location to user's mobile handoff that content source forwards the type comprising requested content.
3. the mobile support method in content center network according to claim 1, it is characterised in that, comprise further:
Hereafter, user's transmission types is the request message of " common " new location to content source mobile handoff; It is that the data-message of " common " is to the user asking this content that content source forwards the type comprising requested content.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310315590.2A CN103415047B (en) | 2013-07-25 | 2013-07-25 | Mobile support method in a kind of content center network |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310315590.2A CN103415047B (en) | 2013-07-25 | 2013-07-25 | Mobile support method in a kind of content center network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103415047A CN103415047A (en) | 2013-11-27 |
| CN103415047B true CN103415047B (en) | 2016-06-01 |
Family
ID=49608023
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310315590.2A Expired - Fee Related CN103415047B (en) | 2013-07-25 | 2013-07-25 | Mobile support method in a kind of content center network |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103415047B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104823479B (en) * | 2013-11-29 | 2018-12-07 | 华为技术有限公司 | A kind of data transmission device based on content center network, method and communication system |
| CN104158842B (en) * | 2014-07-14 | 2017-05-31 | 中国人民解放军信息工程大学 | A kind of dynamic data power supply management method based on many agencies |
| CN106060108A (en) * | 2016-05-05 | 2016-10-26 | 北京邮电大学 | Mobility supporting method and device in network |
| CN107733946B (en) * | 2016-08-11 | 2021-05-07 | 中国电子科技集团公司电子科学研究院 | Content source mobility support method based on active forwarding in CCN (content centric network) |
| CN107733948B (en) * | 2016-08-11 | 2021-01-05 | 中国电子科技集团公司电子科学研究院 | User mobility support method for distinguishing content in CCN (content-centric networking) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102271148A (en) * | 2010-05-13 | 2011-12-07 | 三星电子株式会社 | Terminal for a content centric network and method of communication for a terminal and a hub in a content centric network |
| CN102665190A (en) * | 2012-04-20 | 2012-09-12 | 西安电子科技大学 | Self-organization based mobility support method |
| WO2013010006A2 (en) * | 2011-07-12 | 2013-01-17 | Huawei Technologies Co., Ltd. | Seamless mobility schemes in named-data networking using multi-path routing and content caching |
-
2013
- 2013-07-25 CN CN201310315590.2A patent/CN103415047B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102271148A (en) * | 2010-05-13 | 2011-12-07 | 三星电子株式会社 | Terminal for a content centric network and method of communication for a terminal and a hub in a content centric network |
| WO2013010006A2 (en) * | 2011-07-12 | 2013-01-17 | Huawei Technologies Co., Ltd. | Seamless mobility schemes in named-data networking using multi-path routing and content caching |
| CN102665190A (en) * | 2012-04-20 | 2012-09-12 | 西安电子科技大学 | Self-organization based mobility support method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103415047A (en) | 2013-11-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103415047B (en) | Mobile support method in a kind of content center network | |
| CN103581019B (en) | A kind of information centre's network mobility management method of content-based popularity | |
| CN103339901B (en) | Terminal in content guiding network environment and the communication means of intermediate node and terminal and intermediate node | |
| JP3768406B2 (en) | Information distribution control method and system in mobile communication network, and information storage method in communication node in mobile communication network | |
| CN103731451B (en) | A kind of method and system that file uploads | |
| JP5486590B2 (en) | System and method for managed content delivery | |
| CN103703739A (en) | Method and apparatus for seamless mobility techniques in content-centric network | |
| CN101924785A (en) | Data uploading and downloading methods and system | |
| EP3539269B1 (en) | Node type based control of assistance for data streaming | |
| CN101039309A (en) | Link sharing service apparatus and communication method thereof | |
| JP4306365B2 (en) | Server and content receiving apparatus | |
| CN101102287A (en) | A method and system for transferring files via browser | |
| WO2008022522A1 (en) | Method and system for providing mobile service and management center server therefor | |
| JP2015505426A (en) | Prioritizing application data for transmission in wireless user devices | |
| JP5001880B2 (en) | Streaming service system and method | |
| KR20120038187A (en) | Method and apparatus for sharing contents using information of group changing in content oriented network environment | |
| WO2009000214A1 (en) | Method and device for configuring configuration data of user access network | |
| CN101540969A (en) | Method for realizing number carried in short message system and device thereof | |
| CN102571409B (en) | Service request management system and method for realizing service across-terminal application | |
| JP5476975B2 (en) | Inter-network data distribution system, information communication terminal, content distribution server | |
| TW200808082A (en) | File repair mechanism for MBMS and UMTS network | |
| CN104581421A (en) | Point-to-point flow media download method and node terminal device | |
| CN103095587A (en) | Method of registration service and network ethnic group central control node and system | |
| WO2011066788A1 (en) | Method, apparatus and system for file transmission between support region systems | |
| KR101904195B1 (en) | Apparatus and method for caching and forwarding of layered viedeo |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| EE01 | Entry into force of recordation of patent licensing contract |
Application publication date: 20131127 Assignee: China High Speed Rail Technology Limited by Share Ltd Assignor: Beijing Jiaotong University Contract record no.: 2016990000184 Denomination of invention: Mobility supporting method in content center network License type: Common License Record date: 20160505 |
|
| GR01 | Patent grant | ||
| LICC | Enforcement, change and cancellation of record of contracts on the licence for exploitation of a patent or utility model | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20160601 Termination date: 20200725 |