WO2014101181A1 - 用户设备及异构网络切换的方法 - Google Patents

用户设备及异构网络切换的方法 Download PDF

Info

Publication number
WO2014101181A1
WO2014101181A1 PCT/CN2012/088038 CN2012088038W WO2014101181A1 WO 2014101181 A1 WO2014101181 A1 WO 2014101181A1 CN 2012088038 W CN2012088038 W CN 2012088038W WO 2014101181 A1 WO2014101181 A1 WO 2014101181A1
Authority
WO
WIPO (PCT)
Prior art keywords
interface
service process
tunnel
physical interface
virtual interface
Prior art date
Application number
PCT/CN2012/088038
Other languages
English (en)
French (fr)
Inventor
郑磊斌
尚兴宏
吕黎明
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2012/088038 priority Critical patent/WO2014101181A1/zh
Priority to CN201280001962.8A priority patent/CN104094637B/zh
Publication of WO2014101181A1 publication Critical patent/WO2014101181A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0019Control or signalling for completing the hand-off for data sessions of end-to-end connection adapted for mobile IP [MIP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/14Reselecting a network or an air interface
    • H04W36/144Reselecting a network or an air interface over a different radio air interface technology

Definitions

  • Embodiments of the present invention relate to the field of wireless communications, and more particularly, to user equipment and methods for heterogeneous network handover. Background technique
  • the current seamless handover between heterogeneous networks is mainly based on the Mobile Internet (Internet Protocol) technology, which is divided into two types of network-based and client-based technology architectures.
  • Mobile Internet Internet Protocol
  • the network-based technology architecture mainly includes PMIP (Proxy Mobile IP) and GTP (General Packet Radio Service Tunneling Protocol). It is characterized in that access gateways of heterogeneous networks use IP tunnels to access mobile anchor points (Mobility). Anchor) to ensure that the IP address does not change when the terminal switches between networks.
  • the mobility anchor may be a P-GW (PDN Gateway, PDN Gateway) or an HA (Home Agent, Home Agent).
  • the terminal-based technical architecture mainly includes MIPv4 (Mobile IP Version 4, Mobile IP Version 4) and DSMIPv6 (Dual Stack Mobile IP Version 6, Dual Stack Mobile IP Version 6) technologies, etc., which is characterized in that the terminal directly uses the IP-type protocol to access the mobile. Anchor point, the impact of the underlying IP change on the application layer when switching between networks.
  • the user equipment operating system is required to ensure that the TCP (Transmission Control Protocol) connection can be maintained during the heterogeneous network switching. Switch.
  • TCP Transmission Control Protocol
  • current mainstream mobile terminal operating systems such as Android (Android) are not capable of providing the above technical support.
  • the user equipment operation system needs to be modified.
  • the IP/TCP protocol stack Since modifying the user equipment operating system involves coordinating the operating system provider and a large number of user equipment vendors, it is difficult to actually deploy such user equipment, and thus the heterogeneous network seamless handover scheme is difficult to implement. Summary of the invention
  • the embodiments of the present invention provide a user equipment and a heterogeneous network handover method to implement seamless handover of a heterogeneous network.
  • a user equipment including a handover service process component, an application process component, a first physical interface, and a second physical interface: a handover service process component, configured to establish a virtual interface, and configure an address of the virtual interface as a hometown Address (HoA), and establish communication between the switching service process component and the virtual interface; and also used to establish an internetworking protocol (IP) tunnel with the mobility anchor, and bind the IP tunnel to the currently used
  • the first physical interface is further configured to set an IP routing table, where the IP routing table is used to control routing of data between the application process component and the virtual interface; and is further configured to: after the first physical interface switches to the second physical interface, The tunnel is bound from the first physical interface to the second physical interface, where the first physical interface and the second physical interface are two physical interfaces of the heterogeneous network, and the application process component is configured to send data to the virtual interface according to the IP routing table. Receive data forwarded by the virtual interface.
  • HoA hometown Address
  • IP internetworking protocol
  • the handover service process component is further configured to access the mobility anchor and obtain the HoA of the mobility anchor assignment before establishing an IP tunnel with the mobility anchor.
  • the user equipment further includes a character device driver component: a character device driver component, configured to implement a handover service process component and a virtual Communication between interfaces.
  • the application process component is specifically configured to send uplink data to the virtual interface according to the IP routing table; and the switching service process component drives the component by using the character device.
  • the uplink data received by the virtual interface is read; the switching service process component encapsulates the read uplink data, and sends the uplink data to the mobile fault point through the IP tunnel through the first physical interface.
  • the first physical interface sends the downlink data received from the mobility anchor to the handover service process component through the IP tunnel; switching the service process component Decapsulating the downlink data, and writing the decapsulated downlink data to the virtual interface through the character device driver; the virtual interface receives the decapsulated downlink data according to the IP address.
  • the routing table is forwarded to the application process component.
  • the handover service process component establishes an IP tunnel with the mobility anchor through one of the following protocols: a user datagram protocol ( UDP), Transmission Control Protocol (TCP), IP-Encapsulated IP (IP-in-IP), Generic Routing Encapsulation (GRE), and General Packet Radio Service Tunneling Protocol (GTP).
  • UDP user datagram protocol
  • TCP Transmission Control Protocol
  • IP-Encapsulated IP IP-in-IP
  • GRE Generic Routing Encapsulation
  • GTP General Packet Radio Service Tunneling Protocol
  • the user equipment works in a heterogeneous network of at least two types of systems: Third Generation Partnership Project (3GPP), Wireless Local Area Network (WLAN), Code Division Multiple Access (CDMA), Global Chop Interconnect (WiMAX).
  • 3GPP Third Generation Partnership Project
  • WLAN Wireless Local Area Network
  • CDMA Code Division Multiple Access
  • WiMAX Global Chop Interconnect
  • the second aspect provides a method for heterogeneous network switching, including: in a first possible implementation manner, establishing a virtual interface, and configuring an address of the virtual interface as a home address (HoA); establishing a handover service process component Communication with the virtual interface; establishing an internetworking protocol (IP) tunnel between the switching service process component and the mobility anchor, and binding the IP tunnel to the first physical interface currently in use; setting an IP routing table, where The IP routing table is used to control the routing of data between the application process component and the virtual interface.
  • IP internetworking protocol
  • the IP tunnel is bound from the first physical interface to the second physical interface, where the first The physical interface and the second physical interface are two physical interfaces of a heterogeneous network.
  • the switching service process component accesses the mobility anchor and obtains the HoA of the mobility anchor assignment.
  • communication between the switching service process component and the virtual interface is implemented by a character device driver.
  • the application process component sends the uplink data to the virtual interface according to the IP routing table; the switching service process component reads the virtual interface by using the character device driver. Received uplink data; The handover service process component encapsulates the read uplink data and sends it to the mobility anchor through the IP tunnel through the first physical interface.
  • the first physical interface sends the downlink data received from the mobility anchor to the handover service process component through the IP tunnel; switching the service process component After the downlink data is decapsulated, the decapsulated downlink data is written to the virtual interface by the character device driver; the virtual interface forwards the received decapsulated downlink data to the application process component according to the IP routing table.
  • an IP tunnel between the handover service process component and the mobility anchor is established by one of the following protocols: a user datagram protocol ( UDP), Transmission Control Protocol (TCP), IP-Encapsulated IP (IP-in-IP), Generic Routing Encapsulation (GRE), and General Packet Radio Service Tunneling Protocol (GTP).
  • UDP user datagram protocol
  • TCP Transmission Control Protocol
  • IP-Encapsulated IP IP-in-IP
  • GRE Generic Routing Encapsulation
  • GTP General Packet Radio Service Tunneling Protocol
  • the heterogeneous network includes the following at least two types of wireless systems: Third Generation Partnership Project
  • a user equipment including a processor, a memory, a first physical interface, and a second physical interface: a memory storage processor executes instructions required to execute the following method; a processor, configured to invoke a handover service process, wherein The handover service process is used to establish a virtual interface and configure the address of the virtual interface as a home address (HoA), and establish communication between the handover service process and the virtual interface; and is also used to establish an internet connection with the mobility anchor point.
  • HoA home address
  • IP tunneling and binding the IP tunnel to the first physical interface currently used; also used to set an IP routing table, where the IP routing table is used to control routing of data between the application process and the virtual interface; After the first physical interface is switched to the second physical interface, the IP tunnel is bound to the second physical interface, where the first physical interface and the second physical interface are two physical interfaces of the heterogeneous network;
  • the application process is also used to invoke an application process, where the application process is used to send data and receive virtual information to the virtual interface according to the IP routing table. Port forwarding data.
  • the processor further invokes a handover service process for accessing the mobility anchor and obtaining the HoA of the mobility anchor assignment before establishing an IP tunnel with the mobility anchor.
  • the processor further invokes a character device driver for implementing communication between the switching service process and the virtual interface.
  • the processor invokes the application process to specifically send the uplink data to the virtual interface according to the IP routing table; the processor invokes the handover service process to pass The character device driver reads the uplink data received by the virtual interface; the processor invokes the switching service process to encapsulate the read uplink data, and then sends the uplink data to the mobility anchor through the IP tunnel through the first physical interface.
  • the processor sends the downlink data received by the first physical interface from the mobility anchor to the IP tunnel through the IP tunnel. After the processor invokes the switching service process to decapsulate the downlink data, the decapsulated downlink data is written to the virtual interface through the character device driver; the virtual interface forwards the received decapsulated downlink data to the application according to the IP routing table. process.
  • the processor invokes the handover service process to establish an IP tunnel with the mobility anchor by using one of the following protocols: user datagram Protocol (UDP), Transmission Control Protocol (TCP), IP-Encapsulated IP (IP-in-IP), Generic Routing Encapsulation (GRE), and General Packet Radio Service Tunneling Protocol (GTP).
  • UDP user datagram Protocol
  • TCP Transmission Control Protocol
  • IP-Encapsulated IP IP-in-IP
  • GRE Generic Routing Encapsulation
  • GTP General Packet Radio Service Tunneling Protocol
  • the user equipment works in a heterogeneous network of at least two types of systems: Third Generation Partnership Project (3GPP), Wireless Local Area Network (WLAN), Code Division Multiple Access (CDMA), Global Wave Interconnect (WiMAX).
  • 3GPP Third Generation Partnership Project
  • WLAN Wireless Local Area Network
  • CDMA Code Division Multiple Access
  • WiMAX Global Wave Interconnect
  • the user equipment includes a handover service process component, an application process component, a first physical interface, and a second physical interface, establishes a virtual interface by switching the service process component, and establishes a handover service process component, a virtual interface, and an application process component.
  • Inter-communication by binding the HoA to the IP address of the virtual interface, when the physical interface of the heterogeneous network changes, changing the communication between the switching service process component and the mobility anchor, and still maintaining communication between the virtual interface and the application process component. It is not affected, thus supporting seamless handover of heterogeneous networks and ensuring continuity of service usage.
  • 1 is a schematic diagram of a TCP/IP protocol stack of an operating system of a user equipment in the prior art.
  • 2 is a schematic diagram of an end-to-end TCP/IP protocol stack in accordance with an embodiment of the present invention.
  • FIG. 3 is a schematic block diagram of a user equipment according to an embodiment of the present invention.
  • FIG. 4 is a schematic flow chart of a method for heterogeneous network switching according to an embodiment of the present invention.
  • FIG. 5 is a schematic block diagram of another user equipment according to an embodiment of the present invention.
  • FIG. 6 is a schematic flow chart of a method for heterogeneous network switching according to another embodiment of the present invention.
  • FIG. 7 is a schematic diagram of a data forwarding process of a user equipment according to an embodiment of the present invention.
  • FIG. 8 is a schematic block diagram of another user equipment according to an embodiment of the present invention. detailed description
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • UMTS Universal Mobile Communication Systems
  • LTE Long Term Evolution
  • WLAN Wireless Local Area Networks
  • WiMAX Worldwide Interoperability for Microwave Access
  • a user equipment which may also be called a mobile terminal (Mobile Terminal), a mobile user equipment, a cartridge terminal, etc.
  • a radio access network eg, RAN, Radio Access Network
  • the core network communicates, and the user equipment can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, for example, can be portable, pocket, handheld, computer built, or in-vehicle mobile Devices that exchange voice and/or data with a wireless access network.
  • FIG. 1 is a schematic diagram of a TCP/IP protocol stack 10 of an operating system of a user equipment in the prior art.
  • the TCP/IP protocol stack 10 schematically includes an OSI (Open System Interconnection) model, a Layer 7 protocol, LI (Layer 1 , Network Layer) 11 , L2 ( Layer 2 , Data Link Layer ). 12, IP layer 13, TCP/UDP layer 14 and applications (applications, writes as APP) layer 15, and the like.
  • L2 includes multiple physical interfaces (IF, Interface), such as IF1, IF2 to IFn, etc., where n indicates the serial number and can be a positive integer.
  • the TCP/IP layer is bound to the physical interface, and which physical interface is used for data transmission is determined according to the currently accessed network.
  • the physical interface changes, the operating system clears the TCP/UDP connection on the current interface, and notifies the application physical interface change.
  • the continuity of the session can only ultimately depend on the application processing, and there is no guarantee that the switching process session will be continuous.
  • the current mainstream operating system does not support the seamless switching capability of heterogeneous networks. If the modification of the operating system is not conducive to large-scale deployment, this is the bottleneck in which the heterogeneous network seamless handover solution is difficult to implement.
  • the embodiment of the invention provides a user equipment, which can implement seamless handover of heterogeneous networks without modifying the operating system.
  • the end-to-end includes the relationship between the user equipment and the network equipment, and the network equipment.
  • the protocol stack between the user equipment 21, the mobility anchor 22 and the application server 23 is shown in FIG.
  • the user equipment 21 includes L1 and L2, IP (CoA), UDP, IP (HoA), UDP/TCP and APP.
  • the mobility anchor 22 includes L1 and L2, IP (CoA), UDP, IP (HoA), UDP/TCP, and APP corresponding to each layer of the user equipment 21, and L1 and L2, IP corresponding to each layer of the application server 23 ( HoA), UDP/TCP and APP.
  • the application server 23 includes L1 and L2, IP (HoA), UDP/TCP, and APP corresponding to the layers of the mobility anchor 22.
  • the figure illustrates a UDP tunnel-based protocol stack.
  • the UDP tunnel can be replaced by other tunnel technologies, such as IP-in-IP, General Routing Encapsulation (GRE), or general-purpose wireless.
  • GTP General Packet Radio Service Tunnel Protocal
  • IP tunnel can be collectively referred to as an IP tunnel.
  • the user equipment 21 establishes an IP tunnel with the mobility anchor 22 via a wireless network such as WLAN or 3GPP, and the mobility anchor 22 establishes a connection with the application server 23.
  • HoA home address
  • CoA Core of Address
  • FIG. 3 is a schematic block diagram of user equipment 30 in accordance with an embodiment of the present invention.
  • the user equipment 30 includes a handover service process component 31, an application process component 32, a first physical interface 33, and a second physical interface 34.
  • the handover service process component 31 establishes a virtual interface and configures the IP address of the virtual interface as a home address (HoA), and establishes communication between the handover service process component and the virtual interface; and also establishes a movement with the virtual interface
  • IP routing table is also provided, wherein the IP routing table is used to control application process components 32 And routing the data between the virtual interface and the virtual interface; and after the first physical interface is switched to the second physical interface, binding the IP tunnel from the first physical interface to the second physical interface, where The first physical interface and the second physical interface are two physical interfaces of a heterogeneous network.
  • the application process component 32 sends data to the virtual interface and receives data forwarded by the virtual interface according to the IP routing table.
  • the user equipment of the embodiment of the present invention includes a handover service process component, an application process component, a first physical interface, and a second physical interface, establishes a virtual interface by switching service process components, and establishes a handover service process component, a virtual interface, and an application process component.
  • Inter-communication by binding the HoA to the IP address of the virtual interface, when the physical interface of the heterogeneous network changes, changing the communication between the switching service process component and the mobility anchor, and still maintaining communication between the virtual interface and the application process component. It is not affected, thus supporting seamless handover of heterogeneous networks and ensuring continuity of service usage.
  • the handover service process component is further configured to access the mobility anchor and obtain the HoA of the mobility anchor assignment before establishing an IP tunnel with the mobile anchor.
  • the user equipment further includes a character device driver component: the character device driver component is configured to implement communication between the handover service process component and the virtual interface.
  • the application process component is specifically configured to send uplink data to the virtual interface according to the IP routing table; and the switching service process component reads the device by using the character device driving component.
  • the uplink data received by the virtual interface; the switching service process component encapsulates the read uplink data, and sends the uplink data to the mobility anchor through the IP tunnel through the first physical interface.
  • the first physical interface sends downlink data received from the mobility anchor to the handover service process component by using the IP tunnel; the handover service process component After the downlink data is decapsulated, the decapsulated downlink data is written into the virtual interface by using a character device driver; and the virtual interface forwards the received decapsulated downlink data to the application process component according to the IP routing table.
  • the handover service process component establishes an IP tunnel with the mobility anchor by using one of the following protocols: a User Datagram Protocol (UDP), a Transmission Control Protocol (TCP), and an IP.
  • UDP User Datagram Protocol
  • TCP Transmission Control Protocol
  • IP-in-IP Encapsulated IP
  • GRE Generic Routing Encapsulation
  • GTP General Packet Radio Service Tunneling Protocol
  • the user equipment works in a heterogeneous network of at least two types of systems: Third Generation Partnership Project (3GPP), Wireless Local Area Network (WLAN), Code Division Multiple Access (CDMA) , Worldwide Microwave Interconnect (WiMAX).
  • 3GPP Third Generation Partnership Project
  • WLAN Wireless Local Area Network
  • CDMA Code Division Multiple Access
  • WiMAX Worldwide Microwave Interconnect
  • IP routing table Set an IP routing table, where the IP routing table is used to control routing of data between the application process component and the virtual interface.
  • the embodiment of the present invention establishes a virtual interface, and establishes a communication between the switching service process component, the virtual interface, and the application process component, and binds the HoA to the virtual interface's IP address, and changes when the physical interface of the heterogeneous network changes. Switching the communication between the service process component and the mobility anchor still keeps the communication between the virtual interface and the application process component unaffected, thus supporting seamless handover of heterogeneous networks and ensuring continuity of service usage.
  • the handover service process component accesses the mobility anchor point and acquires the HoA of the mobility anchor point allocation.
  • communication between the switching service process component and the virtual interface is implemented by a character device driver.
  • the application process component sends uplink data to the virtual interface according to the IP routing table; and the switching service process component reads an uplink received by the virtual interface by using a character device driver. Data; the switching service process component encapsulates the read uplink data, and sends the uplink data to the mobility anchor through the IP tunnel through the first physical interface.
  • the first physical interface sends downlink data received from the mobility anchor to the handover service process component by using the IP tunnel; the handover service process component After the downlink data is decapsulated, the decapsulated downlink data is written into the virtual interface by using a character device driver; and the virtual interface forwards the received decapsulated downlink data to the application process component according to the IP routing table.
  • an IP tunnel between the handover service process component and the mobility anchor is established by one of the following protocols: a user datagram protocol UDP, a transmission control protocol TCP, and an IP encapsulation IP (IP) -in-IP), Generic Routing Encapsulation GRE and Generic Wireless Packet Service Tunneling Protocol GTP.
  • IP IP encapsulation IP
  • the heterogeneous network includes at least two wireless systems: 3GPP, 3GPP, WLAN, CDMA, CDMA, and global microwave access.
  • FIG. 5 is a schematic block diagram of another user equipment 50 in accordance with an embodiment of the present invention.
  • 5 includes a handover service process component 51, an application process component 52, a virtual interface 53, a first physical interface 54, and a second physical interface 55, and for convenience of explanation, shows a TCP/IP protocol stack 56 between the components, And a character device drive component 57.
  • Switching service process component 51 runs in user mode and is the core of heterogeneous network switching. Optionally, it can be implemented by client software to facilitate the deployment of user equipment in heterogeneous network switching technology. It can also be in the form of firmware by combining with hardware. Switching Service Process Components 51 Mainly complete the following work.
  • the switch service process component 51 calls the application program interface (API) provided by the operating system to establish a virtual interface 53 in the kernel mode.
  • the handover service process component 51 accesses the mobility anchor (such as HA) through a signaling mechanism such as MIPv4 or DSMIPv6, and the host parameters are allocated by the mobile anchor.
  • the host parameters include HoA; and the IP address of the virtual interface 53 is configured as HoA.
  • the switch service process component 51 can directly establish and move an IP tunnel of an anchor (such as HA) by using a TCP/UDP service provided by the operating system (such as a UDP Socket interface), and bind the tunnel to the currently used physical interface.
  • the switching service process component 51 sets the IP routing table of the user equipment, and routes the external IP data packet to the virtual interface 53 to forward the data of various upper layer applications through the virtual interface 53.
  • the switching service process exchanges data with the virtual interface 53 through the internal interface.
  • the internal interface is, for example, a character device drive component 57.
  • the application process component 52 includes various applications such as Skype, QQ, and the like.
  • the purpose of embodiments of the present invention is to provide these applications with service continuity functions when heterogeneous network handover.
  • the character device driver component 57 provides a way for the switching service process component 51 and the virtual interface 53 to communicate.
  • TCP/IP protocol stack 56 is a TCP/IP connection service provided by the operating system. Refer to Figure 2 The communication method in the mid-end TCP/IP protocol stack 20.
  • the first physical interface 54 and the second physical interface 55 are two physical interfaces in a heterogeneous network, typically implemented by dedicated chips and drive components.
  • the physical interface may include a WLAN interface, a 3GPP interface (including GSM, UMTS, or LTE, etc.), a WiMAX interface, and a CDMA interface, etc., to support various standards in the existing heterogeneous network.
  • the dotted line between the switching service process component 51 and the second physical interface 55 in FIG. 5 represents the IP that the handover service process component 51 will establish with the HA or P-GW after switching from the first physical interface 54 to the second physical interface 55.
  • the /UDP tunnel is bound to the second physical interface 55.
  • the user equipment of the embodiment of the present invention includes a user service switching service process component, an application process component, and a kernel interface virtual interface, a physical interface, and a TCP/IP protocol stack, etc., establish a virtual interface by switching service process components, and establish a handover service process. Communication between components, virtual interfaces, and application process components. By binding the HoA to the IP address of the virtual interface, when the physical interface of the heterogeneous network changes, the communication between the switching service process component and the mobility anchor is changed, and the communication remains virtual. The communication between the interface and the application process components is not affected, thus supporting seamless handover of heterogeneous networks and ensuring continuity of service usage.
  • FIG. 6 is a schematic flow chart of a method 600 for heterogeneous network switching according to another embodiment of the present invention, including the following.
  • the first physical interface is a WLAN interface
  • the second physical interface is a 3GPP interface.
  • the user equipment runs a handover service process component.
  • the user equipment can be installed in advance by the user equipment in the embodiment of the present invention. After the user device starts the client software, the switch service process component is run.
  • the embodiment of the invention is implemented by the client software, and the operating system may not need to be updated.
  • the seamless switching method of heterogeneous networks is easy to promote and deploy.
  • the user equipment first accesses the WLAN network to obtain an IP address.
  • the IP address is CoA, which binds the CoA to the physical interface.
  • the CoA is updated due to physical interface changes.
  • S620 Access a mobility anchor by using a signaling mechanism such as MIPv4 or DSMIPv6, and obtain a HoA allocated by the mobility anchor. S625, then calling an application program interface (API) provided by the operating system to establish a virtual interface in the kernel state, and configuring the virtual interface's IP address as a HoA.
  • API application program interface
  • the protocol stack of the user equipment and the network still follows the wireless communication, for example, the 3GPP standard, and only increases the implementation of the virtual interface that the user equipment generally supports based on the operating system, and is also easy to promote and deploy.
  • the character device driver component is only a way to implement communication between the switching service process component and the virtual interface, and communication between the two can be achieved through other internal interfaces.
  • the handover service process component can directly utilize the UDP service provided by the operating system, that is, establish and move an anchor, such as an HA IP/UDP tunnel, through the TCP/IP protocol stack, and bind the tunnel to the currently used WLAN. interface.
  • an anchor such as an HA IP/UDP tunnel
  • the IP/UDP tunnel can be replaced by other tunnel technologies, such as a GTP tunnel or a GRE tunnel, according to different IP protocol stacks selected by the network, and will not be described here.
  • the terminal is enabled to access the HA or P-GW of the mobile packet core network through the WLAN, thereby achieving service access consistency such as operator self-operated services, and unified charging and policy control, thereby enabling system management and cost saving.
  • S640 Set an IP routing table, and route the external IP data packet to the virtual interface, so that the data of the upper application component is forwarded through the virtual interface.
  • the IP routing table setting controls a specific application, such as a communication tool such as Skype, to forward to the virtual interface to provide a seamless handover service.
  • a specific application such as a communication tool such as Skype
  • the switching service process component establishes an IP/UDP tunnel with the mobility anchor, and also establishes communication with the virtual interface. Next, it is necessary to establish a connection between the application process component and the virtual interface.
  • Various applications on the upper layer such as Skype, call the operating system TCP/IP stack to communicate with the virtual interface.
  • FIG. 7 is a schematic diagram of a data forwarding process of a user equipment according to an embodiment of the present invention, where a solid line represents Line traffic, dotted line represents downstream traffic.
  • Upstream (that is, user equipment to the network) service flow taking the application Skype as an example:
  • the uplink data of the Skype is forwarded to the virtual interface by the application process component after being encapsulated by the TCP/IP protocol stack.
  • the switching service process component reads the data packet of the virtual interface through the character device driver component, and then sends the data to the HA/P-GW through the WLAN interface through the IP/UDP connection.
  • Downstream (that is, network to user equipment) traffic
  • the WLAN interface receives the IP packet from the HA or the P-GW, and adopts the IP/UDP tunnel encapsulation. Since the data packet is carried in the IP tunnel established by the handover service process component and the mobility anchor, it is first forwarded to the handover service. Process component.
  • the switching service process component obtains the Skype IP packet after decapsulating the encapsulated UDP, and then writes the virtual interface through the character device driver component.
  • the virtual interface forwards the IP packet to the application process component because the IP packet is carried over the TCP or UDP connection created by the application process component (Skype).
  • S650 The user equipment moves out of the WLAN area and accesses the 3GPP network.
  • the WLAN interface of the user equipment switches to the 3GPP interface, that is, switches from the first physical interface to the second physical interface.
  • the handover service process component learns the physical interface change, the IP/UDP tunnel established with the mobility anchor, such as the HA or the P-GW, is bound from the WLAN interface to the 3GPP interface.
  • the mobility anchor such as the HA or the P-GW
  • the application process component Since the virtual interface does not change, the application process component is not aware of changes to the physical interface.
  • Various upper-layer applications such as Skype can use the service without interruption, and the specific forwarding process is as described above.
  • the embodiments of the present invention only illustrate the process of switching from a WLAN network to a 3GPP network, and vice versa.
  • the switching between any two physical interfaces in the heterogeneous network in the embodiment of the present invention is not limited, and the actual physical interface is taken as the standard.
  • the embodiment of the present invention establishes a virtual interface, and establishes a communication between the switching service process component, the virtual interface, and the application process component, and binds the HoA to the virtual interface's IP address, and changes when the physical interface of the heterogeneous network changes. Switching the communication between the service process component and the mobility anchor still keeps the communication between the virtual interface and the application process component unaffected, thus supporting seamless handover of heterogeneous networks and ensuring continuity of service usage.
  • FIG. 8 is a schematic block diagram of another user equipment 80 according to an embodiment of the present invention.
  • User device 80 includes a processor 81, a memory 82, a first physical interface 83, and a second physical interface 84.
  • the processor 81 can be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a ready-to-use programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component,
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA ready-to-use programmable gate array
  • the methods, steps, and logic blocks disclosed in the embodiments of the present invention may be implemented or executed and communicated bi-directionally with other devices over a bus.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present invention may be directly implemented as processor execution completion or performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory 82, and the processor 81 reads the information in the memory 82 and combines the hardware to perform the steps of the above method.
  • Memory 82 and processor 81 may also be integrated into a physical module to which embodiments of the present invention are applied, on which the programs implementing the embodiments of the present invention are stored and executed.
  • the memory 82 stores instructions required by the processor to perform the following methods.
  • the processor 81 invokes a handover service process, where the handover service process is used to establish a virtual interface and configure an address of the virtual interface as a home address (HoA), and establish a relationship between the handover service process and the virtual interface. And communicating to establish an internetworking protocol (IP) tunnel with the mobility anchor, and binding the IP tunnel to a first physical interface currently in use; and also for setting an IP routing table,
  • IP internetworking protocol
  • the IP routing table is used to control routing of data between the application process and the virtual interface; and is further configured to: after the first physical interface is switched to the second physical interface, the IP tunnel from the first The physical interface is bound to the second physical interface, where the first physical interface and the second physical interface are two physical interfaces of a heterogeneous network.
  • the processor 81 also invokes an application process, wherein the application process is configured to send data to the virtual interface and receive data forwarded by the virtual interface according to the IP routing table.
  • the processor further invokes the handover service process, configured to access the mobility anchor and obtain the mobility anchor before establishing an IP tunnel with the mobility anchor point.
  • Point assigned HoA configured to access the mobility anchor and obtain the mobility anchor before establishing an IP tunnel with the mobility anchor point.
  • the processor further invokes a character device driver for implementing communication between the switching service process and the virtual interface.
  • the processor invoking the application process is specifically configured to send uplink data to the virtual interface according to the IP routing table; and the processor invokes the handover service process to pass the The character device driver reads the uplink data received by the virtual interface; The processor instructs the handover service process to encapsulate the read uplink data, and then sends the mobility data to the mobility anchor point through the IP tunnel through the first physical interface.
  • the processor sends, by the first physical interface, downlink data received from the mobility anchor to the handover service process by using the IP tunnel; After the switching service process decapsulates the downlink data, the decapsulated downlink data is written into the virtual interface by using the character device driver; the virtual interface receives the decapsulated downlink data according to the IP address.
  • the routing table is forwarded to the application process.
  • the processor invokes the handover service process to establish an IP tunnel with the mobility anchor by using one of the following protocols: a User Datagram Protocol (UDP), a Transmission Control Protocol (TCP) , IP-encapsulated IP (IP-in-IP), Generic Routing Encapsulation (GRE), and General Packet Radio Service Tunneling Protocol (GTP).
  • UDP User Datagram Protocol
  • TCP Transmission Control Protocol
  • IP-encapsulated IP IP-in-IP
  • GRE Generic Routing Encapsulation
  • GTP General Packet Radio Service Tunneling Protocol
  • the user equipment works in a heterogeneous network of at least two of the following: Third Generation Partnership Project (3GPP), Wireless Local Area Network (WLAN), Code Division Multiple Access (CDMA), global Microwave Interconnect (WiMAX).
  • 3GPP Third Generation Partnership Project
  • WLAN Wireless Local Area Network
  • CDMA Code Division Multiple Access
  • WiMAX global Microwave Interconnect
  • the embodiment of the present invention invokes a handover service process by a processor to establish a virtual interface, and establishes a communication between a handover service process, a virtual interface, and an application process, by binding the HoA to the IP address of the virtual interface, and when the physical of the heterogeneous network is When the interface is changed, the communication between the switching service process and the mobility anchor is changed, and the communication between the virtual interface and the application process is still not affected, thereby supporting seamless handover of the heterogeneous network and ensuring service continuity.
  • the disclosed systems, devices, and methods may be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another The system, or some features can be ignored, or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium.
  • the technical solution of the present invention which is essential to the prior art or part of the technical solution, may be embodied in the form of a software product stored in a storage medium, including
  • the instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present invention.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes. .

Landscapes

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

Abstract

一种用户设备及异构网络切换的方法。用户设备包括切换服务进程组件、应用进程组件、第一物理接口和第二物理接口:切换服务进程组件建立虚拟接口且将虚拟接口的IP地址配置为HoA并建立切换服务进程组件与虚拟接口之间的通信;建立与移动锚点之间的IP隧道,且将IP隧道绑定到当前使用的第一物理接口;设置IP路由表,IP路由表用于控制应用进程组件和虚拟接口之间数据的路由;当第一物理接口切换到第二物理接口后,将IP隧道从第一物理接口绑定到第二物理接口,第一物理接口和第二物理接口是异构网络的两种物理接口,应用进程组件根据IP路由表向虚拟接口发送数据和接收虚拟接口转发的数据。本方案支持异构网络无缝切换。

Description

用户设备及异构网络切换的方法 技术领域
本发明实施例涉及无线通信领域, 并且更具体地, 涉及用户设备及异构 网络切换的方法。 背景技术
近年来, 2G (第二代)、 3G(第三代)、 LTE(长期演进, Long Term Evolution ) 和 WLAN ( Wireless Local Area Networks, 无线局域网 )等移动网络技术得 到了较快发展。 2G、 3G、 LTE和 WLAN在网络的覆盖范围、 带宽及移动性 等方面存在较大差异, 由这些技术主导的网络融合组网构成异构网络 ( Heterogeneous Networks ), 能够实现优势互补。 其中, 终端在异构网络间 的无缝切换可以大幅提升用户体验,异构网络间的无缝切换技术是实现网络 融合的重点技术。
当前异构网络之间的无缝切换主要基于移动 IP ( Internet Protocol, 网际 互连协议)技术, 分为基于网络 (Network-based)和基于终端 (Client-based)的 两大类技术架构。
基于网络的技术架构主要有 PMIP ( Proxy Mobile IP )和 GTP ( General Packet Radio Service Tunneling Protocol, GPRS隧道协议;), 特点是各异构网 络的接入网关采用 IP类隧道接入移动锚点 (Mobility Anchor),从而保证终端 在网络间切换时 IP地址不变。 其中移动锚点可以是 P-GW ( PDN Gateway, PDN网关)或 HA ( Home Agent, 家乡代理)。
基于终端的技术架构主要有 MIPv4( Mobile IP Version 4,移动 IP版本 4 ) 和 DSMIPv6 ( Dual Stack Mobile IP Version 6, 双栈移动 IP版本 6 )技术等, 特点是终端直接采用 IP类协议接入移动锚点, 屏蔽网络间切换时底层 IP改 变对应用层的影响。
不管采用基于网络还是基于终端的任一种技术架构,都需要用户设备操 作系统配合, 保证在异构网络切换时可以维持 TCP ( Transmission Control Protocol, 传输控制协议)连接, 从而实现异构网络无缝切换。 然而当前主 流移动终端操作系统例如安卓 (Android ) 均没有能力提供上述技术支持。 作为一种实现方法, 为了解决这个问题, 可选地, 需要修改用户设备操作系 统的 IP/TCP协议栈。 由于修改用户设备操作系统涉及协调操作系统提供商 和众多用户设备的厂商, 所以实际部署这样的用户设备困难, 因此异构网络 无缝切换方案难于实现。 发明内容
有鉴于此, 本发明实施例提供一种用户设备及异构网络切换的方法, 以 实现异构网络无缝切换。
第一方面, 提供了一种用户设备, 包括切换服务进程组件、 应用进程组 件、 第一物理接口和第二物理接口: 切换服务进程组件, 用于建立虚拟接口 且将虚拟接口的地址配置为家乡地址(HoA ), 并建立切换服务进程组件与 虚拟接口之间的通信; 且还用于建立与移动锚点之间的网际互连协议(IP ) 隧道,且将 IP隧道绑定到当前使用的第一物理接口;还用于设置 IP路由表, 其中 IP路由表用于控制应用进程组件和虚拟接口之间数据的路由; 还用于 当第一物理接口切换到第二物理接口后, 将 IP 隧道从第一物理接口绑定到 第二物理接口,其中第一物理接口和第二物理接口是异构网络的两种物理接 口, 应用进程组件, 用于根据 IP路由表向虚拟接口发送数据和接收虚拟接 口转发的数据。
在第一种可能的实现方式中, 切换服务进程组件, 还用于在建立与移动 锚点之间的 IP隧道前, 接入移动锚点并获取移动锚点分配的 HoA。
结合第一方面或第一方面的第一种可能的实现方式,在第二种可能的实 现方式中, 用户设备还包括字符设备驱动组件: 字符设备驱动组件, 用于实 现切换服务进程组件和虚拟接口之间的通信。
结合第一方面的第二种可能的实现方式, 在第三种可能的实现方式中, 应用进程组件具体用于根据 IP路由表将上行数据发送到虚拟接口; 切换服 务进程组件通过字符设备驱动组件读取虚拟接口接收的上行数据; 切换服务 进程组件将读取的上行数据封装后, 通过 IP 隧道经第一物理接口发送到移 动错点。
结合第一方面的第二种可能的实现方式, 在第四种可能的实现方式中, 第一物理接口将从移动锚点接收的下行数据通过 IP 隧道发送到切换服务进 程组件; 切换服务进程组件将下行数据解封装后, 将解封装的下行数据通过 字符设备驱动写入虚拟接口; 虚拟接口将接收的解封装的下行数据根据 IP 路由表转发到应用进程组件。
结合第一方面或第一方面的上述可能的实现方式,在第五种可能的实现 方式中, 切换服务进程组件通过以下协议之一建立与移动锚点之间的 IP 隧 道: 用户数据报协议 ( UDP )、传输控制协议 ( TCP )、 IP封装 IP ( IP-in-IP )、 通用路由封装( GRE )和通用无线分组业务隧道协议( GTP )。
结合第一方面或第一方面的上述可能的实现方式,在第六种可能的实现 方式中, 用户设备在至少两种以下制式的异构网络中工作: 第三代合作伙伴 计划 (3GPP )、 无线局域网 (WLAN )、 码分多址(CDMA )、 全球敫波互联 接入 ( WiMAX )。
第二方面, 提供了一种异构网络切换的方法, 包括: 在第一种可能的实 现方式中, 建立虚拟接口, 且将虚拟接口的地址配置为家乡地址(HoA ); 建立切换服务进程组件与虚拟接口之间的通信; 建立切换服务进程组件与移 动锚点之间的网际互连协议(IP )隧道, 且将 IP隧道绑定到当前使用的第一 物理接口; 设置 IP路由表, 其中 IP路由表用于控制应用进程组件和虚拟接 口之间数据的路由; 当第一物理接口切换到第二物理接口后, 将 IP 隧道从 第一物理接口绑定到第二物理接口,其中第一物理接口和第二物理接口是异 构网络的两种物理接口。
在第一种可能的实现方式中, 在建立与移动锚点之间的 IP 隧道前, 切 换服务进程组件接入移动锚点并获取移动锚点分配的 HoA。
结合第二方面或第二方面的第一种可能的实现方式,在第二种可能的实 现方式中, 通过字符设备驱动实现切换服务进程组件和虚拟接口之间的通 信。
结合第二方面的第二种可能的实现方式, 在第三种可能的实现方式中, 应用进程组件根据 IP路由表将上行数据发送到虚拟接口; 切换服务进程组 件通过字符设备驱动读取虚拟接口接收的上行数据; 切换服务进程组件将读 取的上行数据封装后, 通过 IP隧道经第一物理接口发送到移动锚点。
结合第二方面的第二种可能的实现方式, 在第四种可能的实现方式中, 第一物理接口将从移动锚点接收的下行数据通过 IP 隧道发送到切换服务进 程组件; 切换服务进程组件将下行数据解封装后, 将解封装的下行数据通过 字符设备驱动写入虚拟接口; 虚拟接口将接收的解封装的下行数据根据 IP 路由表转发到应用进程组件。 结合第二方面或第二方面的上述可能的实现方式,在第五种可能的实现 方式中, 通过以下协议之一建立切换服务进程组件与移动锚点之间的 IP 隧 道: 用户数据报协议 ( UDP )、传输控制协议 ( TCP )、 IP封装 IP ( IP-in-IP )、 通用路由封装(GRE )和通用无线分组业务隧道协议(GTP )。
结合第二方面或第二方面的上述可能的实现方式,在第六种可能的实现 方式中, 异构网络包括以下至少两种制式的无线系统: 第三代合作伙伴计划
( 3GPP )、 无线局域网 ( WLAN )、 码分多址( CDMA )、 全球敫波互联接入
( WiMAX )。
第三方面, 提供了一种用户设备, 包括处理器、 存储器、 第一物理接口 和第二物理接口: 存储器存储处理器执行以下方法所需的指令; 处理器, 用 于调用切换服务进程,其中切换服务进程用于建立虚拟接口且将虚拟接口的 地址配置为家乡地址(HoA ), 并建立切换服务进程与虚拟接口之间的通信; 且还用于建立与移动锚点之间的网际互连协议( IP )隧道, 且将 IP隧道绑定 到当前使用的第一物理接口; 还用于设置 IP路由表, 其中 IP路由表用于控 制应用进程和虚拟接口之间数据的路由; 还用于当第一物理接口切换到第二 物理接口后, 将 IP 隧道从第一物理接口绑定到第二物理接口, 其中第一物 理接口和第二物理接口是异构网络的两种物理接口; 处理器, 还用于调用应 用进程, 其中应用进程用于根据 IP路由表向虚拟接口发送数据和接收虚拟 接口转发的数据。
在第一种可能的实现方式中, 处理器还调用切换服务进程, 用于在建立 与移动锚点之间的 IP隧道前, 接入移动锚点并获取移动锚点分配的 HoA。
结合第三方面或第三方面的第一种可能的实现方式,在第二种可能的实 现方式中, 处理器还调用字符设备驱动, 用于实现切换服务进程和虚拟接口 之间的通信。
结合第三方面的第二种可能的实现方式, 在第三种可能的实现方式中, 处理器调用应用进程具体用于根据 IP路由表将上行数据发送到虚拟接口; 处理器调用切换服务进程通过字符设备驱动读取虚拟接口接收的上行数据; 处理器调用切换服务进程将读取的上行数据封装后, 通过 IP 隧道经第一物 理接口发送到移动锚点。
结合第三方面的第二种可能的实现方式, 在第四种可能的实现方式中, 处理器将第一物理接口将从移动锚点接收的下行数据通过 IP 隧道发送到切 换服务进程; 处理器调用切换服务进程以将下行数据解封装后, 将解封装的 下行数据通过字符设备驱动写入虚拟接口; 虚拟接口将接收的解封装的下行 数据根据 IP路由表转发到应用进程。
结合第三方面或第三方面的上述可能的实现方式,在第五种可能的实现 方式中,处理器调用切换服务进程通过以下协议之一建立与移动锚点之间的 IP隧道:用户数据报协议( UDP )、传输控制协议( TCP )、 IP封装 IP ( IP-in-IP )、 通用路由封装(GRE )和通用无线分组业务隧道协议(GTP )。
结合第三方面或第三方面的上述可能的实现方式,在第六种可能的实现 方式中, 用户设备在至少两种以下制式的异构网络中工作: 第三代合作伙伴 计划 (3GPP )、 无线局域网 (WLAN )、 码分多址(CDMA )、 全球 波互联 接入 ( WiMAX )。
上述技术方案中, 用户设备包括切换服务进程组件、 应用进程组件、 第 一物理接口和第二物理接口, 通过切换服务进程组件建立虚拟接口, 并且建 立切换服务进程组件、虚拟接口以及应用进程组件之间的通信,通过将 HoA 与虚拟接口的 IP地址绑定, 当异构网络的物理接口变更时, 改变切换服务 进程组件和移动锚点的通信,仍保持虚拟接口和应用进程组件之间的通信不 受影响, 从而支持异构网络无缝切换, 保证业务使用连续性。 附图说明
为了更清楚地说明本发明实施例的技术方案, 下面将对实施例或现有技 术描述中所需要使用的附图作筒单地介绍, 显而易见地, 下面描述中的附图 仅仅是本发明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造 性劳动的前提下, 还可以根据这些附图获得其他的附图。
图 1是现有技术中用户设备的操作系统的 TCP/IP协议栈的示意图。 图 2是本发明实施例的端到端 TCP/IP协议栈的示意图。
图 3是本发明实施例的用户设备的示意框图。
图 4是本发明实施例的异构网络切换的方法的示意流程图。
图 5是本发明实施例的另一用户设备的示意框图。
图 6是本发明另一实施例的异构网络切换的方法的示意流程图。
图 7是本发明实施例的用户设备内部数据转发过程的示意图。
图 8是本发明实施例的另一种用户设备的示意框图。 具体实施方式
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行 清楚、 完整地描述, 显然, 所描述的实施例是本发明一部分实施例, 而不是 全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有做出创 造性劳动前提下所获得的所有其他实施例, 都属于本发明保护的范围。
本发明的技术方案, 可以应用于各种混网的通信系统, 例如: 全球移动 通信系统( GSM, Global System of Mobile communication ),码分多址( CDMA, Code Division Multiple Access )系统,通用移动通信系统( UMTS , Universal Mobile Telecommunications System ),长期演进 ( LTE, Long Term Evolution )、 无线局域网 (WLAN, Wireless Local Area Networks )和全球微波互联接入 ( WiMAX, Worldwide Interoperability for Microwave Access )等。
用户设备 ( UE , User Equipment ) , 也可称之为移动终端 ( Mobile Terminal ), 移动用户设备, 筒称终端等, 可以经无线接入网 (例如, RAN, Radio Access Network )与一个或多个核心网进行通信, 用户设备可以是移动 终端, 如移动电话(或称为"蜂窝"电话)和具有移动终端的计算机, 例如, 可以是便携式、 袖珍式、 手持式、 计算机内置的或者车载的移动装置, 它们 与无线接入网交换语音和 /或数据。
另外, 本文中术语"系统"和"网络"在本文中常被可互换使用。 本文中术 语中的字符 "/" , 一般表示前后关联对象是一种 "或" 的关系。
图 1是现有技术中用户设备的操作系统的 TCP/IP协议栈 10的示意图。 如图 1所示, TCP/IP协议栈 10示意包括了 OSI( Open System Interconnection, 开放系统互联)模型七层协议中 LI ( Layer 1 , 网络层) 11 , L2 ( Layer 2, 数据链路层) 12, IP层 13、 TCP/UDP层 14和应用 (applications, 筒写为 APP )层 15等。 其中 L2包括多个物理接口 (IF, Interface ), 例如 IF1、 IF2 至 IFn等, 其中 n指示序列号, 可以是正整数。
各种应用程序基于操作系统提供的 TCP/UDP服务进行通信。 TCP/IP层 绑定在物理接口上, 具体使用哪个物理接口进行数据传输根据当前接入的网 络确定。 当发生异构网络之间的切换时, 物理接口改变, 操作系统清除当前 接口上的 TCP/UDP连接, 同时通告应用程序物理接口变更。 会话的连续性 接下来只能最终依赖于应用程序处理, 无法保证切换过程会话连续。 当前主流操作系统并不支持异构网络无缝切换能力,如果修改操作系统 不利于规模部署, 这正是异构网络无缝切换方案难于实施的瓶颈所在。 本发 明实施例提供了一种用户设备, 可以在不修改操作系统的前提下实现异构网 络无缝切换。
图 2是本发明实施例的端到端 TCP/IP协议栈 20的示意图。 此处, 端到 端包括用户设备与网络设备, 以及网络设备之间的关系。 图 2中示出了用户 设备 21、 移动锚点 22和应用服务器 23之间的协议栈。 其中用户设备 21包 括 L1和 L2、 IP ( CoA )、 UDP、 IP ( HoA )、 UDP/TCP和 APP。 移动锚点 22 包括与用户设备 21各层对应的 L1和 L2、 IP ( CoA )、 UDP、 IP ( HoA )、 UDP/TCP和 APP, 以及与应用服务器 23各层对应的 L1和 L2、 IP ( HoA )、 UDP/TCP和 APP。 应用服务器 23包括与移动锚点 22各层对应的 L1和 L2、 IP ( HoA )、 UDP/TCP和 APP。
图中例示了基于 UDP隧道的协议栈, 可选的, UDP隧道还可以由其他 隧道技术代替, 例如 IP封装 IP ( IP-in-IP )、 通用路由封装( General Routing Encapsulation, GRE )或通用无线分组业务隧道协议( General packet radio Service Tunnel Protocal, GTP )等, 可以统称为 IP隧道。
用户设备 21通过无线网络例如 WLAN或 3GPP等与移动锚点 22建立 IP隧道, 且移动锚点 22与应用服务器 23建立连接。 HoA ( home address, 家乡地址) 由移动锚点分配, 在网络切换过程中始终不变。 CoA ( Core of Address, 转交地址) 由无线网络例如 WLAN或 3GPP分配, 切换过程中可 以改变。
图 3是本发明实施例的用户设备 30的示意框图。用户设备 30包括切换 服务进程组件 31、 应用进程组件 32、 第一物理接口 33和第二物理接口 34。
切换服务进程组件 31建立虚拟接口且将所述虚拟接口的 IP地址配置为 家乡地址(HoA ), 并建立所述切换服务进程组件与所述虚拟接口之间的通 信; 且还建立与所述移动锚点之间的网际互连协议(IP )隧道, 且将所述 IP 隧道绑定到当前使用的第一物理接口; 还设置 IP路由表, 其中所述 IP路由 表用于控制应用进程组件 32和所述虚拟接口之间数据的路由; 还当所述第 一物理接口切换到第二物理接口后, 将所述 IP 隧道从所述第一物理接口绑 定到所述第二物理接口, 其中所述第一物理接口和所述第二物理接口是异构 网络的两种物理接口。 应用进程组件 32根据所述 IP路由表向所述虚拟接口发送数据和接收所 述虚拟接口转发的数据。
本发明实施例的用户设备包括切换服务进程组件、 应用进程组件、 第一 物理接口和第二物理接口, 通过切换服务进程组件建立虚拟接口, 并且建立 切换服务进程组件、 虚拟接口以及应用进程组件之间的通信, 通过将 HoA 与虚拟接口的 IP地址绑定, 当异构网络的物理接口变更时, 改变切换服务 进程组件和移动锚点的通信,仍保持虚拟接口和应用进程组件之间的通信不 受影响, 从而支持异构网络无缝切换, 保证业务使用连续性。
可选的, 作为不同的实施例, 切换服务进程组件还用于在建立与所述移 动锚点之间的 IP 隧道前, 接入所述移动锚点并获取所述移动锚点分配的 HoA。
可选的, 作为不同的实施例, 用户设备还包括字符设备驱动组件: 所述 字符设备驱动组件, 用于实现所述切换服务进程组件和所述虚拟接口之间的 通信。
可选的, 作为不同的实施例, 所述应用进程组件具体用于根据所述 IP 路由表将上行数据发送到所述虚拟接口; 所述切换服务进程组件通过所述字 符设备驱动组件读取所述虚拟接口接收的上行数据; 所述切换服务进程组件 将读取的所述上行数据封装后, 通过所述 IP 隧道经所述第一物理接口发送 到所述移动锚点。
可选的, 作为不同的实施例, 所述第一物理接口将从所述移动锚点接收 的下行数据通过所述 IP 隧道发送到所述切换服务进程组件; 所述切换服务 进程组件将所述下行数据解封装后,将解封装的下行数据通过字符设备驱动 写入所述虚拟接口; 所述虚拟接口将接收的所述解封装的下行数据根据 IP 路由表转发到所述应用进程组件。
可选的, 作为不同的实施例, 所述切换服务进程组件通过以下协议之一 建立与所述移动锚点之间的 IP隧道: 用户数据报协议(UDP )、 传输控制协 议(TCP )、 IP封装 IP ( IP-in-IP )、 通用路由封装(GRE )和通用无线分组 业务隧道协议(GTP )。
可选的, 作为不同的实施例, 所述用户设备在至少两种以下制式的异构 网络中工作: 第三代合作伙伴计划 (3GPP )、 无线局域网 (WLAN )、 码分 多址( CDMA ), 全球微波互联接入 ( WiMAX )。 基于图 3中的用户设备,图 4是本发明实施例的异构网络切换的方法 40 的示意流程图, 包括以下内容。
S41 , 建立虚拟接口, 且将所述虚拟接口的 IP 地址配置为家乡地址 ( HoA )。
S42, 建立切换服务进程组件与所述虚拟接口之间的通信。
543, 建立所述切换服务进程组件与所述移动锚点之间的 IP隧道, 且将 所述 IP隧道绑定到当前使用的第一物理接口。
544, 设置 IP路由表, 其中所述 IP路由表用于控制应用进程组件和所 述虚拟接口之间数据的路由。
S45, 当所述第一物理接口切换到第二物理接口后, 将所述 IP隧道从所 述第一物理接口绑定到所述第二物理接口, 其中所述第一物理接口和所述第 二物理接口是异构网络的两种物理接口。
本发明实施例通过建立虚拟接口, 并且建立切换服务进程组件、 虚拟接 口以及应用进程组件之间的通信, 通过将 HoA与虚拟接口的 IP地址绑定, 当异构网络的物理接口变更时, 改变切换服务进程组件和移动锚点的通信, 仍保持虚拟接口和应用进程组件之间的通信不受影响,从而支持异构网络无 缝切换, 保证业务使用连续性。
可选的, 作为不同的实施例, 在所述建立与所述移动锚点之间的 IP 隧 道前, 切换服务进程组件接入所述移动锚点并获取所述移动锚点分配的 HoA。
可选的, 作为不同的实施例, 通过字符设备驱动实现所述切换服务进程 组件和所述虚拟接口之间的通信。
可选的, 作为不同的实施例, 所述应用进程组件根据所述 IP路由表将 上行数据发送到所述虚拟接口; 所述切换服务进程组件通过字符设备驱动读 取所述虚拟接口接收的上行数据; 所述切换服务进程组件将读取的所述上行 数据封装后, 通过所述 IP隧道经所述第一物理接口发送到所述移动锚点。
可选的, 作为不同的实施例, 所述第一物理接口将从所述移动锚点接收 的下行数据通过所述 IP 隧道发送到所述切换服务进程组件; 所述切换服务 进程组件将所述下行数据解封装后,将解封装的下行数据通过字符设备驱动 写入所述虚拟接口; 所述虚拟接口将接收的所述解封装的下行数据根据 IP 路由表转发到所述应用进程组件。 可选的, 作为不同的实施例, 通过以下协议之一建立所述切换服务进程 组件与所述移动锚点之间的 IP隧道: 用户数据报协议 UDP、 传输控制协议 TCP, IP封装 IP ( IP-in-IP )、 通用路由封装 GRE和通用无线分组业务隧道 协议 GTP。
可选的, 作为不同的实施例, 异构网络包括以下至少两种制式的无线系 统: 第三代合作伙伴计划 3GPP、 无线局域网 WLAN、 码分多址 CDMA、 全 球微波互联接入 WiMAX。
图 5是本发明实施例的另一用户设备 50的示意框图。 图 5中包括切换 服务进程组件 51、应用进程组件 52、虚拟接口 53、 第一物理接口 54和第二 物理接口 55 , 以及为方便说明, 示出各组件之间的 TCP/IP协议栈 56, 以及 字符设备驱动组件 57。
切换服务进程组件 51运行在用户态, 是实现异构网络切换的核心。 可 选的, 可以通过客户端软件实现, 方便用户设备在异构网络切换技术中的规 模部署。 也可以, 通过与硬件结合, 以固件形式存在。 切换服务进程组件 51 主要完成如下工作。
切换服务进程组件 51 调用操作系统提供的应用程序接口(API , Application Program Interface)在内核态建立虚拟接口 53。 切换服务进程组件 51例如通过 MIPv4或 DSMIPv6等信令机制接入移动锚点 (如 HA), 由移动 锚点分配主机参数, 主机参数中包括 HoA; 将虚拟接口 53的 IP地址配置为 HoA。 切换服务进程组件 51可直接利用操作系统提供的 TCP/UDP服务 (如 UDP Socket接口)建立和移动锚点 (如 HA)的 IP隧道,并将该隧道绑定到当前 使用的物理接口。 切换服务进程组件 51设置用户设备的 IP路由表, 将对外 的 IP数据包路由到虚拟接口 53 ,使各种上层应用的数据通过虚拟接口 53转 发。 切换服务进程通过内部接口与虚拟接口 53 交换数据。 可选的, 内部接 口例如是字符设备驱动组件 57。异构网络间切换时由切换服务进程组件重新 绑定当前物理接口, 上层的应用进程组件 52无感知。
应用进程组件 52包括各种应用程序, 如 Skype、 QQ等。 本发明实施例 的目的是为这些应用程序提供异构网络切换时的业务连续功能。
字符设备驱动组件 57提供切换服务进程组件 51和虚拟接口 53进行通 信的方式。
TCP/IP协议栈 56为由操作系统提供的 TCP/IP连接服务, 可以参考图 2 中端到端 TCP/IP协议栈 20中的通信方式。
第一物理接口 54和第二物理接口 55是异构网络中的两种物理接口,一 般由专用芯片和驱动组件实现。 在异构网络中, 举例来说, 物理接口可以包 括 WLAN接口、 3GPP接口(包括 GSM、 UMTS或 LTE等制式)、 WiMAX接 口和 CDMA接口等, 用于支持现有异构网络中的各种制式。 图 5中切换服 务进程组件 51和第二物理接口 55之间的虚线代表当从第一物理接口 54切 换到第二物理接口 55后, 切换服务进程组件 51将与 HA或 P-GW建立的 IP/UDP隧道绑定到第二物理接口 55上。
本发明实施例的用户设备包括用户态的切换服务进程组件、应用进程组 件和内核态的虚拟接口、 物理接口及 TCP/IP协议栈等, 通过切换服务进程 组件建立虚拟接口, 并且建立切换服务进程组件、 虚拟接口以及应用进程组 件之间的通信, 通过将 HoA与虚拟接口的 IP地址绑定, 当异构网络的物理 接口变更时, 改变切换服务进程组件和移动锚点的通信, 仍保持虚拟接口和 应用进程组件之间的通信不受影响, 从而支持异构网络无缝切换, 保证业务 使用连续性。
接下来, 为了方便说明, 参考图 5的用户设备的架构, 以从 WLAN接 口切换到 3GPP接口为例, 进行异构网络切换的说明, 但本发明实施例不限 于哪两种具体物理接口之间的切换。 图 6是本发明另一实施例的异构网络切 换的方法 600的示意流程图, 包括以下内容。 其中第一物理接口为 WLAN 接口, 第二物理接口为 3GPP接口。
S610, 用户设备运行切换服务进程组件。
用户设备事先可以安装本发明实施例的客户端软件。待用户设备启动该 客户端软件后, 运行切换服务进程组件。
优选地, 通过客户端软件实现本发明实施例, 可以无需更新操作系统。 这样, 异构网络无缝切换方法筒便, 易于推广和部署
S615, 用户设备首先接入 WLAN网络, 获得 IP地址。
该 IP地址即 CoA, 将 CoA与物理接口绑定。 在异构网络切换的过程中 由于物理接口变更, CoA会更新。 接下来, 由用户设备的切换服务进程组件 完成如下工作
S620, 通过 MIPv4或 DSMIPv6等信令机制接入移动锚点, 获得移动锚 点分配的 HoA。 S625 , 然后, 调用操作系统提供的应用程序接口(API)在内核态建立虚 拟接口, 将该虚拟接口的 IP地址配置为 HoA。
本发明实施例用户设备和网络的协议栈仍旧遵循无线通信例如 3GPP标 准, 仅仅增加了用户设备基于操作系统普遍支持的虚拟接口的实现, 同样易 于推广和部署。
S630, 通过字符设备驱动组件与虚拟接口交换数据。
字符设备驱动组件仅是用于实现切换服务进程组件和虚拟接口之间通 信的一种方式, 还可以通过其他内部接口实现两者的通信。
S635 , 与移动锚点建立 IP隧道并将该 IP隧道绑定到当前使用的物理接 口。
在 WLAN网络中, 切换服务进程组件可直接利用操作系统提供的 UDP 服务, 即通过 TCP/IP协议栈建立和移动锚点如 HA的 IP/UDP隧道, 并将该 隧道绑定到当前使用的 WLAN接口。 可选的, 根据网络选用的不同 IP协议 栈, IP/UDP隧道可以由其他隧道技术代替, 例如 GTP隧道或 GRE隧道等, 此后不再赘述。
基于用户设备发起的 IP隧道机制, 对接入网络无要求, 方便了包含各 种制式的异构网络之间的切换。 此外, 支持终端通过 WLAN接入移动分组 核心网的 HA或 P-GW, 实现业务访问一致性例如运营商自营业务, 以及统 一的计费和策略控制, 从而可以筒化系统管理, 节省成本。
S640, 设置 IP路由表, 将对外的 IP数据包路由到虚拟接口, 使上层的 应用程序组件的数据通过虚拟接口转发。
可选的, 通过 IP路由表设置控制特定应用例如 Skype等通信工具转发 到虚拟接口, 以提供无缝切换服务。
此时, 切换服务进程组件与移动锚点建立了 IP/UDP隧道, 且还与虚拟 接口建立了通信, 接下来需要建立应用进程组件与虚拟接口的连接。
S645 , 应用进程组件与虚拟接口进行通信。
上层的各种应用程序如 Skype等调用操作系统 TCP/IP协议栈与虚拟接 口进行通信。
当建立了应用进程组件、 虚拟接口和切换服务进程组件之间的通信连 接, 可以进行数据的转发。 参考图 7, 具体转发流程如下。 图 7是本发明实 施例的用户设备内部数据转发过程的示意图, 其中出于清楚, 以实线代表上 行业务流, 虚线代表下行业务流。
上行 (也就是用户设备到网络)业务流, 以应用程序 Skype为例:
1、 由于设置了 IP路由表, 根据该 IP路由表, Skype的上行数据由应用 进程组件经过 TCP/IP协议栈的封装后, 先转发到虚拟接口。
2、 切换服务进程组件通过字符设备驱动组件读取虚拟接口的数据包后 通过 IP/UDP连接, 经由 WLAN接口, 将数据发送到 HA/P-GW。
下行 (也就是网络到用户设备)业务流:
1、 WLAN接口收到来自 HA或 P-GW的 IP报文, 采用了 IP/UDP隧道 封装, 由于该数据包承载于切换服务进程组件与移动锚点建立的 IP 隧道, 则首先转发给切换服务进程组件。
2、 切换服务进程组件对封装的 UDP解封装后获取 Skype的 IP报文, 然后通过字符设备驱动组件写入虚拟接口。
3、 由于该 IP报文承载于应用进程组件(Skype )创建的 TCP或 UDP 连接, 虚拟接口将 IP报文转发给应用进程组件。
S650, 用户设备移出 WLAN区域, 接入到 3GPP网络。
用户设备的 WLAN接口切换到 3GPP接口, 即从第一物理接口切换到 第二物理接口。
S655 , 当切换服务进程组件获知物理接口变更后, 将与移动锚点例如 HA或 P-GW建立的 IP/UDP隧道从 WLAN接口绑定到 3GPP接口上。
由于虚拟接口没有变化, 所以应用进程组件对物理接口的变更无感知。 上层各种应用程序如 Skype可以不中断使用业务, 具体转发流程同前所述。
出于筒洁, 本发明实施例仅示意了从 WLAN网络切换到 3GPP网络的 过程, 反之亦然。 本发明实施例异构网络中任意两个物理接口之间的切换不 做限定, 以实际物理接口为准。
本发明实施例通过建立虚拟接口, 并且建立切换服务进程组件、 虚拟接 口以及应用进程组件之间的通信, 通过将 HoA与虚拟接口的 IP地址绑定, 当异构网络的物理接口变更时, 改变切换服务进程组件和移动锚点的通信, 仍保持虚拟接口和应用进程组件之间的通信不受影响,从而支持异构网络无 缝切换, 保证业务使用连续性。
图 8是本发明实施例的另一种用户设备 80的示意框图。用户设备 80包 括处理器 81、 存储器 82、 第一物理接口 83和第二物理接口 84。 处理器 81可以是通用处理器、 数字信号处理器(DSP )、 专用集成电路 ( ASIC ), 现成可编程门阵列 (FPGA )或者其他可编程逻辑器件、 分立门 或者晶体管逻辑器件、 分立硬件组件, 可以实现或者执行本发明实施例中的 公开的各方法、 步骤及逻辑框图, 并通过总线与其他装置双向通信。 通用处 理器可以是微处理器或者该处理器也可以是任何常规的处理器等。 结合本发 明实施例所公开的方法的步骤可以直接体现为处理器执行完成,或者用处理 器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、 只读存储器, 可编程只读存储器或者电可擦写可编程存储器、 寄存器等本领 域成熟的存储介质中。 该存储介质位于存储器 82, 处理器 81读取存储器 82 中的信息, 结合其硬件完成上述方法的步骤。 存储器 82和处理器 81也可以 整合成应用本发明实施例的物理模块,在该物理模块上存储和运行实现该本 发明实施例的程序。
存储器 82存储处理器执行以下方法所需的指令。
处理器 81调用切换服务进程, 其中所述切换服务进程用于建立虚拟接 口且将所述虚拟接口的地址配置为家乡地址(HoA ), 并建立所述切换服务 进程与所述虚拟接口之间的通信; 且还用于建立与所述移动锚点之间的网际 互连协议( IP )隧道, 且将所述 IP隧道绑定到当前使用的第一物理接口; 还 用于设置 IP路由表, 其中所述 IP路由表用于控制应用进程和所述虚拟接口 之间数据的路由; 还用于当所述第一物理接口切换到第二物理接口后, 将所 述 IP 隧道从所述第一物理接口绑定到所述第二物理接口, 其中所述第一物 理接口和所述第二物理接口是异构网络的两种物理接口。
处理器 81还调用应用进程, 其中所述应用进程用于根据所述 IP路由表 向所述虚拟接口发送数据和接收所述虚拟接口转发的数据。
可选的, 作为不同的实施例, 处理器还调用所述切换服务进程, 用于在 建立与所述移动锚点之间的 IP 隧道前, 接入所述移动锚点并获取所述移动 锚点分配的 HoA。
可选的, 作为不同的实施例, 处理器还调用字符设备驱动, 用于实现所 述切换服务进程和所述虚拟接口之间的通信。
可选的, 作为不同的实施例, 所述处理器调用所述应用进程具体用于根 据所述 IP路由表将上行数据发送到所述虚拟接口; 所述处理器调用所述切 换服务进程通过所述字符设备驱动读取所述虚拟接口接收的上行数据; 所述 处理器调用所述切换服务进程将读取的所述上行数据封装后, 通过所述 IP 隧道经所述第一物理接口发送到所述移动锚点。
可选的, 作为不同的实施例, 所述处理器将所述第一物理接口将从所述 移动锚点接收的下行数据通过所述 IP 隧道发送到所述切换服务进程; 所述 处理器调用所述切换服务进程以将所述下行数据解封装后,将解封装的下行 数据通过所述字符设备驱动写入所述虚拟接口; 所述虚拟接口将接收的所述 解封装的下行数据根据 IP路由表转发到所述应用进程。
可选的, 作为不同的实施例, 处理器调用所述切换服务进程通过以下协 议之一建立与所述移动锚点之间的 IP隧道: 用户数据报协议(UDP )、 传输 控制协议(TCP )、 IP封装 IP ( IP-in-IP ), 通用路由封装( GRE )和通用无 线分组业务隧道协议( GTP )。
可选的, 作为不同的实施例, 用户设备在至少两种以下制式的异构网络 中工作: 第三代合作伙伴计划 (3GPP )、 无线局域网 (WLAN )、 码分多址 ( CDMA )、 全球微波互联接入( WiMAX )。
本发明实施例通过处理器调用切换服务进程以建立虚拟接口, 并且建立 切换服务进程、 虚拟接口以及应用进程之间的通信, 通过将 HoA与虚拟接 口的 IP地址绑定, 当异构网络的物理接口变更时, 改变切换服务进程和移 动锚点的通信, 仍保持虚拟接口和应用进程之间的通信不受影响, 从而支持 异构网络无缝切换, 保证业务使用连续性。
本领域普通技术人员可以意识到, 结合本文中所公开的实施例描述的各 示例的单元及算法步骤, 能够以电子硬件、 或者计算机软件和电子硬件的结 合来实现。 这些功能究竟以硬件还是软件方式来执行, 取决于技术方案的特 定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方 法来实现所描述的功能, 但是这种实现不应认为超出本发明的范围。
所属领域的技术人员可以清楚地了解到, 为描述的方便和筒洁, 上述描 述的系统、 装置和单元的具体工作过程, 可以参考前述方法实施例中的对应 过程, 在此不再赘述。
在本申请所提供的几个实施例中, 应该理解到, 所揭露的系统、 装置和 方法, 可以通过其它的方式实现。 例如, 以上所描述的装置实施例仅仅是示 意性的, 例如, 所述单元的划分, 仅仅为一种逻辑功能划分, 实际实现时可 以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个 系统, 或一些特征可以忽略, 或不执行。 另一点, 所显示或讨论的相互之间 的耦合或直接耦合或通信连接可以是通过一些接口, 装置或单元的间接耦合 或通信连接, 可以是电性, 机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作 为单元显示的部件可以是或者也可以不是物理单元, 即可以位于一个地方, 或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或 者全部单元来实现本实施例方案的目的。
另外, 在本发明各个实施例中的各功能单元可以集成在一个处理单元 中, 也可以是各个单元单独物理存在, 也可以两个或两个以上单元集成在一 个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使 用时, 可以存储在一个计算机可读取存储介质中。 基于这样的理解, 本发明 的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部 分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质 中, 包括若干指令用以使得一台计算机设备(可以是个人计算机, 服务器, 或者网络设备等)执行本发明各个实施例所述方法的全部或部分步骤。 而前 述的存储介质包括: U盘、移动硬盘、只读存储器( ROM , Read-Only Memory )、 随机存取存储器(RAM, Random Access Memory ), 磁碟或者光盘等各种可 以存储程序代码的介质。
以上所述, 仅为本发明的具体实施方式, 但本发明的保护范围并不局限 于此, 任何熟悉本技术领域的技术人员在本发明揭露的技术范围内, 可轻易 想到变化或替换, 都应涵盖在本发明的保护范围之内。 因此, 本发明的保护 范围应所述以权利要求的保护范围为准。

Claims

权利要求
1、 一种用户设备, 其特征在于, 包括切换服务进程组件、 应用进程组 件、 第一物理接口和第二物理接口:
所述切换服务进程组件, 用于建立虚拟接口且将所述虚拟接口的 IP地 址配置为家乡地址 HoA,并建立所述切换服务进程组件与所述虚拟接口之间 的通信; 且
还用于建立与所述移动锚点之间的网际互连协议 IP隧道, 且将所述 IP 隧道绑定到当前使用的所述第一物理接口;
还用于设置 IP路由表, 其中所述 IP路由表用于控制应用进程组件和所 述虚拟接口之间数据的路由;
还用于当所述第一物理接口切换到所述第二物理接口后, 将所述 IP 隧 道从所述第一网络接口绑定到所述第二物理接口,其中所述第一物理接口和 所述第二物理接口是异构网络的两种物理接口,
所述应用进程组件, 用于根据所述 IP路由表向所述虚拟接口发送数据 和接收所述虚拟接口转发的数据。
2、 根据权利要求 1所述的用户设备, 其特征在于:
所述切换服务进程组件, 还用于在建立与所述移动锚点之间的 IP 隧道 前, 接入所述移动锚点并获取所述移动锚点分配的 HoA。
3、 根据权利要求 1或 2所述的用户设备, 其特征在于, 所述用户设备 还包括字符设备驱动组件:
所述字符设备驱动组件,用于实现所述切换服务进程组件和所述虚拟接 口之间的通信。
4、 根据权利要求 3所述的用户设备, 其特征在于:
所述应用进程组件具体用于根据所述 IP路由表将上行数据发送到所述 虚拟接口;
所述切换服务进程组件通过所述字符设备驱动组件读取所述虚拟接口 接收的上行数据;
所述切换服务进程组件将读取的所述上行数据封装后, 通过所述 IP 隧 道经所述第一物理接口发送到所述移动锚点。
5、 根据权利要求 3所述的用户设备, 其特征在于:
所述第一物理接口将从所述移动锚点接收的下行数据通过所述 IP 隧道 发送到所述切换服务进程组件;
所述切换服务进程组件将所述下行数据解封装后,将解封装的下行数据 通过字符设备驱动写入所述虚拟接口;
所述虚拟接口将接收的所述解封装的下行数据根据 IP路由表转发到所 述应用进程组件。
6、 根据权利要求 1至 5任一项所述的用户设备, 其特征在于, 所述切 换服务进程组件通过以下协议之一建立与所述移动锚点之间的 IP隧道: 用户数据报协议 UDP、 传输控制协议 TCP、 IP封装 IP、 通用路由封装 GRE和通用无线分组业务隧道协议 GTP。
7、 根据权利要求 1至 6任一项所述的用户设备, 其特征在于, 所述用 户设备在至少两种以下制式的异构网络中工作:
第三代合作伙伴计划 3GPP、 无线局域网 WLAN、 码分多址 CDMA、 全 球微波互联接入 WiMAX。
8、 一种异构网络切换的方法, 其特征在于, 包括:
建立虚拟接口, 且将所述虚拟接口的 IP地址配置为家乡地址 HoA; 建立切换服务进程组件与所述虚拟接口之间的通信;
建立所述切换服务进程组件与所述移动锚点之间的网际互连协议 IP 隧 道, 且将所述 IP隧道绑定到当前使用的第一物理接口;
设置 IP路由表, 其中所述 IP路由表用于控制应用进程组件和所述虚拟 接口之间数据的路由;
当所述第一物理接口切换到第二物理接口后, 将所述 IP 隧道从所述第 一物理接口绑定到所述第二物理接口, 其中所述第一物理接口和所述第二物 理接口是异构网络的两种物理接口。
9、 根据权利要求 8所述的方法, 其特征在于, 在所述建立与所述移动 锚点之间的 IP隧道前, 所述方法还包括:
所述切换服务进程组件接入所述移动锚点并获取所述移动锚点分配的 HoA。
10、 根据权利要求 8或 9所述的方法, 其特征在于, 所述建立切换服务 进程组件与所述虚拟接口之间的通信, 包括:
通过字符设备驱动实现所述切换服务进程组件和所述虚拟接口之间的 通信。
11、 根据权利要求 10所述的方法, 其特征在于, 所述方法具体包括: 所述切换服务进程组件通过字符设备驱动读取所述虚拟接口接收的上 行数据;
所述切换服务进程组件将读取的所述上行数据封装后, 通过所述 IP 隧 道经所述第一物理接口发送到所述移动锚点。
12、 根据权利要求 10所述的方法, 其特征在于, 所述方法具体包括: 所述第一物理接口将从所述移动锚点接收的下行数据通过所述 IP 隧道 发送到所述切换服务进程组件;
所述切换服务进程组件将所述下行数据解封装后,将解封装的下行数据 通过字符设备驱动写入所述虚拟接口;
所述虚拟接口将接收的所述解封装的下行数据根据 IP路由表转发到所 述应用进程组件。
13、 根据权利要求 8至 12任一项所述的方法, 其特征在于, 通过以下 协议之一建立所述切换服务进程组件与所述移动锚点之间的 IP隧道:
用户数据报协议 UDP、 传输控制协议 TCP、 IP封装 IP、 通用路由封装 GRE和通用无线分组业务隧道协议 GTP。
14、 根据权利要求 8至 13任一项所述的方法, 其特征在于, 所述异构 网络包括以下至少两种制式的无线系统:
第三代合作伙伴计划 3GPP、 无线局域网 WLAN、 码分多址 CDMA、 全 球微波互联接入 WiMAX。
15、 一种用户设备, 其特征在于, 包括处理器、 存储器、 第一物理接口 和第二物理接口:
所述存储器存储所述处理器执行以下方法所需的指令;
所述处理器, 用于调用切换服务进程, 其中
所述切换服务进程用于建立虚拟接口且将所述虚拟接口的地址配置为 家乡地址 HoA, 并建立所述切换服务进程与所述虚拟接口之间的通信; 且还 用于建立与所述移动锚点之间的 ip隧道, 且将所述 IP隧道绑定到当前使用 的所述第一物理接口; 还用于设置 IP路由表, 其中所述 IP路由表用于控制 应用进程和所述虚拟接口之间数据的路由; 还用于当所述第一物理接口切换 到所述第二物理接口后, 将所述 IP 隧道从所述第一物理接口绑定到所述第 二物理接口, 其中所述第一物理接口和所述第二物理接口是异构网络的两种 物理接口;
所述处理器, 还用于调用应用进程, 其中
所述应用进程用于根据所述 IP路由表向所述虚拟接口发送数据和接收 所述虚拟接口转发的数据。
16、 根据权利要求 15所述的用户设备, 其特征在于:
所述处理器还调用所述切换服务进程,用于在建立与所述移动锚点之间 的 IP隧道前, 接入所述移动锚点并获取所述移动锚点分配的 HoA。
17、 根据权利要求 15或 16所述的用户设备, 其特征在于:
所述处理器还调用字符设备驱动, 用于实现所述切换服务进程和所述虚 拟接口之间的通信。
18、 根据权利要求 17所述的用户设备, 其特征在于:
所述处理器调用所述应用进程具体用于根据所述 IP路由表将上行数据 发送到所述虚拟接口;
所述处理器调用所述切换服务进程通过所述字符设备驱动读取所述虚 拟接口接收的上行数据;
所述处理器调用所述切换服务进程将读取的所述上行数据封装后,通过 所述 IP隧道经所述第一物理接口发送到所述移动锚点。
19、 根据权利要求 17所述的用户设备, 其特征在于:
所述处理器将所述第一物理接口将从所述移动锚点接收的下行数据通 过所述 IP隧道发送到所述切换服务进程;
所述处理器调用所述切换服务进程以将所述下行数据解封装后,将解封 装的下行数据通过所述字符设备驱动写入所述虚拟接口;
所述虚拟接口将接收的所述解封装的下行数据根据 IP路由表转发到所 述应用进程。
20、 根据权利要求 15至 19任一项所述的用户设备, 其特征在于, 所述 处理器调用所述切换服务进程通过以下协议之一建立与所述移动锚点之间 的 IP隧道:
用户数据报协议 UDP、 传输控制协议 TCP、 IP封装 IP、 通用路由封装 GRE和通用无线分组业务隧道协议 GTP。
21、 根据权利要求 15至 20任一项所述的用户设备, 其特征在于, 所述 用户设备在至少两种以下制式的异构网络中工作:
第三代合作伙伴计划 3GPP、 无线局域网 WLAN、 码分多址 CDMA、 全 球微波互联接入 WiMAX。
PCT/CN2012/088038 2012-12-31 2012-12-31 用户设备及异构网络切换的方法 WO2014101181A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2012/088038 WO2014101181A1 (zh) 2012-12-31 2012-12-31 用户设备及异构网络切换的方法
CN201280001962.8A CN104094637B (zh) 2012-12-31 2012-12-31 用户设备及异构网络切换的方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/088038 WO2014101181A1 (zh) 2012-12-31 2012-12-31 用户设备及异构网络切换的方法

Publications (1)

Publication Number Publication Date
WO2014101181A1 true WO2014101181A1 (zh) 2014-07-03

Family

ID=51019785

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/088038 WO2014101181A1 (zh) 2012-12-31 2012-12-31 用户设备及异构网络切换的方法

Country Status (2)

Country Link
CN (1) CN104094637B (zh)
WO (1) WO2014101181A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111585796B (zh) * 2020-04-27 2022-06-21 青岛海信宽带多媒体技术有限公司 一种接口切换、报文传输方法和网关设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101765092A (zh) * 2008-12-24 2010-06-30 华为技术有限公司 一种网络切换方法、装置及系统
CN101931938A (zh) * 2009-06-26 2010-12-29 华为技术有限公司 网间切换时转发数据的方法、装置及系统
CN102075907A (zh) * 2011-01-26 2011-05-25 北京交通大学 一种虚拟接口支持异构切换的方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1271896B1 (de) * 2001-06-18 2004-07-28 Swisscom Mobile AG Verfahren und System für mobile IP-Nodes in heterogenen Netzwerken
KR101028330B1 (ko) * 2008-06-27 2011-04-12 주식회사 케이티 이종 이동성 프로토콜 혼재망에서의 핸드오버 처리 방법 및 그 시스템과 mip 클라이언트 장치
KR20100121800A (ko) * 2009-05-11 2010-11-19 주식회사 케이티 이기종망간의 연동을 위한 pmip 기반의 핸드오버 처리 방법
US8311014B2 (en) * 2009-11-06 2012-11-13 Telefonaktiebolaget L M Ericsson (Publ) Virtual care-of address for mobile IP (internet protocol)

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101765092A (zh) * 2008-12-24 2010-06-30 华为技术有限公司 一种网络切换方法、装置及系统
CN101931938A (zh) * 2009-06-26 2010-12-29 华为技术有限公司 网间切换时转发数据的方法、装置及系统
CN102075907A (zh) * 2011-01-26 2011-05-25 北京交通大学 一种虚拟接口支持异构切换的方法

Also Published As

Publication number Publication date
CN104094637A (zh) 2014-10-08
CN104094637B (zh) 2017-10-17

Similar Documents

Publication Publication Date Title
JP4464442B2 (ja) リンク層支援移動体ip高速ハンドオフのためのシステム並びに関連移動体ノード,外部エージェント及び方法
JP5451912B2 (ja) ホームエージェント
JP4925280B2 (ja) モバイルネットワーク通信における切換の方法と装置
KR101501541B1 (ko) 무선 디바이스에서의 wlan 오프로드를 위한 아키텍처
JP5890507B2 (ja) ネットワークベースのモビリティドメインにおけるユーザデバイス間転送(iut)のための方法および装置
WO2010098146A1 (en) Method for a communication node with a plurality of communication interfaces to notify dynamic path setup and associated apparatus thereof
US9832695B2 (en) Method, device, network element and system for switching a network
WO2009006848A1 (fr) Procédé de commutation de réseau d'accès, dispositif de gestion d'ancrage, et dispositif d'accès mobile
WO2010130128A1 (zh) 一种接入分组数据服务节点的方法、系统和终端
KR20150074220A (ko) 고속 핸드오프 전이 동안 이동성 액세스 게이트웨이 간의 터널링을 위한 시스템 및 프로토콜들
JP2013169015A (ja) 複数インタフェース装置のアクティブなインタフェースにメッセージをリダイレクトするシステム及び方法
WO2009149631A1 (zh) 状态切换信息处理方法、移动接入网关和移动终端
WO2011153777A1 (zh) 移动通信控制方法、系统、映射转发服务器及接入路由器
EP2850912B1 (en) Efficient distribution of signaling messages in a mobility access gateway or local mobility anchor
KR101680137B1 (ko) Sdn 기반의 단말 이동성 제어 시스템 및 그 방법
WO2013178013A1 (zh) 移动节点注册方法、互通方法、切换方法和网元
WO2010111873A1 (zh) Hrpd系统中非3gpp2消息传输的方法和系统
WO2014101181A1 (zh) 用户设备及异构网络切换的方法
JP2012156796A (ja) 通信システム、通信端末、ゲートウェイ、通信方法及びプログラム
WO2014075263A1 (zh) 传输数据的方法、基站、接入网设备和用户设备
WO2013007129A1 (zh) 报文转发处理方法、网元及系统
KR101314883B1 (ko) 무선 인터넷 서비스 망에서 이기종 망간 연동 지원 방법
WO2015089837A1 (zh) 路由优化的方法、路由器及位置管理实体
JP4605381B2 (ja) 通信制御システム及び管理装置
WO2014194747A1 (zh) 一种路由优化方法、装置及计算机存储介质

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12890880

Country of ref document: EP

Kind code of ref document: A1