WO2008011156A2 - Methods, systems, and computer program products for specifying a particular enum service type in a communications network that utilizes a plurality of different enum service types - Google Patents
Methods, systems, and computer program products for specifying a particular enum service type in a communications network that utilizes a plurality of different enum service types Download PDFInfo
- Publication number
- WO2008011156A2 WO2008011156A2 PCT/US2007/016471 US2007016471W WO2008011156A2 WO 2008011156 A2 WO2008011156 A2 WO 2008011156A2 US 2007016471 W US2007016471 W US 2007016471W WO 2008011156 A2 WO2008011156 A2 WO 2008011156A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- enum
- service type
- server
- query
- query message
- Prior art date
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/09—Mapping addresses
- H04L61/10—Mapping addresses of different types
- H04L61/106—Mapping addresses of different types across networks, e.g. mapping telephone numbers to data network addresses
-
- 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
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4555—Directories for electronic mail or instant messaging
-
- 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
- ENUM service type for a call or other communication in a communications network that utilizes a plurality of different ENUM service types.
- IP Internet Protocol
- PSTN public switched telephone network
- E.164 number which is defined by ITU-T standards, may be designated as a unifying identifier number.
- E.164 number is commonly used in E.164 telephone number mapping (ENUM) systems that associate the E.164 number to a number of URI addresses through which a called party subscriber may be contacted.
- ENUM systems typically utilize DNS queries to obtain translation data (i.e., URI addresses) for a given dialed number (i.e., the unifying identifier number).
- translation data i.e., URI addresses
- dialed number i.e., the unifying identifier number
- new services e.g., text messages, voice messages, video, IMS communications, etc.
- the number of DNS queries that traverse the IP network will also increase.
- the number of URI addresses utilized by subscribers will continue to grow, and thus, will be included in response messages. Consequently, one problem that arises is that a message generated in response to a query message may include more services (both in number and service type) than the query initiator desires. For example, a query initiator may desire only mailto URI addresses because the calling party may only be able to communicate via electronic mail.
- the subject matter described herein includes methods, systems, and computer program products for specifying an ENUM service type in a communications network that uses a plurality of different ENUM service types.
- at least one ENUM service type is identified from a plurality of different ENUM service types. The identification is performed at a signaling point separate from an ENUM database.
- An ENUM query message corresponding to the at least one identified ENUM service type is generated. The ENUM query message is transmitted to an at least one ENUM server for providing the at least one identified ENUM service type.
- Figure 1A is a network diagram illustrating an exemplary communications network adapted to specify an ENUM service type in a communications network according to an embodiment of the subject matter described herein;
- Figure 1 B is a network diagram illustrating exemplary details of signaling point 102 for identifying an ENUM service type according to an embodiment of the subject matter described herein;
- Figure 2 is a diagram illustrating an exemplary ENUM query message according to an embodiment of the subject matter described herein;
- Figure 3 is a diagram illustrating an exemplary ENUM response message according to an embodiment of the subject matter described herein;
- Figure 4 is a network diagram illustrating an exemplary communications network that transmits an ENUM query to an ENUM database that provides a specific type of ENUM service type among a plurality of ENUM databases that provide different ENUM types according to an embodiment of the subject matter described herein;
- FIG. 5 is a network diagram illustrating an exemplary communications network that utilizes a signaling message routing node, referred to herein as an ENUM flexible routing node or E-Flex node, adapted to obtain an ENUM response from a single ENUM server for providing a specific type of ENUM server among plural ENUM servers providing different types of ENUM service according to an embodiment of the subject matter described herein;
- a signaling message routing node referred to herein as an ENUM flexible routing node or E-Flex node
- Figure 6 is a network diagram illustrating an exemplary communications network that utilizes an E-Flex node to obtain ENUM responses from multiple ENUM servers according to an embodiment of the subject matter described herein;
- Figure 7 is a network diagram illustrating exemplary communications network that utilizes an E-Flex node and a subscriber preferences database to obtain ENUM responses of specific ENUM service types in accordance with a subscriber's preferences according to an embodiment of the subject matter described herein;
- Figure 8 is a network diagram illustrating an exemplary communications network that utilizes a signaling point to specify and obtain a maximum number of ENUM responses in accordance according to an embodiment of the subject matter described herein; and Figure 9 is a flow chart illustrating exemplary steps for identifying and specifying an ENUM service type in a communications network according to an embodiment of the subject matter described herein.
- FIG. 1 illustrates an exemplary communications network 100 in which the present subject matter may be implemented according to an embodiment of the subject matter described herein.
- network 100 may include a signaling point 102, an ENUM server 104, and at least one client device 106.
- Signaling point 102 may include a telephone central office switch that connects to client device 106.
- signaling point 102 may include a device called a Class 5 switch or TDM switch, or any other network device configured for TDM-based, circuit-switched telephone calls (e.g., an SS7 service switching point (SSP)).
- SSP SS7 service switching point
- signaling point 102 may be an IP-based element, such as an IP multimedia subsystem (IMS) call session control function (CSCF), a media gateway controller (MGC), a Softswitch, a next generation network (NGN) node, an application server, a service control point, a mobile switching center (MSC) server, a home location register (HLR), an IMS home subscriber server (HSS), a presence server, a SIP proxy server, or an H.323 gatekeeper.
- ENUM server 104 may include a database 108 that contains a plurality of telephone numbers, URI addresses, etc., that a calling party may possibly use to contact the called party.
- database 108 may include E.164 number-to-URI mappings for a plurality of different ENUM service types.
- database 108 may include E.164 number-to-mailto URIs for an email ENUM service type, E.164 number-to-SIP URIs for a voice call ENUM service type, and E.164 number-to-instant messaging URIs for an IM ENUM service type.
- Client device 106 may include a conventional telephone, an Internet Protocol (IP) telephone, a computer, or any other like device capable of communicating with SP 102.
- IP Internet Protocol
- the subject matter described herein is not limited to implementations where SP 102 is connected to a user device.
- SP 102 may be a PSTN tandem office or IP equivalent that connects to other signaling points.
- signaling point 102 detects a communication origination event (e.g., a call placed by client device 106). In response to the event, signaling point 102 may identify an origination address (e.g., calling party's phone number) and a destination address (e.g., the called party's E.164 number). Upon detecting the communications origination event message, signaling point 102 is configured to determine whether ENUM service is required, and, if so, to generate a query message, (e.g., ENUM query message 111 ), which is sent to a translation server (e.g., ENUM server 104) in order to obtain at least one URI in which the subscriber may be reached.
- a communication origination event e.g., a call placed by client device 106.
- signaling point 102 may identify an origination address (e.g., calling party's phone number) and a destination address (e.g., the called party's E.164 number).
- signaling point 102 Upon detecting the
- Signaling point 102 may determine whether ENUM service is required based on the media type of the destination. For example, if the destination is an IP device, ENUM service may be required to translate the E.164 number of the destination to a URI or other suitable IP-based identifier.
- ENUM query message 111 includes both the called party's E.164 number (not shown) and a service type indicator 120 corresponding to an ENUM service type identified by signaling point 102.
- Signaling point 102 may identify the ENUM service type in any suitable manner.
- SP 102 may include an ENUM service type identifier 130 for identifying at least one ENUM service type in a network that utilizes a plurality of ENUM service types and an ENUM query message generator 132 that formulates and sends ENUM queries according to the at least one identified ENUM service type.
- ENUM service type identifier 130 may identify the ENUM service type based on the content of the received signaling message.
- ENUM service type identifier 130 may determine that the communication is a voice call to an IP phone and may instruct ENUM query message generator 132 to construct an ENUM query requesting a SIP URI.
- SP 102 may detect call originations from subscriber devices 136, may identify the ENUM service type as a voice call to an IP phone, and may instruct ENUM query message generator 132 to construct an ENUM query requesting SIP URIs.
- an SP may receive a messaging service message (e.g., short message service message, instant message, multimedia message), and determine based on the message type or message payload, which ENUM service type to request (e.g., mailto URI).
- ENUM service type identifier may receive an SMTP or POP3 message from computer 138 via an IP link, may identify the ENUM service type as email, and may instruct ENUM query message generator 132 to request mailto URIs.
- ENUM service type identifier 130 may receive a SIP message from VoIP device, may examine the context type field in the SIP message to determine the ENUM service type, and may instruct ENUM query message generator 132 to formulate an ENUM query corresponding to the identified context type.
- ENUM service type identifier 130 may identify the ENUM service type based on context of signaling messages and/or type of communication link from which a communication is received.
- ENUM query message 111 may contain a the E.164 number in reversed dotted notation, as specified by ENUM standards. For example, if the E.164 number is 9194605500, the format of the E.164 number in query message 111 may be 0.0.0.0.5.5.0.6.4.e164.arpa.
- the properly formatted E.164 number in addition to service type indicator 120 may be used to index ENUM database 108 in embodiments in which ENUM database 108 includes ENUM data for plural ENUM service types.
- Service type indicator 120 may include any type of marker used to specify the particular type of URIs requested by SP 102. Determination of service type indicator 120 may be made by either the caller or signaling point 102.
- a calling party may want to limit the call session to a certain type or types of media.
- the calling party may have the capability to conduct a voice call or email communications to a particular E.164 number, but may not want to utilize the voice call functionality for a particular communication.
- the user may request URIs that do not involve voice call functionality, such as designating the service type indicator as a mailto indicator only.
- signaling point 102 may be configured to determine the ENUM service type. For instance, signaling point 102 may be configured to inspect certain fields in a received SIP message, such as the context type.
- signaling point 102 determines that only mailto URIs are needed, then signaling point 102 inserts a mailto ENUM service type indicator 120 into query message 111 and forwards the message to ENUM server 104.
- ENUM server 104 Upon receiving message 111 , ENUM server 104 performs a lookup in database 108 using the called E.164 number and service type indicator 120.
- ENUM server 104 locates and returns all the database entries that are associated with the service type indicated by the service type indicator (e.g., mailto, SIP, etc.) and the subscriber identifier (i.e., subscriber's E.164 number).
- ENUM server 104 may be configured to return only the (subscriber related) URIs of the type indicated by service type indicator 120 in message 111.
- Figure 1 A shows that a mailto service type indicator 120 is included in ENUM query message 111 , which is forwarded to ENUM server 104.
- query message 111 includes a mailto service type indicator
- only mailto URI addresses e.g., MAIL TO URI A and MAIL TO URI B in ENUM response 112
- only mailto URIs are included in response message 112.
- query message 111 includes an ENUM query message that contains an ENUM service type indicator 120.
- the mailto service type indicator 120 may be included in the additional section 202 of query message 111. Namely, the additional section enables a user to include a list of desired services (e.g., the manner in which the call should be connected).
- the response message containing the relevant URIs will be smaller and will only provide the data needed for specific services.
- service type indicator 120 may be placed in another section of query message 111. Otherwise, the response message would return all the URI addresses available to contact the called subscriber.
- one implementation of the present subject matter which includes an ENUM database that contains ENUM data for plural ENUM service types provides additional advantages. For example, by utilizing this implementation, one large database with all services combined together may be used instead of having individual databases for each service.
- Figure 3 depicts an exemplary response message 112 that may be generated by ENUM server 104 in response to receiving an ENUM query with a service type indicator according to an embodiment of the subject matter described herein.
- response message 112 includes an ENUM response message to ENUM query message 111 illustrated in Figure 2.
- response message 112 includes an answer section 302 that only contains mailto URI addresses that are returned by the ENUM database 120 (per the ENUM service type identified in query message 111 ).
- answer section 302 of response message 112 is used to list the requested URI types.
- section 302 is shown to include three URI addresses, which are all of the mailto URI type (as requested by query 102). In an alternate embodiment, these URIs may be placed in another section of response message 112.
- Response message 112 may also include a list of the services in the additional section. By including the service information in the additional section, multiple response messages may be generated in response to a single query. For example, one response message containing a SIP URI, one response containing a mailto URI, and one response with the combination of a SIP URI and a mailto URI may be generated. This allows the division of the response into multiple responses as needed.
- the originator of the query messages may subsequently combine the URIs from all of the responses into a complete listing for delivery to the subscriber or to another network device.
- SP 102 inserts an ENUM service type indicator in an ENUM query and forwards the ENUM query to a single ENUM database that contains ENUM data for plural services.
- SP 102 may determine the required ENUM service type and send the ENUM query an ENUM database of a plurality of service specific ENUM databases corresponding to the identified ENUM service type.
- Figure 4 illustrates such an embodiment.
- SP 102 determines or identifies an ENUM service type as described above.
- SP 102 then forwards the ENUM query to one of ENUM databases 404i-404 n containing service specific ENUM data 408i-408 n .
- the ENUM query is sent to ENUM database 404i, which contains only mailto URIs.
- the ENUM response consequently includes mailto URIs and excludes SIP and other service URIs.
- SP 102 sends the
- E-Flex or ENUM flexible routing node may receive an ENUM query and send a modified ENUM query or queries to one or more ENUM databases.
- E-Flex node 402 receives an ENUM query with an ENUM service type indicator indicating that only mailto URIs are desired.
- E-Flex node 402 may examine the ENUM service type indicator and generate a new ENUM query 412 or a modified version of ENUM query without the service type indicator and transmit the new or modified query to mailto ENUM database 404i.
- E-Flex node 402 may receive ENUM response 413 containing the mailto URIs and forward the response to SP 102.
- E-Flex node 402 receives an ENUM query with an ENUM service type indicator indicating that only mailto URIs are desired.
- E-Flex node 402 may examine the ENUM service type indicator and generate a new ENUM query 412 or a modified version of ENUM query without the service type indicator and transmit the new or modified query to
- E-Flex node 402 examines the service type indicators and formulates plural ENUM queries 602 and 604 to ENUM databases 404i and 404 2l which correspond to the indicated ENUM service types. E-Flex node 402 also receives ENUM responses 606 and 608, combines the URIs from the responses, and formulates a new ENUM response 610 to SP 102 containing ENUM URIs of both service types.
- E-Flex routing node 402 may maintain state information, such as a transaction ID and a timer so that responses to ENUM queries can be associated with an original query and sent the appropriate query originator. The timer may be used for requesting retransmissions of ENUM responses in the event that the ENUM responses are not received within a time period.
- E-Flex routing node 402 may utilize subscriber preference data in determining the appropriate ENUM service type.
- Figure 7 illustrates such an embodiment.
- E-Flex node 402 receives an ENUM query 700.
- ENUM query 700 may not include a service type indicator.
- E-Flex node 402 may extract called or calling subscriber preferences from a subscriber preferences databases 702. The subscriber preferences may identify ENUM service types for the called or calling subscriber. Accordingly, E-Flex node 402 may send a new or modified ENUM query 704 to an ENUM database corresponding to the selected service type.
- E- Flex node 402 may send the ENUM query message to an ENUM database that provides the subscriber-preferred ENUM service type among ENUM databases that provide different ENUM service types.
- an originating signaling point and/or E-Flex node 402 may insert a max URIs parameter in an ENUM query message.
- the max URIs parameter may specify the maximum number of URI records that are to be returned for a query.
- the max URIs parameter may be included, for example, in the additional section of an ENUM query and may be specified per service type or as an overall total record or URI record limit.
- Figure 8 illustrates such an embodiment.
- SP 102 formulates an ENUM query 800 containing a max URIs parameter specifying that only two URIs are desired. SP 102 sends the ENUM query to ENUM server 104.
- ENUM server 104 may use the max URIs parameter to limit the number of records returned from database 108. Accordingly, ENUM server 104 may formulate an ENUM response 802 containing a number of URIs corresponding to the maximum number of URIs.
- the max URIs parameter may also be inserted by an intermediate node, such as E-Flex node 402 (now shown in Figure 8), based on subscriber preference or other information.
- FIG. 9 is a flow chart illustrating exemplary overall steps that may be implemented in identifying an ENUM service type according to an embodiment of the subject matter described herein.
- step 900 at least one ENUM service type is identified from a plurality of different ENUM types.
- the ENUM service type is identified at a signaling point separate from an ENUM database.
- the ENUM service type may be identified by an originating node, such as SP 102, or at an intermediate node, such as E-Flex node 402.
- the identified ENUM service type may be a specific ENUM service type, such as an email ENUM service type or a voice call ENUM service type, or an instant messaging ENUM service type.
- step 902 at least one ENUM query message is generated, where the at least one ENUM query message corresponds to the at least one identified ENUM service type.
- the at least one query message may include one or more service type indicators corresponding to the at least one identified ENUM service type.
- plural ENUM query messages for plural identified ENUM service types may be generated.
- the ENUM query message is transmitted to at least one ENUM server for providing the identified at least one ENUM service type. If the ENUM query message includes a service type indicator, the ENUM query message may be transmitted to an ENUM server that contains ENUM data for plural service types. In an alternate implementation, the service type indicator may be omitted, and the ENUM query message or messages may be sent to a service-type-specific ENUM server.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2007800349326A CN101517999B (en) | 2006-07-20 | 2007-07-20 | Methods, systems, and computer program products for specifying a particular enum service type in a communications network that utilizes a plurality of different enum service types |
EP07836168.0A EP2047648B1 (en) | 2006-07-20 | 2007-07-20 | Methods, systems, and computer program products for specifying a particular enum service type in a communications network that utilizes a plurality of different enum service types |
BRPI0715429-1A BRPI0715429A2 (en) | 2006-07-20 | 2007-07-20 | Computer program methods, systems, and products for specifying a particular enum service type in a communications network that uses a plurality of different enum service types |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US83221506P | 2006-07-20 | 2006-07-20 | |
US60/832,215 | 2006-07-20 | ||
US11/880,108 | 2007-07-19 | ||
US11/880,108 US8400947B2 (en) | 2006-07-20 | 2007-07-19 | Methods, systems, and computer program products for specifying a particular ENUM service type in a communications network that utilizes a plurality of different ENUM service types |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2008011156A2 true WO2008011156A2 (en) | 2008-01-24 |
WO2008011156A3 WO2008011156A3 (en) | 2008-04-24 |
Family
ID=38957403
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2007/016471 WO2008011156A2 (en) | 2006-07-20 | 2007-07-20 | Methods, systems, and computer program products for specifying a particular enum service type in a communications network that utilizes a plurality of different enum service types |
Country Status (5)
Country | Link |
---|---|
US (1) | US8400947B2 (en) |
EP (1) | EP2047648B1 (en) |
CN (1) | CN101517999B (en) |
BR (1) | BRPI0715429A2 (en) |
WO (1) | WO2008011156A2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012022098A1 (en) * | 2010-08-16 | 2012-02-23 | 中兴通讯股份有限公司 | Method and system for processing value-added service |
FR2977444A1 (en) * | 2011-06-29 | 2013-01-04 | France Telecom | Hybrid mobile terminal for use in communication system, has control unit controlling voice over Internet protocol communication mode without passing through cellular network using obtained Internet protocol address and communication unit |
Families Citing this family (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8400947B2 (en) | 2006-07-20 | 2013-03-19 | Tekelec, Inc. | Methods, systems, and computer program products for specifying a particular ENUM service type in a communications network that utilizes a plurality of different ENUM service types |
JP2008035250A (en) * | 2006-07-28 | 2008-02-14 | Fujitsu Ltd | Information providing service control system |
US7822035B2 (en) * | 2007-03-07 | 2010-10-26 | Nokia Corporation | Use of communication service identifiers |
US20090034696A1 (en) * | 2007-08-01 | 2009-02-05 | Microsoft Corporation | Mechanism of distributing voice call using email distribution groups |
US8533463B2 (en) * | 2007-08-30 | 2013-09-10 | Red Hat, Inc. | Reduced computation for generation of certificate revocation information |
US8139563B2 (en) * | 2007-10-03 | 2012-03-20 | At&T Knowledge Ventures, L.P. | System for alternate communications in an internet protocol multimedia subsystem network |
US8428233B2 (en) * | 2008-03-05 | 2013-04-23 | Centurylink Intellectual Property Llc | Internet protocol for IP private branch exchanges |
US7746864B1 (en) | 2008-04-30 | 2010-06-29 | Cello Partnership | System and method for routing inter-carrier short message service or multimedia message service messages |
CN102027768B (en) * | 2008-05-19 | 2014-04-23 | 爱立信(中国)通信有限公司 | Handling Enum queries in a communication network |
WO2010057513A1 (en) * | 2008-11-24 | 2010-05-27 | Telefonaktiebolaget Lm Ericsson (Publ) | Routing a call setup request to a destination serving node in an ims network |
US9397862B2 (en) * | 2008-12-12 | 2016-07-19 | At&T Intellectual Property I, L.P. | Method and apparatus for completing a circuit switched service call in an internet protocol network |
US7948967B2 (en) * | 2008-12-17 | 2011-05-24 | At&T Intellectual Property, I L.P. | Methods, systems, and computer program products for enabling non-IMS queries of a common telephone number mapping system |
US8634498B2 (en) * | 2008-12-17 | 2014-01-21 | Entropic Communications, Inc. | Systems and methods for probing wired communication channels |
US8391273B2 (en) * | 2008-12-18 | 2013-03-05 | At&T Intellectual Property I, L.P. | Methods, systems, and computer program products for providing intra-carrier IP-based connections using a common telephone number mapping architecture |
US8432923B2 (en) | 2008-12-18 | 2013-04-30 | At&T Intellectual Property I, L.P. | Methods, systems, and computer program products for providing inter-carrier IP-based connections using a common telephone number mapping architecture |
CN102036281A (en) * | 2010-12-31 | 2011-04-27 | 华为技术有限公司 | Method, device and system for querying routes in CS (circuit switching) domain |
US8693464B2 (en) * | 2011-09-15 | 2014-04-08 | At&T Intellectual Property I, Lp | Method and apparatus for processing calls |
US9241258B2 (en) | 2011-09-15 | 2016-01-19 | At&T Intellectual Property I, Lp | Method and apparatus for managing calls |
CN104168289B (en) * | 2014-08-27 | 2017-06-06 | 中国联合网络通信集团有限公司 | A kind of user data query method and device based on IMS network |
KR101676867B1 (en) * | 2014-09-01 | 2016-11-17 | 티더블유모바일 주식회사 | Communication connecting control system based of mobile application and method of the same |
US20220052980A1 (en) * | 2020-08-13 | 2022-02-17 | Oleksiy Ptashniy | Method of service identification in enum structure |
RU2754606C1 (en) * | 2020-08-13 | 2021-09-03 | Алексей Олегович Пташный | Method for identifying the service in the enum structure |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2004006534A1 (en) | 2002-07-02 | 2004-01-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for routing a service request in a telecommunication system, using e.164 numbers and a dns |
Family Cites Families (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6539077B1 (en) | 1998-06-05 | 2003-03-25 | Netnumber.Com, Inc. | Method and apparatus for correlating a unique identifier, such as a PSTN telephone number, to an internet address to enable communications over the internet |
US7027582B2 (en) | 2001-07-06 | 2006-04-11 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for resolving an entity identifier into an internet address using a domain name system (DNS) server and an entity identifier portability database |
US6839421B2 (en) | 2001-10-29 | 2005-01-04 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus to carry out resolution of entity identifier in circuit-switched networks by using a domain name system |
EP1451714B1 (en) * | 2001-11-01 | 2018-05-02 | Verisign, Inc. | Method and system for updating a remote database |
US7720997B1 (en) * | 2001-12-19 | 2010-05-18 | Cisco Technology, Inc. | Path selection system |
US7274683B2 (en) * | 2002-01-07 | 2007-09-25 | Motorola, Inc. | Method and apparatus for a telecommunications network to communicate using an internet protocol |
EP1361762A1 (en) * | 2002-05-10 | 2003-11-12 | Alcatel | Gateway device and method for managing connections on a gateway device |
FR2841072A1 (en) * | 2002-06-14 | 2003-12-19 | France Telecom | System for consulting and updating DNS servers and LDAP directories, includes using protocol management unit for searching IP address of server hosting first database and transmitting request for reading and updating record to server |
US7240068B2 (en) * | 2002-09-06 | 2007-07-03 | Truetel Communications, Inc. | Service logic execution environment (SLEE) that is running on a device, supporting a plurality of services and that is compliant with a telecommunications computing standard for SLEES |
CN1232135C (en) * | 2002-11-12 | 2005-12-14 | 华为技术有限公司 | An end-to-end routing method of voice core network in wireless internet protocol |
CN100459723C (en) * | 2002-12-15 | 2009-02-04 | 华为技术有限公司 | Method for realizing routing for next-generation network |
JP2005184467A (en) * | 2003-12-19 | 2005-07-07 | Fujitsu Ltd | Network system using common line signal system |
JP4576840B2 (en) * | 2003-12-26 | 2010-11-10 | パナソニック株式会社 | Communication system and IP communication apparatus |
JP4576839B2 (en) * | 2003-12-26 | 2010-11-10 | パナソニック株式会社 | Communications system |
US7864709B2 (en) * | 2004-06-25 | 2011-01-04 | Apple Inc. | Method and apparatus for looking up configuration information for a network node |
US7499998B2 (en) * | 2004-12-01 | 2009-03-03 | Cisco Technology, Inc. | Arrangement in a server for providing dynamic domain name system services for each received request |
US8700729B2 (en) * | 2005-01-21 | 2014-04-15 | Robin Dua | Method and apparatus for managing credentials through a wireless network |
US7856094B2 (en) * | 2005-03-21 | 2010-12-21 | Tekelec | Methods, systems, and computer program products for providing telecommunications services between a session initiation protocol (SIP) network and a signaling system 7 (SS7) network |
US7624417B2 (en) * | 2006-01-27 | 2009-11-24 | Robin Dua | Method and system for accessing media content via the internet |
US8400947B2 (en) | 2006-07-20 | 2013-03-19 | Tekelec, Inc. | Methods, systems, and computer program products for specifying a particular ENUM service type in a communications network that utilizes a plurality of different ENUM service types |
US20080165706A1 (en) * | 2007-01-05 | 2008-07-10 | Bruno Bozionek | Destination service selection for a telephone |
US20080260119A1 (en) * | 2007-04-20 | 2008-10-23 | Rohini Marathe | Systems, methods, and computer program products for providing service interaction and mediation in a communications network |
-
2007
- 2007-07-19 US US11/880,108 patent/US8400947B2/en active Active
- 2007-07-20 EP EP07836168.0A patent/EP2047648B1/en active Active
- 2007-07-20 WO PCT/US2007/016471 patent/WO2008011156A2/en active Application Filing
- 2007-07-20 BR BRPI0715429-1A patent/BRPI0715429A2/en not_active IP Right Cessation
- 2007-07-20 CN CN2007800349326A patent/CN101517999B/en active Active
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2004006534A1 (en) | 2002-07-02 | 2004-01-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Method for routing a service request in a telecommunication system, using e.164 numbers and a dns |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012022098A1 (en) * | 2010-08-16 | 2012-02-23 | 中兴通讯股份有限公司 | Method and system for processing value-added service |
FR2977444A1 (en) * | 2011-06-29 | 2013-01-04 | France Telecom | Hybrid mobile terminal for use in communication system, has control unit controlling voice over Internet protocol communication mode without passing through cellular network using obtained Internet protocol address and communication unit |
Also Published As
Publication number | Publication date |
---|---|
US8400947B2 (en) | 2013-03-19 |
EP2047648A4 (en) | 2013-04-17 |
EP2047648A2 (en) | 2009-04-15 |
US20080025492A1 (en) | 2008-01-31 |
WO2008011156A3 (en) | 2008-04-24 |
CN101517999A (en) | 2009-08-26 |
CN101517999B (en) | 2012-03-21 |
BRPI0715429A2 (en) | 2013-07-09 |
EP2047648B1 (en) | 2018-10-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8400947B2 (en) | Methods, systems, and computer program products for specifying a particular ENUM service type in a communications network that utilizes a plurality of different ENUM service types | |
US8254551B2 (en) | Methods, systems, and computer program products for providing quality of service using E.164 number mapping (ENUM) data in a communications network | |
US9854005B2 (en) | Methods and apparatus for providing network based services to non-registering endpoints | |
EP2011347B1 (en) | Methods, systems, and computer program products for providing internet protocol multimedia subsystem(ims) registration services for non-ims devices | |
US8244905B2 (en) | Routing mechanisms for messaging applications using an enhanced gateway control function | |
US8667150B2 (en) | Method and apparatus for completing a circuit switched service call in an internet protocol network | |
US20080080488A1 (en) | Methods, systems, and computer program products for enabling short code dialing in an ENUM environment | |
KR20030081433A (en) | Ip based service architecture | |
US8358650B2 (en) | Methods, systems, and computer program products for communicating calling name (CNAM) services for session initiation protocol (SIP) originated calls terminating in a circuit switched network | |
US9055083B2 (en) | Interworking method and interworking control unit, method and system for implementing simulation services | |
US20080186956A1 (en) | Method and system for processing call change request in an internet protocol multimedia subsystem | |
EP2467988B1 (en) | Method and apparatus in a telecommunications network | |
KR20090009925A (en) | S-cscf selection for application server originated requests | |
US20110161519A1 (en) | Method and apparatus for providing a transit service for an aggregate endpoint | |
EP1973290A1 (en) | Carrier selection in an IP multimedia subsystem (IMS) | |
US8930574B2 (en) | Voice and other media conversion in inter-operator interface | |
US20100150144A1 (en) | Method and apparatus for completing a circuit switched service call in an internet protocol network | |
CN101137209B (en) | Location routing based system and location routing device and method thereof | |
WO2007090356A1 (en) | Method for realizing wac service, system and calling controller and application server thereof |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200780034932.6 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07836168 Country of ref document: EP Kind code of ref document: A2 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 662/CHENP/2009 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007836168 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: RU |
|
ENP | Entry into the national phase |
Ref document number: PI0715429 Country of ref document: BR Kind code of ref document: A2 Effective date: 20090121 |