Diameter End‐to‐End Communication
This chapter looks at the details of communication between two Diameter nodes that are not adjacent. The routing table is a data structure internal to the Diameter node that contains information on how to handle Diameter request messages: either consuming the request message locally or processing th...
Gespeichert in:
| Hauptverfasser: | , , , |
|---|---|
| Format: | Buchkapitel |
| Sprache: | eng |
| Schlagworte: | |
| Online-Zugang: | Volltext |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
| container_end_page | 80 |
|---|---|
| container_issue | |
| container_start_page | 61 |
| container_title | |
| container_volume | |
| creator | Mahoney, Jean Tschofenig, Hannes Decugis, Sebastien Korhonen, Jouni |
| description | This chapter looks at the details of communication between two Diameter nodes that are not adjacent. The routing table is a data structure internal to the Diameter node that contains information on how to handle Diameter request messages: either consuming the request message locally or processing the request further before routing it to the appropriate adjacent peer. The Diameter request message routing relies on both the destination realm and the Application‐Id. While reaching the final destination, the destination host, if present, is used to forward the message to the correct peer node. Diameter end‐to‐end communication relies on a number of routing AVPs. Unlike what the category name suggests, these AVPs are not used for the request routing or forwarding, but to record the used route and the state information of the traversed agents. The End‐to‐End Identifier is used for detecting duplicated messages. The chapter discusses the topic of large multi‐realm inter‐connecting Diameter networks. |
| doi_str_mv | 10.1002/9781118875889.ch4 |
| format | Book Chapter |
| fullrecord | <record><control><sourceid>proquest_wiley</sourceid><recordid>TN_cdi_proquest_ebookcentralchapters_5731874_75_89</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>EBC5731874_75_89</sourcerecordid><originalsourceid>FETCH-LOGICAL-p123f-2d4b27381d90f1099a02c5c11be5899fd1a32709633088d4f8a01174fd6024953</originalsourceid><addsrcrecordid>eNptUMtOwzAQNEIgoPQDuPXCMWXXj3p9RKUFpEpc4Gw5sa0G2iQ0qRCc-AS-kS_BpYBUicM-NTPaWcbOEIYIwC-MJkQk0orIDIu53GMnvwsF-3-DAX2YBiAaASdujli_bR8hSSDXI4nH7PyqdMvQhdVgUvnP94-uTim1g3G9XK6rsnBdWVen7CC6RRv6P7XHHqaT-_FNNru7vh1fzrIGuYgZ9zLnWhB6AxHBGAe8UAViHhQZEz06wTWYkRDpJC8jOUDUMvp0njRK9BhudV_KRXi1Ia_rp9Yi2I1ru-PaJtebSJzsH84u9q1svvGNjwnPt_hmVT-vQ9ttKUWoupVbFHPXpG-0VmmBpKXVypIRXxSAaLs</addsrcrecordid><sourcetype>Enrichment Source</sourcetype><iscdi>true</iscdi><recordtype>book_chapter</recordtype><pqid>EBC5731874_75_89</pqid></control><display><type>book_chapter</type><title>Diameter End‐to‐End Communication</title><source>O'Reilly Online Learning: Academic/Public Library Edition</source><creator>Mahoney, Jean ; Tschofenig, Hannes ; Decugis, Sebastien ; Korhonen, Jouni</creator><contributor>Tschofenig, Hannes</contributor><creatorcontrib>Mahoney, Jean ; Tschofenig, Hannes ; Decugis, Sebastien ; Korhonen, Jouni ; Tschofenig, Hannes</creatorcontrib><description>This chapter looks at the details of communication between two Diameter nodes that are not adjacent. The routing table is a data structure internal to the Diameter node that contains information on how to handle Diameter request messages: either consuming the request message locally or processing the request further before routing it to the appropriate adjacent peer. The Diameter request message routing relies on both the destination realm and the Application‐Id. While reaching the final destination, the destination host, if present, is used to forward the message to the correct peer node. Diameter end‐to‐end communication relies on a number of routing AVPs. Unlike what the category name suggests, these AVPs are not used for the request routing or forwarding, but to record the used route and the state information of the traversed agents. The End‐to‐End Identifier is used for detecting duplicated messages. The chapter discusses the topic of large multi‐realm inter‐connecting Diameter networks.</description><identifier>ISBN: 1118875907</identifier><identifier>ISBN: 9781118875902</identifier><identifier>EISBN: 1118875850</identifier><identifier>EISBN: 9781118875858</identifier><identifier>EISBN: 1118875885</identifier><identifier>EISBN: 9781118875889</identifier><identifier>DOI: 10.1002/9781118875889.ch4</identifier><identifier>OCLC: 1088602829</identifier><identifier>LCCallNum: TK5105.5663 .T734 2019</identifier><language>eng</language><publisher>United Kingdom: John Wiley & Sons, Incorporated</publisher><subject>Diameter Application‐Id ; Diameter end‐to‐end communication ; Diameter request messages ; ELECTRONICS & COMMUNICATIONS ENGINEERING ; End‐to‐End Identifier ; large multi‐realm inter‐connecting Diameter networks ; request routing ; routing table</subject><ispartof>Diameter, 2019, p.61-80</ispartof><rights>2019 John Wiley & Sons Ltd</rights><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Uhttps://ebookcentral.proquest.com/covers/5731874-l.jpg</thumbnail><link.rule.ids>779,780,784,793,27925</link.rule.ids></links><search><contributor>Tschofenig, Hannes</contributor><creatorcontrib>Mahoney, Jean</creatorcontrib><creatorcontrib>Tschofenig, Hannes</creatorcontrib><creatorcontrib>Decugis, Sebastien</creatorcontrib><creatorcontrib>Korhonen, Jouni</creatorcontrib><title>Diameter End‐to‐End Communication</title><title>Diameter</title><description>This chapter looks at the details of communication between two Diameter nodes that are not adjacent. The routing table is a data structure internal to the Diameter node that contains information on how to handle Diameter request messages: either consuming the request message locally or processing the request further before routing it to the appropriate adjacent peer. The Diameter request message routing relies on both the destination realm and the Application‐Id. While reaching the final destination, the destination host, if present, is used to forward the message to the correct peer node. Diameter end‐to‐end communication relies on a number of routing AVPs. Unlike what the category name suggests, these AVPs are not used for the request routing or forwarding, but to record the used route and the state information of the traversed agents. The End‐to‐End Identifier is used for detecting duplicated messages. The chapter discusses the topic of large multi‐realm inter‐connecting Diameter networks.</description><subject>Diameter Application‐Id</subject><subject>Diameter end‐to‐end communication</subject><subject>Diameter request messages</subject><subject>ELECTRONICS & COMMUNICATIONS ENGINEERING</subject><subject>End‐to‐End Identifier</subject><subject>large multi‐realm inter‐connecting Diameter networks</subject><subject>request routing</subject><subject>routing table</subject><isbn>1118875907</isbn><isbn>9781118875902</isbn><isbn>1118875850</isbn><isbn>9781118875858</isbn><isbn>1118875885</isbn><isbn>9781118875889</isbn><fulltext>true</fulltext><rsrctype>book_chapter</rsrctype><creationdate>2019</creationdate><recordtype>book_chapter</recordtype><recordid>eNptUMtOwzAQNEIgoPQDuPXCMWXXj3p9RKUFpEpc4Gw5sa0G2iQ0qRCc-AS-kS_BpYBUicM-NTPaWcbOEIYIwC-MJkQk0orIDIu53GMnvwsF-3-DAX2YBiAaASdujli_bR8hSSDXI4nH7PyqdMvQhdVgUvnP94-uTim1g3G9XK6rsnBdWVen7CC6RRv6P7XHHqaT-_FNNru7vh1fzrIGuYgZ9zLnWhB6AxHBGAe8UAViHhQZEz06wTWYkRDpJC8jOUDUMvp0njRK9BhudV_KRXi1Ia_rp9Yi2I1ru-PaJtebSJzsH84u9q1svvGNjwnPt_hmVT-vQ9ttKUWoupVbFHPXpG-0VmmBpKXVypIRXxSAaLs</recordid><startdate>2019</startdate><enddate>2019</enddate><creator>Mahoney, Jean</creator><creator>Tschofenig, Hannes</creator><creator>Decugis, Sebastien</creator><creator>Korhonen, Jouni</creator><general>John Wiley & Sons, Incorporated</general><general>John Wiley & Sons, Ltd</general><scope>FFUUA</scope></search><sort><creationdate>2019</creationdate><title>Diameter End‐to‐End Communication</title><author>Mahoney, Jean ; Tschofenig, Hannes ; Decugis, Sebastien ; Korhonen, Jouni</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-p123f-2d4b27381d90f1099a02c5c11be5899fd1a32709633088d4f8a01174fd6024953</frbrgroupid><rsrctype>book_chapters</rsrctype><prefilter>book_chapters</prefilter><language>eng</language><creationdate>2019</creationdate><topic>Diameter Application‐Id</topic><topic>Diameter end‐to‐end communication</topic><topic>Diameter request messages</topic><topic>ELECTRONICS & COMMUNICATIONS ENGINEERING</topic><topic>End‐to‐End Identifier</topic><topic>large multi‐realm inter‐connecting Diameter networks</topic><topic>request routing</topic><topic>routing table</topic><toplevel>online_resources</toplevel><creatorcontrib>Mahoney, Jean</creatorcontrib><creatorcontrib>Tschofenig, Hannes</creatorcontrib><creatorcontrib>Decugis, Sebastien</creatorcontrib><creatorcontrib>Korhonen, Jouni</creatorcontrib><collection>ProQuest Ebook Central - Book Chapters - Demo use only</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Mahoney, Jean</au><au>Tschofenig, Hannes</au><au>Decugis, Sebastien</au><au>Korhonen, Jouni</au><au>Tschofenig, Hannes</au><format>book</format><genre>bookitem</genre><ristype>CHAP</ristype><atitle>Diameter End‐to‐End Communication</atitle><btitle>Diameter</btitle><date>2019</date><risdate>2019</risdate><spage>61</spage><epage>80</epage><pages>61-80</pages><isbn>1118875907</isbn><isbn>9781118875902</isbn><eisbn>1118875850</eisbn><eisbn>9781118875858</eisbn><eisbn>1118875885</eisbn><eisbn>9781118875889</eisbn><abstract>This chapter looks at the details of communication between two Diameter nodes that are not adjacent. The routing table is a data structure internal to the Diameter node that contains information on how to handle Diameter request messages: either consuming the request message locally or processing the request further before routing it to the appropriate adjacent peer. The Diameter request message routing relies on both the destination realm and the Application‐Id. While reaching the final destination, the destination host, if present, is used to forward the message to the correct peer node. Diameter end‐to‐end communication relies on a number of routing AVPs. Unlike what the category name suggests, these AVPs are not used for the request routing or forwarding, but to record the used route and the state information of the traversed agents. The End‐to‐End Identifier is used for detecting duplicated messages. The chapter discusses the topic of large multi‐realm inter‐connecting Diameter networks.</abstract><cop>United Kingdom</cop><pub>John Wiley & Sons, Incorporated</pub><doi>10.1002/9781118875889.ch4</doi><oclcid>1088602829</oclcid><tpages>20</tpages></addata></record> |
| fulltext | fulltext |
| identifier | ISBN: 1118875907 |
| ispartof | Diameter, 2019, p.61-80 |
| issn | |
| language | eng |
| recordid | cdi_proquest_ebookcentralchapters_5731874_75_89 |
| source | O'Reilly Online Learning: Academic/Public Library Edition |
| subjects | Diameter Application‐Id Diameter end‐to‐end communication Diameter request messages ELECTRONICS & COMMUNICATIONS ENGINEERING End‐to‐End Identifier large multi‐realm inter‐connecting Diameter networks request routing routing table |
| title | Diameter End‐to‐End Communication |
| url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2024-12-27T19%3A36%3A57IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_wiley&rft_val_fmt=info:ofi/fmt:kev:mtx:book&rft.genre=bookitem&rft.atitle=Diameter%20End%E2%80%90to%E2%80%90End%20Communication&rft.btitle=Diameter&rft.au=Mahoney,%20Jean&rft.date=2019&rft.spage=61&rft.epage=80&rft.pages=61-80&rft.isbn=1118875907&rft.isbn_list=9781118875902&rft_id=info:doi/10.1002/9781118875889.ch4&rft_dat=%3Cproquest_wiley%3EEBC5731874_75_89%3C/proquest_wiley%3E%3Curl%3E%3C/url%3E&rft.eisbn=1118875850&rft.eisbn_list=9781118875858&rft.eisbn_list=1118875885&rft.eisbn_list=9781118875889&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=EBC5731874_75_89&rft_id=info:pmid/&rfr_iscdi=true |