WO2008009230A1 - Procédé et système de traitement du déplacement de l'interface r3 dans un réseau d'interopérabilité mondiale pour l'accès micro-ondes - Google Patents

Procédé et système de traitement du déplacement de l'interface r3 dans un réseau d'interopérabilité mondiale pour l'accès micro-ondes Download PDF

Info

Publication number
WO2008009230A1
WO2008009230A1 PCT/CN2007/070262 CN2007070262W WO2008009230A1 WO 2008009230 A1 WO2008009230 A1 WO 2008009230A1 CN 2007070262 W CN2007070262 W CN 2007070262W WO 2008009230 A1 WO2008009230 A1 WO 2008009230A1
Authority
WO
WIPO (PCT)
Prior art keywords
interface
migration
service network
asn
target
Prior art date
Application number
PCT/CN2007/070262
Other languages
English (en)
Chinese (zh)
Inventor
Yong Xie
Jianjun Wu
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 WO2008009230A1 publication Critical patent/WO2008009230A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/24—Interfaces between hierarchically similar devices between backbone network devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface
    • H04W36/142—Reselecting a network or an air interface over the same radio air interface technology
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access

Definitions

  • the present invention relates to the field of mobile communications, and in particular to a Worldwide Interoperability for Microwave Access (WiMAX) technology. Background technique
  • Wireless broadband access technology is a high-speed wireless access service that enterprises can use to build a metropolitan area network or obtain Internet access. These wireless services replace traditional Time Division Multiplexing (“TDM”) line services.
  • TDM Time Division Multiplexing
  • the wireless access system is usually owned by a service provider operating in the metropolitan area.
  • the service includes the enterprise, the Maximum Transmission Unit (MTU,), the home, and the local area network (Local Area Network). "LAN”) Bridged Internet access.
  • MTU Maximum Transmission Unit
  • LAN Local Area Network
  • IEEE 802.16 is a wireless interface standard for wireless metropolitan area networks (WMAN), including air interface standards for fixed wireless access, and involves a Microwave Multipoint Distribution System (MMDS). , Local Multipoint Distribution System/Service (“LMDS").
  • WMAN wireless metropolitan area networks
  • MMDS Microwave Multipoint Distribution System
  • LMDS Local Multipoint Distribution System/Service
  • IEEE 802.16 defines different physical layer technologies for different frequency bands.
  • the standard application range is mainly for residential, small office/home office (SOHO), teleworkers, and Short Message Entity (“SME”) markets.
  • SOHO small office/home office
  • SME Short Message Entity
  • WiMAX Worldwide Interoperability for Microwave Access
  • WiMAX aims to promote the global promotion and application of IEEE 802.16 (IEEE 802.16, IEEE 802.16d, IEEE 802.16e) air interface protocols.
  • WiMAX referred to herein refers to a network entity that satisfies the IEEE 802.16 air interface protocol.
  • WiMAX is committed to helping and addressing issues that prevent standards from being used, such as interoperability and product cost issues between products from different vendors.
  • WiMAX will develop a set of interoperability test specifications, use this set of specifications to test and certify products from relevant manufacturers, and issue WiMAX certification marks to those certified products, thereby encouraging all manufacturers of wireless broadband access related industries. Following a unified specification, each product has good interoperability and hopes to promote the development of the wireless broadband access industry.
  • WiMAX mainly includes a mobile station (Mobile Subscribe Station, referred to as "MSS”) / Subscriber Station ("Snack Station”), an Access Service Network ("ASN”), and a connection service network. (Connected Service Network, referred to as "CSN").
  • MSS Mobile Subscribe Station
  • ASN Access Service Network
  • CSN Connection Service Network
  • the ASN is defined as a network function set that provides wireless access services for WiMAX terminals.
  • the ASN includes a Base Station (“BS”) and an Access Service Network GateWay (“SNN-GW”) network element.
  • An ASN may be shared by multiple CSNs.
  • the main functions of the ASN include the functions of the BS and the functions of the ASN-GW.
  • the functions of the BS are: providing L2 connection of BS and MSS/SS, radio resource management, measurement and power control, and compression and encryption of air interface data.
  • the functions of ASN-GW include: providing proxy function for SS/MSS authentication, authorization and charging functions; supporting network discovery and selection of network service provider (NetWork Service Procider, "NSP"); providing L3 for SS Relay function of information (such as IP address allocation).
  • NSP NetworkWork Service Procider
  • the reference model of ASN is shown in Figure 2.
  • the BSs are connected through the R8 interface, and the definition of the R8 interface is still under discussion.
  • the BS and the ASN-GW gateway communicate via the R6 interface, and one BS can be connected to one or more ASN-GWs.
  • the ASN is connected to the CSN through the R3 interface through the ASN-GW gateway, and is connected to other ASNs through the R4 interface.
  • the R3 interface includes a protocol stack of the control plane and the bearer plane to meet the interconnection requirements between the ASN and the CSN.
  • the bearer plane is composed of a network protocol (Internet Protocol, referred to as ' ⁇ ') between the ASN and the CSN.
  • the control plane includes control protocols such as IP tunnel establishment and tunnel release due to terminal movement.
  • the control plane is also Including protocols such as Authentication, Authorization, Account (“AAA”), policies, and QoS enforcement.
  • the R4 interface mainly defines the control plane and bearer plane protocols related to mobility between ASNs.
  • Connection Service Network CSN provides IP connection services for WiMAX terminals.
  • the CSN mainly provides the following functions: IP address allocation of SS/MS S, Internet access, AAA proxy or server, user-based authorization control, ASN to CSN tunnel, WiMAX user billing, and inter-operator settlement and roaming.
  • IP address allocation of SS/MS S Internet access
  • AAA proxy or server user-based authorization control
  • ASN to CSN tunnel WiMAX user billing
  • inter-operator settlement and roaming In the case of tunneling between CSNs, switching between ASNs, and various WiMAX services (such as location-based services, multimedia multicast and broadcast services, IP Multimedia Subsystem services).
  • the MSS/SS is a (mobile) user equipment that the user uses to access the WiMAX network.
  • the R3 interface may need to be migrated to ensure the correct transmission of user data.
  • the migration process of the R3 interface is shown in Figure 3. Before the migration, the BS and the ASN of the current service and the Foreign Agent (FA) of the service are retained. Context information of the R3 interface.
  • the ASN When the R3 interface needs to be migrated, the ASN sends an R3 migration request to the authenticator and the mobile IP client, and then the authenticator and the mobile IP client send the mobile IP registration to the target ASN-GW and the target FA. Request message, the target ASN-GW and the target FA forward the request message to the home agent (Home Agent, referred to as ' ⁇ ") of the MSS, through the transit of the target ASN-GW and the target FA, the authenticator and the mobile IP client.
  • Home Agent Home Agent
  • the ASN that initiates the R3 interface migration request After the response message of the mobile IP registration request from the HA, the ASN that initiates the R3 interface migration request returns a response message of the R3 interface migration, and the BS establishes new context information of the R3 interface with the target ASN_GW and the target FA, and the R3 The old context information of the interface will be deleted.
  • the migration process of the R3 interface is as shown in FIG. 4, and the process is substantially the same as that of FIG. 3, except that the migration of the R3 interface of the MSS of the proxy mobile IP is implemented by the proxy.
  • the migration of the R3 interface of the MSS of the client mobile IP is initiated by the MSS itself.
  • the migration of the R3 interface may affect the service quality of the MSS. This is because in the prior art, the migration of the R3 interface is a separate process performed after the MSS performs the handover. In addition, after the MSS performs the handover, if the R3 interface needs to be migrated, the data channel for the information interaction during the migration needs to be established, and then the R3 migration process is performed, which greatly increases the total handover delay of the MSS. Therefore, May affect the performance of MSS during handover/migration. Summary of the invention
  • the present invention provides a migration processing method and system for an R3 interface in a microwave access global interworking network, so that the total handover delay of the MS is reduced.
  • the present invention provides a migration processing method for an R3 interface in a microwave access global interworking network, which includes the following steps:
  • the information of the original access service network side R3 interface migration is sent to the target access service network.
  • the present invention also provides a migration processing system for an R3 interface, including at least one mobile station, at least two access service networks, a connection service network, and at least two anchor networks, and the anchor network further includes:
  • a decision module for determining whether to perform an R3 interface migration between the access service network and the connected service network
  • An obtaining module configured to obtain context information
  • the decision module determines whether the R3 interface of the mobile station needs to be migrated, and if the decision module decides to migrate the R3 interface, indicating that the acquiring module in the target anchoring network is from the original
  • the anchor network acquires context information required for the migration, and migrates the R3 interface according to the acquired context information.
  • the technical solution provided in the embodiment of the present invention determines whether the R3 interface between the ASN and the CSN needs to be migrated in the anchor network of the MSS in the handover phase of the MSS, if it is decided to the R3 The interface is migrated, and the target anchor network obtains the context information required for the R3 interface migration from the original anchor network, and the R3 interface is migrated to the local. Since the decision timing of whether the R3 interface needs to be migrated is placed in the handover phase of the MSS, the interaction signaling in the handover process can be used to carry the context information required for the R3 interface migration without separately establishing the migration of the R3 interface. Perform message interaction, so that the air interface switching process and R3 connection The port migration process is more closely combined, reducing the interaction of information and shortening the switching delay.
  • the network side can flexibly set the decision timing of whether to perform R3 interface migration, and decide whether to migrate the R3 interface when receiving the handover request. If the migration is decided, the required context information is carried in the handover request message and sent to the target anchor. ASN and FA in the network, or ASN and AR; or, if a handover confirmation message is received, the R3 interface is migrated. If the migration is decided, the required context information is carried in the handover confirmation message and sent to the target anchor. ASN and FA in the network, or ASN and AR. In addition, the ASN and the FA in the target anchoring network, or the ASN and the AR, may carry the indication information of the R3 interface migration in the returned handover response message when receiving the handover request message.
  • the present invention also provides a method for transmitting information migrated from the R3 interface to the target access service network from the original anchor network side, that is, when the terminal switches between the two ASN networks. After the information about the migration of the R3 interface is delivered to the target access service network, the target access service network can perform the migration process of the R3 interface as required.
  • FIG. 1 is a schematic diagram of an end-to-end reference model of WiMAX in the prior art
  • FIG. 2 is a schematic diagram of a reference model of an ASN in the prior art
  • FIG. 3 is a flow chart of R3 interface migration of the MSS of the proxy mobile IP in the prior art
  • FIG. 4 is a flow chart of R3 interface migration of the MSS of the client mobile IP in the prior art
  • FIG. 5 is a flowchart of the R3 interface migration of the MSS of the client mobile IP in the prior art
  • Flowchart of the migration processing method of the R3 interface in the WiMAX system
  • FIG. 6 is a flowchart of a migration processing method of an R3 interface in a WiMAX system according to a second embodiment of the present invention.
  • FIG. 7 is a flowchart of a migration processing method of an R3 interface in a WiMAX system according to a third embodiment of the present invention.
  • FIG. 8 is a flowchart of a migration processing method of an R3 interface in a WiMAX system according to a fourth embodiment of the present invention. detailed description
  • the original access service network refers to the network that the MSS provides services before the handover. It includes the original service access service network (Serving ASN) and the original anchor service network (Anchor ASN).
  • the access service network (Serving ASN) of the original service refers to the access service network directly connected to the BS that is serving the MS; the original anchor service network (Anchor ASN) refers to the connection with the connection service network (CSN).
  • CSN connection service network
  • R3 interface The Serving ASN and the Anchor ASN can be separate, they are connected by an R4 interface; they can also be an entity.
  • the target access service network refers to the access service network (Target ASN) directly connected to the BS to which the MSS is to be switched.este If the R3 migration is to be performed, the target access service network is the target anchor service network.
  • the network side determines whether the R3 interface of the MSS needs to be migrated in the handover phase of the MSS, and if yes, uses the interaction signaling in the handover process to anchor the target in the network.
  • the ASN and the FA, or the ASN and the AR obtain the context information required for the R3 interface migration, and perform the migration of the R3 interface according to the context information, thereby reducing the total handover delay of the MSS and improving the user experience.
  • the migration process of the R3 interface in the WiMAX system is as follows:
  • step 501 the MSS sends a handover request to the serving ASN. Specifically, when the MSS meets the handover condition, sending a handover request message to the serving ASN triggers the handover procedure.
  • Step 502 The serving ASN sends a handover request to the ASN and the FA, or the ASN and the AR in the original anchor network. Specifically, the switching function entity of the serving ASN processes the handover request sent by the MSS, and sends a handover request message to the ASN and the FA, or the ASN and the AR in the original anchor network, where the message carries the decision made by the service ASN.
  • Target BS situation the serving ASN sends a handover request to the ASN and the FA, or the ASN and the AR in the original anchor network.
  • Step 503 the original anchor network ASN and FA, or ASN and AR, whether the decision needs The R3 interface is migrated, and when the migration is decided, the context information required for the R3 interface migration is carried in the handover request message sent to the ASN and the FA, or the ASN and the AR in the target anchor network.
  • the target BS that satisfies the QoS requirement can be further determined, and the ASN and the FA in the original anchor network are also anchored. , or ASN and AR, according to the current resource status, the QoS requirements of the service, etc., whether to need to migrate the R3 interface between the ASN and the CSN to the MSS that is currently requesting handover, that is, to migrate the R3 interface to the new FA.
  • Carrying the context information required for the R3 interface migration requires the target ASN to migrate the R3 interface when the MSS switches to the local ASN or after the handover is complete.
  • the contexts required for the R3 interface migration carried by the ASN and FA, or ASN and AR in the original anchor network, in the handover request message sent to the ASN and FA, or ASN and AR in the target anchor network.
  • the ASN and the FA in the original anchor network, or the ASN and the AR decide whether to migrate the R3 interface when receiving the handover request, and if the migration is decided, use the ASN in the handover process to be sent to the target anchor network.
  • the switching request of the FA, or the ASN and the AR carries the context information required for the R3 interface migration, so that the air interface switching process and the R3 interface migration process are more closely combined, thereby reducing information interaction, thereby reducing handover time. Delay.
  • Step 504 The ASN and the FA in the target anchor network, or the ASN and the AR, return a handover response message to the ASN and the FA, or the ASN and the AR in the original anchor network, and carry whether to accept the R3 interface in the response message. Reply to the migration.
  • the ASN and the FA in the target anchor network, or the switching function entity of the ASN and the AR receive the handover request message sent by the ASN and the FA, or the ASN and the AR in the original anchor network, and process the handover request. And confirm whether the migration of the R3 interface is acceptable.
  • Step 505 The ASN and the FA in the original anchor network, or the ASN and the AR, after receiving the handover response message from the ASN and the FA, or the ASN and the AR in the target anchor network, confirm that the target FA receives the R3. The interface is migrated and a handover response message is sent to the serving ASN.
  • Step 506 The serving ASN returns a handover response to the MSS that initiates the handover process, indicating that the MSS can start the handover.
  • step 507 the MSS sends a handover indication to the serving ASN after determining the handover.
  • Step 508 After receiving the handover indication message from the MSS, the serving ASN notifies the ASN and the FA, or the ASN and the AR in the original anchor network, by using a handover confirmation message.
  • the handover confirmation message is notified to the ASN and FA, or ASN and AR in the target anchor network, by the ASN and FA, or ASN and AR in the original anchor network.
  • Step 506 to step 509 complete the existing air interface switching process.
  • Step 510 or 510' the target ASN or the target FA performs the migration process of the R3 interface according to the obtained context information required for the R3 interface migration.
  • the MSS depending on the type of mobile IP of the MSS, it can be divided into two cases.
  • the target ASN or the target FA sends a notification message to the MSS requesting the MSS to initiate the R3 interface migration process, "Mobility Advertisement".
  • the migration process thereafter is the same as the prior art, and the R3 interface is migrated to the new FA. Since the MSS has confirmed that the MSS has confirmed to switch to the local BS when the target anchors the ASN and the FA in the network, or the ASN and the AR, the MSS is requested to send the request to the MSS.
  • the process of initiating the R3 interface migration enables the process of re-entering the MSS to the target cell and the R3 migration process to be performed in parallel, which reduces the handover delay, thereby improving the service quality of the service at the time of handover.
  • the ASN and the FA in the target anchoring network, or the ASN and the AR may also send a message requesting the MSS to initiate the R3 interface migration after the R6 data channel between the target ASN_GW and the target BS is successfully established. This is because if the R6 data channel is successfully established, it indicates that the MSS has successfully re-entered the target cell. If the establishment of the R6 data channel is successful before receiving the handover confirmation message, the "Mobility Advertisement" message can be directly sent without waiting for the handover confirmation message.
  • the R3 interface migration request message is sent to the proxy mobile IP client entity of the MSS, and the R3 interface migration is required.
  • the migration process is the same as the prior art, and the R3 interface is migrated to the new FA.
  • the ASN and FA, or ASN and AR in the target anchor network may also send the R3 interface to the proxy mobile IP client entity of the MSS after the R6 data channel between the target ASN_GW and the target BS is successfully established.
  • the migration request message if the R6 data channel is successfully established before receiving the handover confirmation message, can directly send the R3 interface migration request message without waiting for the handover confirmation message.
  • this embodiment is also fully applicable to the service ASN and the ASN and FA in the original anchor network, or ASN and AR.
  • the service ASN and the ASN in the original anchor network are only reduced.
  • the interaction with FA, or ASN and AR does not affect the process of making decisions and executions for R3 interface migration.
  • Step 601 and step 602 are the same as steps 501 and 502, respectively.
  • step 603 the ASN and the FA, or the ASN and the AR in the original anchor network, send a handover request to the ASN and the FA, or the ASN and the AR in the target anchor network, and in this step, the original anchor network
  • the ASN and the FA, or the ASN and the AR do not make decisions about whether the R3 interface needs to be migrated, and do not carry the R3 interface migration in the handover request message sent by the ASN and the FA, or the ASN and the AR in the target anchoring network.
  • the required context information is not be used to make decisions about whether the R3 interface needs to be migrated, and do not carry the R3 interface migration in the handover request message sent by the ASN and the FA, or the ASN and the AR in the target anchoring network.
  • step 604 the target anchors the ASN and FA in the network, or the ASN and AR, to return the handover response to the ASN and FA, or ASN and AR in the original anchor network, and this step is the same as the prior art.
  • Step 605 to step 608 are completely the same as steps 505 to 508, and details are not described herein again.
  • step 609 the ASN and the FA in the original anchor network, or the ASN and the AR, decide whether the migration of the R3 interface is required, and when the migration is decided, the network is anchored to the target.
  • the switch confirmation message sent by the ASN and the FA, or the ASN and the AR, carries the context information required for the R3 interface to migrate.
  • the ASN and the FA in the original anchor network, or the ASN and the AR determine whether it is necessary to perform the MSS for the current request handover according to the current resource status, the QoS requirements of the service, and the like.
  • the migration of the R3 interface between the ASN and the CSN that is, the migration of the R3 interface to the new FA. If it is determined that the R3 interface needs to be migrated, the ASN and FA, or ASN and AR in the original anchor network are sent to the handover confirmation message of the ASN and FA, or ASN and AR in the target anchor network.
  • the context information required for the R3 interface migration is carried out, and the target ASN is required to perform the migration of the R3 interface after the MSS switches to the local ASN or the handover is completed.
  • the context required for the R3 interface migration carried by the ASN and FA, or ASN and AR in the original anchor network, in the handover confirmation message sent to the ASN and FA, or ASN and AR in the target anchor network.
  • the information includes: “Anchor DPF Info”, “Anchor SFA Info”, “Anchor DHCP proxy/relay Info”, “Accounting Info”, “Authentication Info”, "MIP Info”, “Idle Info” and so on.
  • Step 610 or step 610', step 610 and step 610' are respectively associated with step 510 and step 510', and details are not described herein.
  • the present embodiment is substantially the same as the first embodiment except that in the first embodiment, the ASN and the FA, or the ASN and the AR in the original anchor network, perform R3 when receiving the handover request.
  • the required context information is carried in the handover request message and sent to the ASN and FA in the target anchor network, or ASN and AR, and in the embodiment, the original anchor
  • the ASN and the FA in the network, or the ASN and the AR decide whether to migrate the R3 interface when receiving the handover confirmation message. If the migration is decided, the required context information is carried in the handover confirmation message and sent to the target anchor.
  • ASN and FA in the network, or ASN and AR decide whether to migrate the R3 interface when receiving the handover confirmation message.
  • the migration processing method of the R3 interface in the WiMAX system is as shown in FIG. 7, and the steps 701 and 702 are the same as the steps 501 and 502, respectively.
  • the ASN and the FA, or the ASN and the AR in the original anchor network send a handover request message to the ASN and the FA, or the ASN and the AR in the target anchor network, and in this step, the original anchor network
  • the ASN and FA, or ASN and AR do not make decisions or make decisions on whether the R3 interface needs to be migrated, but the decision is not to migrate the R3 interface, anchor the ASN and FA, or ASN and AR in the network to the target.
  • the sent handover request message does not carry any context information required for R3 interface migration.
  • Step 704 The ASN and the FA in the target anchoring network, or the ASN and the AR, determine whether it is necessary to perform the migration of the R3 interface between the ASN and the CSN for the MSS currently requesting handover according to the current status of the resource, the QoS requirement of the service, and the like. That is, the R3 interface is migrated to the FA. If it is determined that the R3 interface needs to be migrated, the ASN and the FA in the target anchor network, or the ASN and the AR, are sent in the handover response message to the ASN and FA, or ASN and AR in the original anchor network. And carrying the indication information for performing the R3 interface migration, and carrying the indication information, according to the context information of the MSS that it has, indicating the context information that the original anchor ASN needs to provide in the subsequent process to complete the migration of the R3 interface.
  • Steps 705 to 708 are the same as steps 505 to 508, respectively, and are not described herein again.
  • step 709 because the ASN and the FA in the original anchor network, or the ASN and the AR, according to the indication information carried in the received handover response message, it is learned that the R3 interface needs to be migrated. Therefore, in this step, The ASN and the FA in the original anchor network, or the ASN and the AR, carry the information that agrees to perform the R3 interface migration in the handover confirmation message sent to the ASN and the FA, or the ASN and the AR in the target anchor network. Contains the context information needed to perform the R3 interface migration.
  • Step 710 Proactively send a request message to the ASN and the FA, or the ASN and the AR in the original anchor network, to obtain the context information required for the R3 interface migration.
  • Step 711 The ASN and the FA, or the ASN and the AR in the original anchor network, after receiving the request message, return the context information to the ASN and the FA, or the ASN and the AR in the target anchor network. It should be noted that if the target anchors the ASN and the FA in the network, or the ASN and the AR, and has received the handover confirmation message before the R6 data channel is successfully established, step 710 and step 711 are skipped.
  • Step 712 and step 712' are the same as step 510 or 510', respectively, and are not described herein again. It is not difficult to find that the present embodiment is substantially the same as the first embodiment except that in the first embodiment, the ASN and the FA, or the ASN and the AR in the original anchor network, perform R3 when receiving the handover request. Whether the interface is migrated, if the migration is decided, the required context information is carried in the handover request message and sent to the ASN and FA in the target anchor network, or ASN and AR; In this embodiment, the ASN and the FA in the target anchor network, or the ASN and the AR, decide whether to migrate the R3 interface when receiving the handover request message, and if the migration is decided, in the returned handover response message.
  • the indication information carrying the R3 interface migration is carried in the handover confirmation message sent by the ASN and the FA in the original anchor network, or the ASN and the AR, in the ASN and the FA, or the ASN and the AR in the target anchor network.
  • the required context information is carried in the handover confirmation message sent by the ASN and the FA in the original anchor network, or the ASN and the AR, in the ASN and the FA, or the ASN and the AR in the target anchor network.
  • the migration processing method of the R3 interface in the WiMAX system is substantially the same as that of the third embodiment, except that the handover request message is sent directly to the target anchor by the service ASN without passing through the ASN and FA in the original anchor network, or ASN and AR.
  • ASN and FA, or ASN and AR in the network Therefore, the ASN and the FA in the target anchoring network, or the ASN and the AR, directly transmit the indication information of the R3 interface migration carried in the handover response message to the serving ASN.
  • step 801 when the MSS meets the handover condition, the MSS sends a handover request message to the serving ASN to trigger the handover process.
  • Step 802 The serving ASN sends a handover request message directly to the ASN and the FA in the target anchor network, or the ASN and the AR. Since the handover request message does not pass through the ASN and the FA in the original anchor network, or the ASN and the AR, the ASN and the FA in the original anchor network, or the ASN and the AR, cannot determine whether the R3 interface needs to be migrated.
  • Step 803 The ASN and the FA in the target anchoring network, or the ASN and the AR, determine whether the R3 interface needs to be migrated, and if the migration is decided, the handover response message returned to the serving ASN carries the indication information for performing the R3 interface migration. Indicates that the R3 interface needs to be migrated. At the same time, according to the context information of the MSS that it owns, the indication information is used to indicate which context information the original anchor ASN needs to provide in the subsequent process to complete the migration of the R3 interface.
  • Step 804 and step 805 correspond to step 706 to step 707, respectively.
  • the serving ASN carries the context information related to the R3 interface migration in the ASN in the handover confirmation message sent to the ASN and the FA, or the ASN and the AR in the target anchor network. Since the handover confirmation message is directly sent by the serving ASN to the ASN and FA in the target anchor network, or ASN and AR, does not pass the ASN and FA in the original anchor network, or ASN and AR, so the handover confirmation message may Unable to carry the required R3 interface migration All information, but can carry the context information required by the service ASN for the R3 interface migration.
  • step 807 the ASN and the FA in the target anchor network, or the ASN and the AR, actively to the ASN and the FA in the original anchor network, or the ASN and the AR.
  • Sending a request message requesting to obtain the complete context information required for the R3 interface migration, and in step 808, the ASN and the FA, or the ASN and the AR in the original anchor network, after receiving the request message, the context is The information is returned to the ASN and FA in the target anchor network, or ASN and AR.
  • step 807 and step 808 are skipped.
  • the target anchors the ASN and the FA in the network, or the ASN and the AR after the R6 data channel between the target ASN_GW and the target BS is successfully established, that is, when the MSS has successfully re-entered the target cell, , has not received the handover confirmation message, still need to go to step 807 and step 808, from the ASN and FA, or ASN and AR in the target anchor network, to the ASN and FA, or ASN and AR in the original anchor network.
  • Complete context information required for R3 interface migration is required for R3 interface migration.
  • Step 809 and step 809', step 809 and step 809' are the same as step 510 or 510', respectively, and are not described herein again.
  • a migration system for an R3 interface in a WiMAX network comprising at least one MSS, at least two ASNs, a CSN, and at least two anchor networks.
  • the anchoring network further includes a decision module for determining an R3 interface migration between the ASN and the CSN, and an obtaining module for acquiring the context information.
  • the decision module in the original anchor network or the target anchor network determines whether the R3 interface of the MSS needs to be migrated. If the decision module decides to migrate the R3 interface, The acquisition module in the target anchor network is configured to obtain the context information required for the migration of the R3 interface from the original anchor network, and perform the migration of the R3 interface according to the acquired context information. Since the decision timing of whether the R3 interface needs to be migrated is placed in the handover phase of the MSS, the interaction signaling in the handover process can be utilized to carry the context information required for the R3 interface migration.
  • the target anchor For the MSS whose mobile IP type is Proxy Mobile IP, the target anchors the ASN and FA in the network, or ASN and AR, and moves the IP to the proxy when receiving the handover confirmation message.
  • the client sends a migration request of the R3 interface.
  • the ASN and the FA in the target anchor network, or the ASN and the AR send a request to the MSS when receiving the handover confirmation message.
  • the message that initiates the migration of the R3 interface reduces the interaction of information, thereby reducing the handover delay.
  • modules or steps in the foregoing embodiments may be implemented by a program to instruct related hardware, and the program may be stored in a computer readable storage medium, such as a storage medium, such as ROM/RAM, disk, CD, etc. Alternatively, they may be fabricated into individual integrated circuit modules, or a plurality of modules or steps may be fabricated into a single integrated circuit module. Thus, the invention is not limited to any particular combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Cette invention concerne un procédé et un système de traitement du déplacement de l'interface R3 dans l'Internet d'interopérabilité mondiale pour l'accès micro-ondes permettant de réduire le délai de transfert total d'une station mobile (MS). Selon cette invention, lorsqu'un terminal est transféré d'un réseau de service d'accès à un autre, soit le côté réseau d'ancrage source envoie des informations relatives au déplacement de l'interface R3 au réseau de service d'accès cible, soit le réseau de service cible obtient directement les informations relatives au déplacement de l'interface R3 du côté réseau d'ancrage. Cette invention concerne également un système de traitement du déplacement de l'interface R3. Cette invention utilise l'interconnexion des informations dans le flux de transfert pour obtenir des informations de contexte requises pour le déplacement de l'interface R3. Il n'est donc pas nécessaire d'interconnecter uniquement le message pour le déplacement de l'interface R3.
PCT/CN2007/070262 2006-07-11 2007-07-10 Procédé et système de traitement du déplacement de l'interface r3 dans un réseau d'interopérabilité mondiale pour l'accès micro-ondes WO2008009230A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNA200610106530XA CN101106491A (zh) 2006-07-11 2006-07-11 微波接入全球互通网络中r3接口的迁移方法及其系统
CN200610106530.X 2006-07-11

Publications (1)

Publication Number Publication Date
WO2008009230A1 true WO2008009230A1 (fr) 2008-01-24

Family

ID=38956548

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/070262 WO2008009230A1 (fr) 2006-07-11 2007-07-10 Procédé et système de traitement du déplacement de l'interface r3 dans un réseau d'interopérabilité mondiale pour l'accès micro-ondes

Country Status (2)

Country Link
CN (1) CN101106491A (fr)
WO (1) WO2008009230A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101651593A (zh) * 2008-08-11 2010-02-17 华为技术有限公司 一种辅助移动接入网关迁移的方法与装置
CN101656944B (zh) * 2008-08-19 2012-10-17 华为技术有限公司 一种锚定数据通路功能实体迁移的方法与装置
CN102147752A (zh) * 2010-02-09 2011-08-10 深圳市金蝶中间件有限公司 一种处理事件的方法及装置
CN102365845B (zh) * 2010-04-23 2014-12-03 华为技术有限公司 本地路由实现方法及系统、网络设备
WO2011130920A1 (fr) * 2010-04-23 2011-10-27 华为技术有限公司 Procédé, système et dispositifs de réseau destiné à réaliser un routage local
CN105763661B (zh) * 2014-12-17 2019-02-01 华为技术有限公司 一种网络协议ip地址的获取方法及通信设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1794869A (zh) * 2005-07-09 2006-06-28 华为技术有限公司 一种基于资源优化实现r3接口迁移的方法及系统
CN1794870A (zh) * 2005-07-11 2006-06-28 华为技术有限公司 一种建立接口链路的方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1794869A (zh) * 2005-07-09 2006-06-28 华为技术有限公司 一种基于资源优化实现r3接口迁移的方法及系统
CN1794870A (zh) * 2005-07-11 2006-06-28 华为技术有限公司 一种建立接口链路的方法

Also Published As

Publication number Publication date
CN101106491A (zh) 2008-01-16

Similar Documents

Publication Publication Date Title
US7882266B2 (en) Method and system for negotiating interface data path establishment
US8780856B2 (en) Inter-system handoffs in multi-access environments
US10206152B2 (en) Attachment, handover, and traffic offloading between 3GPP RANS and Wi-Fi RANS
JP5421411B2 (ja) サービスノード
US20210281981A1 (en) Communications Method, Apparatus and System
KR20050089627A (ko) 이동통신의 핸드오버에 적용되는 서비스 정보 전달 방법
KR20100085146A (ko) 다중―모드 모바일 유닛들에 대한 무선 베어러 및 ｍｉｐ 세션 연속성을 유지하기 위한 최선형 핸드오프의 방법
US20230224770A1 (en) Communication method and apparatus
WO2008009230A1 (fr) Procédé et système de traitement du déplacement de l'interface r3 dans un réseau d'interopérabilité mondiale pour l'accès micro-ondes
WO2012152130A1 (fr) Procédé et dispositif de traitement de support
WO2007006224A1 (fr) Procédé et système destinés à réaliser la translation de l’interface r3
WO2011023125A1 (fr) Procédé, dispositif et système pour libération de connexion
WO2009043284A1 (fr) Procédé, entité de réseau et terminal pour le transfert entre réseaux sans fil hétérogènes
WO2007071112A1 (fr) Procede de maintien de transmission de flux de paquets de donnees lors du deplacement d'un terminal mobile dans un reseau d'acces sans fil
WO2011157100A1 (fr) Procédé et système de mise en cache de données
KR101037464B1 (ko) Ａｓｎ간 핸드오버 처리 방법 및 그 방법을 지원하는 ａｓｎ-ｇｗ
KR101372735B1 (ko) 네트워크 기반 이동성 관리 방법
WO2012167460A1 (fr) Procédé et appareil permettant la réalisation de mobilité de connexion d'accès ip local ou de délestage de trafic ip sélectionné
WO2011097988A1 (fr) Procédé et système de communication mobile permettant de gérer des données ip locales
KR100928264B1 (ko) 이동통신의 핸드오버에 적용되는 서비스 정보 전달 방법
WO2011130983A1 (fr) Procédé, système et équipement de réseau d'implémentation de routage local
US20230362740A1 (en) 5g multicast broadcast service handover
WO2009103229A1 (fr) Procédé et dispositif pour obtenir l'adresse d'une fonction de passage de données d'ancrage
WO2012129997A1 (fr) Procédé et dispositif pour traiter une connexion d'accès à un réseau local
WO2011020322A1 (fr) Procédé et appareil de commutation pour système wimax

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: 07764190

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: 07764190

Country of ref document: EP

Kind code of ref document: A1