WO2008017267A1 - Procédé, système et dispositif pour traiter un transfert intercellulaire de couche trois - Google Patents

Procédé, système et dispositif pour traiter un transfert intercellulaire de couche trois Download PDF

Info

Publication number
WO2008017267A1
WO2008017267A1 PCT/CN2007/070390 CN2007070390W WO2008017267A1 WO 2008017267 A1 WO2008017267 A1 WO 2008017267A1 CN 2007070390 W CN2007070390 W CN 2007070390W WO 2008017267 A1 WO2008017267 A1 WO 2008017267A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
address
layer
handover
conflict detection
Prior art date
Application number
PCT/CN2007/070390
Other languages
English (en)
Chinese (zh)
Inventor
Yong Xie
Wenliang Liang
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2008017267A1 publication Critical patent/WO2008017267A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, system and device for processing a layer three handover.
  • IPv6 Internet Protocol version 6, Internet Protocol version 6
  • IPv6 Internet Protocol version 6, Internet Protocol version 6
  • Mobile IPv6 contains three functional entities: mobile node (MN, Mobile Node, or terminal), home agent (HA, Home Agent), and related nodes (CN, Correspondent Node).
  • MN mobile node
  • HA Home Agent
  • CN Correspondent Node
  • the mobile node MN in the foreign network has a home address (HoA, Home Address) and a care-of address (CoA, Care-of Address).
  • the mobile node MN registers with the home agent HA through the Binding Update (BU, Binding Update) process, the home agent HA processes the request, and maintains a correspondence table between the HoA and the CoA.
  • BU Binding Update
  • the home agent HA intercepts the data packet sent to the mobile node MN's home address HoA in the home network, and forwards it to the mobile node's care-of address CoA through the tunnel.
  • the data sent by the mobile node MN also needs to be sent via the reverse tunnel.
  • MIPv6 also defines a route optimization process, so that the data packets sent by the CN to the MN can be forwarded without HA.
  • RFC 3775 Request For Comments
  • RFC for IPv6 mobility For mobile IPv6, its mobility detection is mainly to detect the mobility of L3 (Layer 3, ie IP layer).
  • L3 Layer 3, ie IP layer
  • the mobile node MN usually determines the access path of the current service through the neighboring service node unreachable detection. Whether the device is also reachable in both directions. If it is unreachable, the mobile node MN looks for a new access router (AR, Access Router, or service node) as its current serving router (the default router). This process is a process of L3 handover.
  • the IPv6 host address stateless auto-configuration needs to obtain the prefix information of the network segment to be configured. For example, when the terminal needs to automatically configure the host address, the first need to be performed. A route broadcast message (RA) from the new AR is received, and a new care-of address COA is generated based on the message.
  • RA route broadcast message
  • FIG. 1 is a flow chart of the prior art layer three switching. In this process, in order to complete the L3 handover, the mobile node MN in the prior art needs to complete the following steps:
  • the terminal (such as the mobile node) automatically generates a new care-of address COA according to the RA message sent from the target service node;
  • the mobile node performs address conflict detection (DAD, Duplicate Address Detection) on the new care-of address COA;
  • DAD Duplicate Address Detection
  • the mobile node After detecting that the original service node is unreachable, the mobile node initiates a binding update process, completes the binding update to the HA, and completes the L3 handover.
  • step 103 the DAD detection of the new care-of address COA is completed by a timeout mechanism.
  • the mobile node MN issues a DAD check message, if no other service node responds within the set time, the new care-of address COA is considered. There is no conflict, it can be used, so it takes a long time to wait for other service nodes to answer.
  • step 105 the operation of the mobile node MN detecting that the original service node is unreachable is also completed by the timeout mechanism.
  • the terminal confirms that the L3 switch has occurred. According to the existing specifications, these timeouts are all above the second level. Such a long delay leads to QOS (Quality of Service, Service) Quality) dramatically deteriorates, seriously affecting service quality and network performance.
  • QOS Quality of Service, Service
  • step 105 may not be completed all the time, that is, the L3 switch cannot be completed.
  • the invention provides a processing method, system and device for layer three switching, which can accelerate the layer three switching process of the terminal.
  • the present invention provides a layer 3 handover processing method, including: obtaining information that a terminal is or will undergo a layer three handover; and notifying the terminal that a layer three handover occurs.
  • the present invention also provides a layer 3 handover processing method, including: obtaining information that a terminal is undergoing or is about to undergo a layer three handover; and assisting the terminal to prepare a layer three handover.
  • the present invention further provides a layer 3 handover processing system, including a network side, and further includes a layer 3 handover notification module disposed on the network side, configured to obtain the information that the terminal is or will undergo a layer three handover, and notify the The layer 3 switch occurs on the terminal.
  • the present invention further provides a processing device for layer 3 switching, comprising: an information obtaining module, configured to obtain information that a layer 3 handover is occurring or is about to occur, and a layer three handover notification module, configured to notify the terminal that layer 3 is generated Switch.
  • the present invention further provides a layer three switching processing device, comprising: an information obtaining module, configured to obtain information that a layer is being or is about to undergo a layer three handover; and an address conflict detection module, configured to perform address conflict detection instead of the terminal.
  • the L3 handover occurs by using the active notification terminal, so that the terminal does not need to detect the reachability of the original service node by means of a timeout such as DAD, thereby speeding up the process of the terminal performing the L3 handover.
  • the L3 switching delay is reduced and the wireless air interface traffic is reduced, the service interruption delay is greatly reduced, and the network performance and service quality are greatly improved.
  • the method for actively assisting the terminal to perform the L3 handover enables the terminal to detect whether the new IP address is available by using a timeout manner such as DAD, thereby speeding up the terminal to perform L3 handover.
  • a timeout manner such as DAD
  • FIG. 2 is a flow chart of a processing method for layer 3 switching of the present invention
  • FIG. 3 is a schematic block diagram of a processing system for layer 3 switching of the present invention.
  • FIG. 4 is a schematic structural diagram of a first embodiment of a layer three handover processing device according to the present invention.
  • FIG. 5 is a schematic structural diagram of a second embodiment of a layer three handover processing device according to the present invention.
  • FIG. 6 is a schematic structural diagram of a third embodiment of a layer three switching processing apparatus according to the present invention.
  • the network side In a communication system such as a mobile communication system, in order to effectively utilize wireless resources and improve network performance, the network side generally acts as a controller, and the network side controls the process of communication and most of the behavior of the terminal in the network.
  • the network side can determine whether the terminal with which it is communicating needs to have an L3 switch (a L3 switch is about to occur) or whether an L3 switch is occurring.
  • the network side may actively notify the terminal that an L3 handover has occurred, without using the timeout manner of the terminal to detect whether the new IP address is available or whether the original service node is reachable.
  • the switching of the network side control can implement the context information about the terminal and the link between the original service node and the target service node. With the information, the network side can further complete the context information generation of the target service node, and generate an IP address to implement the network.
  • the L3 switch initiated by the side actively does not need to generate an IP address by interacting with the terminal.
  • the embodiment of the present invention clearly illustrates the technical solution of the present invention by taking the L3 handover of the mobile node in the mobile communication as an example.
  • the router that sends the RA message can obtain the context information of the terminal from other entities in the network or other ways, And when it is determined that the terminal will be connected to the router, the present invention can also be applied to these networks.
  • the original service node, the target service node, the terminal, the network entity where the service node is located, and the functional entity such as the network controller may be involved.
  • the service node may be an access router.
  • the protocol used may be RFC3775 for Mobile IPv6 and related protocols such as RFC3776. Those skilled in the art will recognize that other suitable protocols may also be used, such as RFC 3775 and RFC 3776 described above, which are merely exemplary.
  • One embodiment of the present invention uses the network side to send an RA message carrying the extended control identifier to the terminal to notify the terminal that a layer three handover occurs.
  • the extended control identifier is composed of five retaining bits in the RA message. The definition is as follows:
  • RCI Ring Configuration Indicator
  • Type 9 or other value that does not conflict with the current RFC specification.
  • IID length Length of the entire Option identified by 8 bytes, including the Type and Length fields.
  • IID length The length of the IID or IP address field (in bits). The value is 0 ⁇ 128. When the field is 128, it indicates that it carries a complete IP address. When it is other values, it indicates that it carries IID information.
  • Reserved Reserved field, can be filled in 0, the receiver ignores its contents.
  • IID or IP address The IID or IP address generated by the router for the terminal.
  • the IP address and IID are generated in accordance with the specifications of the RFC protocol.
  • the padding bit is a range of 0 to 63 bits to ensure that the entire Option is an 8-byte integer.
  • the target serving node controls the L3 switching operation of the terminal by using the value of the bit in the RCI in combination with the Option option:
  • the target serving node that sends the RA message can obtain the context information of the terminal from other entities of the network or other means, and determines that the terminal will move to the serving node, send a point-to-point RA message, which includes the RCI bit, Selected, you can also include the IID Option.
  • the above extension of the RA message is mainly applicable to the case of mobile IP.
  • the network can also speed up the access process of the terminal in the service node by adding the above information in the RA message, reducing the delay and improving the quality of service.
  • the terminal node After the terminal node receives the RA message containing the RCI bit (optional, which also contains the IID option), it is divided into four cases:
  • the RCI is the first extended control identifier: 11, indicating that the layer three handover has occurred, and the terminal obtains the IP address according to the RFC specification, and performs subsequent operations after the layer 3 handover has been detected.
  • the network side in the subsequent embodiment of FIG. 2 does not perform address conflict detection for the terminal.
  • the terminal needs to perform DAD subsequently, since it is known that the layer 3 handover has occurred, it is no longer necessary to complete the operation of the original service node unreachable through the timeout mechanism.
  • the time is shortened and the time is accelerated. Layer 3 switching process.
  • the RCI is the second extended control identifier: 10, indicating that the layer three handover has occurred, and the network side has performed DAD detection and passed for the IID currently used by the terminal.
  • the IP address of the terminal is stateless, the IP address on the link (ie, the new link after layer 3 switching) is directly generated by its IID and the RA message, and DAD detection is not required.
  • the IP address on the link is the care-of address, and the target serving node immediately sends the binding update message carrying the IP address to the home agent; If the IP address of the terminal is stateful, and the RA message carries the IID or IP address, the terminal uses the IP address in the RA message or the IP address generated by the IID as its new link (ie, Layer 3).
  • the IP address on the switched new link) is no longer DAD. It can be seen that, in this case, the terminal no longer needs to complete the DAD through the timeout mechanism, so compared with the prior art, the time is shortened and the layer 3 switching process is accelerated.
  • the RCI is the third extended control identifier: 01, indicating that the layer three handover has occurred, and the network side has performed the DAD detection for the IID currently used by the terminal but fails (indicating that a collision has occurred).
  • the terminal performs subsequent operations according to the specifications defined by the RFC; if the RA message carries the IID or IP address
  • the terminal uses the IP address carried in the RA message or the IP address generated by the IID carried thereby as its IP address on the new link, and does not perform DAD detection. It can be seen that, in this case, the terminal no longer needs to complete the DAD through the timeout mechanism, so compared with the prior art, the time is shortened and the layer three switching process is accelerated.
  • the RCI is the fourth extended control identifier: 00, indicating compatibility with the current RFC definition, and the terminal is processed according to the existing RFC specification.
  • FIG. 2 is a flowchart of a method for processing a layer 3 handover according to the present invention. Including the following steps:
  • L3 switching occurs or needs to occur (imminently) L3 switching
  • This step means that the network side knows that the terminal is happening or needs to happen (will happen) L3 handover.
  • IPv6 when resource optimization or regulation by a network controller, the network side can determine whether the terminal with which it is communicating is about to undergo an L3 handover or whether an L3 handover is occurring. If the network side does not replace the terminal to perform address conflict detection on the IP address, the step (201) directly proceeds to the following step 205, that is, the R3 message carrying the first extended control identifier is directly sent to the terminal, and the terminal is sent to the terminal. L3 switches, and the network side does not perform steps 202 to 204. If the network side wants to perform address conflict detection for its IP address for the terminal, the following steps (202 to 204) are performed.
  • the target service node obtains context information of the terminal from the original serving node.
  • the network side can implement the context information about the terminal and the link between the original service node and the target service node, and the context information includes the interface identifier IID currently used by the terminal.
  • the target service node generates a new IP address based on the obtained IID and the prefix information of the serving node (access router).
  • the target service node directly performs address conflict detection on the IP address generated by using the IID.
  • the target service node generates a new IP address according to the terminal IID and the prefix of the serving node (access router), and replaces the terminal to address the new IP address.
  • the collision detection DAD is to test whether the new IP address is available for the terminal to perform a new link after the layer three handover.
  • the target service node (access router) is required to perform DAD instead of the terminal, but the RFC specification of the prior art does not stipulate this aspect. Therefore, the DDA of the network side can be implemented by extending the existing RFC. Steps, here are a few options:
  • the target service node conflicts with the existing IP address by the IP address configured by all the terminal records recorded by the network entity. For some networks, because the network control needs, the network entity where the target service node (access router) is located records the IP address list or IID list of all the terminals configured under it, so this method can be used to DAD the new IP address.
  • the detection object of the address conflict detection is a list of IP addresses of all terminals currently used on the current link saved on the Neighbor Cache, and the target service node finds that an IP address is aged and is ready to be deleted. Before detecting whether the IP address is still valid, if it is still retained, the status is set to reach, otherwise it is deleted.
  • the service node maintains a list of neighbors. The list stores the IP address of the neighbor service node with which the service node has communicated for a certain period of time. If the IP address list is a list of IP addresses of all terminals currently in use on the current link, the network can obtain an IP address to be used by the newly entered terminal that does not conflict with the existing IP address according to this list. It can be seen that the target service node can also implement DAD by using neighbor list information.
  • the address conflict detection is specifically: the target service node directly to the terminal locally
  • the used IP address (such as the IP address generated according to the IID currently used by the terminal) transmits an address conflict detection message for address collision detection.
  • the target service node (access router) can also directly send DAD messages locally, instead of the terminal for address collision detection.
  • step 204 determining whether the address conflict detection is successful, is (ie, successful, no conflict), that the new IP address is considered available, proceeds to step 205, otherwise proceeds to step 206;
  • step 207 Send an RA message to the terminal, indicating that an L3 handover occurs, and no address conflict detection is performed, and then proceeds to step 207.
  • This step corresponds to the case where the RCI described above is the second extended control flag. That is, the RA message indicates that Layer 3 switching has occurred, and the network side has performed DAD detection and passed for the IID currently used by the terminal.
  • the IP address of the terminal is stateless, the IP address on the link is directly generated by the terminal directly with its IID and the RA message, and DAD detection is not required, and the processing method of the layer 3 handover is applied.
  • the IP address on the link is a care-of address
  • the target serving node immediately sends a binding update message carrying the IP address to the home agent; when the IP address of the terminal is stateful And the RA message carries the IID or the IP address, and the terminal uses the IP address carried in the RA message or the IP address generated by the carried IID as its IP address on the new link.
  • the new IP address used by the terminal on the new link after the layer 3 handover may be directly localized by the terminal with the IID currently used and the target service node (access router) prefix information provided by the RA message.
  • the generated may also be obtained by the IID or IP address in the RA message carrying the Option option.
  • steps 206a, 206b, and 206c are remedial measures taken by the terminal to determine, based on the received RA message, that the address conflict detection performed by the network side does not pass.
  • One of 206a, 206b, and 206c may be selected, and then proceeds to step 207.
  • the target service node generates a new IID or IP address information, completes the DAD detection, and sends The RA message carrying the new IID or IP address is sent to the terminal, indicating that the L3 handover occurs, and the terminal is required to use the new IID carried to generate an IP address or directly use the carried IP address. In this way, the DAD fails for the terminal on the network side, and the terminal does not need to perform DAD again.
  • Step 203 is to directly obtain the IID currently used by the terminal from the original serving node, and here the target service node generates a new IID for the terminal and informs the terminal. In addition, this mode corresponds to the case where the foregoing RCI is the third extended control identifier, carrying the IID or the IP address.
  • the target service node directly allocates a non-conflicting IP address to the terminal, and sends the IP address or the IID corresponding to the IP address to the terminal for direct use.
  • the network side actively replaces the terminal to perform DAD or actively informs the terminal that the L3 handover occurs, so that the terminal does not use the timeout manner to detect whether the new IP address is available or the original service node. Whether it is reachable or not, the present invention can reduce the L3 handover delay and reduce the wireless air interface traffic.
  • the active replacement of the terminal for the DAD includes two cases, and the other is to detect that the terminal is not assigned a conflicting IP address with the current use of the terminal.
  • the target serving node can directly allocate a non-conflicting IP address to the terminal, and send an RA message carrying the IP address to the terminal for direct use without steps 202-204.
  • the target service node allocates a non-conflicting IP address to the terminal, the terminal does not need to perform DAD, and the terminal also performs the L3 handover process. It can be seen that both of the above cases have achieved the purpose of replacing the terminal for DAD.
  • the active alternate terminal DAD and the notification terminal may be combined with the L3 switch, which can better reduce the L3 handover delay and accelerate the L3 handover process.
  • the terminal may not be able to obtain information that L3 is handed over. Due to The network side actively informs the terminal that an L3 handover has occurred, so that the process of discovering the L3 handover by the terminal can be accelerated.
  • the target service node can obtain the IP address used by the terminal before sending the RA information to the terminal, it is possible to detect in advance whether the IP address to be used by the terminal in the new service node or the network is conflicting or legal; In the case where the result of the DAD is a conflict, the terminal may further specify a new IP address that does not conflict.
  • the embodiment of the present invention can greatly speed up the handover time when the terminal accesses a new service node, in particular, speeds up the L3 handover in the mobile IP, and greatly reduces the interruption time of the service, which is large.
  • the layer 3 or layer 2 message may be used to notify the terminal to perform the layer 3 handover.
  • the method for extending the RA message in the foregoing embodiment is used to implement the layer 3 handover of the active notification terminal, and the extension may be achieved by other extension methods.
  • the goal can also be implemented by adding a similar message carrying relevant information. However, how these implementations change is within the protection scope of this patent.
  • Another embodiment of the present invention further provides a layer three handover processing system, including a network side, a terminal 320, an address conflict detection module 311 and a layer three handover notification module 312 disposed on the network side.
  • the address conflict detection module 311 and the layer three handover notification module 312 may be disposed in the target service node 310.
  • the target service node obtains the context information of the terminal 320 from the original service node 330, where the context information includes the interface of the terminal 320. Identifies the IID that is used to generate a new IP address along with the prefix broadcast by the target service node.
  • the address conflict detection module 311 is configured to obtain, by the network side, the IID or IP address available to the terminal 320 through address conflict detection when the terminal 320 is aware that the terminal 320 is occurring or needs to be generated (immediately).
  • the layer 3 handover notification module 312 is configured to notify the terminal 320 to perform a layer 3 handover, and enable the terminal 320 to obtain an IP address corresponding to the IID or directly obtain the foregoing IP address.
  • the foregoing network side knows that the terminal 320 is happening or is about to undergo a layer three handover, and can be implemented by obtaining information indicating that the terminal 320 is or will undergo a layer three handover, and the module that performs the function can be called a module. Information acquisition module.
  • the address conflict detection module 311 is specifically configured to: directly determine, according to the IP address list or IID list 340 configured by all the terminals 320 recorded by the network entity where the target service node 310 is located, whether the IP address or the IP address generated by the IID is Conflict with an existing IP address.
  • the address conflict detection module 311 is performing on the current link saved according to the neighbor list information.
  • the IP address list 350 of all terminals used obtains an IP address to be used by a newly entered terminal that does not conflict with an existing IP address.
  • the NS message is sent to detect whether the IP address is still valid, and then the reservation is continued, and the state is set to reach, otherwise, the deletion is performed.
  • the address conflict detection module 311 is further configured to: directly send an address conflict detection message locally to perform address conflict detection.
  • the Layer 3 handover notification module 312 is specifically configured to send an RA message carrying the extended control identifier to the terminal 320 to notify the terminal 320 to perform a layer 3 handover.
  • the extended control identifier may be composed of two of the five reserved bits in the RA message. Since the specific content related to the extended control identifier has been described in detail in the foregoing (see Tables 1, 2, and 3), Let me repeat.
  • the extended control flag indicates that the terminal 320 does not need to perform address collision detection.
  • the terminal 320 is configured to determine whether the network side obtains an available IID or an IP address according to the information notified by the layer three handover notification module 312, and then generates an IP address locally; otherwise, the IID or the network side sends the IID or IP address. If the IID is sent by the network side, an IP address is generated according to the IID.
  • the target serving node 310 sends an RA message to the terminal 320 via the layer three handover notification module 312, indicating that the L3 handover occurs. That is, the RA message indicates that the layer three handover has occurred, and the address conflict detection module 311 has performed DAD detection and passed for the IID currently used by the terminal 320.
  • the terminal 320 directly generates the IP address on the link directly with the IID and the RA message currently used by the terminal 320, and does not need to perform DAD detection.
  • the IP address on the link is the care-of address, and the layer 3 handover notification module 312 immediately sends the binding update message carrying the IP address to the home agent; If the IP address is in the state of stateful generation, and the RA message carries the IID or IP address, the terminal 320 uses the IP address carried by the RA message or the IP address generated by the carried IID as its new link. IP address.
  • the layer 3 handover notification module 312 sends an RA message to the terminal 320, indicating that the L3 handover occurs and indicates that the IID currently used by the terminal conflicts, and the terminal 320 receives Behavior as defined by existing RFCs Take action.
  • the address conflict detection module 311 fails the DAD for the terminal 320, and the terminal 320 is required to complete the DAD;
  • the target service node 310 generates the new IID information, and the address conflict detection module 311 completes the DAD detection.
  • the layer three handover notification module 312 sends the RA message carrying the new IID to the terminal 320, indicating that the L3 handover occurs, and the terminal 320 is required to update the IID, and use the new IID to generate an IP address.
  • the network side fails the DAD for the terminal 320 and assigns a new IID to it, so the terminal 320 is not required to complete the DAD again;
  • the target service node 310 directly generates a non-conflicting IP address for the terminal 320 through the address conflict detection module 311, and the layer 3 handover notification module 312 sends an RA message carrying the IP address to the terminal 320 for direct use.
  • FIG. 4 it is a schematic structural diagram of a first embodiment of a layer three switching processing device according to the present invention.
  • the processing device in this embodiment includes an information obtaining module 410 and a layer three switching notification module 420.
  • the internal structure and the connection relationship are further described below in conjunction with the working principle of the processing device.
  • the information obtaining module 410 of the processing device is configured to obtain information that the terminal is or will undergo a layer three handover and notify the layer three handover notification module. Further, the layer three handover notification module 420 notifies the terminal that a layer three handover occurs. Therefore, the terminal can complete the unreachable operation of the original service node without using the timeout mechanism, and shorten the process of the layer three handover.
  • the processing device may further include an address conflict detection module, configured to perform address conflict detection instead of the terminal.
  • an address conflict detection module configured to perform address conflict detection instead of the terminal.
  • FIG. 5 is a schematic structural diagram of a second embodiment of a layer three handover processing device according to the present invention.
  • the processing device in this embodiment includes an information obtaining module 510, a layer three switching notification module 520, and an address conflict detecting module 530.
  • the information obtaining module 510 is configured to obtain information that the terminal is or will undergo a layer three handover and notify the layer three handover notification module 520 and the address conflict detection module 530.
  • the layer three handover notification module 520 is configured to notify the terminal that a layer three handover occurs.
  • the address conflict detection module 530 is used to perform address conflict detection instead of the terminal, and the specific implementation manner thereof is various.
  • the address conflict detection module includes a first address conflict detection module, configured to perform collision detection on the first IP address used by the terminal on the new link after layer 3 handover.
  • the first IP address may be an IP address generated by the IID currently used by the terminal and the target service node (access router) prefix information, or the terminal may be in the original link.
  • the detection result may be notified to the terminal through the layer three handover notification module 420.
  • the address conflict detection module may further include a second address conflict detection module, configured to allocate a second IP address that does not conflict to the terminal, and pass the interface identifier corresponding to the second IP address or the second IP address through a layer
  • the three handover notification module 420 notifies the terminal.
  • the address conflict detection module 530 may include only the first address conflict detection module or only the second conflict module.
  • the processing device does not perform collision detection on the first address, but directly allocates a non-conflicting IP address to the terminal, so that the terminal can no longer need to perform an address. Conflict detection.
  • the address conflict detection module 530 can include both a first address conflict detection module and a second address conflict detection module. In this case, if the detection result of the first address conflict detection module is not conflicting, the layer 3 notification notification module 420 notifies the terminal, and the terminal does not need to perform address conflict detection again. If the detection result of the first address conflict detection module is a conflict, the second address conflict detection module allocates a non-conflicting second IP address to the terminal for use by the terminal on the new link after the layer 3 handover.
  • FIG. 6 is a schematic structural diagram of a third embodiment of a layer three handover processing device according to the present invention.
  • the layer three handover processing device in the embodiment of the present invention includes an information obtaining module 610 and an address conflict detecting module 630.
  • the information obtaining module 610 is configured to obtain information that the terminal is or will undergo a layer three handover, and notify the address conflict detection module 630.
  • the address conflict detection module 630 may include a third address conflict detection module, configured to perform address conflict detection on the first IP address used on the new link after the layer 3 switchover, and notify the detection result.
  • the terminal may further include a fourth address conflict detection module, configured to allocate a second IP address that does not conflict to the terminal, and notify the interface identifier corresponding to the second IP address or the second IP address. terminal.
  • the address conflict detection module 630 may include only the third address conflict detection module or only the fourth conflict module.
  • the processing device does not perform collision detection on the first IP address, but directly allocates a non-conflicting IP address to the terminal, so that the terminal can be no longer needed. Address conflict detection.
  • the address conflict detection module 630 can include both a third address conflict detection module, and A fourth address conflict detection module is included. In this case, if the detection result of the third address conflict detection module is not conflicting, the detection result of the address non-collision is directly notified to the terminal, and the terminal does not need to perform address conflict detection again. If the detection result of the third address conflict detection module is a conflict, the fourth address conflict detection module allocates a non-conflicting second IP address to the terminal for use by the terminal on the new link after the layer 3 handover.
  • the address conflict detection module 311 actively replaces the terminal 320 for DAD, and the layer three handover notification module 312 actively informs the terminal 320 that an L3 handover has occurred, so that the terminal 320 does not use the timeout method to detect the new IP.
  • the L3 handover delay can be reduced and the wireless air interface traffic can be reduced, the process of the L3 handover can be accelerated by the terminal 320, the service interruption time is greatly reduced, and the network performance is greatly improved. And quality of service.

Abstract

L'invention concerne un procédé pour traiter un transfert intercellulaire de couche trois dans le domaine technique des systèmes de communication. Le procédé comprend les étapes suivantes : obtenir l'information qu'un terminal a ou aura un transfert intercellulaire de couche trois; notifier le terminal du transfert intercellulaire de couche trois. Un autre procédé pour traiter un transfert intercellulaire de couche trois est également fourni, qui comprend les étapes suivantes : obtenir l'information qu'un terminal a ou aura un transfert intercellulaire de couche trois; aider le terminal à préparer le transfert intercellulaire de couche trois. Un système et un dispositif pour traiter un transfert intercellulaire de couche trois sont également fournis. Par l'intermédiaire des projets techniques ci-dessus, la vitesse du transfert intercellulaire de couche trois du terminal peut être augmentée.
PCT/CN2007/070390 2006-07-31 2007-07-31 Procédé, système et dispositif pour traiter un transfert intercellulaire de couche trois WO2008017267A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610104036.X 2006-07-31
CNA200610104036XA CN101119291A (zh) 2006-07-31 2006-07-31 层三切换的处理方法及其系统

Publications (1)

Publication Number Publication Date
WO2008017267A1 true WO2008017267A1 (fr) 2008-02-14

Family

ID=39032644

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/070390 WO2008017267A1 (fr) 2006-07-31 2007-07-31 Procédé, système et dispositif pour traiter un transfert intercellulaire de couche trois

Country Status (2)

Country Link
CN (1) CN101119291A (fr)
WO (1) WO2008017267A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102056236A (zh) * 2009-11-01 2011-05-11 中兴通讯股份有限公司 基于Wimax网络架构实现的通信网络及终端接入方法
CN102170674A (zh) * 2010-02-25 2011-08-31 中兴通讯股份有限公司 实现无固定锚点切换的Wimax系统及其切换方法

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101232698B (zh) * 2007-01-23 2013-04-17 华为技术有限公司 缩短切换时延的方法、系统和终端
US8625421B2 (en) * 2012-02-03 2014-01-07 Telefonaktiebolaget L M Ericsson (Publ) DAD-NS triggered address resolution for DoS attack protection
CN108566639B (zh) * 2018-06-28 2019-07-23 恒宝股份有限公司 一种码号激活方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1543256A (zh) * 2003-04-29 2004-11-03 ���ǵ�����ʽ���� 预先保留新关照地址以实现快速切换的方法
WO2005053187A1 (fr) * 2003-11-26 2005-06-09 Electronics And Telecommunications Research Institute Procede de transfert intercellulaire rapide pour mobile ipv6 base sur un routeur d'acces
CN1705285A (zh) * 2004-05-31 2005-12-07 中国科学院声学研究所 一种基于隧道的移动IPv6快速切换方法
US20060029020A1 (en) * 2004-08-03 2006-02-09 Hee-Young Jung Handover method
CN1809010A (zh) * 2005-01-18 2006-07-26 三星电子株式会社 使用移动节点信息最小化切换时间的方法和设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1543256A (zh) * 2003-04-29 2004-11-03 ���ǵ�����ʽ���� 预先保留新关照地址以实现快速切换的方法
WO2005053187A1 (fr) * 2003-11-26 2005-06-09 Electronics And Telecommunications Research Institute Procede de transfert intercellulaire rapide pour mobile ipv6 base sur un routeur d'acces
CN1705285A (zh) * 2004-05-31 2005-12-07 中国科学院声学研究所 一种基于隧道的移动IPv6快速切换方法
US20060029020A1 (en) * 2004-08-03 2006-02-09 Hee-Young Jung Handover method
CN1809010A (zh) * 2005-01-18 2006-07-26 三星电子株式会社 使用移动节点信息最小化切换时间的方法和设备

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102056236A (zh) * 2009-11-01 2011-05-11 中兴通讯股份有限公司 基于Wimax网络架构实现的通信网络及终端接入方法
CN102056236B (zh) * 2009-11-01 2014-04-30 中兴通讯股份有限公司 基于Wimax网络架构实现的通信网络及终端接入方法
CN102170674A (zh) * 2010-02-25 2011-08-31 中兴通讯股份有限公司 实现无固定锚点切换的Wimax系统及其切换方法
WO2011103753A1 (fr) * 2010-02-25 2011-09-01 中兴通讯股份有限公司 Système wimax réalisant une commutation d'ancrage et son procédé de commutation

Also Published As

Publication number Publication date
CN101119291A (zh) 2008-02-06

Similar Documents

Publication Publication Date Title
JP3923886B2 (ja) 遅延の少ない移動機起動トンネリングハンドオフ
JP4567004B2 (ja) アクセスルータを基盤としたモバイルＩＰｖ６の高速ハンドオーバ方法
KR101375540B1 (ko) 이종망에서 인접 탐색 수행 방법 및 장치
US8224327B2 (en) Method and system for handoff of mobile node in mobile communication system supporting proxy mobile internet protocol
US8570976B2 (en) Method and system for fast handover in hierarchical mobile IPv6
US20120063428A1 (en) Interface Switching System, Mobile Node, Proxy Node, and Mobile Management Node
JP2010532959A (ja) 移動ノード内に実装されたモビリティ機能の検知
US8045522B2 (en) Method and system for performing handoff in wireless networks
JP2009529267A (ja) 移動通信システムでの移動ノード用のデフォルト・ルータの高速構成
WO2009006848A1 (fr) Procédé de commutation de réseau d'accès, dispositif de gestion d'ancrage, et dispositif d'accès mobile
JP2009529265A (ja) 動的ルータ広告を使用する高速ハンドオーバのための方法及びシステム
JP2009530932A (ja) モバイル通信システムにおける高速ハンドオーバ時の移動ノードへのデータのシームレスな伝送
JP2012501129A (ja) ネットワークによって用いられるモビリティマネジメント機能の検出
JPWO2009057296A1 (ja) 移動端末及びネットワークノード並びにパケット転送管理ノード
JP5052675B2 (ja) モバイルノードのプロキシバインディングを制御する方法
US20110255511A1 (en) Handover method and mobile terminal and home agent utilized in said method
WO2008017267A1 (fr) Procédé, système et dispositif pour traiter un transfert intercellulaire de couche trois
US8761119B2 (en) Handover method, and mobile terminal and home agent used in the method
US9148826B2 (en) Handover method and mobile terminal and home agent used in the method
EP2074860B1 (fr) Procédé et système de gestion de l'information de préfixe d'adresse associée au transfert dans les réseaux
KR100915513B1 (ko) 프락시 모바일 ＩＰｖ６에서 패킷 손실을 줄이기 위한 패킷버퍼링 장치 및 방법
JPWO2009054127A1 (ja) 通信システム及び移動端末並びにネットワークノード
KR20090054145A (ko) 네트워크 기반의 고속 핸드오버 수행 방법
Sivagurunathan et al. Experimental comparison of handoff performance of SIGMA and mobile IP
WO2008089671A1 (fr) Procédé, système et terminal pour réduire le temps de transfert

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07785388

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

122 Ep: pct application non-entry in european phase

Ref document number: 07785388

Country of ref document: EP

Kind code of ref document: A1