Abstract: A method of establishing a Host Identity Protocol session between first and second Host Identity Protocol enabled hosts, where at least said second host is located behind a reverse-proxy. The method comprises providing the reverse-proxy with Diffie-Hellman public keying material of the second host, sending said Diffie-Hellman public keying material from the reverse-proxy to the first host as part of the Host Identity Protocol base exchange procedure, this material being bound to the Host Identity of the reverse-proxy for the purpose of the Host Identity Protocol session, and, at the first host, using the Host Identity of the reverse-proxy as the correspondent Host Identity for the Host Identity Protocol session, and, at the second host, using the Host Identity of the reverse-proxy as the originating Host Identity for the Host Identity Protocol session.

Abstract: A method of establishing a connection between a second host and an application socket on a first host. The method utilizes the Host Identity Protocol (HIP). The method includes the steps of establishing either a new or a selected existing HIP Security Association between the first and second hosts; creating a new or selecting an existing Tube Association between the application socket and the Security Association; and forming an association for the connection between the application socket, the Security Association, and the Tube Association. This establishes a connection between the second host and the application socket on the first host through the Security Association and the Tube Association.

Abstract: A method of configuring a plurality of rendezvous servers to provide a Host Identity Protocol, HIP, based mobility service to HIP nodes, where the servers are arranged in a hierarchical branching structure. For each HIP node, a Host Identity Tag, HIT, and contact address mapping is registered with a rendezvous server. That server then identifies itself and the HIT to each higher level server within the same branch, without explicitly identifying the contact address to those higher level servers wherein, in use, when a first rendezvous server receives a HIP contact message addressed to a given HIT, if that first server is unaware of the destination HIT, it forwards the message to a higher level server within the same branch and if the first server is not the server at which the HIT is registered but is aware of the HIT, it forwards the contact message to the neighbouring rendezvous server corresponding to the HIT.

Abstract: A method of authorizing an Internet Protocol (IP) enabled mobile host 1 to access the Internet 2 via an wireless LAN, GSM, UMTS access network 3 comprises initially sending an IP access request from the mobile host 1 to an IP router 5 within the access network 3. In response to receipt of said access request at the IP router 5, an IP address routing prefix is sent from the IP router 5 to the mobile host 1. Electronic cash is then forwarded from the mobile host 1 to a control point 6 within the access network 3. The control point 6 confirms the authenticity and/or sufficiency of the electronic cash and, providing that confirmation is made, sends an authorization message to the IP router 5. The IP router 5 blocks the transmission of IP packets between the mobile host 1 and the Internet 2 prior to receipt of the authorization message and permits the passage of IP packets only after an authorization message has been received.

Abstract: A method of authenticating a mobile wireless terminal 9 in a mobile telecommunications network, the terminal 9 being a subscriber of an Internet Service Provider (ISP) 11 rather than of a mobile network. The terminal 9 is allocated an International Mobile Identity (IMI) which is transmitted from the terminal 9 to a mobile network when the terminal 9 wishes to register with the network. A country code part and an operator ID part of the IMI are used by the network to determine the Internet Protocol (IP) address of the terminal's home ISP 11, which is then contacted by the network over the Internet to authenticate the mobile terminal 9.