EP1386504A1 - Dispositif permettant d'integrer des telephones mobiles en tant que terminaux d'un systeme de communication prive - Google Patents

Dispositif permettant d'integrer des telephones mobiles en tant que terminaux d'un systeme de communication prive

Info

Publication number
EP1386504A1
EP1386504A1 EP02769147A EP02769147A EP1386504A1 EP 1386504 A1 EP1386504 A1 EP 1386504A1 EP 02769147 A EP02769147 A EP 02769147A EP 02769147 A EP02769147 A EP 02769147A EP 1386504 A1 EP1386504 A1 EP 1386504A1
Authority
EP
European Patent Office
Prior art keywords
pcs
pbx
bluetooth
bluetooth interface
interface
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP02769147A
Other languages
German (de)
English (en)
Inventor
Javier P REZ FERN NDEZ
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Priority to EP02769147A priority Critical patent/EP1386504A1/fr
Publication of EP1386504A1 publication Critical patent/EP1386504A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/16—WPBX [Wireless Private Branch Exchange]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/725—Cordless telephones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42314—Systems providing special services or facilities to subscribers in private branch exchanges
    • H04M3/42323—PBX's with CTI arrangements
    • 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
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2207/00—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place
    • H04M2207/18—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place wireless networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2250/00—Details of telephonic subscriber devices
    • H04M2250/02—Details of telephonic subscriber devices including a Bluetooth interface

Definitions

  • the present invention relates to a dual mode mobile station that can operate with two different networks; the first network being, for instance, a public mobile network (PMN), and the second network being, for instance, a private communication network or, more generally, a private communication system (PCS).
  • PMN public mobile network
  • PCS private communication system
  • the invention relates to the method for providing an integration of such MS into the telephony extension's realm of an existing private communication system.
  • a public mobile network provides a mobile telephony service to a wide range of public users using one of the common cellular systems standards, such as Global System for Mobile communications (GSM), Advanced Mobile Phone Service (AMPS), Digital-AMPS (D-AMPS), etc.
  • GSM Global System for Mobile communications
  • AMPS Advanced Mobile Phone Service
  • D-AMPS Digital-AMPS
  • GSM Global System for Mobile communications
  • PMN public mobile network
  • PCS private communication system
  • the PCS usually consist of one private communication node (where the software that controls and/or supervises the communications resides), or a network of interconnected private communication nodes (private communication network or PCN) that serve to the same company, and where the user terminals (voice and/or multimedia extensions) belonging to such company are connected.
  • private communication node where the software that controls and/or supervises the communications resides
  • PCN private communication network
  • the PCS node(s) can use one or more different media switching and signalling technologies, and can be allocated in the company office's premises (Private Branch Exchange or PBX) or be allocated in the premises of a public telecommunication service provided (for instance a CENTREX service).
  • PBX Primary Branch Exchange
  • CENTREX Public telecommunication service
  • the telephony extensions are connected to the PCS in order to exchange signalling and media; being such connection accomplished using different connection technologies (circuit switching oriented or packet oriented) and different connection means (wired and/or wireless).
  • PBX can be used across the present invention to refer also to a PCS.
  • This will be done regardless the media switching and signalling technology used in the private communication node(s) (if circuit switching, packet switching or both), regardless if such PCS consist in one or more private communication nodes, and, in the latest case, regardless the technology used to interconnect such nodes: if dedicated lines, lines shared with other users or applications, virtual private networking (VPN) through another network ( e . g. : public network), etc., or the signalling protocol and means to transport such protocol (if circuit oriented or packet oriented) .
  • VPN virtual private networking
  • the scope of the invention is not affected by any of these different technologies used to implement the PCS .
  • MS shall be used across the present invention to refer in general to a Mobile Station; such MS can be, for instance, a GSM phone, or other kind of mobile terminal that interworks with a PMN.
  • corporate MS can be used across the present invention to refer to a MS that is -in some way- integrated in the private communication system or network.
  • a significant problem is the cost associated to the calls when using a GSM phone (hereinafter referred also as mobile station or MS) instead of the PBX's desk phone while the employees are at the office.
  • MS mobile station
  • This is applicable when calling to a partner and both are at their offices, since the cost is much lower (even zero) when using a PBX's phone for making such calls, than when using the GSM network.
  • It is also applicable when making outgoing external calls through the public network (e.g. through Public Switched Telephone Network or PSTN, or through Integrated Services Digital Network or ISDN), which in most cases are more expensive when made from the MS than when they are made from a PBX's phone.
  • PSTN Public Switched Telephone Network
  • ISDN Integrated Services Digital Network
  • This problem is especially serious in the case of companies that already have international leased lines to link offices located in different countries, since these lines become wasted.
  • Another important problem is the amount of terminals that some users needs to manage when they are at the office; these terminals can be: a PBX desk phone, a MS and a cordless terminal (normally, a Digitally Enhanced Cordless Telecommunications or DECT) terminal. More terminals mean more cost for the company, different user interfaces for the employees and more telephone numbers to manage.
  • Another problem arises due to the difficulties to cover the high density of users of a typical office environment with the traditional PMNs (such as GSM).
  • Patent application WO-A-9734437 discloses methods and means to provide the MS with access to the PBX, as well as to the services provided by the PBX. It defines what it calls a wireless office system that, in one side is connected to the PBX, and in the other to a Mobile Switching Center (MSC) of a public mobile operator. The wireless office system is also provided with what it is called RAN (radio access network) which is emulating a standard BTS for the corporate MS located in the office area. Such wireless office system is "seen” as another MSC from the public mobile operator's MSC, and as either: another PBX, or an ISDN user (extension) with Primary Rate
  • Patent application WO-A-9827761 discloses methods and means pretty similar to the ones described in WO-9734437. The major difference is that, in this case, the radio access from the corporate MS uses the standard
  • Patent application WO-A-9621329 discloses a solution similar to the ones disclosed in WO-A-9734437 and WO-A- 9827761, using what it calls mobility server to link the PBX and the public mobile network. This patent has the same drawbacks as the one cited for WO-A-9734437 and WO-A- 9827761.
  • Patent application WO-A-9736442 (British Telecom) discloses methods and means to provide the MS with an alternative path to reach a BTS of a mobile public operator via PSTN, ISDN, or a fixed point-to-point connection or an alternative microwave radio link becween the company's premises and the call processing part of a mobile public operator's BTS. It defines what it calls an interface unit that, in one side connects with the MS, and in the other side connects with the alternative network (PSTN, ISDN or alternative radio link) .
  • the connection between the MS and the interface unit can be a wired electrical connection, or an optical or ultrasonic link.
  • the operation in such invention involves a method by which the radio transceiver part of the MS is disabled (disconnected) as soon as the MS is connected with the cited interface unit .
  • patent application WO-A-9736442 provides an alternative communication path for the MSs that reduces load on mobile frequency bands, and, probably, contributes to reduce cost of outgoing calls, it has some drawbacks: • Since the mobile radio part of the MS (the one interfacing with the GSM network) is disabled when it is connected to the interface unit, some modifications in the mobile network nodes are needed (disclosed in the patent) in order to receive incoming calls in such MS. Also some modifications in the mobile network nodes are needed (disclosed in the patent) to allow outgoing calls from the MS and to allow specific mobility management functions .
  • Patent application WO-A-9815143 discloses methods and means to provide the MS with an alternative path to reach: the mobile network (via an MSC of a mobile operator), ISDN, PSTN, and other MSs located into the company's office. It defines what it calls a terminal device that, in one side connects with the MS, and in the other side connects with the company's data communication network.
  • the connection between the MS and the terminal device can be a wired electrical connection, or an infrared connection.
  • the company's data communication network is provided with a network server that links the company's data communication network with the other networks (GSM, ISDN, PSTN), performs the corresponding gateway functions and maintain MS status; and also is provided with what it calls telecommunication servers (with no specific function defined).
  • GSM Global System for Mobile communications
  • PSTN Public Switched Telephone Network
  • the MS When the MS is connected with the terminal device, it is addressed in the environment of the company's data communication network by means of its transport address (e.g.: Transmission Control Protocol/Internet Protocol address, or TCP/IP address); then the network server perform the necessary translation to the corresponding phone number of the MS (e.g.: its Mobile Subscriber ISDN number or MSISDN) and vice-versa.
  • transport address e.g.: Transmission Control Protocol/Internet Protocol address, or TCP/IP address
  • TCP/IP address Transmission Control Protocol/Internet Protocol address
  • MSISDN Mobile Subscriber ISDN number
  • the so called network server is linked to a specific MSC of the mobile operator.
  • This invention requires all corporate extensions to be “moved” to the new fashioned MS-terminal device assembly. However, it does not disclosed at all how services, normally provided by today's PBX (or in co- operation with external servers), are going to be provided.
  • Patent application WO-A-9948315 discloses what it calls a wireless intranet office (WIO) that contains the necessary elements to perform the access, control and gateway functions to provide the corporate MS with an alternative path to get the public mobile network, ISDN, PSTN, and also other terminals connected in the WIO or in the company communication network.
  • WIO wireless intranet office
  • This patent is a more detailed application of patent application WO-A-9815143 (actually, it seems a "continuation in part" of that patent; even same inventor).
  • the MS is provided with a secondary network interface to connect it with the WIO via what it calls a personal base unit .
  • All the network layer in the MS (including call control, supplementary services control and mobility management control) in the MS is common for both interfaces : the standard towards the mobile network and the new one towards the WIO; being the only difference that the interface towards the WIO can be accomplished by means of a wired connection or by means of a low power radio-frequency link, such as Bluetooth.
  • the personal base unit acts as a standard BTS for the MS, and converts the GSM signalling to H.323 (CCITT standard for telephony over packet networks).
  • a server located in the enterprise's Intranet acts as H.323-Gatekeeper (call controller in H.323).
  • H.323-Gatekeeper controls the registrations and connections of the H.323 endpoints (i.e.: the personal base units ) and communicates the registrations to another element ( ILR ) that has a standard MAP (Mobile Application Part) interface to the HLR/VLR (Home Location Register/Visitor Location Register) of the mobile network.
  • ILR Information Register
  • VLR Home Location Register/Visitor Location Register
  • Such gateway converts signalling protocol between H.323 and standard GSM protocol, it also performs the needed media transcoding.
  • the WIO can contain standard BTS ' s allocated in the office's premises and a GSM/IP gateway to connect them with the rest of the WIO ' s elements via the corporate data network.
  • the invention involves a method by which the radio transceiver part of the MS is disabled (disconnected) as soon as the MS is connected with the cited personal base unit , just keeping in contact with neighbouring (standard) BTS ' s to perform standard mandatory radio measurements.
  • the legacy PCS node where the corporate MSs are housed is a traditional PBX that uses circuit switching oriented technology for providing telephony service (media switching and signalling), where all telephony extension terminals (traditional wired or wireless PBX voice and/or multimedia extensions) belonging to such PBX are fulfilling any of the existing signalling access protocols and media transfer protocols used for telephony in circuit switching oriented systems.
  • a corporate MS is fully integrated into the PBX extension realm and, consequently, into the corporate PCS; thus gaining access to all telephony services and supplementary services available in such PBX and/or PCS.
  • the legacy PCS communication node where the corporate MSs are housed is a voice over IP (VoIP) telephony system (or IP-PBX) that uses packet switching oriented technology for providing telephony service (media switching and signalling) , where all telephony extension terminals (VoIP voice and/or multimedia extensions) belonging to such IP-PBX are fulfilling any of the existing signalling protocols -such as H.323 or Session Initiation Protocol (SIP)- and media transfer protocols -such as Real Time Protocol (RTP)- used in packet switching oriented systems.
  • VoIP voice over IP
  • IP-PBX packet switching oriented technology for providing telephony service (media switching and signalling)
  • VoIP voice and/or multimedia extensions belonging to such IP-PBX are fulfilling any of the existing signalling protocols -such as H.323 or Session Initiation Protocol (SIP)- and media transfer protocols -such as Real Time Protocol (RTP)- used in packet switching oriented systems.
  • VoIP voice over IP
  • a corporate MS is fully integrated into the IP-PBX extension realm and, consequently, into the corporate PCS; thus gaining for the corporate MS access to all telephony services and supplementary services available in such VoIP telephony system.
  • the legacy PCS communication node where the corporate MSs are housed is a PBX that uses both: circuit switching oriented (first embodiment) and packet switching oriented (second embodiment) technologies for providing telephony service (media switching and signalling), where there is a variety of telephony extension terminals (voice and/or multimedia extensions) belonging to such PBX, some of them using any existing signalling protocol and media transfer protocol used in circuit switching oriented systems, and some others using any existing VoIP signalling protocol and media transfer protocol used in packet switching oriented systems (second embodiment).
  • a corporate MS is fully integrated into the PBX extension realm and, consequently, into the corporate PCS; thus gaining access to all telephony services and supplementary services available in such PBX and/or PCS.
  • PBX For the sake of a greater simplicity, hereinafter only the general term PBX shall be cited to refer the legacy PCS node where the corporate MS is housed, regardless if such PBX and their terminals uses exclusively circuit switching oriented technology (first embodiment), or if it uses exclusively packet switching oriented technology (second embodiment) or a mixture of both (third and preferred embodiment). Nevertheless, and wherever in this invention it is not specified a specific method or mean, it shall be pretty obvious for any person skilled in the art how to apply/extend such methods and means for the particular case where the legacy PCS is a traditional PBX (first embodiment), a VoIP telephony system (IP-PBX referred in the second embodiment), or a mixture of both (third and preferred embodiment).
  • IP-PBX Voice over IP-PBX
  • the main object of the present invention is to characterise the methods and means that, without implying any change affecting the mobile network (e.g. : GSM network), fully integrate the corporate MS into the legacy PCS ' s extensions realm, and avoids all the drawbacks aforementioned related with the present state-of-the-art. That is to say:
  • the corporate MS in the scope of this invention, can be any commercially available MS provided with
  • Bluetooth interface and, more precisely, provided with (at least) the so called Cordless Telephony Profile of the general Bluetooth protocol stack elements .
  • These kind of MSs are becoming more and more common, given the high degree of additional functionality they can gain with such a secondary interface; therefore, its cost will be lower than for other MS equipped with other kind of secondary interfaces (suitable only for more specific applications).
  • the corporate MS will behave as a "normal" MS for the mobile network, and as a "normal” voice and/or multimedia extension for the PCS legacy telephony system, thus not creating any new configuration issue nor modify existing configuration methods or means.
  • Bluetooth is the name given to a new short range (10 to 100 m. ) low-power radio frequency (LPRF) technology , that operates in the 2.4 GHz ISM (Industry, Science and Medicine) band. It is essentially a protocol for wireless connectivity of diverse set of devices (units), allowing point-to-point as well as point-to-multipoint connections among them.
  • LPRF radio frequency
  • Bluetooth Device Address (BD_ADDR).
  • BD_ADDR Bluetooth Device Address
  • the communication channel is shared among several Bluetooth units. Two or more units sharing the same channel form what is called a piconet . In this case, there is one master unit and up to seven active slave units in a piconet.
  • the Bluetooth devices can be in either of the states: active, park, hold and sniff. Multiple piconets with overlapping coverage areas form what is called a scatternet .
  • Bluetooth defines a protocol stack that includes, among others facilities, the physical RF link, audio management, security aspects, a telephony control protocol and even adopt the IETF Point to Point Protocol (PPP) (RFC 1661) to support Transmission Control Protocol (TCP)/User Datagram Protocol (UDP)/Internet Protocol (IP) and Wireless Access Protocol (WAP).
  • PPP Point to Point Protocol
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • IP Internet Protocol
  • WAP Wireless Access Protocol
  • the Cordless Telephony Profile takes some elements of the general Bluetooth protocol stack to enable extra mode of operation to, for instance, mobile phones, using Bluetooth as a short-range bearer for accessing telephony services of another network (e.g.: fixed network) through a Bluetooth base station connected to such network.
  • another network e.g.: fixed network
  • a PBX is a private telephony exchange system that basically consist of: interfaces to connect with end-user terminals (extension line interfaces), interfaces to connect with external lines towards public exchanges or other private exchange (known as trunk lines or external line interfaces), switch means to interconnect, when needed, those interfaces lines, and a processor, or set of processors, that executes the software (control software) that controls and/or supervises the connections, signalling and services demanded for those extension and trunk lines.
  • Analogue line interfaces used to connect Plain Old Telephone Set/Service (POTS) terminals.
  • Digital line interfaces used to connect manufacturer-specific terminals (e.g. : digital telephone set, operator console, etc.; normally using a manufacturer proprietary signalling)
  • ISDN line interfaces used to connect ISDN terminals (e.g. ISDN telephones, ISDN video-terminals, FAX-G4, etc.). These interfaces uses the well known CCITT Q.931 signalling protocol and can provide access to only one user (e.g.: a 2B+D point-to-point), or be shared by multiple users (e.g. : a 2B+D point-to-multipoint, or a 30B+D) .
  • CAS Channel Associated Signalling
  • DECT line interfaces used to connect integrated DECT base stations that provide access to cordless extensions using DECT protocol.
  • Point-to-point Data interfaces used to connect data extensions .
  • Point-to-multipoint Data interfaces used not only to connect with telephony extensions, but to connect multiple devices with varied capabilities, such as VoIP telephony endpoints (that use H.323, SIP or other packet-network based VoIP telephony protocol), telecommunication and/or telephony servers (such as
  • Gatekeeper SIP server, etc.
  • any other kind of terminal or server that are interconnected via Local
  • LAN Local Area Network
  • IP-PBX IP-PBX
  • a first ASPECT [1] of this invention in order to provide the corporate MSs with access to the PBX's basic services (including making and receiving calls), a
  • Bluetooth interface in the MS is used to communicate (call and service control signalling, as well as media transfer) directly with the PBX.
  • the PBX is provided with integrated Bluetooth interfaces (IBT) as a new extension line interface type.
  • IBT integrated Bluetooth interfaces
  • Such a new interface type contains (at least) the so called Cordless Telephony Profile of the general Bluetooth protocol stack elements, including also the physical RF link, to communicate (call and service control signalling, as well as media transfer) with the corporate MS .
  • IBT integrated interface
  • the generic term access unit can be used to refer hereinafter an IBT.
  • the traditional extension lines interfaces of the PBX are provided with gateways (GWs).
  • GWs will convert the Bluetooth radio signals, protocol and media format to the signals, protocols and media format already supported by today's PBX as extension line interfaces (the end-user terminal interfaces), and vice-versa.
  • extension line interfaces the end-user terminal interfaces
  • GW will contain (at least) the so called Cordless Telephony Profile of the general Bluetooth protocol stack elements, including also the physical RF link, to communicate (call and service control signalling, as well as media transfer) with the corporate MS.
  • a GW interface unit of such type will be hereinafter referred as BTGW.
  • BTG.V can hereinafter be referred with the generic term access unit.
  • ASPECT [3] of the invention there can be two different ways for a corporate MS to register its presence (log-on) in the PBX and, once registered, to access to the PBX's services (including making and receiving calls).
  • This aspect is primarily intended to get the PBX aware on the registered corporate MSs, as well as to get it aware of the location of the physical connection (extension line interface) it has to use to communicate (e.g.: to place further incoming calls) with each one of them.
  • FIXA Fixed access way
  • FLEXA Flexible access way
  • FIXA and FLEXA can coexist in the same PBX. That is to say, belonging from the same PBX, there can be access units that implement FIXA access and others access units that implement FLEXA.
  • the PBX is provided with different methods and means to identify the state of the connection (i.e.: present/available or absent/unavailable) of each corporate MSs.
  • This aspect is primarily intended to get the PBX aware of if a given call to a corporate MS can be placed in the corresponding extension line interface or, if instead, such call should be treated in other way; e.g. : forwarded to other destination, since such MS is not available (e.g.: the MS is outside the coverage area of the access unit).
  • the PBX is provided with methods and means to handle the corporate MS ' s identification (i.e.: its telephone extension number) of each corporate MS that will be used when it is registered in the PBX without any kind of additional number translation.
  • This aspect is primarily intended to make possible for other party to address (to call) and to identify (e.g.: as calling or connected party) the corporate MS by means of a number which belongs to the PBX's number series for its extension realm, and which is not the MSISDN number used normally to address a MS from any public network (PSTN, ISDN, GSM, etc.)
  • other party means a telephone extension, which belongs to the PBX (including also a corporate MS), or which belongs to another PBX or network (VPN, PSTN, ISDN, GSM, etc.).
  • the PBX is provided with methods and means to handle incoming calls towards the corporate MSs.
  • This aspect is primarily intended to do not lose incoming calls to a corporate MS received in the PBX from another internal party (including also a corporate MS) or from another external party belonging to any other network connected (directly or indirectly) to the PBX (another PBX, VPN, PSTN, ISDN, GSM, etc). So, the PBX can forward the incoming call either: to the MSISDN number of such corporate MS (thus the MS will receive the call through the public mobile network; e.g.: GSM), or it can forward the call to another answering position, internal to the PBX (e.g.: secretary, voice mail system), or external.
  • GSM public mobile network
  • the corporate MSs and/or the PBX are provided with different methods to perform a bearer selection for handling outgoing calls made from the corporate MSs.
  • an outgoing call made from a corporate MS registered in the PBX can be routed either: via the corresponding access unit through the PBX, or through the public mobile network.
  • This aspect is mainly (but not exclusively) intended to select the least cost path for a call that, in most of the cases, will be to route the outgoing call via the access unit through the PBX.
  • This aspect will apply only when the corporate MS is inside the office environment; that is to say: when it is registered in the PBX via any kind of access unit.
  • ASPECT [8] of the invention and in order to fully integrate the corporate MSs as terminals of the PBX, methods and means are provided so that corporate MSs gain fully access to, at least, the same services/features nowadays available for the already existing telephone extensions belonging to a PBX.
  • services provided today by a PBX for the telephone extensions belonging to its extension realm such as activation/deactivation of call forwarding, intrusion, multiconference (call with more than 3 parties simultaneously), call pick-up, transfer, etc., could be invoked also from any corporate MS, regardless the type of access unit used to connect with the PBX, and be served from the PBX as it does for the other existing types of telephone extensions.
  • the corporate MSs and/or the PBX are provided with different methods that, as soon as a MS successfully registers (logs-on) in the PBX through an access unit, the calls made to its MSISDN number are forwarded to the PBX directory number for such MS defined in aspect [5].
  • a series of figures are included with illustrative and non-limiting character, representing the object of the invention.
  • Figure 1 is a schematic representation of a prior-art Private Communication System (PCS).
  • Figure 2 is a schematic functional block representation of an aspect ( aspect-1) of the present invention where a PCS node is provided with
  • FIG. 3 is a detailed functional block representation of an aspect (aspect-1) of the present invention where a PCS node is provided with Integrated
  • Figure 4 is a functional block representation of the Cordless Telephony Profile elements integrated in the IBT.
  • Figure 5 is a schematic functional block representation of an aspect (aspect-2) of the present invention where a PCS node is provided with Bluetooth Gateways (BTGW) .
  • BTGW Bluetooth Gateways
  • FIG. 6 is a detailed functional block representation of an aspect (aspect-2) of the present invention where a PCS node is provided with Bluetooth
  • BTGW Bluetooth Gateways
  • Figure 7 is a functional block representation of the configuration functions and means in the BTGW.
  • Figures 8, 9, 10 and 11 are schematic functional block representations of an aspect (aspect-3) of the present invention, showing different ways for a corporate MS to register.
  • Figures 12, 13, 14 and 15 are flow details of the different methods of one aspect (aspect-3) of the present invention covering different access/register methods for corporate MSs.
  • Figure 16 is a functional block representation of the different methods of one of the aspects
  • FIG. 3 is a functional block representation of one of the methods described in one aspect (aspect-4) of the present invention.
  • Figure 18 is a functional block representation showing the relationship between some elements in a corporate MS for some aspects (aspects-7 and 9) of the present invention.
  • Figure 19 is a flow chart representing one of the methods of one aspect (aspect-7) of the present invention.
  • Figure 20 is a detailed functional block representation of the elements needed to be added to the
  • FIGS. 21 and 22 are functional block representations showing the relationship between some elements in a PCS node for one aspect (aspect-8) of the present invention.
  • Figure 23 is a functional block representation showing the relationship between some elements a BTGW for one aspect (aspect-8) of the present invention.
  • Figures 24, 25 and 26 are flow details of the different methods one aspect (aspect-9) of the present invention covering methods to provide calls to the corporate MS be received through the PCS .
  • Figure 27 is a generalisation summarising figures 2 and 5.
  • PBX the general term PBX shall be cited to refer the legacy PCS node where the corporate MS is housed, regardless if such PBX and their served terminals use, for signalling and media transfer, exclusively circuit switching oriented technologies (first embodiment), or if they use exclusively packet switching oriented technologies (second embodiment) or a mixture of both (third and preferred embodiment). Nevertheless, and if it is not specified a particular method or mean, it shall be pretty obvious for any person skilled in the art how to apply/extend such methods and means for the particular case where the legacy PCS is a traditional PBX (first embodiment), a VoIP telephony system (IP-PBX referred in the second embodiment), or a mixture of both (third and preferred embodiment).
  • IP-PBX Voice telephony system
  • ASPECT [1] In this aspect, the corporate MSs are provided with access to the PBX's basic services, including making and receiving calls, by means of Bluetooth interfaces integrated in the PBX.
  • a PBX handles today a variety of different interfaces, each one connecting the PBX with one or more "terminals" at the other end.
  • These "terminals” can be end-user terminals (voice and/or multimedia telephony extensions), other telephony node (another PBX, PCS ( 1 ) or a communication node belonging to another network), or a telecommunication and/or telephony servers (such as Call Distribution Server, Voice Server, H.323 Gatekeeper, SIP server, etc) .
  • interfaces serving end-user terminals are usually referred as extension line interfaces.
  • These interfaces can also be of a variety of types depending on the end-user terminal type they serve (e.g.: POTS, ISDN, CAS, H.323, SIP, proprietary -or vendor specific-, etc.), and they are implemented in the PBX system by means of specific software and hardware.
  • the PBX is provided with integrated Bluetooth interfaces (30) (IBT hereinafter) as a new extension line interface type, that will be implemented by means of specific software and hardware, that will be added to be handled among the existing ones in the PBX, and that will serve to the corporate MS's extension types.
  • IBT integrated Bluetooth interfaces
  • the corporate MS will exchange call control signalling, service control signalling directly with the PBX's control software, and, when needed, will exchange media information (e.g. : audio information) directly with the PBX's switching means (59).
  • media information e.g. : audio information
  • Each IBT (30) will found its own Bluetooth piconet that will provide access to the corporate MSs to the PBX services.
  • CTP Cordless Telephony Profile
  • Such elements that also include the physical RF link, will be used to communicate (call and service control signalling, as well as media transfer) with the corporate MS.
  • the Telephony Application (TA) element of the CTP (29) defined by Bluetooth specifications can be performed by the present telephony control common software of the PBX without any substantial modification for the scope of the present aspect.
  • This software is, in today's PBX, already in charge of control and/or supervision for the connections, signalling and services demanded for the different interfaces (whatever type), and has slight differences, or no differences at all, when dealing with different extension line interface types.
  • IBT (30) extension line interface types they can be treated as any other extension line type.
  • the TCS-Binary element of the CTP (29) defined by Bluetooth specifications is a mere Network Layer (ISO Layer-3) communication protocol based on CCITT standard Q.931.
  • This kind of elements (Layer-3 communication protocols) are part of the present state-of-the-art in any PBX that has to deal with different communication protocols used in the different interfaces (whatever type) it handles.
  • Such elements are usually implemented by means of different software modules (or software functions), each one specialised in a particular Layer-3 communication protocol; although implementation in firmware (located in the memory of the board that contains the physical layer of the specific communication protocol) is also used in the present state-of-the-art .
  • this kinds of elements (software modules implementing Layer-3 communication protocols) belong (monitored and driven/controlled by) on the previously cited telephony control common software of the PBX; and they, in turn, handle (monitor, drive and control ) the lower layers ( layers 2 and 1 ) of their respective communication protocols. So, in a particular PBX, a new software module that performs the functions required by TCS-Binary protocol shall be placed as a new element serving a specific Layer-3 protocol .
  • the Service Discovery Protocol (SDP) element of the CTP (29) defined by Bluetooth specifications provides a means for the applications (Cordless Telephony application in this case) to discover which services are available, and to determine their characteristics.
  • the PBX shall be provided with, at least, the SDP-server part defined by Bluetooth specifications that must contain, at least, a service- attribute defined in CTP (29) for the gateway configuration/role.
  • This element can be implemented as a stand-alone software module that will be place at the same functional level in the PBX software architecture as the module implementing the TCS-Binary element, and that will interwork with such element, and with the Logical Link Control and Adaptation Protocol (L2CAP) element according to the Bluetooth specification for CTP (29). Other option could be to merge it with the software module implementing the TCS-Binary element.
  • L2CAP Logical Link Control and Adaptation Protocol
  • L2CAP Logical Link Control and Adaptation Protocol
  • LMP Link Manager Protocol
  • BaseBand and Bluetooth Radio are mere ISO layer-2 protocols dealing with data link management (LMP and L2CAP) and ISO layer-1 protocols dealing with physical aspects of the connections (BaseBand and Bluetooth Radio).
  • the layer-1 elements BaseBand and Bluetooth Radio are used to convey, not only call and service control signalling in both directions (from corporate MS to PBX, and vice versa), but also media (e.g.: voice) in one or in both directions (from corporate MS to PBX switching means (59), and vice versa) when needed (upon demand of upper layers ) .
  • This kind of elements are part of the present state-of-the-art in any PBX that has to deal with different communication protocols used in the different interfaces (whatever type) it handles. Due to the low-time response requirements for Layers 2 and 1 functions, such elements are usually realised by means of different hardware and firmware modules (or firmware functions) that are allocated in the specific board(s) or physical device(s) that connect (using whatever mean wired or wireless) the terminal (whatever type) with the control and switching means (59) of the PBX serving to such terminal; also such boards (or physical devices) are provided with an interface (board interface) that is used to exchange control and media information with the rest of the PBX elements (software and hardware), using a data-format coding and physical communication means that -in most of the cases- is common for all boards (or physical devices) of this type, regardless the specific layers 1 and 2 of the protocol they implement.
  • Such hardware and firmware modules in the cited boards (or physical devices) implements, not only the data link layer (layer-2) and the physical layer (layer-1) of every specific communication protocol, but also the transcoding and adaptations functions for media exchange between the terminal (whatever type) and the switching means (59) of the PBX serving such terminal.
  • a new board (or physical device) type containing hardware and firmware modules needed to implement the functions required by L2CAP , LMP, BaseBand and Bluetooth Radio shall be placed as a new element serving a specific Layer-2 and Layer-1 protocol, as well as the transcoding and adaptations functions for media exchange between the corporate MS and the switching means (59) of the PBX.
  • BaseBand and Bluetooth Radio that can be placed in any existing board-firmware architecture used presently by the PBX.
  • configuration means i.e.: operation and maintenance means
  • configuration means i.e.: operation and maintenance means
  • the presently used configuration means ' s structure common and/or type-specific for extension line interfaces, that apply in a particular PBX, will apply also for the new extension line interface type.
  • common configuration means for extension line interfaces that generally apply regardless the specific communication protocol and particular characteristics of the interface type; and/or - when needed- specific configuration means, that are specific for every communication protocol and particular characteristics of the interface type.
  • the presently used common configuration means used for extension line interfaces will apply also for the new IBT (30) interface type.
  • new configuration means will be needed.
  • Such new type-specific configuration means for IBT (30) will, in the scope of the present aspect, provide data related to capacity of the physical parts of each IBT interface (30); that is to say: the number of corporate MSs able to be connected concurrently (even with simultaneous conferences -calls-) to the same IBT (30) physical interface.
  • the required IBT (30) for this invention can be of two types:
  • SIBT Single IBT (30) (SIBT), having capacity to hold (to control and to serve) only one corporate MS per IBT (30) physical interface; that is to say: only one corporate MS per IBT (30) physical interface
  • MS in the piconet belonging to a given IBT (30) physical interface MS in the piconet belonging to a given IBT (30) physical interface .
  • the maximum number of simultaneous conferences (calls) to/from such MS (2) is a mater of internal implementation option both: in the MS (2) and in the PBX.
  • the most simple solution is to support only one call; so, in this case, if the corporate MS has already one call established, the PBX will consider it as busy for subsequent incoming calls towards this corporate MS. Therefore, with the help of this feature, automatic busy services available for telephony extensions (such as call forwarding on busy, etc.) can be served by the PBX to the "busy" corporate MS.
  • MIBT Multiple IBT (30) (MIBT), having capacity to hold (to control and to serve) concurrently more than one corporate MS per IBT physical interface; that is to say: more than one corporate MS in the piconet belonging to a given IBT physical, being the limit imposed by Bluetooth technology (up to 7).
  • the maximum number of simultaneous conferences (calls) to/from each MS (2) held by one MIBT is a mater of internal implementation option both: in the MS (2) and in the PBX.
  • the most simple solution is to support only one call per MS (2) held in one MIBT; so, in this case, if a corporate MS has already one call established, the PBX will consider it as busy for subsequent incoming calls towards this corporate MS. Therefore, with the help of this feature, automatic busy services available for telephony extensions (such as call forwarding on busy, etc.) can be served by the PBX to the "busy" corporate MS.
  • MIBT MIBT shall behave as the master device in its Bluetooth piconet. Both kinds of IBT: SIBT and MIBT can hereinafter be referred as access units.
  • the apparatus for integrating mobile telephones as terminals of a PCS (Private Communication System) (1) is provided with control means including extension realm control means.
  • Said apparatus comprises integrating means for integrating at least one MS (Mobile Terminal) (2) into the PCS (1) as an admissible MS.
  • Said MS (2) is equipped with a first interface (3) for communicating with at least one PMN (public mobile network) (3a) and with a second interface which is a Bluetooth interface (4).
  • PMN public mobile network
  • Said integrating means comprise at least one stationary
  • Bluetooth interface (5) connected to Bluetooth radio transceiver means (6) which have A limited radio coverage area for communicating with each admissible MS located within the radio coverage area.
  • Said stationary Bluetooth interface (5) comprises first transcoding means (7) for enabling communication between the PCS control means (8) and said Bluetooth radio transceiver means (6).
  • the stationary Bluetooth interface (5) may be integrated in the PCS (1) (connected in this way named as IBT (Integrated BlueTooth) (30)).
  • Said IBT (Integrated BlueTooth) (30) comprises:
  • transcoding means (7, 23) for enabling media transfer and control signalling between the elements of the CTP (29) defined by Bluetooth specifications and
  • the corporate MSs are provided with access to the PBX's basic services, including making and receiving calls, by means of Bluetooth interfaces acting as gateways between Bluetooth protocol and any extension line communication protocol used already in the PBX; thus, without affecting, nor requiring any modification, in any existing PBX's component (interface type, specific hardware, specific software, etc.) nor in its methods (configuration, operation, maintenance, etc.).
  • the physical connection means of traditional (existing) extension lines interfaces of the PBX are connected to gateways (GWs) (27).
  • Such GWs (27) will convert the Bluetooth radio signals, protocol and media format to the signals, protocols and media format already supported by today's PBX as extension line interfaces (the end-user terminal interfaces), and vice- versa.
  • a GW (27) of such type will be hereinafter referred as BTGW ( 27 ) .
  • the required BTGW (27) for this invention is a device provided, in one side, with (at least) one communication protocol stack used in one of the extension line interfaces existing in today's PBX to communicate (call and service control signalling, as well as media transfer) with the PBX, thus acting as any end- user terminal endpoint (telephony extension, multimedia extension, etc.) from the PBX's point of view; and, in the other side, with (at least) the so called Cordless Telephony Profile of the general Bluetooth protocol stack elements (the same as cited in the previous aspect-1) to communicate (call and service control signalling, as well as media transfer) with the corporate MS.
  • IWFs interworking functions
  • the TA (34) element can be common for both sides of the interworking (Bluetooth and extension line communication protocol used) . Its final complexity and functions will depend on the extension line communication protocol used (e.g.: very simple for POTS, and more complex for ISDN, H.323, etc.).
  • the TA (34) will, at least, be in charge of control and supervision for the connections (media and signalling) demanded to/from the corporate MS. To accomplish this it will interact, in one side, by means of service primitives with the TCS-Binary element, and with the BaseBand element according to Bluetooth' Cordless Telephony Profile; and, in the other side, with the Layer-3 specific protocol stack used in its interface towards the PBX, as well as with the transcoding and other media adaptation (Layer-1) and channel allocation functions needed for media interworking between both sides.
  • Layer-3 specific protocol stack used in its interface towards the PBX
  • the TA (34) will receive primitives indicating reception of messages and/or protocol events from TCS-Binary element or from the Layer-3 protocol used in the PBX side, and -after processing, and if needed- will send the corresponding primitives to the corresponding side (TCS-Binary or Layer-3 protocol used in the PBX side) for sending the corresponding message or taking the corresponding protocol action.
  • TCS-Binary protocol is based in Q.931 (which is quite versatile and complex, and there are many communication protocols based on it), it should be pretty obvious for any person skilled in the art how the translation of primitives between the TA (34) and the Layer-3 (if existing) protocol used in the PBX side (and vice-versa) should look like: for Q-931-like protocols, it should be a direct translation (e.g.: SETUP- indication from one side, should be translated to SETUP request to the other side); and for simpler protocols (such as POTS), it should consist on translate message indications from the Bluetooth side to orders to electrical devices in the other side (e.g.: SETUP- indication or RELEASE-indication from TCS-Binary, should be translated to an order to open or close electrical loop in the POTS side).
  • Q-931-like protocols it should be a direct translation (e.g.: SETUP- indication from one side, should be translated to SETUP request to the other side); and for simpler protocols (such as PO
  • the TCS-Binary element will perform the same functions as described in previous aspect (1). It will interact with the TA (34) by means of service primitives that, among other functions, will be used to indicate to the TA (34) the reception of a given message (or protocol event), as well as to receive from the TA (34) a request for sending a given message (or taking a given action).
  • TA (34) delegates protocol message transcoding (according to explanations above) into a specific IWF located either: in the TCS-Binary element, in the Layer-3 protocol used in the PBX side of the BTGW (27), or a stand-alone IWF that interacts with the TCS-Binary and with the Layer-3 protocol used in the PBX side for mere translation purposes.
  • the SDP element will have the same functions as described in previous aspect (1), and no IWF for functions related to this element is needed.
  • the BTGW (27) shall be provided with, at least, the SDP-server part defined by Bluetooth specifications that must contain, at least, a service-attribute defined in CTP (29) for the gateway configuration/role.
  • This element can be implemented as a stand-alone software/firmware module that interworks with the TCS-Binary element, and with the L2CAP element according to the Bluetooth specification for CTP (29). Another option could be to merge it with the software/firmware module implementing the TCS-Binary element.
  • the L2CAP and LMP elements will have the same functions as described in previous aspect (1), and no IWF for functions related to these elements is needed.
  • the BaseBand element will need an IWF to adapt the format and coding of the media received from the MS ( 2 ) to the format and coding used in the PBX side of the BTGW (27) and vice-versa.
  • This IWF will be driven by the TA (34), and will be in charge of media transcoding and channel allocation for synchronous connection oriented information flows (media flows) from the corporate MS to the PBX and vice-versa. It will also be provided with switching functions for those flows if the BTGW (27) has capacity to serve concurrently call to/from more than one corporate MS (Multiple BTGW (27) referred later in this aspect).
  • the Bluetooth Radio element since it is the endpoint of the bearer mean used to convey information (control and media transmission) to/from the corporate MS to the BTGW
  • the required BTGW (27) for this invention can be of two types : • Single BTGW (SBTGW) (27), having capacity to hold (to control and to serve) only one corporate MS; being the maximum number of simultaneous conferences (calls) to/from such MS (2) limited by internal implementation in the MS (2), and also by the capacity of simultaneous conferences (calls) supported by the interface used between the SBTGW (27) and the PBX; that is to say: limited by the extension line protocol used in such interface (e.g.: some extension line protocols consider "user busy" condition if the user has just one ongoing call, and other protocols does not have this limitation, but other
  • MBTGW Multiple BTGW
  • a MBTGW (27) shall behave as the master device in its Bluetooth piconet .
  • the configuration control of BTGWs (27) can be performed, as an implementation option, either: in every access unit (SBTGW or MBTGW) (27), by means configuration parameters and a local configuration interface, or, in a centralised manner, in the PBX control software.
  • SBTGW or MBTGW access unit
  • MBTGW mobility management protocol
  • SNMP remote configuration/management
  • SBTGW and MBTGW can hereinafter be referred as access units (same as stated before for SIBT and MIBT) .
  • the apparatus for integrating mobile telephones as terminals of a PCS (Private Communication System) (1) is provided with:
  • Second transcoding means (23) for enabling media transfer between the PCS switching means (59) and said
  • Bluetooth radio transceiver means (6) Bluetooth radio transceiver means (6).
  • Configuration control means (25) provided by the stationary Bluetooth interface (5) by means of configuration parameters and a local, remote or a combination thereof, configuration interface providing at least data related to the capacity of the physical parts of each stationary Bluetooth interface (5) and the number of integrated MSs able to be connected concurrently).
  • Said configuration control means (25) of the stationary Bluetooth interface (5) are located either in every stationary Bluetooth interface (5) or centralised in the PCS control software (8) or a combination thereof.
  • At least one stationary Bluetooth interface (5) belonging to at least one of the types selected from:
  • Said stationary Bluetooth interface (5) which control and serve more than one integrated MS.
  • Said stationary Bluetooth interface (5) is connected to an already existing extension line type interface (26) of the PCS (1) (connected in this way named as BTGW (BlueTooth Gateway) (27)).
  • Said BTGW (BlueTooth Gateway) (27) comprises: • A RF link to antenna (28) operating under Bluetooth protocol.
  • FIXA Fixed access way
  • FLEXA Flexible access way
  • SIBT SIBT, MIBT, SBTGW (27) or MBTGW (27)
  • MBTGW MBTGW
  • the same access unit if capable to support multiple users (MIBT or MBTGW (27)) can implement both kind of accesses: FIXA and FLEXA (e.g.: a certain MIBT or MBTGW (27) can accept both: registration of a set of predefined users, and have capacity to accept registration of a certain number of non-predefined users).
  • MIBT or MBTGW (27) can implement both kind of accesses: FIXA and FLEXA (e.g.: a certain MIBT or MBTGW (27) can accept both: registration of a set of predefined users, and have capacity to accept registration of a certain number of non-predefined users).
  • the standardised access mechanisms defined in Bluetooth shall be used to authenticate (recognise/identify) the corporate MS of a particular user by means, primarily, of its individual (and unique) BD_ADDR (which is known by the access unit in the "Device Discovery” and “Link Establishment” phases defined by Bluetooth) , and so to guarantee that such a particular user can access to the PBX through any Bluetooth access unit (SIBT, MIBT, SBTGW (27) or MBTGW (27)) only if such a user is allowed to do it according to previously configured data (i.e.: defined set of users allowed to access the PBX).
  • SIBT Bluetooth access unit
  • MIBT MIBT
  • SBTGW SBTGW
  • MBTGW Mobility Management Function
  • DB-BD_ADDR-A one data-base type storing the BD_ADDRs of all authorised corporate MSs
  • DB-BD_ADDR-B another data- base type storing the BD_ADDR(s) allowed per each access unit
  • a data-base DB-BD_ADDR-B shall be realised in every access units of kind FIXA storing its particular data (allowed BD_ADDR(s) in this access unit).
  • DB-BD_ADDR-A data-base DB-BD_ADDR-A is not needed in the access unit (it will exist elsewhere if FIXA and FLEXA accesses types coexist in the same PBX) .
  • DB-BD_ADDR-B shall be realised in an unique data-base accessible to the PBX's control software storing the particular data of every access unit (allowed BD_ADDR(s) in every access unit) .
  • DB-BD_ADDR-A data-base DB-BD_ADDR-A is not needed, although it shall be realised elsewhere if FIXA and FLEXA accesses types coexist in the same PBX.
  • DB-BD_ADDR-B is not needed regardless the case (case-1 or case-2) in the access unit (it will exist elsewhere if FIXA and FLEXA accesses types coexist in the same PBX) .
  • This data-base DB-BD_ADDR-A can, as an implementation option: be realised in every access units of kind FIXA (case-1), or realised in an unique data-base accessible to the PBX's control software (case-2). In any case
  • data-bases DB-BD_ADDR-A and/or DB-BD_ADDR-B can contain a one-to-one relationship between each
  • MSISDN number can be used for number translation purposes both: when the corporate MS register in the PBX, and at call to/from the corporate MS when it is registered (present) in the PBX (e.g.: for calling number, called number, connected number, etc.).
  • BD_ADDR-B does not contain MSISDN numbers; for each corporate MS that has successfully registered in the PBX through any kind of access unit, the PBX can handle an internal identifier (telephone number) that, for the extent of this aspect, will be its MSISDN number.
  • DB-BD_ADDR-C DB-BD_ADDR-C that contain a one-to-one relationship between the BD_ADDRs of each authorised corporate MS and their corresponding MSISDN number.
  • DB-BD_ADDR-C shall be realised in an unique data-base accessible to the PBX's control software and, as an implementation option, can be the same data-base as DB- BD_ADDR-A (if it is already realised as unique and accessible to the PBX's control software) by pairing BD_ADDR/MSISDN data.
  • Such DB-BD_ADDR-C shall be used for number translation purposes (e.g.: for calling number, called number, connected number, etc.) at call to/from the corporate MS when it is registered (present) in the PBX.
  • the PBX shall establish the association between the corresponding individual user profile(s) inside the PBX domain defined for each corporate MS ' s identification number (BD_ADDR or MSISDN number) and the access unit (SIBT, MIBT, SBTGW (27) or MBTGW (27)) where such user is physically located (registered/connected) for the forthcoming traffic (e.g. : calls) to/from such corporate MS .
  • BTGW Communication via the used existing protocol ("X” protocol) and then, via internal communication means between interface specific functions for this protocol ("X" protocol) in the PCS and the Common Control Software in the PCS.
  • BD_ADDR of the MS is known in the access unit).
  • Notify register including BD_ADDR and/or MSISDN number.
  • BTGW Communication via the used existing protocol ("X” protocol) and then, via internal communication means between interface specific functions for this protocol ("X" protocol) in the PCS and the Common Control Software in the PCS.
  • BD_ADDR of the MS is known in the access unit).
  • Request register including BD_ADDR and/or MSISDN number.
  • BTGW Communication via the used existing protocol ("X” protocol) and then, via internal communication means between interface specific functions for this protocol ("X" protocol) in the PCS and the Common Control Software in the PCS.
  • 55 Link establishment request (register request) (the BD_ADDR of the MS is known in the access unit).
  • 12 Check data-base DB-BD_ADDR-A and result.
  • BTGW Communication via the used existing protocol ("X” protocol) and then, via internal communication means between interface specific functions for this protocol ("X" protocol) in the PCS and the Common Control Software in the PCS.
  • Link establishment request (register request) (the BD_ADDR of the MS is known in the access unit).
  • Request register including BD_ADDR and/or MSISDN number.
  • the apparatus for integrating mobile telephones as terminals of a PCS (Private Communication System) (1) is provided with: • Bluetooth mode communication means for communicating with each present MS.
  • Bluetooth mode communication means which activate a Bluetooth mode communication in replacement of said at least one PMN capability which has been inhibited in said PMN-inhibited MS, thereby enabling the PMN- inhibited MS, to communicate with the PCS (1) by said Bluetooth mode communication means in a PCS-operated mode as an integrated MS being integrated into the PCS (1) as a PCS extension enabled to communicate through the PCS (1) .
  • Bluetooth mode communication means which activate a Bluetooth mode communication enabling said integrated MS to place calls through the PCS (1) when said MS call placing capabilities have been inhibited.
  • Bluetooth mode communication means which activate a Bluetooth mode communication enabling the integrated MS to receive calls through the PCS (1) when said MS call receiving capabilities have been inhibited.
  • At least one stationary Bluetooth interface (5) which comprises access control means for determining if a particular MS (2) has access or not to the PCS (1) through said stationary Bluetooth interface (5).
  • at least one stationary Bluetooth interface (5) and the PCS (1) comprising access control means for determining if a particular MS (2) has access or not to the PCS (1) through a unique predefined stationary Bluetooth interface (31), through a set of predefined stationary Bluetooth interfaces (31) or through any available stationary Bluetooth interface (32).
  • Storage means (9) for storing identification data of each admissible MS.
  • Said storage means (9) comprise identification assigning means for assigning at least a first telephone extension number belonging to the PCS (1) to each admissible MS.
  • the storage means (9) have the capacity for each admissible MS of establishing an association between: an identifier of said admissible MS corresponding to its BD_ADDR (Bluetooth Device Address); and at least a second attribute corresponding to its MSISDN (mobile phone number) .
  • BD_ADDR Bluetooth Device Address
  • MSISDN mobile phone number
  • the storage means (9) have also the capacity of at least establishing further associations between each admissible MS and other attributes concerning to said MS selected from at least one of the following attributes: internal user profile, user name identification, category barring, secondary telephone extensions, user location based on the stationary Bluetooth interface (5) used by the MS (2), and usable information for the operation of the PCS (1).
  • the PBX is provided with different methods and means to identify the state of the connection (i.e.: present or absent) of each corporate MSs.
  • This aspect is primarily intended to get the PBX aware of if a given call to a corporate MS can be placed in the corresponding extension line interface or, if instead, such call should be treated in other way; e.g.: forwarded to other destination, since such MS (2) is not available (e.g.: the MS (2) is outside the coverage area of the access unit) .
  • the present state-of-the-art techniques that applies in today's PBX to deal with incoming calls to not-available telephone extensions (e.g.: extensions that are switched-off or disconnected), can also be available for corporate MS.
  • the methods described for this aspect will apply both: when the MS (2) register its presence in the PBX extension realm (via any kind of access unit), and later, for every registered corporate MS, in order to know its availability state (i.e.: if it is still in the coverage area of an access unit) .
  • a first method referred in this invention as soft-method, is mainly intended to be applied to integrated access units (IBTs: SIBT and MIBT), and for gateway access units (BTGWs (27): SBTGW or MBTGW) that handle a message- oriented protocol towards the PBX as extension line interface.
  • IBTs integrated access units
  • MIBT integrated access units
  • BTGWs gateway access units
  • SBTGW or MBTGW gateway access units
  • This first method is accomplished by indicating from the access unit (SIBT, MIBT, SBTGW (27) or MBTGW (27)) the presence/absence (i.e.: MS (2) registering, MS (2) registered, or MS (2) not registered/out of coverage) of the corporate MS by means of control messages sent through the signalling interface between the access unit and the PBX.
  • Said first method can be based on similar flows as described in previous aspect 3 wherein the MS registers its presence in the PBX.
  • one of the methods by means of which the PBX identifies the state of the connection (i.e. present or absent) of each coroporate MS is illustrated in figures 12, 13, 14 and 15.
  • IBT integrated access unit
  • MIBT magnetic resonance imaging
  • the PBX can periodically request to the SIBT or MIBT such status for the registered corporate MS indicating (when needed) the relevant data identifying the particular corporate MS.
  • gateway access unit SBTGW or MBTGW
  • this can be attained by indication from the BTGW (27) (e.g.: at MS (2) registration, and periodically while the MS (2) is in idle state) of a message specific of the protocol used between the BTGW (27) and the PBX including (when needed) the relevant data identifying the particular corporate MS.
  • the PBX can emit periodically such kind of message for each already registered corporate MS indicating (when needed) the relevant data for identifying the particular corporate MS, in order to check its connection state.
  • the protocol used between the gateway and the PBX already regards such kind of information in standard messages, then such standard messages can be used (e.g.
  • a second method is mainly intended to be applied to gateway access units (BTGWs (27): SBTGW or MBTGW) that does not handle a message-oriented protocol towards the PBX as extension line interface (e.g.: POTS interface); although it can also apply to gateway access units that handle a message- oriented protocol towards the PBX.
  • This second method is accomplished by the connection/disconnection from the BTGW (27) of one or more of its communication layers (33) (OSI model layers) towards the PBX, depending of the presence/absence of the corporate MS in the BTGW (27) neighbourhood.
  • the simple connection/disconnection of such layer-1 upon corporate MS's presence/absence situations, it is enough for the PBX to know if a given corporate MS is available or not.
  • a SBTGW (27) is connected to the PBX with a POTS interface (i.e. analogue extension line that handle only one user terminal)
  • the gateway can notify the PBX that the MS (2) is not connected (MS not registered, or connection lost) by opening the loop (high-ohmic state, e.g.
  • the protocol used between the BTGW (27) and the PBX is ISDN (e.g.: an SO interface)
  • the BTGW (27) maintains its layer-2 link with the PBX disconnected.
  • the BTGW (27) re-establish the layer-2 link again, so network-layer (layer-3) messages can be exchanged with the PBX to notify the registration and for further traffic (calls) to/from this MS (2).
  • the BTGW (27) lost the contact with the MS (2) (e.g.: out of coverage), then it disconnect the layer-2 again.
  • the method can be extended to any other upper communication layer (33) (OSI layers 3 to 7) by, for instance, neglecting any function or message pertaining to such layer, and re-establishing the "normal" operation upon absence/presence user(s) situations.
  • Figure 17 is a functional block representation this method.
  • the PBX is provided with methods and means to handle the corporate MS ' s identification (i.e.: its telephone number) when it is registered in the PBX without any kind of additional number translation.
  • This aspect is primarily intended to make possible for other party to address (to call) and to identify (e.g.: as calling or connected party) the corporate MS by means of a number which belongs to the PBX's number series for its extension realm, and which is not the MSISDN number used normally to address a MS (2) from any public network (PSTN, ISDN, GSM, etc.)
  • other party means a telephone extension, which belongs to the PBX (including also a corporate MS), or which belongs to another PBX or network (VPN, PSTN, ISDN, GSM, etc. ) .
  • a method assigns to every corporate MS an individual extension number belonging to the PBX's internal number series, which is not the MSISDN number used normally to address a MS (2) from any public network (PSTN, ISDN, GSM, etc.).
  • the extension number can include, not only its internal representation in the PBX realm - Normally a short number with, for instance, 4 or 5 digits- , but also the corresponding network prefixes to reach the PBX's extension realm from any other network).
  • Such assignation can be done for some or all authorised corporate MSs (the ones allowed to register and make use of the PBX via any kind of access unit), regardless the kind of access unit (SIBT, MIBT, SBTGW (27) or MBTGW (27)), and regardless the used access method (FIXA or FLEXA); Such assignation will performed based on a relationship between either: the BD_ADDR and the assigned extension number, or the MSISDN number (got from BD_ADDR as explained in Aspect-3) and the assigned extension number.
  • the telephony application in the corporate MS contains such extension number. Among other data, it transmits such extension number when it registers in to the PBX via any kind of access unit, and continues using it later in its interface with the access unit. Then the access unit uses such extension number in its interface with the PBX.
  • the access unit contains the relationship between the BD_ADDR (or the MSISDN number got from the BD_ADDR) and the extension number. It uses the BD_ADDR (received, among other data, from the MS (2) when it register) on its interface with the MS (2), and then, the access unit uses such extension number in its interface with the PBX. Optionally, the access unit can send the extension number to the corporate MS when it has successfully registered. Such extension number can be used in the corporate MS for local information purposes, and also for further communication with the access unit.
  • the PBX contains the relationship between the BD_ADDR (or the MSISDN number got from the BD_ADDR or received from the access unit) and the corresponding extension number. It uses the BD_ADDR on its interface towards the access unit, and the extension number for internal purposes . This feature can be achieved with the help of the previously cited (Aspect-3) DB-BD_ADDR-C , where the values of MSISDN numbers are replaced by the corresponding extension numbers .
  • the PBX can send the extension number to the corporate MS via the access unit when it has successfully registered (for BTGW (27) this is only feasible if the protocol between the PBX and the BTGW (27) allows any method to convey such information).
  • extension number can be used in the corporate MS for local information purposes, and also for further communication with the access unit.
  • the PBX has a fixed assignment, for some or all access units, of one extension number per access unit.
  • This solution can be suitable, for instance, for access units of the type BTGW (27) that handle a protocol that does not regards registration procedures (e.g.: POTS for analogue telephone lines), and also for accesses of type FIXA.
  • the PBX can send the extension number to the corporate MS via the access unit when it has successfully registered (for BTGW (27) this is only feasible if the protocol between the PBX and the BTGW (27) allows any method to convey such information).
  • Such extension number can be used in the corporate MS for local information purposes, and also for further communication with the access unit.
  • the association between the directory number of a user and the access unit where that user is physically located can also be made manually by the user, e.g. by means of dialling a keypad procedure.
  • the user shall indicate its directory number and, optionally, some kind of PIN to authenticate it; so, after analysing the keypad procedure, the PBX software can establish the relation between that access unit and the user's directory number.
  • This solution can be suitable, for instance, when there is need to provide flexible access (FLEXA) with access units of the type BTGW (27) that handle a protocol that does not regards registration procedures (e.g.: POTS for analogue telephone lines).
  • the apparatus for integrating mobile telephones as terminals of a PCS (Private Communication System) (1) is provided with storage means (9) having the capacity for each admissible MS of establishing an association between: an identifier of said admissible MS; and at least a first attribute corresponding to a first telephone extension number belonging to the PCS ' s extension realm.
  • Said storage means (9) store the BD_ADDR (Bluetooth Device Address) of each admissible MS as an identifier of said admissible MS.
  • BD_ADDR Bluetooth Device Address
  • the storage means (9) have the capacity for each admissible MS of establishing an association between: an identifier of said admissible MS corresponding to its BD_ADDR (Bluetooth Device Address); and at least a second attribute corresponding to its MSISDN (mobile phone number) .
  • BD_ADDR Bluetooth Device Address
  • MSISDN mobile phone number
  • the storage means (9) have also the capacity of at least establishing further associations between each admissible MS and other attributes concerning to said MS selected from at least one of the following attributes: internal user profile, user name identification, category barring, secondary telephone extensions, user location based on the stationary Bluetooth interface (5) used by the MS (2), and usable information for the operation of the PCS (1).
  • association between an admissible MS and at least one of its attributes may be established in different moments, selected from at least: association accomplished when the admissible MS becomes a present MS; association previously established and remains fixed until a new parameterisation is done;
  • the association between an admissible MS and at least one of its attributes may be stored in different locations, selected from at least: within the MS (2), within the stationary Bluetooth interface (5) and within the PCS (1).
  • the PBX is provided with methods and means to handle incoming calls towards the corporate MSs.
  • This aspect is primarily intended to do not lose incoming calls to a corporate MS received in the PBX from another internal party (including also a corporate MS) or from another external party belonging to any other network connected (directly or indirectly) to the PBX (another PBX, VPN, PSTN, ISDN, GSM, etc).
  • This method is accomplished by establishing, for every corporate MS, a relationship in the PBX's control software between the extension number cited in the previous aspect [5], and the corresponding MSISDN number for this corporate MS .
  • the PBX when a corporate MS is called through the PBX, and either: it does not answer, or, with the help of a previous aspect [4] described in this invention, the PBX is aware that such MS (2) it is not reachable (e.g.: switched off or out of coverage); the PBX can forward the incoming call either: to the MSISDN number of such corporate MS (thus the MS (2) will receive the call through the public mobile network; e.g.: GSM), or it can forward the call to another answering position, internal to the PBX (e.g.: secretary, voice mail system), or external to the PBX.
  • GSM public mobile network
  • the apparatus for integrating mobile telephones as terminals of a PCS (Private Communication System) (1) is provided with integrating means that further comprises first call-forward executing means in the PCS (1) ordering the PCS (1) that communications addressed to the aforementioned first telephone extension number, be forwarded from the PCS (1) either: to another telephone extension number belonging to the PCS ' s extension realm via internal communication means in said PCS (1), or to another public or private network.
  • PCS Principal Communication System
  • the first call-forward executing means in the PCS (1) further orders to forward said phone call from the PCS (1), either: to another extension number belonging to the PCS ' s extension realm, via internal communication means in said PCS (1); or to another party external to the PCS (1), including the MSISDN number of the MS (2) itself, via any existing external communication means in said PCS (1) with another public or private network.
  • the corporate MS and/or the PBX are provided with different methods to perform a bearer selection for handling outgoing calls made from the corporate MSs.
  • an outgoing call made from a corporate MS registered in the PBX can be routed either: via the corresponding access unit through the PBX, or through the public mobile network.
  • This aspect is mainly (but not exclusively) intended to select the least cost path for a call that, in most of the cases, will be to route the outgoing call via the access unit through the PBX.
  • This aspect will apply only when the corporate MS is inside the office environment; that is to say: when it is registered in the PBX via any kind of access unit.
  • calls from the corporate MS when it is outside the office environment that is: not registered in the PBX
  • a first method to accomplish this aspect is to provide this bearer selection as an option in the ' corporate MS ' s user interface. Since such feature will probably be provided in all commercial mobile telephones provided with Bluetooth, then a corporate MS can use such built-in function to perform the bearer selection for outgoing calls among the PBX and the mobile network.
  • a second method to accomplish this aspect is to provide a bearer selection function on top of the GSM and Bluetooth protocol stacks in the corporate MS. That is to say, such function would belong to a telephony application in the corporate MS that lies in two legs: one of them interworking with the GSM protocol stack, and the other interworking with the Bluetooth protocol stack.
  • Such function would analyse the digits dialled for the user and, according to predefined criteria, would place the call through the PBX (via Bluetooth interface with the access unit), or place it through the public mobile network (via the standard GSM interface with the BTS).
  • the predefined criteria can be based on: a list of numbers, a list of number series (e.g.: all numbers starting with certain digits), a combination of both (list of numbers and number series), in the link status availability with the PBX and with the public mobile network (e.g. : all call routed through PBX if the contact with the public mobile network has been lost) and also in the time of the day of day of the week.
  • such function includes manipulation (rearrangements) of the digits dialled by the user in order to adapt such dialled digits to the network (PBX or GSM) that will primarily serve such call. For instance, if a corporate MS user dials another MS user's MSISDN number, then this function can add to such number the PBX ' s defined prefix for external calls (e.g. : 00) if a call to such number (or number type) is intended (predefined) to be routed through the PBX.
  • PBX network
  • a third method to accomplish this aspect is achieved by a co-ordinated interworking between the corporate MS and the PBX control software.
  • the function in the MS (2) would belong to the previously cited telephony application in the corporate MS that controls both legs of the two communication protocol stacks (GSM and Bluetooth) .
  • the digits dialled by the user in the MS (2) shall be sent to the PBX, via the corresponding access unit (the one where the corporate MS is presently linked), to be checked there.
  • a specific function in the PBX control software shall return to the corporate MS, via the corresponding access unit, the result indicating what interface to use for such outgoing call: if the standard GSM interface, or the Bluetooth interface towards the PBX via the access unit, as well as digit re-arrangements when needed .
  • the realisation of the communication protocol between the access unit (IBT or BTGW (27)) and the PBX will depend on the signalling interface between the access unit and the PBX.
  • IBT integrated access unit
  • gateway access unit SBTGW or MBTGW
  • this can be attained by means of a messages specific of the protocol used between the BTGW (27) and the PBX.
  • standard messages can be used (e.g.: an ARQ/ACF sequence of messages in case H.323 protocol is used).
  • a message available in such protocol that can convey upper-layer information (e.g.
  • user data not intended to be interpreted by such protocol, but by its user instead, can be used to convey transparently this information (e.g.: a User-Information message in case ISDN/Q.931 protocol, or other kind of message that allows tunnelling of information through the used protocol).
  • the method to send the dialled digits from the MS ( 2 ) to the PBX and the order from the PBX to the MS (2) indicating what interface to use for such outgoing call and the digits to dial, can be based on a
  • WAP (44) or HTTP is transported over the Bluetooth link from the MS (2) to the access unit, and over the data network from the access unit to the
  • the apparatus for integrating mobile telephones as terminals of a PCS (Private Communication System) (1) is provided with inhibiting means for converting a present MS into a PMN-function-inhibited MS, by at least partially and at least temporarily inhibiting at least one PMN capability in a present MS (said PMN capability is selected from MS (2) call placing capabilities for establishing outgoing communications directly to the PMN (3a) in order to convert the present MS into a PMN- calling-inhibited MS, and MS (2) call receiving capabilities for receiving incoming communications directly from the PMN (3a) in order to convert the present MS into a PMN-receiving-inhibited MS .
  • PMN capability is selected from MS (2) call placing capabilities for establishing outgoing communications directly to the PMN (3a) in order to convert the present MS into a PMN- calling-inhibited MS, and MS (2) call receiving capabilities for receiving incoming communications directly from the PMN (3a) in order to convert the present MS into a PMN-receiving-inhibited MS.
  • At least one admissible MS is provided with bearer selection means located in a TA (Telephony Application) (34) of said MS, in order to select which network to use for making an outgoing call: if the PMN (3a) or the PCS (1); where said bearer selection means perform a control selection for outgoing calls between the two available interfaces: the standard interface (3) with the PMN (3a), and the Bluetooth interface (4) with the PCS (1), said selection based either: in a user indication, or in an analysis of the digits dialled by the user according to a list of numbers previously stored in the MS (2) containing the criteria of selection per stored number or series of numbers .
  • TA Telephony Application
  • At least one admissible MS is provided with a TA (Telephony Application) software (34) enhanced with bearer selection means to perform a re-arrangement (35) of the digits dialled by the user depending on the bearer selected: PMN (36) or PCS (37).
  • TA Telephony Application
  • the PCS (1) comprises bearer selection means to select which network to use for making an outgoing call: either the PMN (3a) -vr the PCS (1); said selection being accomplished by means of a co-ordinated operation via the stationary Bluetooth interface (5), between: the TA (Telephony Application) (34) of the MS (2) and the bearer selection means of the PCS (1); where the TA (34) first sends the dialled digits to the PCS (1) and then, the PCS (1) returns to the TA (34) either: an indication containing the network to be use, a re-arrangement of the dialled digits to make the call, which implicitly contains information about which network to use, or a combination thereof .
  • the Keypad Method consists in the mere transmission of the digit (s) related to the specific procedure. This method is the most suitable (but not limited to) to be used for BTGW (27) that have a POTS interface towards the PBX.
  • This keypad method can also be invoked when the corporate MS has already an established call by means of Dual Tone Multifrequency (DTMF) digits.
  • DTMF Dual Tone Multifrequency
  • the access unit will analyse the dialled DTMF digit and, depending on the digit itself and on the traffic case of the present call, will either: transfer the DTMF information to the connected party, or invoke a given service.
  • dialling digit "2" for an already established call could imply to park such call and have the possibility to make a new one; then, later dialling digit "3" the present call would be mixed in the PBX with the previous parked call into a three-party conference; etc..
  • Such transparent transmission of digits from the corporate MS to the access unit can lean in the telephony application defined in the Cordless Telephony Profile protocol profile already defined by Bluetooth protocol stack with the help of the DTMF service defined in the TCS-Binary protocol. In this way, no modification would be needed in such telephony application nor in the TCS-Binary protocol to achieve the purpose of this aspect .
  • Confirmation of successful/unsuccessful activation or deactivation of service can be provided back, from the access unit to the corporate MS, via confirmation audible tone, by means of text messages, by means of Bluetoot 's specific progress messages, or by any other method already available for any telephony application defined in the Cordless Telephony Profile protocol profile of Bluetooth protocol stack.
  • the set of all available services accessible to be invoked in a given state e.g.: while in idle state, while in call to other party, while in call to busy party, etc.
  • the confirmation of successful/unsuccessful activation or deactivation of service can be shown in the corporate MS's display.
  • the corporate MS shall be provided with a standard browser protocol (such as WAP (44) or HTTP).
  • the corresponding information related to available services shall be dynamically (depending on the present MS's state) posted from the PBX, via access unit of type IBT, by sending WML or HTML pages; or posted from the access unit of type BTGW (27) upon either : internal information related to services available per possible communication state stored in the BTGW (27), or - information received dynamically from the PBX.
  • the telephony application in the corporate MS shall post this information via the used protocol (WAP (44) or HTTP) into the PBX via the access unit.
  • WAP (44) or HTTP used protocol
  • This kind of method should not imply any modification in a commercial MS (2) provided with Bluetooth interface, if they are provided also with a standard WAP (44) or HTTP browser able to any of the radio interfaces: Bluetooth (at least) and GSM.
  • the access unit IBT or BTGW (27)
  • the invocation from the corporate MS of a given service, as well as the subsequent confirmation of successful/unsuccessful activation or deactivation of service can be carried out by different methods. These methods will basically depend on the type of access unit used (IBT or BTGW (27)).
  • the access unit is IBT (SIBT or MIBT)
  • SIBT SIBT or MIBT
  • the function in the IBT will vary depending on the method used to request/confirm the services in its interface towards the corporate MS.
  • Keypad Method upon reception of keypad digits from the corporate MS, two options can be implemented: the digits are transmitted towards the PBX Common Control Software as received from the MS (2); or they are interpreted in the IBT, so an explicit service (45) indication is sent to the PBX Common Control Software.
  • the IBT shall be previously instructed from the PBX Common Configuration Functions, or programmed internally, about every correspondence between a keypad digit combination and the corresponding service (e.g. : "*21*extension_n#” means "unconditional call forwarding" (48) to extension with number 'extension_nr •' ) .
  • the appropriate tone, text message, etc. (as cited before for this method), shall be sent to the corporate MS.
  • the Graphical User Interface Method is used, then, upon reception of the post message from the corporate MS, two options can be implemented: the posted message is transmitted towards the PBX Common Control Software transparently (40) as received from the MS (2); or it is interpreted in the IBT, so a explicit and specific service indication is sent to the PBX.
  • the IBT shall be previously instructed from the PBX Common Configuration Functions, or programmed internally, about every correspondence between every content in the message and the corresponding service.
  • the access unit is BTGW (27) (SBTGW or MBTGW)
  • SBTGW or MBTGW the service request from the BTGW (27) to the PBX
  • the subsequent confirmation of successful / unsuccessful activation or deactivation of service from the PBX to the BTGW (27) shall be signalled by using the same procedures that applies today to request and confirm services in the specific signalling interface (standard or proprietary) used between the BTGW (27) and the PBX.
  • the service request and confirmation can run according to two standard protocols: Generic Functional Protocol or Keypad Protocol, since both protocols are defined as standard for requesting supplementary services (39) through ISDN-SO interfaces.
  • the service request will consist in Dual Tone Multifrequency (DTMF) sent from the BTGW (27) towards the PBX, and the confirmations will be performed by means of audible tone sent from the PBX to the BTGW (27).
  • DTMF Dual Tone Multifrequency
  • the function in the BTGW (27) will vary depending on the method used to request/confirm the services in its interface towards the corporate MS, and needs to be programmed internally.
  • the BTGW (27) shall interpret the requested service and translate it to the appropriate format according to the protocol used in its interface towards the PBX. If such protocol is, for instance POTS, then the function in the BTGW (27) can be so simple as to transform these digits into DTMF signals or decadic pulses. For other more complex protocols, such as H.323 or ISDN-SO, then, once the keypad digits have been interpreted, the BTGW (27) shall perform the corresponding coding of the service, and then send the subsequent message requesting the service to the PBX.
  • the appropriate tone, text message, etc. (as cited before for this method) shall be sent to the corporate MS.
  • the BTGW (27) upon reception of the post message from the corporate MS, the BTGW (27) shall interpret the requested service and translate it to the appropriate format according to the protocol used in its interface towards the PBX. That is to say, once the BTGW (27) has interpreted the requested service, it shall act as described above for the Keypad Method.
  • a particular case when a Graphical User Interface Method is used is to provide the end-point for the WAP (44) or HTTP communication in the PBX instead than in the BTGW (27). This is applicable if the underlying network (and underlying network protocol) that links the BTGW (27) with the PBX allows several network connections towards the same device (such as H.323 or SIP over IP network).
  • the BTGW (27) acts just as a transparent bridge of information between the client application using WAP (44) or HTTP in the corporate MS, and the server application using WAP (44) or HTTP in the PBX. That is to say, there is not any end-point application using WAP (44) or HTTP in the BTGW (27), but the application in the BTGW (27) just act as a relay for the WAP (44) or HTTP messages received from the corporate MS via radio and the ones received from the PBX via, for instance, IP network.
  • the corporate MS is provided with a function that, as soon as it successfully register (logs-on) in the PBX through an access unit, all calls that are made to this MS (2) using its MSISDN number (the "normal" way to call a MS (2)) are forwarded to the extension number cited in aspect [5], and thus will be received in the corporate MS from the PBX via the corresponding access unit.
  • the cited function in the MS (2) would belong to the previously cited telephony application in the corporate MS that controls both legs of the two communication protocol stacks (GSM and Bluetooth); and it could implement three different methods:
  • the first method implies that the corporate MS user has previously programmed a "call forwarding on no reachable" (46) against the public mobile network, stating the PBX extension number (with the corresponding network prefixes to reach the PBX) as "forwarding-to number” .
  • the second method does not imply any previously programmed "call forwarding on no reachable" in the public mobile network. Instead such number is either: previously stored in the corporate MS, or got from the PBX or from the access unit in the registration procedure (as described in aspect [5]).
  • the cited function when the corporate MS successfully register into the PBX (68, 69, 70, 71), the cited function will first request a "call forwarding on no reachable" against the public mobile network (72), stating the extension number (with the corresponding network prefixes to reach the PBX) as "forwarding-to number”. Then, upon successful result of the forwarding request, it will disconnect the GSM radio link (73) that the MS (2) has established with the public mobile network.
  • the third method does not imply to disconnect the GSM radio link. Instead, when the corporate MS successfully register into the PBX (76, 77, 78, 79), the cited function will first request an "unconditional call forwarding" (48) against the public mobile network, stating the extension number (with the corresponding network prefixes to reach the PBX) as "forwarding-to number". This extension number can be previously stored in the corporate MS, or got from the PBX or from the access unit in the registration procedure as described in aspect [5] .
  • the public mobile network will forward subsequent incoming calls to this MS (2) to the previously programmed forwarding number (that is the cited extension number). Therefore, subsequent incoming calls to this MS (2) that are made to its MSISDN number will be received in the PBX where the corporate MS is currently located. Also regardless the method used, the cited function will perform the reverse procedure when the corporate MS lose its contact with the access unit (64, 74, 80).
  • the cited function will, e.g., turn on the GSM radio link (66, 49) for cases where said radio link was previously disconnected and/or send automatically a request to "cancel call forwarding" (67, 50, 82) to the public mobile network. So, subsequent calls to this MS (2) that are made to its MSISDN number will be directly received in the MS (2) via the public mobile network.
  • the details of the features disclosed in this aspect are illustrated in figures 24, 25 and 26. Thus, in figure 24 the following elements can be seen:
  • MS has previously requested to the PMN network a "Call Forwarding On No Reachable” indicating, as "forwarding to" number, its extension number in the PCS realm (corresponding prefixes are added).
  • 60, 61, 62 and 63 Corporate MS successfully registers into the PCS .
  • Bluetooth stack Telephony Application in the corporate MS orders to PMN stack to enable radio-link to PMN or to attach to PMN network.
  • OPTIONALLY order to PMN stack to cancel the previous call forwarding.
  • Bluetooth stack Telephony Application in the corporate MS orders to PMN stack to enable radio-link to PMN or to attach to PMN network.

Landscapes

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

Abstract

L'invention concerne un dispositif permettant d'intégrer des terminaux mobiles (MS) (2) en tant que terminaux supplémentaires d'un système de communication privé (PCS) (1). Le système de communication privé (PCS) (1) peut comprendre un noeud de communication et un ensemble de noeuds de communication interconnectés desservant des postes multimédia et/ou vocaux. Les terminaux mobiles intégrés selon le mode de réalisation décrit dans cette invention représentent, pour le PCS (1) des postes normaux (câblés ou sans fil), ce qui permet l'accès à tous les services téléphoniques ainsi qu'à des services supplémentaires prévus dans le système de communication privé (1) pour les postes téléphoniques. Les terminaux mobiles (2) décrits dans cette invention consistent en un dispositif équipé d'une interface classique qui permet la connexion avec un ou plusieurs réseaux mobiles publiques, ainsi que d'une interface Bluetooth. L'interface Bluetooth équipant le dispositif (MS) (2) est utilisée pour connecter ledit dispositif au réseau de communication privé (1) au moyen d'une interface Bluetooth homologue (5) qui est, soit intégrée dans le système de communication privé (1), soit attribuée à une passerelle qui traduit le protocole et le format du support.
EP02769147A 2001-05-08 2002-05-07 Dispositif permettant d'integrer des telephones mobiles en tant que terminaux d'un systeme de communication prive Withdrawn EP1386504A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP02769147A EP1386504A1 (fr) 2001-05-08 2002-05-07 Dispositif permettant d'integrer des telephones mobiles en tant que terminaux d'un systeme de communication prive

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
EP01217000 2001-05-08
EP01201700A EP1257132A1 (fr) 2001-05-08 2001-05-08 Appareil pour l'integration des téléphones mobile comme terminals de un réseau de communication privé
PCT/EP2002/005215 WO2002091768A1 (fr) 2001-05-08 2002-05-07 Dispositif permettant d'integrer des telephones mobiles en tant que terminaux d'un systeme de communication prive
EP02769147A EP1386504A1 (fr) 2001-05-08 2002-05-07 Dispositif permettant d'integrer des telephones mobiles en tant que terminaux d'un systeme de communication prive

Publications (1)

Publication Number Publication Date
EP1386504A1 true EP1386504A1 (fr) 2004-02-04

Family

ID=8180278

Family Applications (2)

Application Number Title Priority Date Filing Date
EP01201700A Withdrawn EP1257132A1 (fr) 2001-05-08 2001-05-08 Appareil pour l'integration des téléphones mobile comme terminals de un réseau de communication privé
EP02769147A Withdrawn EP1386504A1 (fr) 2001-05-08 2002-05-07 Dispositif permettant d'integrer des telephones mobiles en tant que terminaux d'un systeme de communication prive

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP01201700A Withdrawn EP1257132A1 (fr) 2001-05-08 2001-05-08 Appareil pour l'integration des téléphones mobile comme terminals de un réseau de communication privé

Country Status (2)

Country Link
EP (2) EP1257132A1 (fr)
WO (1) WO2002091768A1 (fr)

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1692603A (zh) * 2001-07-06 2005-11-02 通用仪表公司 利用移动手机访问移动及基于ip的语音电话网络的方法、装置及系统
DE10220919B4 (de) * 2002-05-10 2004-04-15 Tenovis Gmbh & Co. Kg Verfahren zum Betrieb eines Bluetooth-Handsets an Basisstationen
FR2846175B1 (fr) * 2002-10-17 2005-01-28 Wavecom Procede de controle d'acces a un reseau de communication, reseau sans fil, dispositif et programmes d'ordinateurs correspondant
KR100489893B1 (ko) * 2002-11-20 2005-05-17 한국전자통신연구원 무선랜 셀룰러 시스템 및 그의 동작 방법
FI118710B (fi) * 2004-01-22 2008-02-15 Bluegiga Technologies Oy Mobiilin VOIP-päätelaitteen hälytys ja yhteydenmuodostus
EP1856932B1 (fr) * 2005-03-08 2019-09-04 Vodafone Holding GmbH Dispositif comportant deux unites emettrices / receptrices pour l'echange d'informations entre un terminal mobile et un reseau de telephonie mobile
DE102005018768A1 (de) * 2005-04-22 2006-11-02 Avaya-Tenovis Gmbh & Co. Kg Pushen von Informationen in Telekommunikationsanlagen mit drahtlos angebundenen Endgeräten
KR100882187B1 (ko) * 2005-07-14 2009-02-06 삼성전자주식회사 아이피 멀티미디어 서브시스템 기반의 음성패킷서비스제공을 위한 장치 및 방법
US8019279B2 (en) 2005-10-25 2011-09-13 International Business Machines Corporation System and method for using mobile phones as handsets for IP softphones
US20070280200A1 (en) * 2006-05-31 2007-12-06 Patel Mehul B System and method for controlling a voip client using a wireless personal-area-network enabled device
EP2472812B1 (fr) * 2010-12-29 2014-02-12 Rtx A/S Architecture VOIP multicellulaire sans fil adaptative
US9026097B2 (en) * 2012-11-09 2015-05-05 Symbol Technologies, Inc. Device and method for communication devices
WO2017074272A1 (fr) * 2015-10-27 2017-05-04 Özalp Özer Système de suivi de mode occupé de téléphone mobile
CN113709710B (zh) * 2020-05-21 2023-08-08 成都鼎桥通信技术有限公司 接口管理方法及设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5890064A (en) * 1996-03-13 1999-03-30 Telefonaktiebolaget L M Ericsson (Publ) Mobile telecommunications network having integrated wireless office system
US5995843A (en) * 1996-12-18 1999-11-30 Telefonaktiebolaget Lm Ericsson Method and arrangement for using a mobile phone in a wireless office network
US6223055B1 (en) * 1997-10-24 2001-04-24 Lucent Technologies, Inc. Wireless office architecture and method of operation thereof
FI107979B (fi) * 1998-03-18 2001-10-31 Nokia Mobile Phones Ltd Järjestelmä ja laite matkaviestinverkon palvelujen hyödyntämiseksi
WO2000004732A1 (fr) * 1998-07-15 2000-01-27 Yaron Ruziack Telephone cellulaire a liaison par infrarouge

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO02091768A1 *

Also Published As

Publication number Publication date
WO2002091768A1 (fr) 2002-11-14
EP1257132A1 (fr) 2002-11-13

Similar Documents

Publication Publication Date Title
US20220386213A1 (en) System and method for executing originating services in a terminating network for ims and non-ims applications
US10034220B2 (en) System and method for enabling VPN-less session setup for connecting mobile data devices to an enterprise data network
CA2453069C (fr) Procedes, appareils et systemes d'acces a des reseaux de telephonie mobile et voix sur ip a l'aide d'un combine mobile
EP1155579B1 (fr) Systeme de transmission selective d'appels a des dispositifs mobiles
US8005070B2 (en) Extension of a local area phone system to a wide area network with handoff features
US7380022B2 (en) Method and apparatus for transmitting wired data voice over IP data and wireless data through a common IP core network
US7742768B2 (en) Extension of a local area phone system to a wide area network
US7277724B2 (en) Multi-mode mobile station and method
CA2495093C (fr) Fourniture de donnees de routage dans un systeme de communication
US6560223B1 (en) Wireless multi-site networking using signaling and voice-over-IP
JP2004519119A (ja) 電話呼出のｉｐ接続からの遠隔自動転送のための方法およびシステム
WO2000035176A1 (fr) Dispositif et procede pour l'integration telephonique sur le rtpc et internet
EP1350370A1 (fr) Reselection de telephone mobile entre un reseau cellulaire commute par circuit et internet et utilisation d'internet pour coupler des centres de commutation mobile a des antennes
US7369539B1 (en) System and method for providing service control to a single telephone end terminal from multiple service providers
EP1257132A1 (fr) Appareil pour l'integration des téléphones mobile comme terminals de un réseau de communication privé
EP1536621B1 (fr) Portabilité de numéros de terminal dans un réseau de télécommunications IP
US7369844B2 (en) Supplementary call grabber service for mobile networks
JP2002305588A (ja) Ｉｐ電話との相互接続通信システムおよび通信方法
WO2006042139A2 (fr) Services de telephonie communs a de multiples dispositifs associes a de multiples reseaux
US20010003092A1 (en) System and method relating to private telecommunication systems
EP1345462A1 (fr) Système de télécommunication sans fils et procédé d'operation correspondant
JPH11168773A (ja) 移動電話システム
WO2006011865A1 (fr) Station mobile wwan/wlan multimode et procede permettant d'enregistrer ladite station mobile dans un wwan par le biais d'un wlan

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20031022

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

AX Request for extension of the european patent

Extension state: AL LT LV MK RO SI

RIN1 Information on inventor provided before grant (corrected)

Inventor name: PEREZ FERNANDEZ, JAVIER

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20081202