WO2006127417A1 - Systeme permettant d'effectuer un double enregistrement aupres d'un reseau de telephonie ip, et d'un reseau de telephonie a commutation de circuits - Google Patents

Systeme permettant d'effectuer un double enregistrement aupres d'un reseau de telephonie ip, et d'un reseau de telephonie a commutation de circuits Download PDF

Info

Publication number
WO2006127417A1
WO2006127417A1 PCT/US2006/019331 US2006019331W WO2006127417A1 WO 2006127417 A1 WO2006127417 A1 WO 2006127417A1 US 2006019331 W US2006019331 W US 2006019331W WO 2006127417 A1 WO2006127417 A1 WO 2006127417A1
Authority
WO
WIPO (PCT)
Prior art keywords
telephony network
message
circuit
client device
switched telephony
Prior art date
Application number
PCT/US2006/019331
Other languages
English (en)
Inventor
Nagaraja Rao
Original Assignee
Nokia Siemens Networks Gmbh & Co. Kg
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 Nokia Siemens Networks Gmbh & Co. Kg filed Critical Nokia Siemens Networks Gmbh & Co. Kg
Publication of WO2006127417A1 publication Critical patent/WO2006127417A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/253—Telephone sets using digital voice transmission
    • H04M1/2535—Telephone sets using digital voice transmission adapted for voice communication over an Internet Protocol [IP] network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/04—Registration at HLR or HSS [Home Subscriber Server]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/06—Registration at serving network Location Register, VLR or user mobility server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/10—Mobility data transfer between location register and external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • Embodiments may generally relate to mobile telephony. More particularly, some embodiments are concerned with interoperation of a mobile client telephony device with both a circuit-switched telephony network and an Internet Protocol (IP) telephony network.
  • IP Internet Protocol
  • GSM Global System for Mobile Telecommunications
  • IP telephony networks e.g., IP Multimedia Subsystem (IMS) networks
  • IMS IP Multimedia Subsystem
  • An IP telephony network client device may communicate wirelessly (e.g., via WiFi) with such a network.
  • WLANs wireless Local Area Networks
  • dual mode handsets have been contemplated to provide mobile communication with a conventional circuit-switched network (e.g., GSM, Public Switch Telephone Network (PSTN), etc.) or with an IP telephony network.
  • GSM Global System for Mobile communications
  • PSTN Public Switch Telephone Network
  • Such handsets generally consist of two separate subsystems, one each for supporting IP telephony and circuit-switched telephony. Of course, the two subsystems may share certain hardware elements such as a speaker, a microphone, a display and a keypad.
  • the IP telephony subsystem of a dual mode handset When operating in an IP telephony mode, the IP telephony subsystem of a dual mode handset may place and receive telephone calls using an IP telephony network with which the handset is in communication. Similarly, the circuit-switched telephony subsystem of a dual mode handset may be used to place and receive telephone calls in conjunction with a circuit-switched telephony network.
  • the foregoing capabilities currently require the handset to be registered with the IP telephony network (i.e., to provide the former capabilities) or with the circuit-switched telephony network (i.e., to provide the latter).
  • the dual mode handset may be associated with one telephone number of the IP network and a different telephone number for the circuit-switched network. Simultaneous registration with both the circuit- switched telephony network and the IP telephony network is not supported by current systems.
  • Systems are desired that provide simultaneous registration of a client telephony device with a circuit-switched telephony network and an IP telephony network. Such systems may provide selectable termination of calls to the client telephony device via either telephony network.
  • Some embodiments provide a system, method, program code and/or means to provide simultaneous registration of a client telephony device with a circuit-switched telephony network and with an Internet Protocol (IP) telephony network.
  • IP Internet Protocol
  • an International Mobile Subscriber Identity associated with the client telephony device is associated with an application server of the IP telephony network.
  • a first message is received at the IP telephony network from a Mobile Switching Center of the circuit-switched telephony network, and a second message based on the first message is transmitted from the IP telephony network to a Home Location Register of the circuit- switched telephony network.
  • Receiving the first message may comprise emulating the Home Location Register of the circuit-switched telephony network, and transmitting the second message may comprise emulating a Visitor Location Register of the circuit-switched telephony network.
  • Some aspects may include receiving, at the IP telephony network, a first message to update a location of the client device within the circuit- switched telephony network, the first message including an identifier of the client device within the circuit-switched telephony network, and determining a server based on the identifier.
  • the determined server may be associated with the IP telephony network if the identifier is associated with the IP telephony network. If the identifier is associated with the circuit-switched telephony network, a second message may be transmitted to the server to associate the client device with a server of the IP telephony network within the circuit- switched telephony network.
  • a first message is received from a Home Location Register of the circuit-switched telephony network, the first message to request a roaming number for routing a call to a telephone number associated with the client device in the circuit-switched telephony network, a second message is transmitted to a Mobile Switching Center of the circuit- switched telephony network, the second message to request the roaming number corresponding to the telephone number, the roaming number is received from the Mobile Switching Center, and the roaming number is transmitted to the Home Location Register. It may be determined to offer the call to the client device via the circuit-switched telephony network, and, moreover, the client device may be roaming in the IP telephony network.
  • a first message is received at the IP telephony network from the client device, the message to register a number of the circuit-switched telephony network, and a second message is transmitted to a Home Location Register of the circuit-switched telephony network to associate a server of the IP telephony network with the number.
  • Further aspects may include receiving, at the IP telephony network, a first message to initiate a call to a telephone number associated with the client device in the IP telephony network, determining to offer the call to the client device via the circuit-switched telephony network, and transmitting a second message to a Mobile Switching Center of the circuit-switched telephony network, the second message to request a roaming number corresponding to the client device in the circuit-switched telephony network. Also included may be receiving the roaming number from the Mobile Switching Center, and transmitting a third message to the Mobile Switching Center to initiate the call to the client device via the circuit-switched telephony network, the third message including the roaming number.
  • FIG. 1 is a block diagram of a system according to some embodiments
  • FIG. 2 is a block diagram of IP and circuit-switched network components according to some embodiments
  • FIG. 3 is a functional block diagram of a Mobility Management Application Server (MM-AS) according to some embodiments;
  • MM-AS Mobility Management Application Server
  • FIG. 4 is a tabular representation of telephone numbers of an IP telephony network and telephone numbers of a circuit-switched telephony network as associated with Mobile Switching Centers of the circuit-switched telephony network;
  • FIG. 5 is a block diagram of a hardware architecture of a client telephony device according to some embodiments.
  • FIG. 6 is a block diagram of a software architecture to support IP- based and circuit-switched-based telephony signaling according to some embodiments
  • FIG. 7 is a block diagram of a software architecture to support telephony audio signals according to some embodiments.
  • FIG. 8 is a flow diagram of a process to support registration of a telephone number in a circuit-switched telephony network according to some embodiments
  • FIG. 9 is a diagram to illustrate registration of a circuit-switched telephony network telephone number in a circuit-switched telephony network according to some embodiments.
  • FIG. 10 is a diagram to illustrate registration of an IP telephony network telephone number in a circuit-switched telephony network according to some embodiments
  • FIG. 11 is a flow diagram of a process to support terminating a call to a circuit-switched telephony network telephone number at a circuit-switched telephony network according to some embodiments
  • FIG. 12 is a diagram to illustrate termination of a call to a circuit- switched telephony network telephone number at a circuit-switched telephony network according to some embodiments
  • FIG. 13 is a flow diagram of a process to register a circuit-switched telephony network telephone number in an IP telephony network according to some embodiments
  • FIG. 14 is a diagram to illustrate registration of a circuit-switched telephony network telephone number in an IP telephony network according to some embodiments
  • FIG. 15 is a flow diagram of a process to support terminating a call to an IP telephony network telephone number at a circuit-switched telephony network according to some embodiments.
  • FIG. 16 is a diagram to illustrate termination of a call to an IP telephony network telephone number at a circuit-switched telephony network according to some embodiments.
  • FIG. 1 is a block diagram of system 1 according to some embodiments.
  • System 1 comprises client telephony device 10, IP telephony network 20 and circuit-switched (CS) telephony network 30.
  • System 1 may provide simultaneous registration of device 10 with IP telephony network 20 and CS telephony network 30. Simultaneous registration of device 10 with each of networks 20 and 30 may provide selectable termination of calls to client telephony device 10 via either of networks 20 or 30.
  • CS circuit-switched
  • Device 10 may comprise a mobile telephony client device, and may also be configured to support a "fixed" connection to one or both of networks 20 and 30.
  • Examples of device 10 according to some embodiments include cellular telephones, personal digital assistants (PDAs), digital media players, digital cameras, wireless email devices, and any other device for supporting wireless telephony that is or becomes known.
  • Device 10 includes processor 12 for executing program code to enable some or all of the functions attributed herein to device 10. Also included are hardware, software and/or firmware elements of IP network I/O 14 and CS network I/O 16. IP network I/O 14 and CS network I/O 16 support wireless communication with IP telephony network 20 and CS telephony network 30, respectively. Further details of hardware elements and software stacks of device 10 according to some embodiments are set forth below.
  • IP telephony network 20 may comprise any number of LANs, Wide Area Networks (WANs), and/or the Internet itself. IP telephony network 20 provides at least one wireless access point that may be accessed by device 10. IP telephony network 20 supports the IMS protocol according to some embodiments. In some embodiments, IP telephony network 20 includes an application server that is associated with an International Mobile Subscriber Identity corresponding to a user of client telephony device 10. As will be described below, such an association may cause a Mobile Switching Center of CS network 30 to identify the application server as a Home Location Register for client device 10.
  • CS telephony network 30 also provides at least one wireless access point to device 10.
  • CS network 30 may comprise one or a combination of CS telephony networks, including but not limited to CDMA/IS-41 , WCDMA/UMTS, TDMA, GSM, PCS, and PSTN networks. As described above, such telephony networks may be owned by several separate providers.
  • FIG. 2 is a more detailed block diagram of system 1 according to some embodiments.
  • MM-AS Mobility Management Application Server
  • the core functionality of each illustrated element is known.
  • some embodiments may require one or more illustrated elements to function differently than is currently known.
  • CS telephony network 30 includes PSTN 305, which is in communication through known interfaces with GSM network 310.
  • GSM network 310 may comprise one or more GSM networks having different ownership.
  • GSM network 310 comprises Home Location Registers (HLRs) 312, Mobile Switching Centers (MSCs) 314, and Visitor Location Registers (VLRs) 316. Current usage often combines the functions of an MSC and a VLR under the label MSC/VLR.
  • HLRs Home Location Registers
  • MSCs Mobile Switching Centers
  • VLRs Visitor Location Registers
  • embodiments may be used in conjunction with additional or alternative CS mobile telephony networks (e.g., CDMA/IS-41 , WCDMA/UMTS, TDMA, PCS).
  • additional or alternative CS mobile telephony networks e.g., CDMA/IS-41 , WCDMA/UMTS, TDMA, PCS.
  • Such embodiments utilize known messages and protocols of the additional or alternative wireless networks.
  • the messages and protocols may be roughly analogous to the messages described below with respect to GSM networks.
  • an HLR provides a central subscriber database that maintains a location of a client device within a GSM network.
  • a GSM network may include many HLRs.
  • a location of a client device is maintained in a single HLR, and a single HLR may maintain locations of many client devices within several geographic areas.
  • An MSC/VLR is assigned to each geographic area, which may include several cellular communication towers.
  • a client device is registered with an MSC/VLR if the client device is located in a geographic area to which the MSC/VLR is assigned. This registration is stored in an HLR associated with the MSC/VLR.
  • Session control unit 210 includes Home Subscriber Server (HSS) 212, Call Session Control Function (CSCF) 214, and MM-AS 400. Core functions of HSS and CSCF are known and are roughly equivalent, within the IP domain, to the core functions of an HLR and an MSC/VLR, respectively.
  • HSS Home Subscriber Server
  • CSCF Call Session Control Function
  • Some embodiments leverage the existing infrastructure and protocols by having MSCs 314 identify MM-AS 400 as the HLR which maintains the location of client device 10, and by having HLRs 312 identify MM-AS 400 as the MSC/VLR with which client device 10 is registered. Simultaneously, client device 10 may be registered with HSS 212 and CSCF 214 in the IP telephony domain.
  • MM-AS 400 may provide simultaneous registration of device 10 with IP telephony network 20 and CS telephony network 30, and may emulate an HLR to MSCs 314 and a VLR to HLRs 312. MM-AS 400 may also and/or alternatively provide much of the functionality described herein.
  • MM-AS 400 may implement IP-based interfaces for communicating with HSS 212, CSCF 214 and Media Gateway Control Function (MGCF) 222, and may implement Mobile Application Part (MAP) interfaces for communicating with GSM elements such as HLRs 312, MSCs 314 and VLRs 316.
  • MGCF 222 is an element of legacy internetworking unit 220 and may allow interoperability between IP telephony network 20 and CS network 30 signaling protocols over a legacy interface, such as a Signaling System No. 7 (SS7) interface.
  • SS7 Signaling System No. 7
  • Media Gateway 224 of unit 220 enables the transfer of audio data (e.g. representing the voices of the calling and called parties) between IP telephony network 20 and CS network 30.
  • Applications unit 230 provides telephony applications to IP network 20.
  • instant messaging server 232 may provide instant messaging services
  • Rich Voice-over-IP (VoIP) Application Server 234 may provide other telephony applications such as call forwarding, call transfer, call waiting, etc. within IP telephony network 20.
  • IP telephony network 20 may support conventional IP telephony client devices using conventional means.
  • Such conventional devices may include fixed IP client devices 50 (e.g., coupled to network 20 via a Digital Subscriber Line connection) and mobile IP client devices 40 (e.g., coupled to network 20 via a General Packed Radio System connection).
  • Fixed IP client devices may comprise desktop computers, fixed IP telephones, conventional PSTN telephones coupled to an IP-PSTN telephone router, or the like.
  • Mobile IP client devices 40 may include, but are not limited to, cellular telephones, PDAs, digital media players, digital cameras, and wireless email devices.
  • FIG. 3 is a functional block diagram of MM-AS 400 according to some embodiments.
  • the illustrated functional blocks may be implemented by any combination of hardware and/or software, some of which may be located remote from one another. According to some embodiments, the functional blocks are implemented in program code for execution by a processor.
  • MM-AS 400 includes subscriber and call data module 410, mobility management module 420 and protocol stacks 430.
  • Subscriber and call data module 410 includes information for tracking client devices within IP telephony network 20 and CS telephony network 30 and for associating CS- based telephone numbers with client devices during certain scenarios. Accordingly, module 410 provides an ENUM interface to MGCF 222 for receiving a CS-based telephone number from MGCF 222 and transmitting an identifier of an associated client device to MGCF 222 in response. MGCF 222 may use the identifier to connect a call from network 30 to the client device.
  • Mobility management module 420 includes mobility management state event handling block 422, MAP state event handling block 424, and Session Initiation Protocol (SIP) state event handling block 426 for executing the processes described herein in response to received SIP and MAP messages.
  • the MAP messages are received from GSM network 310 via MAP protocol stack 432 and the SIP messages are received from CSCF 214 via the SIP protocol stack 434.
  • FIG. 4 is a tabular representation that may be used by MM-AS 400 in some embodiments. The illustrated data may be stored in any location, media, and form that are accessible to MM-AS 400.
  • Table 440 associates each of several International Mobile Subscriber Identities (IMSIs) with several data fields.
  • IMSIs International Mobile Subscriber Identities
  • table 440 indicates whether a telephone number associated with the IMSI is owned by network 20 or network 30.
  • Table 440 also associates each IMSI with an MSC with which a corresponding client device is registered and, if the associated telephone number is owned by CS telephony network 30, with an HLR that stores VLR registration and other information associated with the IMSI. Processes for using the data of table 440 are described below.
  • FIG. 5 is a block diagram of an internal hardware architecture of device 10 according to some embodiments.
  • Device 10 may be referred to as a dual mode handset due to its capability to operate as an IP telephony network client and a wireless CS telephony network client.
  • Device 10 may include primarily conventional components, and may include program code to perform certain functions described herein. Embodiments may operate in conjunction with devices that differ in part or in whole from device 10 of FIG. 5.
  • Device 10 includes microphone 52 to receive audio signals that may represent speech of a user.
  • the audio signals may comprise commands for operating device 10, such as a command to dial a particular telephone number.
  • Speaker 55 emits audio signals from device 10.
  • the audio signals may comprise speech or other audio signals received from telephony networks and/or ring tones, beeps and other tones used during operation of device 10.
  • Analog/digital coder/decoder (A/D codec) 60 may receive analog signals from microphone 52, convert the analog signals to digital signals, and pass the digital signals to processor 12. Conversely, processor 12 may transmit digital signals to A/D codec 60, which converts the digital signals to analog signals and passes the analog signals to speaker 55. Speaker 55 then emits sound based on the analog signals.
  • Processor 12 may be a conventional microprocessor, microcontroller and/or digital signal processor (DSP) or other control circuit conventionally provided in a mobile telephony client device.
  • DSP digital signal processor
  • Processor 12 is also in communication with input 65 and display 70.
  • Input 65 may comprise any system to receive input from a user, including but not limited to an alphanumeric keypad, dedicated function keys, a touchscreen, etc.
  • Display 70 may comprise any system to display a user interface for presenting information to a user.
  • Antennae 75 and 85 may receive and transmit radio frequency signals from and to a CS telephony network and an IP telephony network, respectively.
  • Antennae 75 and 85 may be configured to transmit and receive any types of signals that comply with the communication protocol of a CS telephony network or IP telephony network in which device 10 is employed.
  • GSM transceiver 80 is operatively coupled to antenna 75 and WiFi transceiver 90 is operatively coupled to antenna 85.
  • GSM transceiver 80 and WiFi transceiver 90 may be configured to operate at different frequencies.
  • Transceivers 80 and 90 may, in accordance with conventional practices, each comprise a combination of two or more different receive/transmit modules (not separately shown) that operate in accordance with mutually different radio communication protocols to provide various services for device 10.
  • Device 10 also includes internal memory 95 and removable memory 100.
  • Internal memory 95 may include one or more of ROM (read only memory), RAM (random access memory, e.g., static RAM), and flash memory.
  • Removable memory 100 may comprise a flash memory, a Subscriber Identity Module (SIM) card or any other removable memory that is or becomes known.
  • SIM Subscriber Identity Module
  • Such a SIM card may store an IMSI to identify a subscriber within a GSM network.
  • the IMSI may be used by an MSC to determine a HLR associated with the subscriber.
  • the IMSI is associated with MM-AS 400.
  • Memories 95 and 100 may store program code that is executable by processor 12 to control device 10 in accordance with the processes described herein.
  • the program code may include but is not limited to operating system program code, application program code, device driver program code, and database connector program code.
  • Memories 95 and 100 may also store data used in the operation of device 10. Such data may include contacts, phone numbers, addresses, voice mailbox access numbers, voice mailbox access codes, and other data. Some or all of the data may be read-only, while other of the data may be rewritable.
  • FIG. 5 is simplified in a number of ways. For example, all power and power management components of device 10 are omitted from the diagram. Also, some embodiments may employ an internal architecture somewhat different or completely different from that shown in FIG. 5. Each illustrated element of device 10 may comprise any combination of hardware and/or software components suitable for providing the functions attributed thereto herein.
  • FIG. 6 is a block diagram of a software architecture for device 10 to signal speech in accordance with some embodiments. Accordingly, each block of FIG. 6 may be implemented in software.
  • the architecture of FIG. 6 supports operation in conjunction with GSM and IMS networks, but other CS or IP networks may be supported.
  • User interface 110 may provide a common user experience regardless of whether device 10 is registered with a GSM network or an IMS network. User interface 110 may provide an indication of a current mode of operation, a menu for changing the mode of operation, and a common dialing application for GSM and IMS-based modes.
  • Mode manager 115 may support simultaneous registration within GSM and IMS networks. For example, mode manager 115 may monitor signal strengths of GSM and WiFi signals, determine a mode to use based on the determined signal strengths, manage a handover algorithm during a call, and route a user request and indication to GSM services 120 or IMS services 125 depending on the mode of operation. Mode manager 115 or any other software block of FIGS. 6 and 7 may comprise a plug-in application written in Java or C and may also or alternatively be embodied in native program code of device 10.
  • GSM signaling stack 130 and IMS signaling stack 135.
  • seamless handover may require a change to the known function of Radio Resource layer 132 of GSM signaling stack 130.
  • SIP/RTP layer 137 complies with the 3 rd Generation Partnership Project (3GPP) SIP call control specification.
  • FIG. 7 is a block diagram of a software architecture for device 10 to support speech in accordance with some embodiments. Again, each block of FIG. 7 may be implemented in software, and the architecture of FIG. 7 is intended for use with GSM and IMS networks.
  • the FIG. 7 architecture includes audio driver 140 for execution by processor 12, mode manager 115, GSM audio stack 145 and WiFi IMS audio stack 150.
  • FIG. 8 is a flow diagram of process 500 to support registration of a client telephony device in a CS telephony network.
  • Process 500 addresses scenarios in which the telephone number of the client device is owned by a CS network operator and in which the telephone number is owned by an IP network operator.
  • process 500 and the other flow diagrams herein are described below in reference to a GSM telephony network, an IMS telephony network and associated signaling protocols, the teachings thereof may be applied to implementations associated with other CS telephony networks and IP telephony networks.
  • Process 500, as well as the other processes described herein may be executed by MM-AS 400 using any suitable hardware and/or software arrangement, and may be executed by any suitable device or devices that are or become known.
  • process 500 may be embodied in program code executed by a processor.
  • FIG. 9 illustrates one scenario in which client device 10 has moved into the area of MSC 314.
  • device 10 transmits a Location Update message to MSC 314.
  • the Location Update message includes an IMSI associated with client device 10.
  • MSC 314 attempts to determine a server (e.g., an HLR) of CS telephony network 30 based on the IMSI.
  • MSC 314 may perform Global Title Translation on the IMSI to determine that MM-AS 400 is the "HLR" associated with the IMSI.
  • MSC 314 therefore transmits a MAP Location Update message to MM-AS 400 because MSC 314 believes that MM-AS 400 is a "conventional" HLR 312.
  • the message is received by MM-AS 400 at step S510.
  • the message is intended to update a location of client device 10 within CS network 30.
  • the received message also includes the IMSI as an identifier of client device 10.
  • MM-AS 400 determines a server based on the IMSI.
  • MM-AS 400 consults table 440 to determine that the received IMSI is associated with a telephone number owned by CS network 30 and with HLR 312 of FIG. 9. MM-AS 400 may also update the MSC field that is associated with the received IMSI to identify MSC 314 from which the MAP Location Update message was received. As a result, MM-AS 400 remains apprised of the MSC with which each client device is currently registered. Flow proceeds from step S530 to S540 because the received IMSI is associated with a telephone number owned by CS network 30. At step S540, a second message is transmitted to the determined server to associate client device 10 with a server of IP telephony network 20. In particular, MM-AS 400 may transmit a MAP Location Update message to HLR 312 at step S540 to indicate a registration of client device 10 with MM-AS 400.
  • HLR 312 stores information indicating that MM-AS 400 is a VLR 316 (i.e., as shown in FIG. 2) associated with client device 10. Since either no other VLR is associated with client device 10 in HLR 312 (if client device 10 is initially registering with network 30), or MM-AS 400 is currently associated with client device 10 in HLR 312, HLR 312 would not transmit a MAP Cancel Location message in response to the MAP Location Update message received from MM-AS 400.
  • HLR 312 may return profile data associated with client device 10 to MM-AS 400 via a MAP Insert Subscriber Data message.
  • MM-AS 400 may use the profile data to update a record of VLR database 450 associated with client device 10, and may also transmit a MAP Insert Subscriber Data message including some profile data to MSC 314.
  • MSC 314 may acknowledge the Location Update message received from client device 10.
  • FIG. 10 illustrates an alternative scenario of process 500 in which the telephone number of client device 10 is owned by IP telephony network 20.
  • MM-AS 400 receives the MAP Location Update message from MSC 314, which includes an IMSI associated with an IP network-owned telephone number.
  • MM-AS 400 determines that no HLR is associated with the received IMSI based on table 440.
  • MM-AS 400 also determines that the IMSI is not associated with the CS network at step S530.
  • Process 500 thereafter terminates.
  • MM-AS 400 may respond to MSC 314 with a MAP Insert Subscriber Data message including profile data from HSS 212. Since the telephone number of client device 10 is owned by IP network 20, associated profile data is maintained in HSS 212 and need not be retrieved from an HLR of CS network 30. Again, MSC 314 may then acknowledge the original Location Update message received from client device 10.
  • Process 500 may therefore allow MM-AS 400 to emulate an HLR from the point of view of an MSC, and to emulate a VLR, if necessary, from the point of view of an HLR.
  • Process 500 may also allow profile data of IP network subscribers to be primarily maintained in IP network 20 and profile data of CS network subscribers to be primarily maintained in an HLR of network 30 as dictated by conventional protocols.
  • FIG. 11 is a flow diagram of process 600 to provide termination of a call to a CS network-owned telephone number according to some embodiments.
  • the call may be terminated by a client device roaming in an IP telephony network and/or in a CS telephony network.
  • Process 600 may be executed by MM-AS 400 in some embodiments.
  • a call is placed from a CS telephony network to a telephone number owned by the CS telephony network. Since the telephone number is owned by the CS telephony network, the call may be routed from PSTN 305 to Gateway MSC (GMSC) 314 as illustrated in FIG. 12. Moreover, the call may be routed via an Integrated Service Digital Network User Part (ISUP) Initial Address Message (IAM) that includes the telephone number.
  • ISUP Integrated Service Digital Network User Part
  • IAM Initial Address Message
  • GMSC 314 may query HLR 312 for an MSC/VLR with which client device 10 is currently registered.
  • This query may comprise an MAP Send Routing Info message that includes the telephone number received from PSTN 305.
  • the subscriber database of HLR 312 indicates that MM-AS 400 is the MSC/VLR currently serving device 10. Therefore, and again according to conventional GSM protocols, HLR 312 transmits a message requesting MM-AS 400 to generate a roaming number associated with client device 10.
  • the message is received at step S610 of process 600.
  • the message may comprise a MAP Provide Roaming Number message including the IMSI of client device 10, which HLR 312 has determined from the received telephone number.
  • MM-AS 400 transmits a second message to MSC 314 to request a roaming number that corresponds to the telephone number.
  • MM-AS 400 may determine the particular MSC 314 to which the message is transmitted based on table 440 and the IMSI received at step S610.
  • table 440 maintains an updated indication of a particular MSC with which each client device is registered.
  • MSC 314 then generates a roaming number associated with client device 10.
  • the generated roaming number is a number that terminates to MSC 314, and is received by MM-AS 400 from MSC 314 at step S630.
  • MM- AS 400 then transmits the roaming number to HLR 312 at step S630 via a response to the MAP Provide Roaming Number message received in step S610.
  • GMSC 314 receives the roaming number from HLR 312 and places a call thereto using an ISUP IAM message that includes the roaming number. The message is received by MSC 314 because the roaming number terminates at MSC 314. MSC 314 then sets up the call with client device 10 using conventional GSM protocols.
  • client device 10 is roaming in IP telephony network 20 during process 600.
  • Some embodiments of process 600 include determining, after step S610, to offer the call to the client device via the CS telephony network or the IP telephony network. Such a determination may be based on one or more of an operator policy (e.g., offer via IP network if client device is connected to a WLAN), a type of the call (e.g., some types of calls are offered via CS network, others via IP network), or a preference associated with the client device (e.g., only offer via CS network). The latter preference may be stored in VLR database 450 and/or in a HLR 312 associated with the client device.
  • an operator policy e.g., offer via IP network if client device is connected to a WLAN
  • a type of the call e.g., some types of calls are offered via CS network, others via IP network
  • a preference associated with the client device e.g., only offer via CS network.
  • Process 700 of FIG. 13 may provide registration of a telephone number owned by a CS telephony network while a client device is roaming in an IP telephony network.
  • WLAN-connected device 10 of FIG. 14 Prior to process 700, and following standard IMS registration procedures, WLAN-connected device 10 of FIG. 14 transmits a message to register the telephone number to IP network 20.
  • the transmitted message includes an SIP Uniform Resource Identifier (URI) associated with device 10, and the SIP URI is an identifier of device 10 within IP network 20.
  • Any suitable message (e.g., SIP Register, SIP Publish) may be transmitted by device 10 in some embodiments.
  • the message from client device 10 is received at IP network 20 in step S710.
  • the message is received by CSCF 214 of network 20 and is transmitted to MM-AS 400.
  • HSS 212 of network 20 may include a table mapping an SIP URI of each supported client device to an IMSI of the client device.
  • MM-AS 400 therefore accesses the table to determine an IMSI that is associated with the SIP URI received at step S710.
  • the determined IMSI is an identifier of client device 10 within GSM network 30.
  • MM-AS 400 may then use table 440 to identify an HLR 312 associated with the IMSI. Since the corresponding telephone number is owned by CS network 30, table 440 should include an identifier of an HLR 312 that is associated with the IMSI.
  • a second message is transmitted to the identified HLR 312 to associate a server of IP telephony network 20 with the telephone number.
  • MM-AS 400 may transmit a MAP Location Update message to HLR 312 at step S720 to indicate a registration of client device 10 with MM-AS 400.
  • HLR 312 therefore stores information indicating that MM- AS 400 is a VLR 316 associated with client device 10.
  • HLR 312 may also return profile data associated with client device 10 to MM-AS 400 via a MAP Insert Subscriber Data message, as shown in FIG. 14.
  • MM-AS 400 may use the profile data to update a record of VLR database 450 associated with client device 10.
  • Process 800 of FIG. 15 may provide termination of a call to an IP network-owned telephone number according to some embodiments.
  • the call may be offered via a CS network and terminated by a client telephony device roaming in an IP telephony network.
  • the call may be initially placed from a CS telephony network to a telephone number owned by an IP telephony network.
  • the CS network routes the call to a gateway between the CS network and the IP network, since the telephone number is owned by IP network 20.
  • FIG. 16 illustrates PSTN 305 routing such a call to a first MGCF/Media Gateway (MG) 222/224 of IP network 20.
  • PSTN 305 of FIG. 16 routes the call via an Integrated Service Digital Network User Part (ISUP) Initial Address Message (IAM) that includes the telephone number.
  • ISUP Integrated Service Digital Network User Part
  • IAM Initial Address Message
  • the first MGCF/MG 222/224 transmits an SIP Invite message to CSCF 214, which may determine a corresponding SIP URI from the telephone number based on data stored in HSS 212.
  • HSS 212 may also store a user profile in association with the SIP URI indicating that the CSCF 214 is to forward all SIP calls to MM-AS 400.
  • MM-AS 400 receives a message from CSCF 214 to initiate a call to the telephone number.
  • MM-AS 400 determines to offer the call to client device 10 via the CS telephony network.
  • the determination at step S820 may be based on one or more of an operator policy, a type of the call, or a preference associated with the client device.
  • MM-AS 400 transmits a second message at step S830 to an MSC 314 of CS network 30.
  • the second message requests a roaming number that corresponds to client device 10.
  • MM-AS 400 may determine the particular MSC 314 to which the message is transmitted based on table 440 and on the SIP URI determined by CSCF 214.
  • MSC 314 generates a roaming number associated with client device 10.
  • the generated roaming number is a number that terminates to MSC 314, and is received by MM-AS 400 from MSC 314 at step S840.
  • MM-AS 400 then transmits the roaming number to CSCF 214 via another SIP Invite message.
  • CSCF 214 then transmits a second SIP Invite message to a second MGCF/MG 222/224 that is associated with the roaming number (e.g., geographically).
  • the second MGCF/MG 222/224 may be located physically closer than the first MGCF/MG 222/224 to the determined MSC 314.
  • the second MGCF/MG 222/224 transmits a third message to MSC 314 to initiate the call to client device 10 via CS network 30.
  • the message may comprise an ISUP IAM message including the roaming number.
  • MSC 314 receives the message, identifies client device 10 as being associated with the roaming number, and sets up the call with client device 10 using conventional CS network protocols.
  • the above-mentioned signals and messages may pass through any number of networks, devices and protocols before reaching their intended recipient.
  • networks include but are not limited to local area networks, wide area networks, telephone networks, cellular networks, fiber-optic networks, satellite networks, infra-red networks, radio frequency networks, and any other type of networks which may be used to transmit information between devices.
  • data may be transmitted using one or more currently- or hereafter-known network protocols, including but not limited to Asynchronous Transfer Mode (ATM), Internet Protocol (IP), Hypertext Transfer Protocol (HTTP) and Wireless Application Protocol (WAP).
  • ATM Asynchronous Transfer Mode
  • IP Internet Protocol
  • HTTP Hypertext Transfer Protocol
  • WAP Wireless Application Protocol

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des systèmes et des procédés permettant d'enregistrer simultanément un dispositif de téléphonie client (10) auprès d'un réseau de téléphonie à commutation de circuits (20) et d'un réseau de téléphonie IP (20). Les systèmes et les procédés selon l'invention peuvent fournir une émulation d'un registre d'abonnés locaux GSM (312) à un centre de commutation mobile (314), ainsi qu'une émulation d'un registre d'abonnés visiteurs GSM (316) à un registre d'abonnés locaux (312). Ainsi, un serveur d'application (400) du réseau de téléphonie IP peut être associé à une identité internationale d'abonné mobile du dispositif de téléphonie client.
PCT/US2006/019331 2005-05-24 2006-05-18 Systeme permettant d'effectuer un double enregistrement aupres d'un reseau de telephonie ip, et d'un reseau de telephonie a commutation de circuits WO2006127417A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US68397405P 2005-05-24 2005-05-24
US60/683,974 2005-05-24

Publications (1)

Publication Number Publication Date
WO2006127417A1 true WO2006127417A1 (fr) 2006-11-30

Family

ID=37022849

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2006/019331 WO2006127417A1 (fr) 2005-05-24 2006-05-18 Systeme permettant d'effectuer un double enregistrement aupres d'un reseau de telephonie ip, et d'un reseau de telephonie a commutation de circuits

Country Status (1)

Country Link
WO (1) WO2006127417A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008104225A1 (fr) 2007-02-28 2008-09-04 Telefonaktiebolaget Lm Ericsson (Publ) Gestion de données d'abonné dans des réseaux de communication
EP2073599A1 (fr) * 2007-12-21 2009-06-24 Research In Motion Limited Commutation d'appel selon la présence
WO2011023091A1 (fr) * 2009-08-28 2011-03-03 中兴通讯股份有限公司 Procédé et système de gestion du repli vers une transmission vocale à commutation de circuits dans un réseau
US8521155B2 (en) 2007-12-21 2013-08-27 Research In Motion Limited Presence-based call switching

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003032658A2 (fr) * 2001-10-09 2003-04-17 Motorola Inc Registre d'emplacement d'un reseau de communication et unite d'abonne
EP1523208A1 (fr) * 2003-09-11 2005-04-13 Alcatel Enregistrement d'un terminal radiotéléphonique bimode dans un réseau cellulaire et un réseau de type WLAN

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003032658A2 (fr) * 2001-10-09 2003-04-17 Motorola Inc Registre d'emplacement d'un reseau de communication et unite d'abonne
EP1523208A1 (fr) * 2003-09-11 2005-04-13 Alcatel Enregistrement d'un terminal radiotéléphonique bimode dans un réseau cellulaire et un réseau de type WLAN

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
BRIDGEPORT NETWORKS, LG ELECTRONICS, MOTOROLA: "S2-051043: Anchored Call Control Model: Termination", 3GPP TSG SA WG2, 9 May 2005 (2005-05-09), Athens, Greece, pages 1 - 3, XP002401012, Retrieved from the Internet <URL:www.3gpp.org> [retrieved on 20060929] *
SIEMENS, BRIDGEPORT NETWORKS: "S2-051262: Architecture, Registration and Roaming", 3GPP TSG SA WG2 S2#46, 9 May 2005 (2005-05-09), Athens, Greece, pages 1 - 6, XP002401011, Retrieved from the Internet <URL:www.3gpp.org> [retrieved on 20060929] *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008104225A1 (fr) 2007-02-28 2008-09-04 Telefonaktiebolaget Lm Ericsson (Publ) Gestion de données d'abonné dans des réseaux de communication
CN101627603B (zh) * 2007-02-28 2013-06-12 艾利森电话股份有限公司 通信网络中的订户数据管理
EP2073599A1 (fr) * 2007-12-21 2009-06-24 Research In Motion Limited Commutation d'appel selon la présence
US8521155B2 (en) 2007-12-21 2013-08-27 Research In Motion Limited Presence-based call switching
WO2011023091A1 (fr) * 2009-08-28 2011-03-03 中兴通讯股份有限公司 Procédé et système de gestion du repli vers une transmission vocale à commutation de circuits dans un réseau

Similar Documents

Publication Publication Date Title
US8521170B2 (en) System and method for routing an incoming call to a proper domain in a network environment including IMS
US8503976B2 (en) Method and apparatus for handling emergency calls
EP2140607B1 (fr) Système et procédé pour faciliter l&#39;intégration et la gestion des capacités de service dans un environnement de réseau
US9444854B2 (en) Session initiation protocol (SIP) router
US9148288B2 (en) Conditional telecommunications
KR20070074553A (ko) 단일 번호를 갖는 유-무선 통합에서 의사 번호 이동성
US20090185665A1 (en) Method and server/module for service configurations test
KR20120039321A (ko) 회선 교환 망과 인터넷 프로토콜 멀티미디어 서브시스템 망간 로밍 서비스 제공 방법 및 시스템과 그 장치
US20080176586A1 (en) System and method for effectuating remote control of a network node by a user equipment (UE) device
US8326298B2 (en) Technique for service domain selection
WO2006105223A1 (fr) Interoperabilite d&#39;un reseau ip et d&#39;un reseau a commutation de circuits
WO2006127417A1 (fr) Systeme permettant d&#39;effectuer un double enregistrement aupres d&#39;un reseau de telephonie ip, et d&#39;un reseau de telephonie a commutation de circuits
US7519358B2 (en) Over the air provisioning of a wireless mobile station using IP multimedia subsystem mode
US20080175176A1 (en) System and method for establishing reliable data connectivity with a network node by a user equipment (UE) device
EP1807986A1 (fr) Habilitation d&#39;un client de reseau par paquets comme terminal mobile
US8340713B2 (en) Method and devices for supporting message services to a dual mode mobile station via a session initiation protocol
KR101743578B1 (ko) 호 연속 서비스 제공 시스템 및 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

122 Ep: pct application non-entry in european phase

Ref document number: 06760134

Country of ref document: EP

Kind code of ref document: A1