Einzeltreffer — DigiBib

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.

Titel:	HIP Node Reachability
Autor/in / Beteiligte Person:	Salmela, Patrik ; Jokela, Petri ; Vuopionperä, Raimo ; Melén, Jan
Link:	Zum Volltext
Veröffentlichung:	2010
Medientyp:	Patent
Sonstiges:	Nachgewiesen in: USPTO Patent Applications Sprachen: English Document Number: 20100306350 Publication Date: December 2, 2010 Appl. No: 12/599714 Application Filed: May 08, 2008 Claim: 1. 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: arranging the rendezvous servers in a hierarchical branching structure; for each HIP node, registering a Host Identity Tag, HIT, and contact address mapping with a rendezvous server, and identifying to each higher level rendezvous server within the same branch of the hierarchical structure the HIT and a neighbouring or other lower level rendezvous server within the branch, without explicitly identifying the contact address to those higher level rendezvous servers, wherein in use, when a first rendezvous server receives a HIP I1 message addressed to a given HIT, if that first rendezvous server is unaware of a destination HIT of the I1 message, it forwards the message to a higher level rendezvous server within the same branch, and if the first rendezvous server is not the rendezvous server at which the HIT is registered but is aware of the HIT, it forwards the I1 message to a neighbouring or other lower level rendezvous server corresponding to the HIT. Claim: 2. The method according to claim 1 and comprising, following registration of a HIP node at a registration rendezvous server, sending a notification from that registering rendezvous server to one or more other rendezvous servers within the same hierarchical layer to identify to the other rendezvous server(s) the HIT to contact address mapping for the HIP node. Claim: 3. The method according to claim 2 and comprising sending said notification to rendezvous servers within the same geographic region as the registration rendezvous server. Claim: 4. The method according to claim 1, wherein upon registration of a HIP node the registration rendezvous server sends notifications to other rendezvous servers accompanied with a certificate verifying that the registration rendezvous server is an approved rendezvous server. Claim: 5. The method according to claim 1, wherein upon registration of a HIP node the registration rendezvous server sends notifications to other rendezvous servers with which it has an established trust relationship. Claim: 6. The method according claim 1, wherein said contact address is an IP address. Claim: 7. The method according to claim 1, wherein both the destination HIP node and the originating HIP node of said HIP I1 message are registered with one of said rendezvous servers. Claim: 8. The method according to claim 1, wherein said step of identifying to each higher level rendezvous server within the same branch the HIT and a neighbouring or other lower level rendezvous server within the branch, comprises informing each rendezvous server above the rendezvous server at which the HIP node is registered of the HIT and the identity of the registering rendezvous server. Claim: 9. The method according to claim 1, wherein said step of identifying to each higher level rendezvous server within the same branch the HIT and a neighbouring or other lower level rendezvous server within the branch, comprises identifying to each higher level rendezvous server in the same branch the HIT and an identity of a neighbouring rendezvous server and lower level rendezvous server. Claim: 10. A method according to claim 1, further comprising receiving an I1 HIP message at a rendezvous server, determining whether or not a contact address mapping for the destination HIT of the I1 message is registered at the rendezvous server and, if a mapping is not registered, forwarding the I1 message to a rendezvous server higher in the hierarchical rendezvous server structure. Claim: 11. 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: receiving a HIP I1 message destined for a HIP node and determining whether or not a contact address mapping for the destination HIT of the I1 message is registered at the rendezvous server, if a contact address is registered forwarding the I1 message to a contact address associated with the HIT or to another rendezvous server associated with the HIT and positioned lower in a hierarchical rendezvous server structure and, if a contact address is not registered, forwarding the I1 message to another rendezvous server positioned higher in the hierarchical rendezvous server structure. Claim: 12. 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. Claim: 13. The rendezvous server according to claim 12 and being arranged at registration of a HIP node to inform one or more other rendezvous servers within the same layer of the hierarchical structure of the HIT to contact address mapping. Claim: 14. The A rendezvous server according to claim 13 and being arranged to inform said rendezvous servers within the same geographic region as the registration rendezvous server. Claim: 15. The A rendezvous server according to claim 12 and being arranged, upon registration of a HIP node, to send notifications to other rendezvous servers accompanied with a certificate verifying that the sending rendezvous server is an approved rendezvous server. Claim: 16. The A rendezvous server according to claim 12 and being arranged, upon registration of a HIP node, to send notifications to other rendezvous servers with which it has an established trust relationship. Claim: 17. The A rendezvous server according to claim 12, wherein said contact address is an IP address. Current U.S. Class: 709/220 Current International Class: 06; 06

Klicken Sie ein Format an und speichern Sie dann die Daten oder geben Sie eine Empfänger-Adresse ein und lassen Sie sich per Email zusenden.

BibTeX Citavi, JabRef, u.a.
(Literaturverwaltung)

PDF kein Volltext!
(Merkzettel, Notizen)

RIS Endnote, Citavi u.a.
(Literaturverwaltung)

MODS
(XML zur Weiterverarbeitung)

oder

Wählen Sie das für Sie passende Zitationsformat und kopieren Sie es dann in die Zwischenablage, lassen es sich per Mail zusenden oder speichern es als PDF-Datei.

Gewünschter Zitations-Stil:

oder

Bitte prüfen Sie, ob die Zitation formal korrekt ist, bevor Sie sie in einer Arbeit verwenden. Benutzen Sie gegebenenfalls den "Exportieren"-Dialog, wenn Sie ein Literaturverwaltungsprogramm verwenden und die Zitat-Angaben selbst formatieren wollen.

HIP Node Reachability