EP2918064A1 - Procédé de résolution d'un numéro de téléphone porté en un identifiant de ressource réseau - Google Patents
Procédé de résolution d'un numéro de téléphone porté en un identifiant de ressource réseauInfo
- Publication number
- EP2918064A1 EP2918064A1 EP13801646.4A EP13801646A EP2918064A1 EP 2918064 A1 EP2918064 A1 EP 2918064A1 EP 13801646 A EP13801646 A EP 13801646A EP 2918064 A1 EP2918064 A1 EP 2918064A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- domain
- network
- telephone number
- server
- dns
- 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.)
- Ceased
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
- H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
- H04M7/128—Details of addressing, directories or routing tables
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4557—Directories for hybrid networks, e.g. including telephone numbers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/60—Types of network addresses
- H04L2101/618—Details of network addresses
- H04L2101/65—Telephone numbers
Definitions
- the present invention relates to telecommunications networks, in particular networks of the IP ("Internet Protocol”) type.
- the present invention relates to the identification of the network or domain to which a user belongs, based on the user's public telephone number. It will be said that a user "belongs" to a certain domain of the network of a given operator when this user has an account with this operator, and this, regardless of the access network or the device (s) ) used by this user to connect to the operator network.
- ITU-T Recommendation E.164 the format of international public telephone numbers is defined by ITU-T Recommendation E.164; the ITU-T is a part of the ITU ("International Telecommunication Union") responsible for the development of international standards.
- IP networks support conversational services, such as “VoIP” (VoIP), “Content Sharing”, or “Instant Messaging”.
- VoIP Voice over IP
- VoIP Voice over IP
- Content Sharing Voice over IP
- IP networks are generally able to implement advanced session control protocols, such as H. 323 or SIP.
- H.323 is a combination of a set of audiovisual communication protocols in an IP network developed by the ITU-T. They concern signaling, negotiation of data encoding parameters, and data transport. They are widely used in Voice over IP and in video conferencing as well as only in several real-time Internet applications such as "NetMeeting".
- the SIP protocol (initials of the words “Session Initiation Protocol” meaning “Session Initiation Protocol”) was defined by the Internet Engineering Task Force (IETF) in RFC 3261. This protocol allows the establishment, modification and termination of multimedia sessions in a network using the IP protocol.
- IETF Internet Engineering Task Force
- the SIP protocol is used in particular in infrastructure type IMS (initials of the words "IP Multimedia Subsystem” meaning “Multimedia subsystem over IP”).
- the IMS is defined by the 3rd Generation Partnership Project (3GPP).
- 3GPP 3rd Generation Partnership Project
- This network architecture applicable to both mobile and fixed access networks, enables the dynamic establishment and control of multimedia sessions between two clients as well as the reservation of resources at the level of the network for transporting multimedia streams. Through this architecture, network operators can conveniently implement a management policy, provide a predetermined Quality of Service, and calculate the amounts to be billed to customers.
- the IMS currently provides access to telephony, videophone, Presence and Instant Messaging services, which it also manages.
- IP network communication services can identify physical or virtual resources by means of strings, for example an H.323 alias or a "URI" (initials of the English words “Uniform Resource Identifier” meaning “Uniform Resource Identifier”). ).
- the syntax of URIs is defined in RFC 3986 of the IETF; the knowledge of the URI of a resource makes it possible to obtain the IP address of a device of the network of the operator managing this resource.
- two types of resource identifiers are distinguished: those of the form "SIP-URI” as defined in RFC 3261, or those of the form "tel-URI” as defined in RFC 3966.
- a SIP-URI is of the form "sip: user @ host” (for example, sip: alice @ domain1), where the "host” part identifies the domain of the operator responsible for the identity represented by the "user” part.
- URI any type of physical or virtual application resource identifier accessible on a network.
- DNS system (initials of the words "Domain Name System” meaning “System of Domain Names”) is a service for finding information from a domain name.
- DNS servers make available to any computer-client ("DNS resolver") that has issued a DNS query domain-name / information-of-certain-type associations, called “resource records” ( “Resource records”).
- DNS resolver any computer-client
- resource records “Resource records”
- NAPTR Natural Authority Pointer Resource Records
- RFC 3403 specify substitution rules to be applied to a string of NAMS. characters in order to produce a certain result, such as, for example, another domain name or a URI.
- the DNS system via NAPTR records, allows to match one character string to another by means of a domain name search: it suffices, by applying a rule specific to the application concerned, to transform the chain from original characters to a domain name, which will be associated with a substitution rule to apply to the original string to produce the desired result.
- the network / domain hereinafter referred to as the "originating domain”, to which the caller belongs must therefore know the identity of the network / domain, referred to as " recipient domain "below, to reach the called user.
- the caller knows very often only the telephone number of the called user, said phone number being in public format according to recommendation E.164 or in a private format.
- this phone number does not easily determine the identity of the recipient domain; in other words, there is no automatic association between the identifier E.164 and the URI (or URIs) of the destination domain.
- a domain may have several input URIs, which may also possibly be a function of the identity of the domain of the caller; for the sake of brevity, in this document, the "URI of the destination domain” is sometimes referred to as the input URI (s) of this domain.
- the original domain route calls on the basis of slices of telephone numbers, similar to the routing performed in the Public Switched Telephone Network (PSTN) Public Or PSTN, in English) or in mobile switched networks such as the Public Land Mobile Network (PLMN). But such a routing is expensive in operational management (initial configuration, plus any modifications).
- PSTN Public Switched Telephone Network
- PLMN Public Land Mobile Network
- the originating domain has only partial knowledge of the management of the numbering plan of the country of destination, which may impose intermediaries and prevent the establishment of a direct relationship. between the origin domain and the destination domain.
- This type of solution requires dedicated, non-mutualizable processing with the processing implemented for the routing of alphanumeric URIs, that is to say URIs whose component "user” (as “alice” in sip: alice @ domain1 ) is not a telephone number, said routing using the "host” component of the URI (as "domainl” in sip: alice @ domain1).
- the original domain implements an ENUM application.
- the ENUM application uses a database specific to the network to which this original domain belongs and which contains particular NAPTR records defined in RFC 3761.
- the ENUM application makes it possible, by DNS query by means of an interrogation key (as described above) representative of a telephone number in E.164 format, to know the URIs that can be used to reach a correspondent.
- These URIs point to resources or services associated with the correspondent's E.164 number such as, for example, an e-mail address, a web page, a directory service, fixed or mobile forwarding numbers, or an alias of Voice over IP, video telephony or instant messaging for SIP or H.323 protocols.
- two cases may arise when querying an ENUM database.
- the query key appears in this ENUM database and the corresponding NAPTR record configures the value "u” to a parameter called “Flags” (provided in RFC 3761).
- This value "u” indicates that this request ENUM is final ("terminal” in English), in that the response to the request directly provides one or more URI (s) of the called (in case of plurality of URIs , the answer also provides a recommendation as to their order of treatment).
- the interrogation key does not appear in this ENUM database.
- the routing can not be performed in accordance with the mechanism just described, but requires, inconveniently, that the operator of this network set up an ad hoc mechanism dedicated to unknown telephone numbers.
- This ad hoc mechanism which varies from one operator to another, may consist of complicating the methods for analyzing numbers at the call server level, or defining a default route, for example imposing the transit via the switched network. RTC.
- This problem of portability concerns any type of telephone call, that is to say any operation intended to establish a network session (Voice over IP, videoconference, instant messaging, and so on) using for this purpose a number of calls. called phone. More generally, this problem concerns any message of a session control protocol (for example, SIP or H.323) using a telephone number as a routing identifier, whatever the purpose of this message, for example the establishment of a phone call, logging in, subscribing to the status of a resource (SIP SUBSCRIBE message), or requesting the capacity of a resource (SIP OPTIONS message).
- a session control protocol for example, SIP or H.323
- the "user" associated with a telephone number serving as a routing identifier may be a human person or a machine (for example, an answering machine), but also a service, said service having been initially hosted. by a first operator domain, then ported to a second operator domain.
- One solution to this problem could be to record in each ENUM database all the portability data (for example, the current network / domain to which the user associated with the telephone number belongs), or at least those concerning outgoing numbers of the network considered; but such a solution would have big impacts on the management processes of the data of portability (power supply, update, control of coherence, and so on), in particular due to the fact that the infrastructures DNS managed by distinct operators are of made separate and waterproof; this solution is therefore very difficult to implement in practice.
- a second solution would be to upgrade the existing ENUM servers to include a query interface of the historical number portability database. But such a solution is contrary to DNS logic; moreover, it assumes as many developments as separate ENUM servers deployed, which would make the network operator highly dependent on its ENUM server providers.
- a first drawback of this "NS records" solution is that the operators involved must agree on a common ENUM root.
- a second disadvantage is that it multiplies by three the amount of records stored at the taker operator; the licenses of ENUM server manufacturers can be proportional to the volume, this solution would be extremely expensive.
- the present invention therefore relates to an ENUM database, containing at least one CNAME or DNAME record providing a return domain in response to an interrogation key function of the telephone number of a called called user.
- Said ENUM database is remarkable in that said called party belongs to said return domain and in that said telephone number has been ported in relation to a network / domain change of the called party.
- a redirection of DNS queries is implemented by means of DNS records of particular types, called CNAME and DNAME (the definition of which will be recalled below).
- DNS records of particular types, called CNAME and DNAME (the definition of which will be recalled below).
- These records which are generally known, make it possible to substitute for the domain name to which the DNS request relates a new domain name, referred to as the "return domain", which will serve as a search key for a subsequent interrogation of an ENUM application. It is thus known to which domain, and with which interrogation key, a DNS request can be redirected in order to obtain information concerning the current URI associated with a telephone number which has previously been ported.
- the name of this return domain was in fact entered into said ENUM database during the procedure of portability of the telephone number, that is to say when the user of this telephone number has changed domain.
- the invention does not require any naming convention between operators.
- the supply of an ENUM database required to implement the invention is very simple, and does not require frequent updating of the data, because it does not manipulate the portability data themselves. , by nature variable in time, but data configurations, which are essentially static.
- the present invention makes it possible to have separate DNS roots and to simply switch from one tree to another. It does not therefore require managing a common root in a dedicated server; it does not require delegation of zones to the assignor operator and therefore does not oblige to create multiple zones in the operator's server.
- the present invention thus makes it possible:
- the ENUM database according to the invention can be advantageously associated with a fixed or mobile circuit switched telephone network. This may be, for example, the "historical" database conventionally used by the RTC.
- said ENUM database is entirely dedicated to ported phone numbers.
- the manager of the ENUM database includes CNAME or DNAME records relating to a set of respective telephone numbers coming out of various respective networks / domains and for which this manager knows the respective return domain, in order to be able to answer (possibly for a fee) a request for information regarding the portability of a particular telephone number.
- the invention relates to a DNS server associated with an ENUM database as briefly described above.
- the invention relates to the use of an ENUM database as briefly described above.
- the invention relates to a method of resolution by a network / domain, said domain of origin, the telephone number of a user, called called, belonging to a network / domain, said destination domain, comprising the following steps:
- a server of the domain of origin in charge of routing said message or a DNS server, generates a key of interrogation function of the telephone number and a domain name, said domain penultimate, c) a request DNS is sent to a DNS server associated with the penultimate domain,
- said DNS server associated with the penultimate domain performs, by means of said interrogation key, a search in an associated ENUM database,
- said search provides at least one CNAME or DNAME record containing a representation of a network / domain, referred to as the return domain, and
- Said method is remarkable in that said return domain comprises said destination domain, and in that said telephone number was, prior to sending said message, related to a network / domain change of the called party.
- said message may be a telephone call
- said server of the original domain in charge of routing the message be a call server.
- a URI may optionally identify a user of a non-IP network (for example, a URI of type "tel:" according to RFC 3966 may identify a user of a PSTN or GSM network)
- the method according to the invention applies to messages using as a routing identifier a telephone number which has been ported from an IP or non-IP network to another IP or non-IP network.
- the term "penultimate domain” refers to the domain associated with an ENUM database as briefly described above, that is to say containing a type registration.
- the term "penultimate domain” refers to the domain associated with the last DNS server consulted before consulting a DNS server associated with the destination domain.
- the DNS server of the origin domain first queried by the origin domain server in charge of routing the message will return directly to the destination domain: the penultimate domain will then be identical to the original domain.
- the penultimate domain will then not necessarily be identical to the domain of origin; for example, said penultimate domain could be a third party network separate from said origin domain and said destination domain, and in this case the called party's telephone number could belong to a slot whose use has been delegated to the operator of said third party network.
- a database comprising a record associating a representation of said telephone number with a representation of a user identifier. current resource (URI) of the called party.
- URI current resource
- the "resolver" DNS that is to say the server of the network issuing a new DNS query can be, recursively, the DNS server that has just been interrogated, or, iteratively, the server of the original domain in charge of routing the message.
- the advantages offered by these methods are essentially the same as those offered by the ENUM databases succinctly described above.
- the invention also relates to a computer program downloadable from a communication network and / or stored on a computer readable medium and / or executable by a microprocessor.
- This computer program is notable in that it includes instructions for performing the steps of the method of resolving a telephone number succinctly set forth above, when executed on a computer.
- FIG. 1 shows examples of conventional NAPTR recordings
- FIG. 2 schematically illustrates the successive steps of a method for resolving a ported telephone number, according to one embodiment of the invention
- FIG. 3a shows a first record obtained during the implementation of this embodiment
- FIG. 3b shows a second record obtained during the implementation of this embodiment
- NAPTR records specify how to produce a URI from an original string from which a query key in the form of a name is derived. domain, on which the DNS request is. This original string is called AUS (initials of the words “Application Unique String” meaning “Character String for Single Application”). Equally, NAPTR records are also said to represent "rewrite” rules to be applied to an AUS.
- the parameters of the NAPTR records are:
- Order indicates the order in which to evaluate NAPTR records; as long as there are still records of the same Order value to review, the records of the following "Order" values are irrelevant;
- Flags indicates, for example, whether the record describes a transient rewrite (the result of which is a domain name pointing to another record) or a final rewrite; the precise semantics of the "Flags” parameter depends on the DDDS application used (DDDS are the initials of the words “Dynamic Delegation Discovery System” meaning “Dynamic System of Delegation Discovery", this system is described in RFC 3401);
- the ENUM function is precisely a special DDDS application in which the AUS consists of a telephone number.
- the AUS consists of a telephone number.
- the value of "Services" specifies the type of the resulting URI (for example, SIP-URI, or tel-URI, or email address).
- a domain name identifies a network node, including an IP network.
- Each node has a set (possibly empty) of resource information.
- the set of resource information associated with a given name is composed of "Resource Records" (RR).
- RR Resource Records
- a DNAME non-terminal DNS name redirection
- a PTR which is a pointer to other data in the DNS system
- hosts and other resources often use multiple names to identify the same resource. For example, the names orange.com and orange-ftgroup.arpa could identify the same host. Similarly, in the case of mailboxes, many organizations provide multiple names that actually relate to the same mailbox.
- a CNAME / DNAME type RR identifies its owner name as a nickname, and specifies the corresponding canonical name in a section of the RR called RDATA.
- the CNAME and DNAME RRs share the fact that a query of such RR returns data corresponding to a domain name different from the domain name being queried.
- the difference between these two types of resource records is that a CNAME RR redirects presented DNS queries to the owner of the record to another (unique) name, while a DNAME RR redirects DNS queries presented to a descendant. from the owner of the record to corresponding names under another (unique) node of the tree.
- a DNAME RR redirects a query from one part of the DNS name tree to another part of the DNS name tree.
- a DNS server When a DNS server fails to find the desired RR in the resource set associated with the domain name, it checks whether the resource set consists of a CNAME or DNAME record with a corresponding "class". If this is the case, the DNS server includes this record in its response, and resumes the search at the domain name specified in the RDATA field of the CNAME / DNAME record.
- DNS servers must be well-designed to respond properly when presented with a CNAME / DNAME string, or a loop: they are expected to follow the CNAME / DNAME string, and report CNAME / DNAME loops as errors.
- domain of origin belonging to an IP domain
- Boernardo the "Bernardo”
- the routing of this call requires knowledge of the input URI of the IP domain, called "recipient domain” B, to which Bernardo belongs.
- the call sent by Alice is received by a call server of the operator A managing the origin domain A.
- a call server of the operator A managing the origin domain A.
- the origin domain A is, or is included in, an IMS type network - in which case the call server is generally constituted by an S-CSCF server; it is recalled in this respect that the IMS networks comprise one or more servers called "S-CSCF" (initials of the words "Serving-Call Session Control Function” meaning “Function of Session Call Control Session”), which are apt (among other functions) to manage the procedure for registering users on the network.
- S-CSCF server
- this S-CSCF server having determined that the called number complies with the E.164 standard, performs a conversion of this number into an expression constituting a domain name, and which will allow, as a that interrogation key, a search of the URI attached to the called Bernardo in an ENUM database of a DNS server of the original domain A. Then, the S-CSCF server sends a request containing this key d query to this DNS server.
- the S-CSCF server constructs the expression "98765432133” by inverting the order of digits, then inserting dots between each pair of digits. successively, the expression "9.8.7.6.5.4.3.2.1 .3.3”. Then, this last expression is concatenated to a predefined domain name, let's call it "root”, to obtain the expression "9.8.7.6.5.4.3.2.1 .3.3. root ".
- RFC 3761 defines the value of "root” as "e164.arpa. For public DNS servers; For private DNS servers, it is allowed to define its own root.
- the ENUM function searches its database by means of the interrogation key "9.8.7.6.5.4.3.2.1 .3.3. root ". In the case where "root” is "e164.arpa.
- These records may be, for example, those shown in Figure 1.
- the second record makes it possible to obtain the URI "h323: bernardo @ example1 .corn" associated with an H.323 network, and
- the third record provides the email address "mailto: bernie@example2.com”.
- these URIs are sent to the call server (here, S-CSCF server) of the original domain A, in response to the DNS request.
- the call establishment request is routed, preferably (taking into account the values of the "Order” and "Preferences” parameters), to another SIP server associated with the "b.com” domain.
- This SIP server which is the entry point to the network associated with the domain name "b.com" is generally an l-CSCF server (initials of the words “Interrogating-Call Session Control Function” meaning “Command Function Interrogator Call Session ”) in the case of an IMS network.
- Steps ⁇ , E'2 and E'3 are then implemented, which are respectively analogous to steps E1, E2 and E3 above.
- the (private) value of "root” is "e164.RootA0".
- step E'4-a the ENUM function of the root server performs a search in its database by means of the interrogation key "9.8.7.6.5.4.3.2.1 .3.3.e164. RootA0 ", and there is the record of Figure 3a.
- This figure 3a shows an example of a DNAME record for a French telephone number, the effect of which is that any DNS request for a domain name under 3.3.e164.RootA0 is redirected to a DNS server (or an application emulating the functionality of a DNS server) - let's call it RootA - associated with the original domain A and loaded with phone numbers starting with "+33".
- the ENUM function deduces that the search must continue using a return domain, namely "3.3. e164.RootA.fr republic
- ENUM database containing a DNAME record is considered here, whereas conventional ENUM databases usually contain only NAPTR records.
- l-ENUM ENUM Infrastructure
- said record type DNAME allow, pending the completion of this construction, to send DNS queries concerning the domain "e164.arpa" to a DNS server belonging to this unique tree; such a DNAME type record could then be associated with an iterative string of CNAME records.
- this information is sent to the call server (here, S-CSCF server) of the original domain A, in response to the DNS request.
- the call server here, S-CSCF server
- the call server sends a new DNS request to the DNS server RootA, by means of the interrogation key "9.8.7.6.5.4.3.2.1 .3.3. e164.RootA.fr Farm
- This DNS server finds in its ENUM database a CNAME record, illustrated in FIG. 3b, containing, in its RDATA field, the expression "9.8.7.6.5.4.3.2.1 .3.3. RootB.fr ", which provides a return domain" RootB.fr "managed by an operator B.
- an ENUM database containing a CNAME record is considered here, whereas, as noted above, conventional ENUM databases usually contain only NAPTR records.
- this new information is sent to the call server (here, S-CSCF server) of the original domain A.
- the call server performs, by means of the interrogation key "9.8.7.6.5.4.3.2.1 .3.3. RootB.fr ", a search in the records of the DNS server of the operator B, and there finds the recording illustrated in figure 3c.
- This record, NAPTR type provides a current SIP-URI Bernardo, namely "sip: bernardo@b.com", similar to step E4 described above.
- the ENUM database of the RootA DNS server is an ENUM database according to the invention since it contains a record of CNAME type returning to the destination domain B.
- this server is associated to domain of origin A, this domain of origin A is here a "penultimate domain" within the meaning of the invention.
- this URI is sent to the call server (here, S-CSCF server) of the original domain A, in a similar manner to the step E5 described above.
- step E'6 is implemented, which is similar to step E6 described above.
- the slice for example, "+3312345”
- a third party network for example, "lambda.fr”
- the consultation in step E'4- a of the root server of the original domain A discovers a DNAME record returning to this third party network, and is interrogated at the step E'4-b an ENUM base associated with this third party network by means of an appropriate interrogation key (for example, "9.8.7.6.5.4.3.2.1 .3.3.lambda.fr-operator").
- this third network may be a "penultimate domain" within the meaning of the invention.
- the example of a caller connected to an IMS network, and hence of an S-CSCF server as a call server issuing a DNS request was considered. More generally, the invention obviously applies to any call server capable of sending a DNS request, for example a Border Gateway ("Border Gateway" in English), or an interworking gateway with the RTC, or still a service platform with routing functions.
- the invention can be implemented within a node of a network or domain, in particular within a DNS server, by means of software and / or hardware components.
- the present invention also relates to a computer system.
- This computer system conventionally comprises a central processing unit controlling signals by a memory, as well as an input unit and an output unit.
- this computer system may be used to execute a computer program comprising instructions for implementing any of the methods for resolving a telephone number according to the invention.
- the invention also relates to a downloadable computer program from a communication network comprising instructions for executing the steps of a method for resolving a telephone number according to the invention, when it is executed. on a computer.
- This computer program may be stored on a computer readable medium and may be executable by a microprocessor.
- This program can use any programming language, and be in the form of source code, object code, or intermediate code between source code and object code, such as in a partially compiled form, or in any another desirable form.
- the invention also relates to an information carrier, irremovable, or partially or completely removable, readable by a computer, and comprising instructions of a computer program as mentioned above.
- the information carrier may be any entity or device capable of storing the program.
- the support can include storage means, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or a magnetic recording means such as a hard disk, or a USB flash drive (“USB flash drive”) in English).
- the information medium may be a transmissible medium such as an electrical or optical signal, which may be conveyed via an electrical or optical cable, by radio or by other means.
- the computer program according to the invention can in particular be downloaded to an Internet type network.
- the information carrier may be an integrated circuit in which the program is embedded, the circuit being adapted to execute or to be used in the performance of any of the methods of resolving a telephone number according to the invention.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
FR1260742A FR2998127A1 (fr) | 2012-11-12 | 2012-11-12 | Procede de resolution d'un numero de telephone porte en un identifiant de ressource reseau |
PCT/FR2013/052703 WO2014072665A1 (fr) | 2012-11-12 | 2013-11-12 | Procédé de résolution d'un numéro de téléphone porté en un identifiant de ressource réseau |
Publications (1)
Publication Number | Publication Date |
---|---|
EP2918064A1 true EP2918064A1 (fr) | 2015-09-16 |
Family
ID=47428738
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP13801646.4A Ceased EP2918064A1 (fr) | 2012-11-12 | 2013-11-12 | Procédé de résolution d'un numéro de téléphone porté en un identifiant de ressource réseau |
Country Status (4)
Country | Link |
---|---|
US (1) | US9591142B2 (fr) |
EP (1) | EP2918064A1 (fr) |
FR (1) | FR2998127A1 (fr) |
WO (1) | WO2014072665A1 (fr) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150350153A1 (en) * | 2014-05-30 | 2015-12-03 | Vonage Business Solutions, Inc. | System and method for account-based dns routing |
JP6738362B2 (ja) * | 2018-02-20 | 2020-08-12 | 日本電信電話株式会社 | Enum/dnsサーバ、enum/dnsシステム、及びenum/dnsシステムの制御方法 |
US11962585B2 (en) | 2019-08-20 | 2024-04-16 | Cisco Technology, Inc. | Guest onboarding of devices onto 3GPP-based networks with use of realm-based discovery of identity providers and mutual authentication of identity federation peers |
US11956628B2 (en) | 2020-11-23 | 2024-04-09 | Cisco Technology, Inc. | Openroaming for private communication systems |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6882838B1 (en) * | 1999-11-04 | 2005-04-19 | Lucent Technologies Inc. | System and method for providing dynamic call disposition service to wireless terminals |
DE60126595D1 (de) * | 2001-07-19 | 2007-03-29 | Ericsson Telefon Ab L M | Verfahren und Vorrichtung für die Lösung der Nummernübertragbarkeit am Ursprungsort |
US6718021B2 (en) * | 2002-02-19 | 2004-04-06 | Sbc Properties, L.P. | Method and system for presenting customized call alerts in a service for internet caller identification |
US8756341B1 (en) * | 2009-03-27 | 2014-06-17 | Amazon Technologies, Inc. | Request routing utilizing popularity information |
WO2013163634A1 (fr) * | 2012-04-27 | 2013-10-31 | Interdigital Patent Holdings, Inc. | Systèmes et procédés pour personnaliser et/ou adapter une interface de service |
US20150080128A1 (en) * | 2013-09-18 | 2015-03-19 | Zynga Inc. | Content management system |
US9560074B2 (en) * | 2014-10-07 | 2017-01-31 | Cloudmark, Inc. | Systems and methods of identifying suspicious hostnames |
-
2012
- 2012-11-12 FR FR1260742A patent/FR2998127A1/fr not_active Withdrawn
-
2013
- 2013-11-12 EP EP13801646.4A patent/EP2918064A1/fr not_active Ceased
- 2013-11-12 US US14/442,337 patent/US9591142B2/en active Active
- 2013-11-12 WO PCT/FR2013/052703 patent/WO2014072665A1/fr active Application Filing
Non-Patent Citations (1)
Title |
---|
GSM ASSOCIATION: "IR.67 - DNS/ENUM Guidelines for Service Providers & GRX/IPX Providers 5.1", 13 August 2010 (2010-08-13), Craiova, pages 1994, XP055500989, Retrieved from the Internet <URL:https://www.scribd.com/doc/161813967/GSMA-IR67-5-1-GSMA-DNS-Guidelines> [retrieved on 20180821] * |
Also Published As
Publication number | Publication date |
---|---|
FR2998127A1 (fr) | 2014-05-16 |
US9591142B2 (en) | 2017-03-07 |
WO2014072665A1 (fr) | 2014-05-15 |
US20160065747A1 (en) | 2016-03-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3085065B1 (fr) | Procédé de mise a jour dynamique d'informations obtenues de la part d'un serveur dns | |
WO2014072665A1 (fr) | Procédé de résolution d'un numéro de téléphone porté en un identifiant de ressource réseau | |
FR2982107A1 (fr) | Procede de gestion d'une communication destinee a un utilisateur et serveur d'application | |
EP2080345B1 (fr) | Procede de gestion d'identites publiques dans un reseau de transmission d'informations, serveur de gestion d'enregistrements d'identites publiques, equipement de gestion d'une identite publique de groupe et programmes d'ordinateur correspondants | |
EP3646554B1 (fr) | Procédé de traitement d'une requête et serveur d'un coeur de réseau ip multimédia | |
WO2011095522A1 (fr) | Procede de generation d'une adresse sip publique permanente associee a une identite privee sur un reseau ims | |
EP2873211A1 (fr) | Procede d'enregistrement d'au moins une adresse publique dans un reseau ims et application correspondante | |
Boucadair | Inter-Asterisk Exchange (IAX): Deployment Scenarios in SIP-Enabled Networks | |
WO2015197937A1 (fr) | Procédé de sélection dynamique par un appelant parmi une pluralité de terminaux d'un appelé | |
FR2974472A1 (fr) | Procede de resolution d'un numero de telephone porte en un identifiant de ressource ip | |
EP3391615B1 (fr) | Procédé de communication entre un terminal appelant et une pluralité de terminaux appelés | |
FR2969453A1 (fr) | Procede de localisation et d'identification d'un abonne connecte a un reseau emulant le rtc/rnis | |
FR2980328A1 (fr) | Procede de traitement d'une requete d'un service dependant de la localisation d'un terminal mobile | |
EP3337208B1 (fr) | Procédé et dispositif de transmission d'un message | |
EP2801178B1 (fr) | Procédé dynamique de détermination d'une liste de services dans un réseau sip | |
WO2013121158A1 (fr) | Procédé d'enregistrement d'un serveur d'application et serveur d'application | |
US20060165065A1 (en) | Communications address provisioning system and method therefor | |
FR3121808A1 (fr) | Procédés et dispositifs d’enrichissement et de traitement d’un message de signalisation | |
EP1940133A1 (fr) | Système et procédé de gestion de joignabilité via au moins un réseau de communication | |
EP2030418A2 (fr) | Procede de routage pour numeros non standard dans un mecanisme de routage pour numeros standard | |
WO2015086460A1 (fr) | Procede de gestion d'un identifiant public, systeme, serveur et element de securite correspondant | |
FR2965999A1 (fr) | Procede de traitement des flux de presence dans un reseau sip | |
FR2911034A1 (fr) | Systeme et procede de gestion de joignabilite via au moins un reseau de communication | |
WO2010112740A2 (fr) | Procede de routage d'une demande d'etablissement d'appel | |
WO2012117178A1 (fr) | Procédé de gestion d'identites publiques par un utilisateur d'un reseau ims |
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: 20150610 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR |
|
AX | Request for extension of the european patent |
Extension state: BA ME |
|
DAX | Request for extension of the european patent (deleted) | ||
17Q | First examination report despatched |
Effective date: 20160805 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R003 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED |
|
18R | Application refused |
Effective date: 20181014 |