WO2008017267A1

WO2008017267A1 - Method and system and device for processing layer three handoff

Info

Publication number: WO2008017267A1
Application number: PCT/CN2007/070390
Authority: WO
Inventors: Yong Xie; Wenliang Liang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-07-31
Filing date: 2007-07-31
Publication date: 2008-02-14
Also published as: CN101119291A

Abstract

A method for processing layer three handoff in the technical field of communication system is provided. The method includes the following steps: obtaining the information that a terminal has or will have layer three handoff; notifying the terminal of the layer three handoff. Another method for processing layer three handoff is also provided, which includes the following steps: obtaining the information that a terminal has or will have layer three handoff; assisting the terminal to prepare the layer three handoff. A system and a device for processing layer three handoff are also provided. By the above technical projects, the speed of the layer three handoff process of terminal can be increased.

Description

Layer three switching processing method, system and device

This application claims priority to Chinese Patent Application No. 200610104036.X, filed on July 31, 2006, entitled "Layer 3 Switching Processing Method and System", the entire contents of which are incorporated by reference. In this application.

Technical field

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.

Background technique

In response to the rapidly growing demand for IP (Internet Protocol) addresses due to the rapid development of mobile and broadband technologies, the next generation Internet Protocol, IPv6 (Internet Protocol version 6, Internet Protocol version 6), was proposed. The most essential improvement of IPv6 is to increase the address length of the original IPv4 (Intemet Protocol version 4, Internet Protocol version 4) from 32 bits to 128 bits, resulting in an almost unlimited IP address space. In addition, IPv6 also uses many technologies such as host address stateless autoconfiguration.

Mobile IPv6 (MIPv6) contains three functional entities: mobile node (MN, Mobile Node, or terminal), home agent (HA, Home Agent), and related nodes (CN, Correspondent Node). In the mobility IPv6 access process of the terminal, 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. Thereafter, 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. In addition, MIPv6 also defines a route optimization process, so that the data packets sent by the CN to the MN can be forwarded without HA.

In order to support mobile IPv6 access of the terminal, Internet Engineering Task Force (IETF, Internet)

Engineering Task Force defines RFC 3775 (Request For Comments) and related security specifications RFC for IPv6 mobility. For mobile IPv6, its mobility detection is mainly to detect the mobility of L3 (Layer 3, ie IP layer). In the above RFC specification, 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.

When the mobile node MN detects that the L3 (IP layer) is switched, 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. Please refer to FIG. 1, which 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:

101, L3 switching occurs or needs to occur (imminently) L3 switching, the terminal still does not know;

102. 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;

103. The mobile node performs address conflict detection (DAD, Duplicate Address Detection) on the new care-of address COA;

104. Determine whether the address conflict detection is successful, and (ie, the success, the address does not conflict), that the new care-of address COA address is considered to be available;

105. 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.

For the terminal to confirm that the L3 handover occurs, the above steps 103 and 105 are in no particular order.

During the process of implementing the present invention, the inventor has found that in the handover process of the prior art L3, the process of discovering the L3 handover or completing the handover from the original service node to the target service node is very time consuming, and the L3 cannot be completed in some scenarios. Switching. First, in step 103, the DAD detection of the new care-of address COA is completed by a timeout mechanism. When 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. Secondly, in step 105, the operation of the mobile node MN detecting that the original service node is unreachable is also completed by the timeout mechanism. After performing the above two steps, 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.

In addition, in the wireless network, in order to ensure the quality of service, it is sometimes required that during the handover process, when the new communication parties have not completed communication establishment, the old communication link is not removed, because the original service node is always reachable in this process. State, so step 105 may not be completed all the time, that is, the L3 switch cannot be completed.

Summary of the invention

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.

It can be seen from the above technical solution of the present invention that 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.

It can be seen from the above other technical solutions of the present invention that 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. Process, reduce L3 handover delay and reduce wireless air interface traffic, greatly reduce service interruption time, and greatly improve network performance and service Quality.

DRAWINGS

1 is a flow chart of a prior art layer 3 switching;

2 is a flow chart of a processing method for layer 3 switching of the present invention;

3 is a schematic block diagram of a processing system for layer 3 switching of the present invention;

4 is a schematic structural diagram of a first embodiment of a layer three handover processing device according to the present invention;

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.

detailed description

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. In general, 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. In the technical solution provided by the embodiment of the present invention, 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. In addition, 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. Of course, in other general networks, when 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. In the mobile communication, when the L3 handover is performed, 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.

Embodiments of the present invention will be described in detail below with reference to the embodiments and the accompanying drawings. 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:

Table 1: Extended Control ID in RA Messages

The value of the RCI (Router Configuration Indicator) is as follows:

Table 2: Value of RCI:

Table 3: Definition of the extended Option option

among them:

Type: 9 or other value that does not conflict with the current RFC specification.

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.

Padding: The padding bit is a range of 0 to 63 bits to ensure that the entire Option is an 8-byte integer.

The above IID Option is merely exemplary, and the present invention is not limited to other suitable definitions. In complete, in the present invention, 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:

1. When 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. However, for the general IP situation, if the above conditions are met, 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.

2. 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. Corresponding to the case where the network side in the subsequent embodiment of FIG. 2 does not perform address conflict detection for the terminal. In this case, although 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. Furthermore, compared with the existing operation of detecting the address conflict by the timeout mechanism and the unreachable operation of the original service node, 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. In the case that 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. In the case that the processing method of the layer three handover is applied to the mobile IP, 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). In the case that the IP address of the terminal is stateless, and the RA message does not carry the IID or the IP address, 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.

Please refer to FIG. 2 , which is a flowchart of a method for processing a layer 3 handover according to the present invention. Including the following steps:

201, 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. In 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.

202. 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).

203. 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.

In the embodiment of the present invention, 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:

203a. 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.

203b, 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. As specified in the RFC, 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.

203c, 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.

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;

The following steps are: the network side actively notifies the terminal that a layer 3 switch occurs:

205. 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. In the case that 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. In the case of mobile IP, the IP address on the link is a care-of address, and 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.

As described above, 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.

The following 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.

206a, sending an RA message to the terminal, indicating that an L3 handover occurs and indicating that the terminal currently uses an IID conflict. Therefore, after receiving the terminal, the terminal operates according to the behavior defined by the existing RFC after detecting the DAD conflict. This mode corresponds to the case where the foregoing RCI is the third extended control identifier and does not carry the IID or IP address.

206b, 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. This method is different from step 203. 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.

206c. 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.

In addition, when a terminal that does not support the extended RA message receives an RA message containing the extended control identifier, the extended content is ignored as specified by the RFC. This mode corresponds to the case where the aforementioned RCI is the fourth extended control flag.

207. Initiate a binding update process, complete binding update to the HA, and complete the L3 handover. Specifically, after obtaining the new IP address available above, the terminal initiates a binding update process, completing the binding update to the HA, thereby completing the L3 handover.

It can be seen from the above technical solution that, in the embodiment of the present invention, 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. In the latter case, similar to 206c, 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. In this case, since 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.

As described in the foregoing embodiment, 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.

In some cases of wireless communication, 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. In addition, since 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.

In summary, 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 increase in network performance and quality of service.

The layer 3 or layer 2 message may be used to notify the terminal to perform the layer 3 handover. For example, 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. When the handover, 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. A person skilled in the art can understand that 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. Normally, before the address conflict detection module 311 finds that an IP address is aging and is ready to be deleted, 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.

in particular:

When it is determined that the network side obtains the available IID or IP address, 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. In the case that the IP address of the terminal 320 is stateless, 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. When the processing method of the handover is applied to the mobile IP, 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.

When it is determined that the network side cannot obtain the available IID or IP address, the following one is adopted: 1. 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. In this case, 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. In this case, 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.

Another embodiment of the present invention further discloses a processing device for implementing layer three switching. Referring to 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.

Further, optionally, the processing device may further include an address conflict detection module, configured to perform address conflict detection instead of the terminal. Specifically, please refer to FIG. 5, which 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. For example, 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 IP address used. The detection result (no conflict or conflict) 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.

It should be noted that the address conflict detection module 530 may include only the first address conflict detection module or only the second conflict module. When only the second conflicting module is included, 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.

In addition, 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.

Please refer to FIG. 6, which is a schematic structural diagram of a third embodiment of a layer three handover processing device according to the present invention. As described in the foregoing embodiment, if the address conflict detection is performed instead of the terminal, and the layer 3 handover is not notified to the terminal, the process of the layer 3 handover may be accelerated. Therefore, 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. Specifically, 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. The address conflict detection module 630 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.

It should be noted that the address conflict detection module 630 may include only the third address conflict detection module or only the fourth conflict module. When only the fourth conflicting module is included, 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.

In addition, 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.

It can be seen from the above that 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. Whether the address is available or whether the original service node 320 is reachable, 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.

The foregoing detailed description of a layer three switching processing method and system thereof provided by the present invention is only for helping to understand the method of the present invention and its core idea; and, for a person of ordinary skill in the art, The present invention is not limited by the scope of the present invention.

Claims

Rights request

A processing method for layer 3 switching, comprising:

Obtaining information that the terminal is or will undergo a layer three handover;

Notifying the terminal that a layer three handover occurs.

2. The method according to claim 1, further comprising: after obtaining information that the terminal is or will undergo a layer three handover:

Address conflict detection is performed instead of the terminal.

3. The method according to claim 2, wherein the step of performing address conflict detection by the substitute terminal comprises:

Detecting whether the first IP address used by the terminal on the new link after the layer 3 handover conflicts.

4. The method according to claim 3, wherein if the detection result is non-conflict, the method further comprises:

Notifying the terminal that address conflict detection is not required.

The method according to claim 2, wherein the step of performing address conflict detection by the substitute terminal comprises:

Assigning, to the terminal, a second IP address that does not conflict;

Notifying the terminal of the interface identifier corresponding to the second IP address or the second IP address, and notifying the terminal that address conflict detection is not required.

6. A method according to any one of claims 1 to 5, characterized in that

The obtaining information that the terminal is performing or about to perform the layer three handover specifically includes: obtaining, by the network side, information that the terminal is currently occurring or is about to undergo a layer three handover;

The informing the terminal to generate the layer 3 handover specifically includes: the network side notifying the terminal to perform a layer three handover.

The method according to claim 3 or 4, wherein the first IP address is an IP address generated by an interface identifier currently used by the terminal and prefix information of the target serving node, or the terminal is in the original link. The IP address used.

The method according to claim 3 or 4, wherein the detecting whether the first address conflicts comprises:

Detecting whether the first IP address conflicts according to the recorded IP address list or interface identifier list of all terminals configured; or

Detecting whether the first IP address conflicts according to the IP address list of all terminals currently used on the current link saved in the neighbor list information;

Or

The address conflict detection message is sent directly to the first IP address to be used by the terminal to detect whether the first IP address conflicts.

The method according to any one of claims 1 to 5, wherein the notifying the terminal to perform the layer 3 handover specifically includes:

The network side notifies the terminal to perform a layer three handover by sending a layer three message or a layer two message.

A processing method for layer 3 switching, comprising: obtaining information that a terminal is currently occurring or is about to undergo a layer three handover;

Assist the terminal to prepare for Layer 3 switching.

The processing method according to claim 10, wherein the assisting the terminal to prepare the layer 3 handover comprises: performing address conflict detection instead of the terminal.

The method according to claim 11, wherein the step of performing address conflict detection by the substitute terminal specifically includes:

It is detected whether the first IP address used by the terminal on the new link after the layer 3 switching is conflicted.

The method according to claim 12, wherein, if the detection result is not conflicting, the method further comprises: notifying the terminal that address conflict detection is not required.

The method according to claim 11, wherein the performing the address conflict detection by the substitute terminal comprises:

Assigning, to the terminal, a second IP address that does not conflict;

The method according to any one of claims 10 to 14, further comprising: after obtaining information that the terminal is or will undergo a layer three handover:

Notifying the terminal that a layer three handover occurs.

16. A method according to any one of claims 10 to 14, characterized in that The obtaining information that the terminal is performing or is about to undergo a layer three handover specifically includes: obtaining, by the network side, information that the terminal is occurring or is about to undergo a layer three handover;

The assisting the terminal to prepare the layer 3 handover specifically includes: the network side assisting the terminal to prepare the layer three handover.

A layer-three-switching processing system, including a network side, further comprising: a layer three handover notification module disposed on the network side, configured to obtain information about that the terminal is or will undergo a layer three handover, and notify the The terminal generates a layer three handover.

The system according to claim 17, wherein the network side includes a target service node, and further includes an address conflict detection module, which determines that the interface identifier of the terminal is available or does not conflict with the terminal by using address conflict detection. IP address.

19. A layer three switching processing device, comprising:

The information obtaining module is configured to obtain information that the layer is being or is about to undergo a layer three handover, and the layer three switching notification module is configured to notify the terminal that a layer three handover occurs.

The device according to claim 19, further comprising:

An address conflict detection module is configured to perform address conflict detection instead of the terminal.

The device according to claim 20, wherein the address conflict detection module is specifically:

The first address conflict detection module is configured to perform address conflict detection on the first IP address used by the terminal on the new link after the layer 3 switchover.

The device according to claim 21, wherein the detection result of the first address conflict detection module is notified to the terminal by the layer three handover notification module.

a second address conflict detection module, configured to allocate a second IP address that does not conflict with the terminal, and notify the interface identifier corresponding to the second IP address or the second IP address by using the layer three handover notification module terminal.

The device according to any one of claims 19 to 23, wherein the processing device of the layer three switching is specifically a target service node.

25. A layer three switching processing device, comprising:

An information obtaining module, configured to obtain information that a terminal is performing or is about to undergo a layer three handover; An address conflict detection module is configured to perform address conflict detection instead of the terminal.

The device according to claim 25, wherein the address conflict detection module is specifically:

The third address conflict detection module is configured to perform address conflict detection on the first IP address used by the terminal on the new link after the layer 3 switchover, and notify the terminal of the detection result.

The fourth address conflict detection module is configured to allocate a second IP address that does not conflict to the terminal, and notify the terminal of the interface identifier corresponding to the second IP address or the second IP address.