WO2010052626A1 - Procédé et système de mise en correspondance d'identifiant avec une capacité de service - Google Patents

Procédé et système de mise en correspondance d'identifiant avec une capacité de service Download PDF

Info

Publication number
WO2010052626A1
WO2010052626A1 PCT/IB2009/054832 IB2009054832W WO2010052626A1 WO 2010052626 A1 WO2010052626 A1 WO 2010052626A1 IB 2009054832 W IB2009054832 W IB 2009054832W WO 2010052626 A1 WO2010052626 A1 WO 2010052626A1
Authority
WO
WIPO (PCT)
Prior art keywords
user identifier
service
ims
database
request
Prior art date
Application number
PCT/IB2009/054832
Other languages
English (en)
Inventor
Edoardo Gavita
Zhongwen Zhu
Nazin Hossain
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2010052626A1 publication Critical patent/WO2010052626A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/09Mapping addresses
    • H04L61/10Mapping addresses of different types
    • H04L61/106Mapping addresses of different types across networks, e.g. mapping telephone numbers to data network addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/38Graded-service arrangements, i.e. some subscribers prevented from establishing certain connections
    • H04M3/387Graded-service arrangements, i.e. some subscribers prevented from establishing certain connections using subscriber identification cards
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/45Network directories; Name-to-address mapping
    • H04L61/4547Network directories; Name-to-address mapping for personal communications, i.e. using a personal identifier
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/45Network directories; Name-to-address mapping
    • H04L61/4557Directories for hybrid networks, e.g. including telephone numbers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/1016IP multimedia subsystem [IMS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1069Session establishment or de-establishment

Definitions

  • the present invention relates to the area of address mapping.
  • a user's contact list has limited types of addresses that can be stored therein.
  • the contact list can store phone numbers and e-mail addresses, but can't store SIP URI's (Session Initiation Protocol Uniform Resource Identifier).
  • one of the contacts in the users' contact list has multiple phone numbers that have different service capabilities associated with them (for example, one identifier number can only be used to make either a voice call, SMS (Short Message Service) or MMS (Multimedia Messaging Service) , whereas another identifier number can only be used for IMS Services (IP Multimedia Subsystem) there is presently no way to qualify the identifier number with service capability in the contact list.
  • SMS Short Message Service
  • MMS Multimedia Messaging Service
  • IMS Services IP Multimedia Subsystem
  • a partial solution to the aforementioned problem can be to configure the terminating user's network to provide a mechanism for routing incoming requests via appropriate means based on user B's terminal capabilities, or User B's preferences.
  • the problem persists in a multi-operator environment; for example, in the scenario where a user tries toreach (via his IMS network) another User (ex. user B) served by a different operator.
  • FIG. 1 shows this exemplary multi-operator environment.
  • UE-A (160) served by Operator 1 (102) is trying to reach via an IMS network (140)
  • UE-B (170) served by Operator 2(104).
  • UE-B (170) has multiple communication addresses, and if UE-A (160) does not or is not capable of selecting the correct communication address from his client, UE-A (160) originating operator network (120) would not be able to route the IMS requests to the appropriate terminating foreign operator's network. If the wrong identifier number of UE-B (170) is used in the SIP request, the originating side's DNS (ENUM) (Domain Number System E-number) (150) look up would fail.
  • ENUM Domain Number System E-number
  • the ENUM could be configured to associate UE-B's (170) identifier number to the appropriate IMS capable address.
  • UE-B (170) is served by a different operator (104)
  • DNS configuration would not be enough, especially in the scenario where the operator (104) is not the same operator (106) that is providing UE-B (170) with the IMS Services.
  • Monnet et al describes how to modify the structure of an address.
  • the method involves receiving an electronic mail by an electronic mail transfer,system of a simple mail transfer protocol (SMTP) type messaging server.
  • An electronic mail's header processing module is used to modify user addresses in the header, by a transformation unit, by adding a domain name indicating an application server and displacing at-sign from one position towards another position in front of the added name to increase the length of a user name in a modified address.
  • An at-sign replacement character is added to the former position of the at-sign by the unit.
  • Figure 1 is an exemplary high-level network diagram illustrating a multi- operator environment where UE-A, served by one operator, is trying to reach UE-B, served by another operator, according to a known prior art scheme;
  • Figure 2a is an exemplary high-level network and signal flow diagram of an IP
  • IMS Multimedia Subsystem
  • Figure 2b is an exemplary diagram of a database containing a further variant of the preferred embodiment of the present invention.
  • Figure 3 is an exemplary nodal operation and signal flow diagram of a multi-operator environment where UE-A, served by one operator, communicates with UE-B, served by another operator according to a variant of the preferred embodiment of the present invention
  • Figure 4 is an exemplary flowchart diagram of a method for mapping a service request from one user identifier to a second user identifier according to a preferred embodiment of the present invention.
  • Figure 5 is an exemplary flowchart diagram a method for mapping a service request from one user identifier to a second user identifier according to a further embodiment of the present invention.
  • FIG. 2a shows an exemplary high-level network and signal flow diagram of an IP Multimedia Subsystem (IMS) network containing a variant of the preferred embodiment of the present invention.
  • IMS IP Multimedia Subsystem
  • FIG. 2a Shown in Figure 2a is a multi-operator network wherein a first user wishes to communicate with a second user without being aware of the service capabilities of the second user. It is to be understood that this is only an exemplary scenario, and that the invention can be advantageously implemented in various types of networks.
  • FIG. 2a Shown in Figure 2a is a user UE-A (210) served by an Operator l's IMS Network
  • SIP Session Initiated Protocol
  • 'Request URI Uniform Resource Identifier
  • MSISDNl MS International ISDN Numberl
  • the new service logic (218) verifies (step 214) with a database (270) if the address in the Request URI can be used for SIP requests, i.e. if for example the requested service can be started using the MSISDNl.
  • the database sends back a message (step 216) to the new service logic (218) that an IMS capable address of UE-B (220) is needed.
  • the 'Request URI' header value of the SIP request is modified so that it contains another address, for example an IMS capable address of UE-B (220), MSISDN2.
  • the SIP request is then forwarded from the originating Serving Call Session Control Function (S-CSCF)(230) to the terminating S- CSCF (240) in Operator 2(290).
  • S-CSCF Serving Call Session Control Function
  • the modified request URI allows the SIP request to reach UE-B 's (220) IMS Network, on the terminating side.
  • FIG. 2b shows a diagram of a exemplary database containing a further variant of the preferred embodiment of the present invention.
  • FIG. 2b Shown in Figure 2b is the same database (270) found in figure 2a but showing in more detail the mapping of a User ID to a service capability.
  • the database (270) stores the Identifier mapping to Service Capability for a plurality of users.
  • UE-B (220) has three different identifiers (also called herein addresses) mapped to three different service capabilities.
  • UE-B (Identifier 1) is mapped to a circuit switch voice call.
  • UE-B (Identifier 2) is mapped to IMS-IM, while UE-B (Identifier 3) is mapped to IMS Chat.
  • Such an association shows the particular identifiers of UE-B that should be used when requesting establishment of the associated service with UE-B. For example, if a user would like to do IMS chat with UE- B, the service request should use UE-B 's Identifier 3.
  • FIG. 3 shows an exemplary nodal operation and signal flow diagram of a multi-operator environment where UE-A (210) served by operator l's IMS Network (280), communicates with UE-B (220) served by another operator (290). It is to be understood that this is only an exemplary scenario, and that the invention can be advantageously implemented in various types of networks, such as for example email networks, non-IMS Instant messaging networks, etc.
  • Operator l's IMS Network a SIP message to UE-B (220) using MSISDNl.
  • Operator l's IMS Network (280) further comprises a Serving Call Session Control Function (S-CSCF) (330) which performs the session control services for the endpoint. This includes routing of originating sessions to external networks and routing of terminating sessions to visited networks.
  • the operator l's IMS Network (280) further comprises an Application Server (AS) (250) that provides verification of identifier information, MSISDNl lookup, querying for MSISDNl and identifier replacement.
  • the Operator 1 further comprises a database (270) for the storage of the identifier mapping to Service capability.
  • the DNS Domain Name System
  • the DNS Domain Name System
  • 340 is a network of databases that translates Internet Domain Systems into IP addresses.
  • the exemplary scenario in Figure 3 may start with User A UE-A (210) sending a SIP message to User B UE-B (220) using MSISDNl (MS International ISDN Number).
  • the SIP message is sent to the S-CSCF (330) where there is a trigger (304) for sending SIP messages to the AS (250) with the identifier mapping service.
  • the verification of the Uniform Resource Identifier (308) is carried out to see if it is a Telephone Uniform Resource Identifier.
  • the DNS (340) is checked to see if the MSISDNl can be mapped to a SIP URI, such as for example if the user ID be mapped to a particular user capability as shown in Figure 2b.
  • the process starts at step 400 which is followed by the receipt of the SIP request at step 410.
  • the request is then checked if the URI contained in the SIP request is a SIP URI (step 420). If at step 422 it is determined that the URI is a SIP URI then the request is sent back to IMS core (step 440) and from there to the destination (e.g. to User B). If at step 422 it is otherwise determined that the URI is not a SIP URI, then it is checked if it is possible to map the MSISDN to the SIP URI (via e.g. the DNS), step 430.
  • step 432 If the determination is yes (step 432), then the request is sent back to the IMS Core (step 440), and from there to the destination (e.g. to User B). If the determination is negative (step 432), the database is queried for IMS services capable address, using MSISDN (step 450). If the user has an IMS service capable address then the requested URI is replaced with the new MSISDN or the SIP URI (Step 460). Thereafter, the request is sent back to the IMS Core (Step 440). The flow ends at step 480. If at step 452 the determination is that the user does not have an IMS capable address, then an error message is sent back to the sender (step 470). The flow ends at step 480.
  • FIG. 5 shows an exemplary flowchart diagram of a method for mapping a service request from one user identifier to a second user identifier according to a further embodiment of the present invention.
  • a receive request for service is directed to a 1 st user identifier (step 510). It is then determined if the user identifier can be used to initiate the service (step 520). For example, it is determined if the first ID is associated with an IMS-SIP service, or if the first ID is appropriate for such a service, or otherwise, if there is not another more appropriate ID of that user that could be used for that service. If it is then determined that the user identifier can be used to initiate the service, then the flow proceeds as normal (step 560) and the service is initiated. Once this is completed, the flow ends (step 570).
  • an alternate user identifier is determined (step 530) that is able to initiate the service.
  • the first user identifier is then replaced with the alternate user identifier in the request (step 550).
  • the flow then proceeds as normal (step 550), with the alternate user identifier in the request, and the service is initiated using the alternate user identifier.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention porte sur un procédé et un serveur de communication pour faire correspondre une adresse à une capacité de service, dans lesquels un serveur détermine si un service demandé dans une requête de service, tel que par exemple dans un message invite SIP (protocole d'ouverture de session), peut être déclenché avec un premier identifiant d'utilisateur. Le serveur détermine en outre un identifiant d'utilisateur de remplacement lorsqu'il est déterminé que le service ne peut pas être déclenché avec le premier identifiant d'utilisateur, remplace le premier identifiant d'utilisateur par l'identifiant d'utilisateur de remplacement dans la requête de service, de telle sorte que le service demandé peut être établi avec succès.
PCT/IB2009/054832 2008-11-05 2009-10-30 Procédé et système de mise en correspondance d'identifiant avec une capacité de service WO2010052626A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US12/265,455 US20100112985A1 (en) 2008-11-05 2008-11-05 Method and system for identifier mapping to service capability
US12/265,455 2008-11-05

Publications (1)

Publication Number Publication Date
WO2010052626A1 true WO2010052626A1 (fr) 2010-05-14

Family

ID=41664716

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2009/054832 WO2010052626A1 (fr) 2008-11-05 2009-10-30 Procédé et système de mise en correspondance d'identifiant avec une capacité de service

Country Status (2)

Country Link
US (1) US20100112985A1 (fr)
WO (1) WO2010052626A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090248799A1 (en) * 2008-03-31 2009-10-01 Telefonaktiebolaget Lm Ericsson (Publ) Method and server for user identifier update
WO2010090426A2 (fr) * 2009-02-03 2010-08-12 Samsung Electronics Co., Ltd. Procédé et système de fourniture de service supplémentaire pour un réseau à base d'ims
CN104754545B (zh) * 2013-12-30 2018-07-24 中国移动通信集团公司 一种自有业务访问方法、装置及系统
US9854003B2 (en) * 2014-05-24 2017-12-26 NetTalk.com, Inc. System and method for initiating telecommunications sessions through an electronic mail address
CN105407033A (zh) * 2015-09-18 2016-03-16 云活科技有限公司 一种聊天消息归集显示方法及装置
US20220052980A1 (en) * 2020-08-13 2022-02-17 Oleksiy Ptashniy Method of service identification in enum structure

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004006534A1 (fr) * 2002-07-02 2004-01-15 Telefonaktiebolaget Lm Ericsson (Publ) Procede d'acheminement d'une demande de service dans un systeme de telecommunications en utilisant les numeros e.164 et un systeme de noms de domaines

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8909701B2 (en) * 2003-05-02 2014-12-09 Nokia Corporation IMS conferencing policy logic
US7319857B2 (en) * 2004-09-13 2008-01-15 Tekelec Methods, systems, and computer program products for delivering messaging service messages
US7529231B2 (en) * 2006-01-13 2009-05-05 At&T Intellectual Property L.L.P. Routing methods and systems using ENUM servers internal and external to a service provider network
US7760712B2 (en) * 2006-08-11 2010-07-20 Research In Motion Limited System and method for managing call continuity in IMS network environment

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004006534A1 (fr) * 2002-07-02 2004-01-15 Telefonaktiebolaget Lm Ericsson (Publ) Procede d'acheminement d'une demande de service dans un systeme de telecommunications en utilisant les numeros e.164 et un systeme de noms de domaines

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 version 8.6.0 Release 8); ETSI TS 123 228", ETSI STANDARD, EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE (ETSI), SOPHIA ANTIPOLIS CEDEX, FRANCE, vol. 3-SA2, no. V8.6.0, 1 October 2008 (2008-10-01), XP014042398 *

Also Published As

Publication number Publication date
US20100112985A1 (en) 2010-05-06

Similar Documents

Publication Publication Date Title
US10218744B2 (en) User device selection
US9124603B2 (en) Methods and apparatus to select a peered voice over internet protocol (VoIP) border element
US8244905B2 (en) Routing mechanisms for messaging applications using an enhanced gateway control function
US8254551B2 (en) Methods, systems, and computer program products for providing quality of service using E.164 number mapping (ENUM) data in a communications network
EP2047648B1 (fr) Procédés, systèmes et produits-programmes informatiques pour spécifier un type de service particulier de mise en correspondance du numéro e.164 (enum) dans un réseau de communication qui utilise une pluralité de types de services enum différents
US9712341B2 (en) Methods, systems, and computer readable media for providing E.164 number mapping (ENUM) translation at a bearer independent call control (BICC) and/or session intiation protocol (SIP) router
US8358768B2 (en) Methods, systems, and computer program products for providing a country code identifier in an international ENUM system
US8537993B2 (en) Telephone number mapping
JP5444003B2 (ja) 分散ハッシングテーブルを使用したimsアーキテクチャ
US20080165706A1 (en) Destination service selection for a telephone
US20100112985A1 (en) Method and system for identifier mapping to service capability
US9184940B2 (en) Method and apparatus for completing a circuit switched service call in an internet protocol network
WO2008052476A1 (fr) Procédé de gestion de conversation, client de message universel et serveur de message universel associés
EP2220842B1 (fr) Procédés et appareils d'interfonctionnement basé sur ip pour des communications vocales et de données
CN109936827B (zh) 短信路由方法和系统、主叫短信中心和域名系统
EP2467988B1 (fr) Procédé et appareil dans un réseau de télécommunication
US20110145343A1 (en) Method and apparatus for enabling communications between users
US10834149B2 (en) Method and system for routing of session-based services
KR100807863B1 (ko) 통신 시스템에서의 서비스 제공

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09756841

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09756841

Country of ref document: EP

Kind code of ref document: A1