EP2014030A1 - Verfahren zum propagieren von ip-konnektivitätsinformationen zwischen distinkten ip-telefoniedomänen, lokalisierungsserver und computerprogramm - Google Patents
Verfahren zum propagieren von ip-konnektivitätsinformationen zwischen distinkten ip-telefoniedomänen, lokalisierungsserver und computerprogrammInfo
- Publication number
- EP2014030A1 EP2014030A1 EP07731922A EP07731922A EP2014030A1 EP 2014030 A1 EP2014030 A1 EP 2014030A1 EP 07731922 A EP07731922 A EP 07731922A EP 07731922 A EP07731922 A EP 07731922A EP 2014030 A1 EP2014030 A1 EP 2014030A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- propagation
- location server
- information
- list
- telephony
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
- H04L45/04—Interdomain routing, e.g. hierarchical routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/80—Responding to QoS
Definitions
- a method of propagating IP connectivity information between separate IP telephony domains, location server and corresponding computer program is described.
- Telephony is understood to mean both conventional telephony services or integrating advanced services such as video telephony or digital data transfer.
- the present invention is in the context of the exchange of information concerning datagram transport services used to route information flows between IP telephony domain management entities.
- the invention relates to the transfer of domain identifiers
- IP Internet Protocol
- BGP Border Gateway Protocol
- Interdomain Routing Protocol IP telephony domains
- IP network is the backbone adopted by operators to pool their heterogeneous service offerings including IP telephony commonly referenced by the abbreviation VoIP (or "Voice over IP” for “Voice over IP”) or more generally grouped under the topic of conversational services.
- VoIP Voice over IP
- VoIP over IP Voice over IP
- telephony offers deployed over an IP network must meet quality constraints such as high availability and high fault tolerance.
- the availability constraint of the service does not only concern the service layer but also the transport layer.
- LS ( "Location Server” for “Location Server”) is an entity of a telephony domain (ITAD) that manages customer locations and routes of a local ITAD. This equipment can interface with a neighboring LS to learn the location of clients managed by other ITADs; AS (“Autonomous System” for “Autonomous System”): It is a set of IP resources managed by a single administrative entity, also called “IP connectivity provider”. As part of the Border Gatevvaj Protocol, [RFC 1771], each AS is identified by a unique identifier. An AS is also referred to as the "IP Transfer Domain” as it refers to the Network and Transport layers of the OSI model. 2 SOLUTIONS OF THE PRIOR ART 2.1 Prior Art
- TRlP allows interconnected ITADs to exchange all the destinations they can reach and in particular facilitates the selection of the most appropriate "Gateway” or "backbone” to evacuate IP telephony traffic to the RTC network.
- the TRIP protocol is implemented by LS ("Location Servers” for “Location Servers”) that propagate TRJP routes containing attributes to qualify the routes in question. The use of this particular protocol is independent of the type of signaling protocol deployed for the actual establishment of calls. TRIP can be used in conjunction with SIP, H.323, or any other signaling protocol.
- Each LS maintains a local routing database called TRIB ("Telephony Routing Information Database” for "Telephony Routing Information Database”).
- This routing base is powered by advertisements received from neighboring LSs (from another telephony domain, for example).
- the operation of the TRIP protocol is similar to that of the Border Gateway Protocol (BGP). Advertisements between neighboring LSs are performed as route update messages, called UPDATE messages. These messages are defined by the TRIP protocol and are exchanged between the LSs to inform a neighboring domain of the available routes.
- each ITAD being administered by a single telephone operator.
- IP IP
- These operators each have one or more LSs.
- Each LS maintains a database of routing it feeds with advertisements received from its neighbors (ie other areas) and LS its own domain. These ads are updated and redistributed to other neighbors if interconnection agreements allow.
- the T1TAD4 LS 14 for example, updates the advertisements received from the FITAD5 LS 15 and re-propagates them to ITAD3 13. It should be noted that an ITAD is not necessarily deployed on a single AS or " IP transfer domain ".
- an LS treats three types of routes: - external routes, received from LS located in neighboring ITADs; internal routes (Internai Routes), received from LS located in the same
- ITAD Local Routes, configured locally in each LS for injection into TRIP processes. This operation is performed either by static configuration or by redistributing information from other routing protocols.
- Adj-TRIBs-In 22 stores the routing information conveyed by UPDATE messages. This routing information, also called “routes”, is the input to a route selection process.
- Ext-TRIB 24 Only one "Ext-TRIB” (“external TRlB”) table is maintained by LS. This table contains the result of a route selection process applied to the external roads 25 ("Adj-TRIBs-IN”) and local roads 26 ("Local Routes"). Prior art techniques allow only one route to be chosen per destination;
- Loc-TRIB 20 (“Local TRIB”): This table contains local routes resulting from the application of local routing policies to each LS; “Adj-TRIBs-Out” 23 (“Adjacent TRIB out”): These are the roads that the
- the QoS-Enhanced Border Gateway Protocol can be used to determine the QoS processing that will be reserved for voice streams by the layers. network / Transport.
- the service layer managed by the TRIP protocol, for example, does not have any information on the status of the transfer of data at the level of the transport layer, and even less on the crossed AS for the placement.
- an LS does not have means to select a data transfer path based on the IP connectivity operator that supports the routing of the traffic.
- the TRIP protocol is able to maintain the path of crossed ITADs (service layer) but not that of traversed AS (network / transport layers).
- a provider or operator of telephony services has, so far, no way of knowing by which AS, the voice data transit, and can thus ensure that they transit through AS of a competitor, even if the path to the "service" level is determined.
- the ITADl 31 1 on which the client S 301 depends chooses the telephone level route through ITAD2 312, ITAD3 313 and finally ITAD6 316 on which the recipient D 302 depends, to control the transfer of the voice data.
- this telephone-level route assumes the existence of an IP route traversing AS1 domains 321, AS2 322.
- the solution proposed by the invention makes it possible to overcome these disadvantages of the prior art, by means of a method for propagating at least one routing route of at least one digital stream between a first location server of a first IP telephony domain and a second location server of a second IP telephony domain, said first location server belonging to an autonomous system, for transferring said at least one digital stream, according to the invention, such a method comprises a phase propagating at least one identification information relating to said autonomous system of said first location server to said second server.
- the invention is based on an approach quite the propagation of routes routing, enabling a location server to obtain the identity of the loaded autonomous system to perform the actual transfer Datas.
- location servers propagate telephony routes that may not be associated with actual data transport routes.
- the method according to the invention makes it possible to obtain the identification of the autonomous systems used during transport at the level of the telephony routes.
- the telephony domain entity may be any system for transferring / advertising / exchanging telephony routes in telephony domains.
- said propagation phase comprises the following steps: identification of said autonomous system; composing a propagation message comprising said identification information relating to said autonomous system to said second location server; transmitting said propagation message to said second location server.
- the propagation of a road is carried out in three stages.
- the step of identification of the autonomous system (AS) by the entity of the first IP telephony domain allows the recovery of the identity of the autonomous system.
- This identity is then inserted into a route propagation message, announcing or updating a telephony route to a given destination and transmitted to the second location server.
- This second location server thus becomes aware of the autonomous system of the first location server (or of the list of autonomous systems to join said destination).
- said composing step comprises the following steps: obtaining a list of propagation information within said first location server; modifying said propagation information list obtained by adding the identification information relating to said system standalone if said second IP telephony domain of said second location server is different from said first IP telephony domain of said first location server inserting said modified list of propagation information in said propagation message.
- the composition of the propagation message to said second telephony domain location server begins with obtaining a list of propagation information.
- This list previously present in said first location server is updated if the second location server is different from the first if a route is already present in the LS, otherwise the list is initialized to the value of the local autonomous system.
- This update consists of adding the autonomous system identifier of the first location server to the propagation list.
- the propagation list thus makes it possible to broadcast the identification data of the crossed ASs to reach the destination, to the telephony domain entities (local or neighbor).
- said propagation information list comprises a sequence of propagation information segments, and one of said propagation information segments contains attributes belonging to the group comprising at least: information representative of a scheduling of propagation information autonomous systems; information representative of a number of autonomous systems; at least one identification information of an autonomous system.
- the propagation list therefore contains data segments. These segments gather information about autonomous systems. The information may contain this segment allow to know the scheduling of autonomous systems, the number of systems in the segment and the identification of autonomous systems. Thus, the domain entity of telephony that receives this list is able to build a database of routing routes identifying the autonomous systems to borrow to reach a given destination.
- said step of obtaining said list of propagation information comprises: a copying step of said propagation information list if said propagation information list exists; a step of creating a new list of propagation information if said list of propagation information does not exist.
- the telephony domain entity can still provide a list of propagation information to another telephony domain entity if the latter requests it.
- the invention also relates to a location server of a first IP telephony domain, capable of propagating at least one of at least routing route a digital stream to a second location server of a second domain IP telephony, said first location server belonging to an autonomous system, for transferring said at least one digital stream,
- a location server comprises means for propagating at least one identification information of said autonomous system from said first location server to said second location server.
- the location server is able to provide information identifying autonomous systems to cross during the actual transfer of digital streams.
- such a location server comprises means for implementing the steps of the method of propagation of routing routes.
- the invention also relates to a program product downloadable from a computer network communication and / or stored on a computer readable medium and / or executable by a microprocessor.
- such a computer program product includes program code instructions for executing the routing route propagation method as described above.
- FIG. 1 presented in relation with the prior art, presents an exemplary architecture of a network managed by the TRIP protocol;
- FIG. 2 illustrates the structure of the routing databases (TRIB) used by the location servers (LS) routing the calls in the telephony domains (ITAD) presented in FIG. 1;
- Figure 3 already introduced, illustrates one of the disadvantages of the state of the art, such as spirals;
- Figure 4 describes the route propagation between two location servers.
- the invention therefore proposes to improve the operation of the TRIP protocol and thus to allow new functionalities.
- the general principle of the invention is based in particular on the introduction of a new attribute, in which are contained information on the IP connectivity service providers used to route the voice traffic. More clearly, the invention allows the service layer to identify the ASs, or IP connectivity operators used for the routing of voice traffic.
- this information can be used to improve the quality of service of inter-domain telephone calls.
- an LS has a simple and effective way to optimize an end-to-end path for a given destination.
- This same information also makes it possible to detect anomalies, such as IP spirals, for example, since the service layer is aware of the ASs through which data travels to reach the final destination of a given call.
- the present application details only the principle of the feedback of information, or identifiers, relating to the transport layer.
- a list of identifiers relating to the transport layer is obtained, then to be propagated between the LSs implemented by the ITADs. More precisely, a new attribute containing one or more numbers (identifiers) of AS is now described. It makes it possible to identify the traversed AS to convey voice to a given destination. This number / identifier is provided to an administrative management domain (ITAD) which transmits it to a neighboring domain.
- ITAD administrative management domain
- This document presents an embodiment based on the location servers LS. It is understood that this embodiment is only an example of implementation. In particular, the invention can be implemented entirely using proxy servers (also called servers "Proxy”) or other functional element defined in a future protocol but whose features incorporate those defined for an LS in the context of this invention.
- the TRIP protocol is implemented by the LS (location servers) that propagate TRIP routes, containing attributes to qualify the routes exchanged.
- TRlP Transcription Routing over IP
- AS_PATH In order to know the IP connectivity service providers used to route voice traffic from an ITAD to a given destination, a new attribute named AS_PATH is introduced. This attribute is defined as follows: Conditional Mandatory; true
- TRIP Type Code To be defined by IANA.
- This parameter indicates whether the attribute in question should be filled in or not in a TRIP message.
- TRIP Type Code This parameter indicates a unique identifier of the TRiP message in question.
- This attribute is to create and store a list of traversed ASs to reach the destination in question.
- U is then propagated an IP telephony domain (ITAD) to a neighboring IP telephony domain and so on.
- ITID IP telephony domain
- the AS-PATH attribute consists of a sequence of segments, or fields, "AS path".
- Each "AS path” segment is composed of a ⁇ path segment type, path segment length, and path segment value> triplet, defined as follows: each "path segment type” has a length of 1 byte which can take the following values:
- AS_SET Unordered series of AS traversed by a route contained in an UPDATE TRJP message.
- AS_SEQUENCE An ordered series of AS traversed by a route contained in an UPDATE TRJP message.
- each path segment length has a length of 1 byte and contains the number of ASs contained in the path segment value; the field "path segment value" contains one or more AS numbers, each encoded as a field of 2 bytes long.
- This new attribute therefore lists the succession of AS traversed by the data associated with a call.
- Each LS maintains a routing table that it feeds with advertisements received from LSs of neighboring domains or those of its own domain. These ads are updated and redistributed to other neighbors if interconnection agreements allow. The procedure is described in connection with FIG.
- an LS 41 when an LS 41 propagates (41 1) a TRIP 412 route that it has learned in an UPDATE message 410 from another neighbor LS 40, it is expected that it modifies the new attribute AS_PATH 413 of the route depending on the type of LS 42 to which it must re-propagate the route, according to the following procedure.
- a given LS announces the route to another TRlP LS peer located in its own ITAD, this LS does not modify the AS_PATH attribute related to that route.
- the local system adds the number of its IP connectivity service provider (ie the AS identifier) as the last element of the sequence; if the first segment of AS_PATH is of type AS_SET, the local system adds a new segment of type AS_SEQUENCE at the beginning of I 1 ASJPATH; this new segment contains the domain number of its IP connectivity service provider.
- the advertisement includes the IP connectivity service provider's number in the AS PATH attribute of all UPDATE messages to be sent to its TRIP peers in neighboring ITADs.
- the LS includes an empty AS_PATH in all UPDATE messages to send to its TRIP peers located in its own ITAD.
- This attribute can be exploited by the route selection process to eliminate routes containing spirals at the IP level.
- this attribute can be used by an ITAD to guide the process of updating Quality of Service information contained in TRIP routes.
- This attribute can also be used to determine the IP processing associated with a given call.
- an ITAD In the case where an ITAD is attached to several ASs, it can advertise some of its prefixes by indicating that these prefixes are managed (at the IP level) by a provider X and another part of its prefixes indicating that these prefixes are managed by a supplier Y.
- New alphanumeric numbers are introduced here. Such numbers allow the routing of calls to numbers other than those defined by E.164. With this extension, VoIP service platforms such as those that do not use traditional telephone numbers can interconnect with other operators to provide a global voice service.
- the "Address Family" field of a TRIP route can take the value
- DIGIT mark
- separators alpha lowalpha
- upalpha upalpha "A" I "B” I "C” I "D” I "E” I "F”
- New numbers proposed to be propagated using the TRIP protocol can then have the following format; 1. medf @ franceteleeom
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| FR0603624 | 2006-04-21 | ||
| PCT/FR2007/051147 WO2007122352A1 (fr) | 2006-04-21 | 2007-04-20 | Procede de propagation d'information de connectivite ip entre domaines de telephonie ip distinct, serveur de localisation et programme d'ordinateur correspondants |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| EP2014030A1 true EP2014030A1 (de) | 2009-01-14 |
Family
ID=37546331
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| EP07731922A Withdrawn EP2014030A1 (de) | 2006-04-21 | 2007-04-20 | Verfahren zum propagieren von ip-konnektivitätsinformationen zwischen distinkten ip-telefoniedomänen, lokalisierungsserver und computerprogramm |
Country Status (3)
| Country | Link |
|---|---|
| US (1) | US8457105B2 (de) |
| EP (1) | EP2014030A1 (de) |
| WO (1) | WO2007122352A1 (de) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2014030A1 (de) | 2006-04-21 | 2009-01-14 | France Télécom | Verfahren zum propagieren von ip-konnektivitätsinformationen zwischen distinkten ip-telefoniedomänen, lokalisierungsserver und computerprogramm |
| EP2014031A1 (de) * | 2006-04-21 | 2009-01-14 | France Télécom | Verfahren zur auswahl einer telefonieroute in einer ip-telefoniedomäne, entsprechende einrichtung und computerprogramm |
Family Cites Families (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6584093B1 (en) | 1998-08-25 | 2003-06-24 | Cisco Technology, Inc. | Method and apparatus for automatic inter-domain routing of calls |
| US6741585B1 (en) | 2000-05-05 | 2004-05-25 | Lucent Technologies Inc. | Interworking of addressing in an internetwork |
| US7002973B2 (en) | 2000-12-11 | 2006-02-21 | Acme Packet Inc. | System and method for assisting in controlling real-time transport protocol flow through multiple networks via use of a cluster of session routers |
| US7072303B2 (en) * | 2000-12-11 | 2006-07-04 | Acme Packet, Inc. | System and method for assisting in controlling real-time transport protocol flow through multiple networks |
| US7565448B1 (en) | 2004-02-03 | 2009-07-21 | Sprint Communications Company L.P. | Network control system for a communication network |
| US7756998B2 (en) * | 2004-02-11 | 2010-07-13 | Alcatel Lucent | Managing L3 VPN virtual routing tables |
| US7814227B2 (en) | 2005-03-04 | 2010-10-12 | Cisco Technology, Inc. | Computation of a shortest inter-domain TE-LSP across a set of autonomous systems |
| US20060262776A1 (en) * | 2005-05-23 | 2006-11-23 | Pollock Graham S | System and method for auto-discovery of peering and routing in a combined circuit -switched/packet-switched communication network using trip protocol |
| FR2900300A1 (fr) | 2006-04-21 | 2007-10-26 | France Telecom | Procede de propagation de routes de telephonie ip multiples, dispositif et programme d'ordinateur correspondants |
| EP2014030A1 (de) | 2006-04-21 | 2009-01-14 | France Télécom | Verfahren zum propagieren von ip-konnektivitätsinformationen zwischen distinkten ip-telefoniedomänen, lokalisierungsserver und computerprogramm |
| US8761155B2 (en) | 2006-04-21 | 2014-06-24 | France Telecom | Method of taking account of quality of service between distinct IP telephony domains, and a corresponding location server and computer program |
| US7565488B2 (en) * | 2006-07-26 | 2009-07-21 | International Business Machines Corporation | Apparatus, system, and method for integrated blade raid controller and storage |
| US9065888B2 (en) | 2007-02-16 | 2015-06-23 | Orange | Method for optimizing the routing of communications between a plurality of telephony domains, corresponding signal, device and computer program |
-
2007
- 2007-04-20 EP EP07731922A patent/EP2014030A1/de not_active Withdrawn
- 2007-04-20 WO PCT/FR2007/051147 patent/WO2007122352A1/fr not_active Ceased
- 2007-04-20 US US12/297,985 patent/US8457105B2/en not_active Expired - Fee Related
Non-Patent Citations (1)
| Title |
|---|
| See references of WO2007122352A1 * |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2007122352A1 (fr) | 2007-11-01 |
| US20090175267A1 (en) | 2009-07-09 |
| US8457105B2 (en) | 2013-06-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2014031A1 (de) | Verfahren zur auswahl einer telefonieroute in einer ip-telefoniedomäne, entsprechende einrichtung und computerprogramm | |
| EP2469428B1 (de) | Datenauswertung für Dienste | |
| JP2004538671A (ja) | スクリーニングによって、複数のネットワークを流れるリアルタイムトランスポートプロトコルの制御を支援するシステム及び方法 | |
| EP3085065B1 (de) | Verfahren zur aktualisierung der von einem dns server erhaltenen informationen. | |
| EP3732829B1 (de) | Verfahren zur durchführung von daten aus einer initialisierten sitzung zwischen terminal und server | |
| WO2009125158A2 (fr) | Procede de routage d'un paquet de donnees dans un reseau et dispositif associe | |
| US20070280225A1 (en) | Extended services and recommendations | |
| EP2057795B1 (de) | Verfahren zum propagieren von mehreren ip-telefonierouten, entsprechender lokalisierungsserver und computerprogramm | |
| EP2109991B1 (de) | Optimierung der leitweglenkung von kommunikationen zwischen mehreren telefoniedomänen | |
| EP2052505A1 (de) | Verfarhen zur berücksichtigung der dienstgüte zwischen distinkten ip-telefoniedomänen, entsprechender lokalisierungsserver und computerprogramm | |
| WO2007122352A1 (fr) | Procede de propagation d'information de connectivite ip entre domaines de telephonie ip distinct, serveur de localisation et programme d'ordinateur correspondants | |
| EP2984786B1 (de) | Zentralisierte architektur zur herstellung von gruppen von inhaltsverteilern | |
| EP2801178B1 (de) | Dynamisches verfahren zur bestimmung einer liste von diensten in einem sip-netzwerk | |
| Bons et al. | IPv6: Drivers and Barriers for Adopting | |
| FR2872369A1 (fr) | Procede de gestion d'une interconnexion entre reseaux de telecommunication et dispositif mettant en oeuvre ce procede | |
| US20100067399A1 (en) | Method and apparatus for analyzing proposed service features in a communication network | |
| EP2254288B1 (de) | Verfahren zur Vermeidung von Schleifen im Inter-Domain Routing | |
| US20060165065A1 (en) | Communications address provisioning system and method therefor | |
| WO2020002792A1 (fr) | Procédé de communication mis en œuvre par un premier routeur d'un système autonome utilisant un protocole de routage interne | |
| George et al. | Shared Transition Space: Is it necessary? | |
| WO2007063211A1 (fr) | Declenchement automatique de communications |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
| 17P | Request for examination filed |
Effective date: 20081114 |
|
| AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC MT NL PL PT RO SE SI SK TR |
|
| AX | Request for extension of the european patent |
Extension state: AL BA HR MK RS |
|
| DAX | Request for extension of the european patent (deleted) | ||
| RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: ORANGE |
|
| 17Q | First examination report despatched |
Effective date: 20160311 |
|
| STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
| 18D | Application deemed to be withdrawn |
Effective date: 20171103 |