WO2012171403A1

WO2012171403A1 - Method and system supporting multi-interface multi-connection communication

Info

Publication number: WO2012171403A1
Application number: PCT/CN2012/073841
Authority: WO
Inventors: 严为; 魏元; 潘云波
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-06-14
Filing date: 2012-04-11
Publication date: 2012-12-20
Also published as: JP5778861B2; CN102833724A; CN102833724B; JP2014517635A

Abstract

Disclosed are a method and system supporting multi-interface multi-connection communication. A multi-interface multi-access server is deployed in a multi-interface multi-connection network, and the multi-interface multi-access server deployed in the multi-interface multi-connection network acquires status information about a terminal and/or a network and distributes a service stream strategy to the terminal and the network; and the multi-interface multi-access server facilitates a mobility management entity in performing mobility management on the terminal according to the acquired status information and the distributed service stream strategy. The present invention supports the technology of multi-interface multi-connection communications, enabling service stream strategy synchronization between the terminal side and the network side to be ensured, and effectively achieving mobility management aimed at a terminal.

Description

Method and system for supporting multi-interface multi-connection communication

The present invention relates to the field of communications, and in particular, to a method and system for supporting multi-interface (If, InterFace) multi-connection communication. Background technique

In the current network architecture development, it is necessary to fully utilize the advantages of various networks such as 2G/3G/Long Term Evolution (LTE) and Wireless Local Area Network (WLAN) to achieve interoperability between different networks. , to provide users with a better business experience.

Multi-network collaborative work requires mobile terminals and networks to support multiple interfaces and multiple connections. Specifically, as shown in FIG. 1 , for multiple interfaces, a mobile terminal needs to support multiple access modes at the same time, such as LTE, WLAN, and the like. For multi-interface and multi-connection, multi-interface terminals need to be able to access multiple networks at the same time. The terminal or network can select a more suitable network for users according to factors such as service characteristics, network quality, network economy, etc., and support different services on different networks. Simultaneous transmission, providing users with a better business experience, improving the utilization and cost performance of different network resources.

At present, proxy mobile ΙΡν6 ( ΡΜΙΡνό, Proxy Mobile IPv6) allows mobile nodes (MNs, Mobile Nodes) to connect to the same PMIPv6 domain through different interfaces, and anchor network elements such as Local Mobility Anchor (LMA). Control the execution of stream migration. Typically, the anchor network element can be referred to as a mobility management entity.

However, in a multi-interface multiple access scenario, there is no corresponding mechanism to ensure that the service flow policies of the terminal side and the network side are synchronized, so that mobility management for the terminal cannot be effectively implemented. Summary of the invention

In view of this, the main purpose of the present invention is to provide a method and system for supporting multi-interface multi-connection communication, so as to ensure synchronization of service flow policies at the terminal side and the network side, and effectively implement mobility management for terminals.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

A method for supporting multi-interface multi-connection communication, in which a multi-interface multi-access server is deployed in a multi-interface multi-connection network, the method further includes:

Obtaining status information of the terminal and/or the network by the multi-interface multi-access server deployed in the multi-interface multi-connection network, and distributing the service flow policy to the terminal and the network; according to the acquired status information and the distributed service flow policy, The multi-interface multi-access server assists the mobility management entity in mobility management of the terminal.

The status information of the terminal includes interface status information and location information of the terminal. The status information of the network includes load information of the access network.

The process of acquiring interface state information of the terminal includes:

The terminal or the access network element reports the interface status information of the terminal to the multi-interface multiple access server, so as to update the interface status to the multi-interface multi-access server;

After the current interface information of the terminal is updated, the multi-interface multiple access server actively sends the updated interface state information to the anchor network element; or responds to the interface state information request message of the anchor network element, and sends the corresponding interface state information to the anchor point. Network element

The process of obtaining location information of the terminal includes:

Initiating update of the terminal location information by the terminal or the access network element to update terminal location information on the multi-interface multiple access server;

After the current interface information of the terminal is updated, the multi-interface multiple access server actively sends the updated interface location information to the access network element before the handover or the access network element after the handover; or responds to the interface location of the access network element before/after the handover. Information request, sending corresponding interface location information to the relevant network element; The process of obtaining load information of accessing a network includes:

The access point directly informs its current network load situation; the multi-interface multiple access server creates or updates the current network load status; or, the access point reports its current access network load information to the access device, and the access device receives After the wireless network load information is acquired, the network load status learned by itself is integrated, and the network load notification is sent to the multi-interface multi-access server; the multi-interface multi-access server creates or updates the current network load status;

The anchor network element actively requests the multiple access multi-interface server to request the current access network load information; the multi-interface multiple access server actively announces the access network load information to the anchor network element.

The distribution of the service flow policy includes two processes: the terminal obtains a service flow policy from the multi-interface multi-access server, and the anchor network element obtains a service flow policy from the multi-interface multiple access server.

The mobility management entity includes an anchor network element, and the process of the multi-interface multiple access server assisting the mobility management entity to perform mobility management on the terminal includes:

The anchor network element provides the mobility management service to the user according to the terminal interface state information, the terminal location information, the access network load information, and the service flow policy obtained from the multi-interface multiple access server.

A system for supporting multi-interface multi-connection communication, comprising a state information acquisition unit and a mobility management unit; wherein

The status information acquiring unit is configured to acquire status information of the terminal and/or the network, and distribute the service flow policy to the terminal and the network;

The mobility management unit is configured to assist the mobility management entity to perform mobility management on the terminal according to the state information acquired by the state information acquiring unit.

The status information acquiring unit, when acquiring the interface status information of the terminal, is configured to: trigger the terminal or the access network element to report the interface status information of the terminal to the multi-interface multiple access server. Information to update the interface status to the multi-interface multi-access server;

After the current interface information of the terminal is updated, the multi-interface multiple access server is triggered to actively send the updated interface state information to the anchor network element; or respond to the interface state information request message of the anchor network element, and send the corresponding interface state information to the anchor. Point network element

When the status information acquiring unit acquires the location information of the terminal, it is used to:

Triggering the terminal or accessing the network element to initiate update of the location information of the terminal, so as to update the location information of the terminal on the multi-interface multi-access server;

After the current interface information of the terminal is updated, the multi-interface multiple access server is triggered to actively send the updated interface location information to the access network element before the handover or the access network element after the handover; or the interface that accesses the network element before or after the handover. The location information request, the corresponding interface location information is sent to the relevant network element; when the state information acquisition unit acquires the load information of the access network, it is used to:

The triggering access point directly informs the current network load condition; triggers the multi-interface multiple access server to create or update the current network load status; or triggers the access point to report the current access network load information to the access device, triggering After receiving the wireless network load information, the access device integrates the network load status learned by itself, and sends a network load notification to the multi-interface multiple access server; triggers the multi-interface multiple access server to create or update the current network load status;

The triggering anchor network element actively requests the multi-access multi-interface server to request the current access network load information; triggering the multi-interface multi-access server to actively notify the anchor network element to access the network load information.

The state information obtaining unit, when distributing the service flow policy, is configured to: trigger the terminal to obtain a service flow policy from the multi-interface multiple access server, and trigger the anchor network element to obtain a service flow policy from the multi-interface multiple access server. .

The mobility management entity includes an anchor network element, and the mobility management unit assists the mobility management entity in performing mobility management on the terminal, and is used to:

The triggering anchor network element provides mobility management for the user according to terminal interface state information, terminal location information, access network load information, and service flow policy obtained from the multi-interface multiple access server. Service.

The method and system of the present invention deploys a multi-interface multi-access server in a multi-interface multi-connection network, and acquires state information of the terminal and/or the network by the multi-interface multi-access server deployed in the multi-interface multi-connection network, and distributes the service. The flow policy is to the terminal and the network; according to the obtained status information and the distributed service flow policy, the multi-interface multiple access server assists the mobility management entity to perform mobility management on the terminal. Therefore, the service flow policies of the terminal side and the network side can be synchronized, and the mobility management for the terminal can be effectively realized. DRAWINGS

FIG. 1 is a schematic structural diagram of a multi-interface multiple access network;

2 is a schematic diagram of a network structure for deploying a multi-interface multi-access server in a multi-interface multi-connection network according to an embodiment of the present invention;

3 is a flow chart of reporting interface status information according to an embodiment of the present invention;

4 is a flowchart of a location information report according to an embodiment of the present invention;

FIG. 5 is a flowchart of reporting load information of an access network according to an embodiment of the present invention;

FIG. 6 is a flowchart of a user policy release according to an embodiment of the present invention;

FIG. 7 is a schematic flowchart of supporting multi-interface multi-connection communication according to an embodiment of the present invention; FIG.

FIG. 8 is a system diagram of supporting multi-interface multi-connection communication according to an embodiment of the present invention. detailed description

In a multi-interface multi-connection scenario, the LMA needs to control the flow migration according to the real-time connection status of the terminal multi-interface (such as the activation and disconnection status of the interface). When a new interface is connected to the network, the LMA migrates the existing service flow that is more suitable for the new interface to the new interface according to the real-time interface status. When the interface leaves the network (such as the connection is disconnected), the LMA needs to be based on the interface. The disconnected state, the traffic on this interface is transferred to the active available interface. In this case, the above operation process of the LMA needs to be based on the service flow policy, and the service flow policy needs and ends. Side synchronization.

In a multi-interface multi-connection scenario, when the MN switches between different access networks, in order to improve handover performance (such as reducing packet loss and handover delay during handover), it is necessary to establish a bidirectional tunnel between the access device before and after the handover. , used to tunnel messages. In addition, some parameters need to be exchanged between the access devices before and after the handover to assist in the fast and smooth handover process. Therefore, the real-time location information of the multi-interface and multi-connection needs to be recorded on the server, such as an access point (AP, Access Point) ID, access network element ID, etc., for the access device to obtain each other's address, and is used to assist in switching. Information interaction.

In an actual application, as shown in FIG. 2, a multi-interface multi-access server may be deployed in a multi-interface multi-connection network, and the multi-interface multi-access server may be connected to an anchor network element, and may also be connected to an access point. The access network element such as the ingress device is connected, and can also be connected to the terminal such as the MN.

The terminal or access network element such as the MN can report the status information of the terminal (such as the interface status information, location information, etc. of the terminal) to the multi-interface multiple access server. The anchor network element can obtain the above information from the multi-interface multi-access server to trigger a mobility management process (such as stream migration or perform fast handover, etc.) for the terminal.

Moreover, the access network element such as the access point and the access device can report the load information of the access network to the multi-interface multiple access server. The anchor network element can obtain the above information from the multi-interface multi-access server to trigger a mobility management process (such as stream migration or perform fast handover, etc.) for the terminal.

In addition, the terminal may also obtain the service flow policy information from the multi-interface multi-access server by sending a request, to perform interface selection, or to migrate the service flow between different interfaces, or select appropriate access for the service according to the characteristics of the service flow. technology. Similarly, the anchor network element can also obtain service flow policy information from the multi-interface multi-access server, and perform better mobility management on the terminal accordingly.

In general, a multi-interface multi-access server can be deployed in a multi-interface multi-connection network, and the multi-interface multi-access server obtains location information and interface state information of the terminal from the terminal and/or the access network element, and accesses the network. Load information, etc., to trigger mobility management processes (such as flows) for the terminal Migrate or perform fast switching, etc.). Moreover, the foregoing information may also be synchronized to the anchor network element and the access network element.

When the interface status information reporting process shown in FIG. 3 is performed, the interface status information reporting process may be initiated by the terminal or the access network element to update the interface status to the multi-interface multiple access server. The access network element may be an access point, such as a BS, an AP, an eNodeB, or the like, and an access device, such as an access controller (AC, Access Controller), a serving gateway (S-GW, a Serving GateWay), or the like.

In Figure 3, the update of the MN interface status information can be initiated by the terminal, as shown in steps 1, 2. The MN initiates an interface state information update request to the multi-interface multiple access server using the connected interface.

For example, the MN has two interfaces at the same time: Cellular interface If 1 and WLAN interface If 2. The MN can use the current connection interface If 1 to report the interface status information to the multi-interface multiple access server, that is, the current interface information of the interfaces If 1 and If 2. The interface status information includes information such as MN_ID (identification), access technology type, interface status (strong wireless signal quality / poor wireless signal quality / no connection), interface ID, and so on.

The multi-interface multi-access server updates the information in the request according to the received interface status information, and creates or updates the status information of the current interface for the MN. Interface status includes:

The wireless signal quality of the interface is strong: When the interface signal strength is higher than a certain threshold for a certain period of time, the air quality of the air interface is good.

The quality of the interface wireless signal is poor: When the interface signal strength is lower than a certain threshold for a certain period of time, the air quality of the air interface is poor and is not suitable for communication. In this case, use the available interface to send the interface status information update request to the multi-interface multi-access server.

No connection on the interface: no signal strength. In this case, you should use the connected interface to send the interface status information update request to the multi-interface multi-access server.

It should be noted that the foregoing description is only a specific classification form, and the interface status may also be classified into suitable communication and unsuitable communication. The interface status in the actual application can be based on the actual application. Division of environment, operator needs, etc.

The update of the MN interface state information may also be initiated by the access network element, as shown in steps 3 and 4. If the access device, such as the AC and the S-GW, knows the status of the currently connected interface of the MN, the interface status information update request may be sent to the multi-interface multiple access server, where the update request includes the MN_ID, the access technology type, the interface status, and the interface ID. And other information.

The access point can know the current interface status of the MN when the interface accesses the network. For example, the AP detects the status of the MN interface through the detection of the MN interface status. The access point may be an evolved base station (eNodeB, Evolved Node B), a WALN AP, etc., and the access device may be an AC, an S-GW, or the like.

The access point can be informed of the interface status of the MN through Layer 2 detection or other mechanisms. For example, in some access technologies, after the access point forwards the packet to the terminal, it will receive a Layer 2 acknowledgment message from the corresponding interface of the terminal. If the access point does not receive the Layer 2 acknowledgment message from the terminal within a certain period of time after forwarding the packet, the interface is considered to be disconnected.

The multi-interface multi-access server updates the request according to the interface status information sent by the access network, and creates or updates the status information of the current interface for the MN.

The multi-interface multi-access server maintains the status information of the current interface of the MN.

As shown in steps 5, 6, and 7, after the current interface information of the MN is updated, the multi-interface multiple access server may respond to the interface state information request message of the anchor network element, and send the corresponding interface state information to the anchor network element. You can also actively send updated interface status information to the anchor network element.

Specifically, Step 5: The anchor network element actively requests the interface status information of the mobile node to the multi-interface multiple access server.

Step 6: The multi-interface multiple access server responds to the mobile node interface status information requested by the anchor network element;

Step 7: In addition, the multi-interface multi-access server may also actively push the interface state information of the mobile node to the anchor network element. For example, an anchor can make a flow migration decision based on the state information of the current interface. The service flow on the connectionless or poor signal quality interface is migrated to the available connection interface to ensure uninterrupted data flow and ensure user experience.

When the location information reporting process shown in FIG. 4 is performed, the location information of the MN may be composed of the geographic location information and the network location information corresponding to the MN interface. among them,

Address location information: longitude and latitude;

Network location information: Access network identifier corresponding to the connection interface, Public Land Mobile Network (PLMN) ID or Service Set Identifier (SSID) or Network Access Point (NAP) ID, connected access NE ID or IP address.

The update of the MN location information may also be initiated by the terminal or the access network element (such as AC, S-GW, etc.) to update the MN location information on the multi-interface multiple access server.

The update of the MN location information can be initiated by the terminal, as shown in steps 1, 2. The MN sends the MN location information update request to the multi-interface multiple access server using the connected interface.

For example, the MN has two interfaces at the same time, the cellular interface If 1 and the WLAN interface If 2. The MN can use the current connection interface If 1 to report the location information of the current connection interface of the MN to the multi-interface multiple access server, that is, the location information of the interface If 1.

The multi-interface multi-access server updates the information in the request according to the MN location information, and creates or updates the location information of the current connection interface for the MN.

The MN location information may also be initiated by the access network element, as shown in steps 3 and 4. If the access device, such as the AC and the S-GW, obtains the location information of the current connection interface of the MN, the MN location information update request may be sent to the multi-interface multiple access server, where the update request includes the MN_ID, the access technology type, the interface ID, and the Location information, etc.

The access device learns the MN location information through related channels, such as: obtaining the current geographic location information of the terminal through a specific mechanism of the related access network. During the process of accessing the network, the network location information of the currently connected interface may be obtained, for example, the access point informs the access device of the location information of the currently connected interface of the MN.

The multi-interface multiple access server creates or updates the MN location information for the MN according to the MN location information update request of the current connection interface sent by the access network element.

The multi-interface multi-access server maintains MN location information.

As shown in steps 5, 6, and 7, after the current interface information of the MN is updated, the multi-interface multiple access server may respond to the interface location information request of the network element device such as the network element before and after the handover, and send the corresponding interface location information. To the relevant network element, the updated interface location information may be actively sent to the network element device such as the access network element before the handover or the access network element after the handover.

Specifically, step 5: the access network element actively requests the interface location information of the mobile node from the multi-interface multiple access server;

Step 6: The multi-interface multiple access server responds to the mobile node interface location information requested by the access network element;

Step 7: In addition, the multi-interface multi-access server can also actively push the interface location information of the mobile node to the access network element.

For example, the mobility of the MN causes the MN to switch from the previous access network element to the new access network element (which may be the handover of the same access technology, or may be the handover of the heterogeneous access technology). The pre-access network element can obtain the IP address of the new access network element from the multi-interface multi-access server, and the new access network element can also obtain the IP address of the pre-access network element from the multi-interface multi-access server, thereby facilitating the fast. The smoothing of the completion of the switch.

When performing the access network load information reporting process as shown in FIG. 5, the access network element may advertise the access network load information to the multi-interface multiple access server, and the multi-interface multiple access server maintains the access network load information. The load information can be created by using the access NE as an index. The notification of the network load can be reported directly by the access point or reported by the access device. The access device may be an S-GW, an AC, an evolved packet data gateway (ePDG, Evolved Packet Data) Gateway) and so on.

In steps 1 and 2, the access point directly informs its current network load situation; the multi-interface multi-access server creates or updates the current network load status;

In steps 3 and 4, the access point reports its current access network load information to the access device, and after receiving the wireless network load information, the access device integrates the network load status learned by itself, and sends a network load notification to multiple interfaces. Multiple access servers; multi-interface multiple access servers create or update current network load conditions;

In steps 5 and 6, the anchor network element actively requests the current access network load information to the multi-access multi-interface server;

In step 7, the multi-interface multi-access server actively announces to the anchor network element that the access network load-signal anchor network element obtains terminal interface status information, terminal location information, and access network load information obtained from the multi-interface multiple access server. , business flow strategy, to provide users with rapid switching, stream migration and other mobility management services.

When the service flow policy is delivered as shown in FIG. 6, the service flow policy may be sent in two processes: The terminal obtains a service flow policy from the multi-interface multiple access server, and the anchor network element is connected from multiple interfaces. The process of getting the service flow policy into the server.

Step 1 and Step 2 describe the policy download process initiated by the terminal. This process can define new messages separately, and also use the existing network access process to define new specific attributes in existing messages for requesting service flow policies;

Specifically, step 1.1: The mobile node requests a service flow policy, and sends a service flow policy request message to the access device. The service flow policy request message includes a user identifier;

Step 1.2: After receiving the service flow policy request message, the access device sends a service flow policy request message to the multi-interface multiple access server.

Step 2.1: After the multi-interface multiple access server receives the request message from the access device, the root According to the user identifier carried in the message, the service flow policy of the user is delivered to the access device. Step 2.2: The access device delivers the user service flow policy to the MN.

In step 3, when the service flow policy changes, the multi-interface multi-access server can also actively push the service flow policy to the mobile terminal. For example, the server actively sends the service flow policy to the access device where the user is currently located, and the access device sends the received service flow policy to the MN;

In step 4 and step 5, after the user registers, the anchor network element requests the service flow policy of the user from the multi-interface multiple access server. The service flow policy on the anchor network element needs to be consistent with the service flow policy on the MN.

The MN can select a suitable interface for various services according to the service flow policy. The anchor network element can perform flow migration in a specific scenario according to the service flow policy.

It should be noted that, in the foregoing embodiment, the multi-interface multi-access server is a logical function entity, and may be a single network element entity or may be deployed on an existing network element entity according to an actual operation plan. Moreover, the service flow policy is delivered, and the multi-interface multi-access server actively pushes to the terminal and the anchor network element; or the terminal and the anchor network element actively request from the multi-interface multiple access server.

The service flow policy includes: selecting a policy of a corresponding access technology interface according to a service flow characteristic, and adjusting a policy for selecting a flow migration according to network congestion.

Moreover, similar to the status information of the terminal, the access network load information also belongs to the status information; therefore, the status information of the terminal and/or the network can be acquired by the multi-interface multiple access server.

According to the above description, the present invention supports the operation of multi-interface multi-connection communication, and needs to first deploy a multi-interface multi-access server in a multi-interface multi-connection network, and then can execute the process shown in FIG. 7, which includes the following steps. :

Step 710: Acquire status information of the terminal and/or the network by the multi-interface multi-access server deployed in the multi-interface multi-connection network, and distribute the service flow policy to the terminal and the network.

Step 720: The multi-interface multi-access server assists mobility according to the obtained status information. A management entity (such as an anchor network element) performs mobility management on the terminal.

In order to ensure that the above description and operation ideas can be smoothly implemented, the settings shown in Figure 8 can be performed. Referring to FIG. 8, FIG. 8 is a system diagram of supporting multi-interface multi-connection communication according to an embodiment of the present invention, where the system includes a connected state information acquiring unit and a mobility management unit, and both units can be set to multiple interfaces and multiple accesses. In the server.

In actual application, the state information acquiring unit can acquire state information of the terminal and/or the network, and distribute the service flow policy to the terminal and the network; and the mobility management unit can assist the state information acquired by the state information acquiring unit, and assist A mobility management entity (such as an anchor network element) performs mobility management on the terminal.

In summary, the present invention supports the technology of multi-interface multi-connection communication, and can ensure the synchronization of the service flow policies on the terminal side and the network side, and effectively realize the mobility management for the terminal.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A method for supporting multi-interface multi-connection communication, deploying a multi-interface multi-access server in a multi-interface multi-connection network, the method further comprising:

2. The method according to claim 1, wherein the status information of the terminal includes interface status information and location information of the terminal; and the status information of the network includes load information of the access network.

3. The method according to claim 2, wherein

The process of obtaining interface state information of the terminal includes:

The process of obtaining location information of the terminal includes:

After the current interface information of the terminal is updated, the multi-interface multiple access server actively sends the updated interface location information to the access network element before the handover or the access network element after the handover; or responds to the interface location of the access network element before/after the handover. Information request, sending corresponding interface location information to the relevant network element;

The process of obtaining load information of accessing a network includes:

The access point directly informs its current network load situation; multi-interface multiple access server creation Or update the current network load status; or, the access point reports its current access network load information to the access device, and after the access device receives the wireless network load information, it synthesizes the network load status that it knows, and sends the network. The load is notified to the multi-interface multi-access server; the multi-interface multi-access server creates or updates the current network load status;

The method according to any one of claims 1 to 3, wherein the distribution of the service flow policy comprises two processes: the terminal acquires a service flow policy from the multi-interface multiple access server, and the anchor network element is from a plurality of The interface multiple access server obtains a service flow policy.

The method according to claim 4, wherein the mobility management entity includes an anchor network element, and the process of the multi-interface multiple access server assisting the mobility management entity to perform mobility management on the terminal includes:

6. A system for supporting multi-interface multi-connection communication, comprising a state information acquisition unit and a mobility management unit; wherein

The system according to claim 6, wherein the status information of the terminal includes interface status information and location information of the terminal; and the status information of the network includes load information of the access network.

8. The system according to claim 7, wherein

When the status information acquiring unit acquires the interface status information of the terminal, it is used to: The triggering terminal or the access network element reports the interface status information of the terminal to the multi-interface multiple access server, so as to update the interface status to the multi-interface multi-access server;

The system according to any one of claims 6 to 8, wherein the status information obtaining unit, when distributing the service flow policy, is configured to: trigger a terminal to obtain a service flow policy from a multi-interface multiple access server, and The triggering anchor network element obtains a service flow policy from the multi-interface multiple access server.

The system according to claim 9, wherein the mobility management entity includes an anchor network element, and the mobility management unit, when the mobility management entity assists the mobility management entity in performing mobility management on the terminal, is used to: The triggering anchor network element provides the mobility management service for the user according to the terminal interface state information, the terminal location information, the access network load information, and the service flow policy obtained from the multi-interface multiple access server.