# US 8,543,703 B1 · Method of tracking mobile user sessions > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 8,543,703 B1 - Document ID: US8543703B1 - Status: Granted - Kind: B1 - Application number: 10/395,243 - Filed: 2003-03-25 - Granted: 2013-09-24 - Earliest claimed: 2003-03-25 - Assignees: Apple Inc. - Applicants: Ron Pon - Inventors: Ron Pon - Web page: https://patentgrep.com/patent/US8543703B1 ## CPC - H04L 67/14: Session management (for real-time applications in data packet communications networks H04L65/1066) - H04L 67/1044: {Group management mechanisms (management of multicast group membership H04L12/185; reconfiguring of node membership in a computing system to eliminate errors G06F11/1425)} - H04W 12/02: Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII] - H04W 12/10: Integrity - H04W 36/0038: {of security context information} - H04L 61/103: across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP] - H04L 61/2514: between local and global IP addresses - H04L 63/164: {at the network layer} - H04W 88/08: Access point devices - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract In order to improve the mobility of mobile clients, network efficiency and increase the performance of mobile computing and communication environments, provided by the invention is a method of tracking mobile client sessions. The method according to an embodiment of the invention enables mobile computing and communication environments to provide seamless handoffs of both non-secure and secure IP connections between access points and between network domains. ## Claims ### Claim 1 A method for a first computing device to identify a second computing device, wherein both the first and second computing devices have addresses, the method comprising: the first computing device associating a unique tag with the second computing device that is not the respective address of the second computing device or another address; the first computing device transmitting the unique tag to the second computing device so that the second computing device is made aware of the unique tag; the first computing device determining whether or not packets received by the first computing device are from the second computing device by identifying the unique tag and not the respective address of the second computing device. ### Claim 2 (depends on 1) The method of claim 1, wherein the first and second computing devices subscribe to Internet Protocol (IP) and accordingly: the respective addresses of the first and second computing devices are IP addresses; the connection between the first and second computing devices is considered an IP session unique to the connection between the first and second computing devices; and the transmissions between the first and second computing devices are IP packets, each IP packet having a respective payload. ### Claim 3 (depends on 2) The method of claim 2, wherein the first computing device is an IP gateway (or server) and the second computing device is a mobile computing device. ### Claim 4 (depends on 3) The method of claim 3, wherein there is at least one wireless access point coupled to the IP gateway, the wireless access point providing a coverage area from within which the mobile computing device can communicate with the wireless access point. ### Claim 5 (depends on 2) The method of claim 2, wherein the unique tag is a static element associated with overhead of the IP session that would normally be present in IP packets. ### Claim 6 (depends on 2) The method according to claim 2, wherein the respective payloads or IP packets are encrypted so that only the first and second computing devices can decrypt the respective payloads. ### Claim 7 (depends on 6) The method according to claim 6, wherein the encryption is done according to IPSec. ### Claim 8 (depends on 2) The method according to claim 2, wherein the unique tag is encrypted so that only the first and second computing devices can decrypt the unique tag. ### Claim 9 (depends on 8) The method according to claim 8, wherein the encryption is done according to IPSec. ### Claim 10 A method for a first computing device to identify a plurality of other computing devices that each communicate with the first computing device, the first computing device and the plurality of other computing devices each having a respective address, the method comprising: the first communicating device associating the plurality of other computing devices with a corresponding plurality of unique tags that are not the respective addresses of the plurality of other computing devices or other respective addresses; and the first computing device respectively transmitting each of the plurality of unique tags to each of the corresponding plurality of other computing devices such that each computing device receives one of the plurality of unique tags; whereby in use each of the plurality of unique tags is used by the first computing device to identify transmissions from a corresponding one of the plurality of other computing devices without the first computing device having to rely on the respective addresses of the plurality of other computing devices. ### Claim 11 (depends on 10) The method of claim 10, wherein the first computing device and the plurality of other computing devices all subscribe to Internet Protocol (IP) and accordingly: the respective addresses of the first computing device and the plurality of other computing devices are IP addresses; each respective connection between the first computing device and each of the plurality of other computing devices is considered a unique IP session between the first computing device and a respective one of the plurality of other computing devices; and the transmissions from any one of the plurality of other computing devices to the first computing device are IP packets. ### Claim 12 A first computing device adapted to identify a plurality of other computing devices that each communicate with the first computing device, the first computing device and the plurality of other computing devices each having a respective address, wherein the first computing device comprises: communication circuitry, configured to perform communication with at least the other computing devices; and processing hardware coupled to the communication circuitry, wherein the processing hardware is configured to operate with the communication circuitry to identify any one of the plurality of other computing devices by: associating the plurality of other computing devices with a corresponding plurality of unique tags that are not the respective addresses of the plurality of other computing devices or other respective addresses; and transmitting each of the plurality of unique tags to each of the corresponding plurality of other computing devices such that each computing device receives one of the plurality of unique taps; whereby in use each of the plurality of unique tags is used by the first computing device to identify transmissions from a corresponding one of the plurality of other computing devices without the first computing device having to rely on the respective addresses of the plurality of other computing devices. ### Claim 13 (depends on 12) The apparatus of claim 12, wherein the first computing device and the plurality of other computing devices are all adapted to subscribe to Internet Protocol (IP) and accordingly: the respective addresses of the first computing device and the plurality of other computing devices are IP addresses; each respective connection between the first computing device and each of the plurality of other computing devices is considered a unique IP session between the first computing device and a respective one of the plurality of other computing devices; and iii) the transmissions from any one of the plurality of other computing devices to the first computing device are IP packets. ### Claim 14 A method for identification of a mobile computing device by a first computing device, wherein both the mobile computing device and the first computing device have addresses, the method comprising: the mobile communication device receiving a unique tag from the first computing device, wherein the unique tag is associated with the mobile computing device and is not the respective address of the mobile computing device or another address; the mobile computing device including the unique tag in subsequent transmissions to the first computing device so that the first computing device may determine whether or not packets received by the first computing device are from the mobile computing device by identifying the unique tag and not the respective address of the mobile computing device. ### Claim 15 (depends on 14) The method of claim 14, wherein the mobile computing device and the first computing device subscribe to Internet Protocol (IP) and accordingly: the respective addresses of the mobile computing device and the first computing device are IP addresses; the connection between the mobile computing device and the first computing device is considered an IP session unique to the connection between the mobile computing device and the first computing device; and the transmissions between the mobile computing device and the first computing device are IP packets, each IP packet having a respective payload. ### Claim 16 (depends on 14) The method of claim 14, wherein the first computing device is an IP gateway. ### Claim 17 (depends on 14) The method of claim 14, wherein the unique tag is a static element associated with overhead of an IP session that would normally be present in IP packets. ### Claim 18 A mobile computing device, comprising: communication circuitry, configured to communicate with at least a first computing device, wherein both the mobile computing device and the first computing device have addresses; and processing hardware coupled to the communication circuitry, wherein the processing hardware is configured to operate with the communication circuitry to: receive a unique tag from the first computing device, wherein the unique tag is associated with the mobile computing device and is not the respective address of the mobile computing device or another address; include the unique tag in subsequent transmissions to the first computing device so that the first computing device may determine whether or not packets received by the first computing device are from the mobile computing device by identifying the unique tag and not the respective address of the mobile computing device. ### Claim 19 (depends on 18) The mobile computing device of claim 18, wherein the first computing device is an IP gateway. ### Claim 20 (depends on 18) The mobile computing device of claim 18, wherein the unique tag is a static element associated with overhead of an IP session that would normally be present in IP packets.