Back to results
US 2010/0306350 A1Published application
HIP Node Reachability
AssigneeOptis Wireless Technology, LLC
InventorsPatrik Salmela, Petri Jokela, Raimo Vuopionperä, Jan Melén
Life of this patent
Estimating the term…
Loading patent…
Loading patent…
AssigneeOptis Wireless Technology, LLC
InventorsPatrik Salmela, Petri Jokela, Raimo Vuopionperä, Jan Melén
Estimating the term…
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.
A method of operating a plurality of rendezvous servers to provide a Host Identity Protocol, HIP, based mobility service to HIP nodes, the method comprising:
A method of operating a rendezvous server for use in providing a Host Identity Protocol, HIP, based mobility service to HIP nodes, the method comprising:
A rendezvous server for use in a Host Identity Protocol, HIP, based network, the rendezvous server being arranged to register Host Identity Tag, HIT, to contact address mappings for HIP nodes and, upon registration, to inform one or more other rendezvous servers positioned higher in the hierarchical rendezvous server structure that it knows the contact address for the HIP node without explicitly identifying the contact address.
Dependencies are inferred from the claim text.