US9271193B2 - Care-of-address handover - Google Patents
Care-of-address handover Download PDFInfo
- Publication number
- US9271193B2 US9271193B2 US13/758,240 US201313758240A US9271193B2 US 9271193 B2 US9271193 B2 US 9271193B2 US 201313758240 A US201313758240 A US 201313758240A US 9271193 B2 US9271193 B2 US 9271193B2
- Authority
- US
- United States
- Prior art keywords
- address
- care
- network interface
- server
- communication node
- Prior art date
- Legal status (The legal status 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 status listed.)
- Expired - Fee Related, expires
Links
- 238000004891 communication Methods 0.000 claims abstract description 66
- 238000000034 method Methods 0.000 claims abstract description 24
- 230000007704 transition Effects 0.000 claims abstract description 6
- 230000015654 memory Effects 0.000 claims description 14
- 238000012546 transfer Methods 0.000 abstract description 5
- 230000008859 change Effects 0.000 description 6
- 230000008569 process Effects 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 230000001934 delay Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000008901 benefit Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000002513 implantation Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0016—Hand-off preparation specially adapted for end-to-end data sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
Definitions
- Today's mobile computing environment requires the ability to seamlessly route communication content associated with nodes that routinely connect to a data network at different points of attachment, e.g., via air and wireline interfaces.
- nodes include cellular telephones, Personal Digital Assistants (PDAs), laptop computers, and other mobile wireless communication equipment.
- PDAs Personal Digital Assistants
- laptop computers and other mobile wireless communication equipment.
- a mobile node may wirelessly and continuously be connected to a network infrastructure using the same Internet Protocol (IP) address regardless of the mobile node's physical location.
- IP Internet Protocol
- the mobile node may be identified by a home address associated with the mobile node's home network.
- the mobile node connects to the network infrastructure, the mobile node is identified by the home address and by at least one care-of-address.
- Information sent across the network infrastructure to the mobile node's home address is transparently routed to the mobile node's care-of-address.
- the information destined for the mobile node's home address is received at the home link by a home gateway or router that tunnels the information to the mobile node's care-of address via an IP tunnel.
- the mobile node As the mobile node changes its physical location or connects to a different network interface (e.g., wireline or wireless) and switches to a different foreign gateway or router to maintain connectivity to the network infrastructure, the mobile node updates the home gateway or router with its new care-of address. In this way, the mobile node can relocate, connect to various foreign gateways or routers, and maintain a constant IP address presence without interruptions or disturbances in network connectivity.
- a different network interface e.g., wireline or wireless
- the IP connection is interrupted at the moment the mobile node leaves the old network link. This connection is interrupted at least until at the mobile node the new link to the network has been made and until the new location, i.e. the new care-of-address, is known and has been updated in the home gateway. If the interruption time for the change exceeds the time-out delays specified e.g. in the TCP (Transfer Control Protocol) for dead times, the IP connection is interrupted. Even when the interruption time lies within the time-out delays specified in the TCP, however, the IP applications are not able to maintain the connection if a network interface is not permanently available and uninterrupted. This leads to the IP applications having to be restarted normally when a mobile node switches between two different network interfaces in order to be able to access a particular IP data tunnel.
- TCP Transfer Control Protocol
- Another problem is that, on the side of the mobile node, the data packets get lost in downtime between the connections since no physical network device is assigned anymore. This is particularly problematic in point-to-point connections, such a VoIP, that require uninterrupted data transfer.
- FIG. 1 is a graphical representation of a communication system that may implement, at least in part, the disclosed care-of-address handover techniques and processes.
- FIG. 2 is a schematic of an example communication block, according to an implementation.
- FIG. 3 illustrates a representative process to initiate a change in a care-of address associated with computing device, such as the requester 135 .
- FIG. 4 illustrates an example computing device within which the described systems and methods can be either fully or partially implemented.
- a message is sent to a server in a point-to-point communication session.
- the message includes a care-of-address of a first network interface (e.g., wireless network interface) and a care-of-address of a second network interface (e.g., wireline network interface).
- the care-of-address of the first network interface is a current care-of-address being used in the communication session and the care-of-address of the second network interface is a new care-of-address that a device (e.g., a mobile node) is going to transition to (e.g., handover).
- the message may also include the server's IP address and TCP (Transfer Control Protocol) port.
- the message may include the mobile node's TCP port.
- the server establishes a NAT (Network Address Translation)/proxy that properly routes data communicated from the server to the mobile node.
- the server continues to address and send data to the care-of-address of the first network interface (i.e., the old care-of-address).
- the NAT/Proxy modifies data that passes there-through to include the new care-of-address of the second network interface.
- FIG. 1 is a graphical representation of a communication system 100 that may implement, at least in part, the disclosed care-of-address handover techniques and processes.
- communication system 100 includes a proxy 103 (e.g., NAT/proxy) and a content server 121 .
- the proxy 103 is, for example, a computing device configured to route and handle requests for content managed by a content server 121 , which is also a computing device.
- the content typically contains items that are provided by the content server 121 in real-time. Such items may include, data communications, real-time media streaming, VoIP data, or the like.
- Such items may be stored in a data store 105 .
- the data store 105 may be any type of computer-readable media, such as volatile and non-volatile media, and removable and non-removable media.
- the computer-readable media may be tangible.
- the proxy 103 may be configured to receive a request for content from a requester 135 , which may be a mobile node, a user's computer, another network computer, computing device, or some other device capable of communicating with the proxy 103 .
- the proxy 103 may be alternatively configured to only deliver information to the requester 135 .
- the server 121 and the requester 135 may be in a peer-to-peer, point-to-point, or end-to-end communication configuration, or the like.
- one or both of the server 121 and the requester 135 may be stationary or moving (e.g., nomadic). Therefore, the server 121 and the requester 135 may be regularly changing network interface types. For example, from a first wireless network interface to a second wireless network interface, or from a wireless network interface to a wireline network interface, or from a wireline network interface to a wireless network interface, and so forth.
- the proxy 103 is configured to communicate with the requester 135 through a computer network, such as a Wide Area Network (WAN) 123 .
- the WAN 123 may be wireless and/or wireline based network. Specifically, when processing or routing data from the content server 121 , proxy 103 is configured to forward the data to the requester 135 .
- Proxy 103 may be implemented as a computing device, such as a server.
- the proxy 103 may also be implemented as a network appliance, such as a network filter configured to handle outgoing and incoming content.
- the proxy 103 may be integrated with the content server 121 , or a standalone module.
- the WAN 123 may be any type of wide area network, such as the Internet, wireless network, or the like. In alternate embodiments, any type of network or other communication link can be used to communicate information between the proxy 103 and the content server 121 and between the proxy 103 and the requester 135 .
- the proxy 103 is capable of routing information for delivery from the content server 121 to a care-of-address associated with the requester 135 .
- the proxy 103 receives content from the content server 121 that is indicated as being for delivery to a first care-of-address.
- the proxy 103 having stored in a storage thereof a second care-of-address that is an update of the first care-of-address, forwards the content to the second care-of-address. Therefore, the content server 121 is insulated from having to use the second care-of-address.
- the content server 121 is a computing device configured to receive a request for content from the requester 135 and to generate the content or provide content in accordance with the request.
- Events 141 - 144 represent an example signal flow of communication system 100 .
- the proxy 103 receives a message from the requester 135 .
- the message is an Internet Control Message Protocol (ICMP) message.
- the message is one or more packets that carry information.
- the message associated with the event 141 includes at least a first care-of-address and a second care-of-address.
- the message may also include a destination address of the content server 121 , which may be an IP address, a TCP port of the content server 121 and a TCP port of the requester 135 .
- the message serves to inform the proxy 103 that the requester 135 is moving from the first care-of-address to the second care-of-address. Moreover, the message serves, if such content is part of the message, to inform the proxy 103 that content for delivery from the content server 121 , having the associated destination address (e.g., IP address) and TCP port, is to be routed to the second care-of-address and TCP port of the requester 135 rather than the first care-of-address.
- the proxy 103 stores the content of the message for future reference.
- additional data or information is included with the message, it is routed to the content server 121 .
- the change of care-of-address and other related information from the message is not routed to the content server 121 . That is, in one implementation, only data is routed to the content server 121 .
- the content server 121 communicates data for delivery to the requester 135 .
- Packets associated with the data identify the recipient's care-of-address as being the first care-of-address of the requester 135 .
- the proxy 103 having stored the content of the message from event 141 , which at least includes the second care-of-address of the requester 135 , routes the data to the second care-of-address of the requester 135 .
- the packets associated with the data from event 143 may also identify a TCP port associated with the first care-of-address of the requester 135 .
- the proxy 103 may also store a TCP port of the second care-of-address that is different than the TCP port identified in the packets associated with the data. In such a circumstance, the proxy 103 , at event 144 , routes the data to the second care-of-address and its associated TCP port of the requester 135 .
- the proxy 103 is to implement a change of care-of-address at the requester 135 .
- the requester 135 sends the same message (e.g., a message with at least a first care-of-address and a second care-of-address) to inform the content server 121 of a change of care-of-address at the requester 135 .
- the content server 121 may update the TCP/IP stack by replacing the first care-of-address with the second care-of-address.
- FIG. 2 is a schematic of an example communication block 200 , according to an implementation.
- the communication block 200 is a message packet that may be used to convey care-of-address information.
- the communication block 200 may include a payload 210 with a header 220 .
- a preamble 230 is prepended to or associated with the communication block 200 .
- the preamble 230 is the first part of the communication block 200 , and intended so that the receiver (e.g., proxy 103 and/or server 121 ) can detect the presence of the frame on a medium, adjust the gain of front end, and synchronize the clock.
- the header 220 carries necessary information for the receiver to address, demodulate, and decode the payload 210 .
- the payload portion of the communication block 200 carries a message 240 that includes a current care-of-address (e.g., a first care-of-address) and a new care-of-address (e.g., a second care-of-address). That message 240 may be an ICMP message. Furthermore, the message 240 may also include an address of a destination device (e.g., server 121 ), a port of a source device (e.g., the requester 135 ), and a port of the destination device. The communication block may be generated by a computing device, such as the requester 135 . Moreover, although the message 240 is illustrated as being part of the payload 210 , the message 240 located in any portion of the communication block 200 , such as the preamble 230 or the header 220 .
- a current care-of-address e.g., a first care-of-address
- a new care-of-address
- FIG. 3 illustrates a representative process 300 to initiate a change in a care-of-address associated with computing device, such as the requester 135 .
- a computing device determines that it will transition from a first network interface to a second network interface.
- the computing device may be the requester 135 .
- the computer device such as the requester 135 , ascertains or obtains a care-of-address for the second network interface. It is assumed here that the requester 135 is already aware of its current care-of-address (e.g., a first care-of-address).
- the computing device such as the requester 135 , generates a message, such as an ICMP message, that includes at least the care-of-address of the first network interface and a care-of-address of the second network interface.
- the message may also include a destination address of a destination computing device, such as the content server 121 or the data store 105 , which may be an IP address, a TCP port of the destination computing device, and a TCP port of generating computing device.
- the message is conveyed to the destination computing device.
- the message is conveyed to a proxy associated with the destination computing device, where the proxy is positioned between the computing device, such as the requester 135 , and the destination device, such as the content server 121 .
- the computing device commences conveying and receiving data (e.g., messages) via the second network interface.
- data e.g., messages
- FIG. 4 illustrates an example computing device 400 within which the described systems and methods can be either fully or partially implemented.
- Computing device 400 is only one example of a computing system and is not intended to suggest any limitation as to the scope of the use or functionality of the invention.
- Computing device 400 can be implemented with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use include, but are not limited to, personal computers, server computers, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, gaming consoles, distributed computing environments that include any of the above systems or devices, and the like.
- the components of computing device 400 can include, but are not limited to, processor 402 (e.g., any of microprocessors, controllers, and the like), system memory 404 , input devices 406 , output devices 408 , and network devices 410 .
- the network devices 410 may include a first and second network device interface.
- the first network device may be a wireless device interface that may have an associated care-of-address and the second network device may be a wireline device interface with an associated care-of-address.
- Computing device 400 typically includes a variety of computer-readable media. Such media can be any available media that is accessible by computing device 400 and includes both volatile and non-volatile media, removable and non-removable media.
- System memory 404 includes computer-readable media in the form of volatile memory, such as random access memory (RAM), and/or non-volatile memory, such as read only memory (ROM).
- RAM random access memory
- ROM read only memory
- System memory 404 typically contains data and/or program modules that are immediately accessible to and/or presently operated on by processor 402 .
- System memory 404 can also include other removable/non removable, volatile/non-volatile computer storage media.
- a hard disk drive may be included for reading from and writing to a non-removable, non-volatile magnetic media
- a magnetic disk drive may be included for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”)
- an optical disk drive may be included for reading from and/or writing to a removable, non-volatile optical disk such as a CD ROM, DVD, or any other type of optical media.
- the disk drives and their associated tangible computer-readable media provide non volatile storage of computer-readable instructions, data structures, program modules, and other data for computing device 400 .
- computer readable media which can store data that is accessible by computing device 400 , such as magnetic cassettes or other magnetic storage devices, flash memory cards, CD-ROM, digital versatile disks (DVD) or other optical storage, random access memories (RAM), read only memories (ROM), electrically erasable programmable read-only memory (EEPROM), and the like, can also be utilized to implement exemplary computing device 400 .
- Any number of program modules can be stored in system memory 404 , including by way of example, an operating system 420 , application programs 428 , and data 432 .
- Computing device 400 can include a variety of computer readable media identified as communication media.
- Communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
- modulated data signal refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
- communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media. Combinations of any of the above are also included within the scope of computer readable media.
- a user can enter commands and information into computing device 400 via input devices 406 such as a keyboard and a pointing device (e.g., a “mouse”).
- input devices 406 such as a keyboard and a pointing device (e.g., a “mouse”).
- Other input devices 406 may include a microphone, joystick, game pad, controller, satellite dish, serial port, scanner, touch screen, touch pads, key pads, and/or the like.
- Output devices 408 may include a CRT monitor, LCD screen, speakers, printers, and the like.
- Computing device 400 may include network devices 410 for connecting to computer networks, such as local area network (LAN), wide area network (WAN), and the like.
- network devices 410 for connecting to computer networks, such as local area network (LAN), wide area network (WAN), and the like.
- the arrangements, procedures and protocols of the described implementations may be implemented on a special purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit element(s), an ASIC or other integrated circuit, a digital signal processor, a flashable device, a hard-wired electronic or logic circuit such as discrete element circuit, a programmable logic device such as PLD, PLA, FPGA, PAL, a transmitter/receiver, any comparable device, or the like.
- any apparatus capable of implementing a state machine that is in turn capable of implementing the methodology described and illustrated herein may be used to implement the various communication methods, protocols and techniques according to the implementations.
- the disclosed procedures may be readily implemented in software using object or object-oriented software development environments that provide portable source code that can be used on a variety of computer or workstation platforms.
- the disclosed arrangements may be implemented partially or fully in hardware using standard logic circuits or VLSI design.
- the communication arrangements, procedures and protocols described and illustrated herein may be readily implemented in hardware and/or software using any known or later developed systems or structures, devices and/or software by those of ordinary skill in the applicable art from the functional description provided herein and with a general basic knowledge of the computer and telecommunications arts.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims (11)
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/758,240 US9271193B2 (en) | 2012-02-24 | 2013-02-04 | Care-of-address handover |
CN201810783254.3A CN108811013A (en) | 2012-02-24 | 2013-02-22 | Care-of Address switches |
CN2013100567154A CN103297558A (en) | 2012-02-24 | 2013-02-22 | Care-of-address handover |
DE201310101814 DE102013101814A1 (en) | 2012-02-24 | 2013-02-25 | Mobile node for use in communication system of data network, has data main memory comprising instructions to establish communication for communicating on mediums, which comprise reference data with message that consists of care-of addresses |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201261602801P | 2012-02-24 | 2012-02-24 | |
US13/758,240 US9271193B2 (en) | 2012-02-24 | 2013-02-04 | Care-of-address handover |
Publications (2)
Publication Number | Publication Date |
---|---|
US20130223404A1 US20130223404A1 (en) | 2013-08-29 |
US9271193B2 true US9271193B2 (en) | 2016-02-23 |
Family
ID=49002807
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/758,240 Expired - Fee Related US9271193B2 (en) | 2012-02-24 | 2013-02-04 | Care-of-address handover |
Country Status (2)
Country | Link |
---|---|
US (1) | US9271193B2 (en) |
CN (2) | CN108811013A (en) |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030018810A1 (en) * | 2000-10-18 | 2003-01-23 | Telefonaktiebolaget L M Ericsson (Publ) | Seamless handoff in mobile IP |
US20030179731A1 (en) * | 2002-03-20 | 2003-09-25 | Nec Corporation | Communication method and system |
US20030225892A1 (en) * | 2002-06-04 | 2003-12-04 | Hideaki Takusagawa | Handover method in mobile communication system and router device used in mobile communication system |
US20040120328A1 (en) | 2002-12-18 | 2004-06-24 | Farid Adrangi | Method, apparatus and system for a secure mobile IP-based roaming solution |
US20050271015A1 (en) * | 2004-06-08 | 2005-12-08 | Ntt Docomo, Inc. | Mobile communication system, access router, management device and mobile communication method |
US7545766B1 (en) * | 2003-05-16 | 2009-06-09 | Nortel Networks Limited | Method for mobile node-foreign agent challenge optimization |
US20090245150A1 (en) | 2008-04-01 | 2009-10-01 | Mediatek Inc. | Method and system for managing idle mode of a mobile node with multiple interfaces |
US20100157947A1 (en) * | 2003-07-31 | 2010-06-24 | Hernandez-Mondragon Edwin A | System, Apparatus, and Methods for Proactive Allocation of Wireless Communication Resources |
US20100313024A1 (en) * | 2007-05-16 | 2010-12-09 | Panasonic Corporation | Methods in Mixed Network and Host-Based Mobility Management |
US20110090794A1 (en) * | 2009-04-17 | 2011-04-21 | George Cherian | Wireless Data Communications Employing IP Flow Mobility |
CN102202286A (en) | 2010-03-24 | 2011-09-28 | 华为技术有限公司 | Method for terminal access in heterogeneous network, and method and equipment for heterogeneous network switching |
-
2013
- 2013-02-04 US US13/758,240 patent/US9271193B2/en not_active Expired - Fee Related
- 2013-02-22 CN CN201810783254.3A patent/CN108811013A/en active Pending
- 2013-02-22 CN CN2013100567154A patent/CN103297558A/en active Pending
Patent Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030018810A1 (en) * | 2000-10-18 | 2003-01-23 | Telefonaktiebolaget L M Ericsson (Publ) | Seamless handoff in mobile IP |
US20030179731A1 (en) * | 2002-03-20 | 2003-09-25 | Nec Corporation | Communication method and system |
US20030225892A1 (en) * | 2002-06-04 | 2003-12-04 | Hideaki Takusagawa | Handover method in mobile communication system and router device used in mobile communication system |
US7428226B2 (en) | 2002-12-18 | 2008-09-23 | Intel Corporation | Method, apparatus and system for a secure mobile IP-based roaming solution |
CN1509111A (en) | 2002-12-18 | 2004-06-30 | ض� | Method for roaming solution scheme based on IP for safety moving, its apparatus and system |
US20040120328A1 (en) | 2002-12-18 | 2004-06-24 | Farid Adrangi | Method, apparatus and system for a secure mobile IP-based roaming solution |
US7545766B1 (en) * | 2003-05-16 | 2009-06-09 | Nortel Networks Limited | Method for mobile node-foreign agent challenge optimization |
US20100157947A1 (en) * | 2003-07-31 | 2010-06-24 | Hernandez-Mondragon Edwin A | System, Apparatus, and Methods for Proactive Allocation of Wireless Communication Resources |
US20050271015A1 (en) * | 2004-06-08 | 2005-12-08 | Ntt Docomo, Inc. | Mobile communication system, access router, management device and mobile communication method |
US20100313024A1 (en) * | 2007-05-16 | 2010-12-09 | Panasonic Corporation | Methods in Mixed Network and Host-Based Mobility Management |
US20090245150A1 (en) | 2008-04-01 | 2009-10-01 | Mediatek Inc. | Method and system for managing idle mode of a mobile node with multiple interfaces |
CN101552731A (en) | 2008-04-01 | 2009-10-07 | 联发科技股份有限公司 | Method and system for controlling first interface and second interface on mobile node |
US8103278B2 (en) | 2008-04-01 | 2012-01-24 | Mediatek Inc. | Method and system for managing idle mode of a mobile node with multiple interfaces |
US20110090794A1 (en) * | 2009-04-17 | 2011-04-21 | George Cherian | Wireless Data Communications Employing IP Flow Mobility |
CN102202286A (en) | 2010-03-24 | 2011-09-28 | 华为技术有限公司 | Method for terminal access in heterogeneous network, and method and equipment for heterogeneous network switching |
Also Published As
Publication number | Publication date |
---|---|
CN108811013A (en) | 2018-11-13 |
CN103297558A (en) | 2013-09-11 |
US20130223404A1 (en) | 2013-08-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10237089B2 (en) | Packet tunneling method, switching device, and control device | |
US10715634B2 (en) | System and method for creating virtual interfaces based on network characteristics | |
US10136363B2 (en) | Facilitation of mobility management across various radio technologies | |
EP2540064B1 (en) | Enabling ipv6 mobility with nat64 | |
US7890662B2 (en) | System and method for providing unified IP presence | |
US7016328B2 (en) | Method for allowing a client to access a wireless system | |
US20150071289A1 (en) | System and method for address resolution | |
CN108718269B (en) | Message processing method and device | |
US20160380789A1 (en) | Media Relay Server | |
US11283730B2 (en) | Data migration method and apparatus | |
US20060171370A1 (en) | Home agent, mobile router, and mobile communication method using the same | |
WO2012041604A1 (en) | Aggregation of mobile broadband network interfaces | |
US9172598B2 (en) | Scalable reliable failover in a network | |
JP6693799B2 (en) | Relay method and corresponding communication network device, system, computer program and computer-readable storage medium | |
US9271193B2 (en) | Care-of-address handover | |
US20170079000A1 (en) | Binding registration method, data forwarding method, related device, and network system | |
CN105991372B (en) | Link detection method and device | |
US8634429B2 (en) | Communication system and method | |
WO2022218132A1 (en) | Route update method, apparatus and system | |
JP2005006218A (en) | Mobile terminal and method for switching network interface | |
CN117527690A (en) | Network addressing method, device, communication equipment and storage medium | |
CN116489075A (en) | Method for executing on processing circuit, network device and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTEL MOBILE COMMUNICATIONS GMBH, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KOLDE, MARTIN;REEL/FRAME:029921/0640 Effective date: 20130204 |
|
ZAAA | Notice of allowance and fees due |
Free format text: ORIGINAL CODE: NOA |
|
ZAAB | Notice of allowance mailed |
Free format text: ORIGINAL CODE: MN/=. |
|
AS | Assignment |
Owner name: INTEL DEUTSCHLAND GMBH, GERMANY Free format text: CHANGE OF NAME;ASSIGNOR:INTEL MOBILE COMMUNICATIONS GMBH;REEL/FRAME:037057/0061 Effective date: 20150507 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
AS | Assignment |
Owner name: INTEL CORPORATION, CALIFORNIA Free format text: CONFIRMATORY ASSIGNMENT EFFECTIVE AS OF JANUARY 1, 2018;ASSIGNOR:INTEL DEUTSCHLAND GMBH;REEL/FRAME:053477/0001 Effective date: 20200615 |
|
AS | Assignment |
Owner name: APPLE INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTEL CORPORATION;REEL/FRAME:053518/0586 Effective date: 20191130 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20240223 |