Patent Application
20130294386
The present invention relates to telecommunications, and more particularly telecommunications including enterprise servers, wireless communications, and the interoperability of communication technologies.
Corporations are increasingly relying on the use of cellular technology by their employees. Yet enterprises do not have adequate means to control cellular service, in terms of costs, Quality of Service, and corporate monitoring. This is because cellular service is independently managed and controlled by wireless carrier networks with no connectivity to the enterprise voice and data networks, as shown in
Enterprises today control their enterprise fixed voice and data networks, as is shown on the left of the diagram. They own and manage their own PBXs, within each branch, and between branch offices. They also own and manage their own data networks and corporate LAN/WAN. They purchase bulk voice minutes and data capacity from land line carriers, or from other providers that have purchased bulk minutes and data capacity from carriers, to connect branch offices, using public IP Network providers (e.g. MCI, Sprint, L3, etc.) for Data and Voice over IP (VoIP).
With this invention, the enterprise is able to equally extend this paradigm to cellular service by connecting the public wireless voice and data network (on the right side of the diagram) into the enterprise. This is shown in
The invention achieves technical advantages as a method of establishing a communication link between a mobile terminal of a wireless network and a subscriber of a network, such as an enterprise network, and/or a residential network.
Effectively in one preferred embodiment of the invention, a gateway mobile server is provided that runs a turnkey cellular system that does not include any radio network components. The gateway mobile server is appropriately scaled down to the smaller subscriber base of a large enterprise, compared with that of a public carrier. The gateway mobile server advantageously supports call routing between a legacy, hybrid or IP-PBX, and the public cellular network in support of the enterprise/virtual operator business model.
This solution ultimately enables enterprises to change the way they purchase cellular service from cellular operators by enabling enterprises to effectively become a Mobile Virtual Network Operator (MVNO) for their own employees, and ultimately even sell cellular service external to the enterprises corporation. Thus, the enterprise is able to purchase discount bulk rate cellular minutes of use from a public cellular carrier, and “resell” them internally to their cost centers, or externally to other entities. The solution effectively enables the enterprise to “plug-in” cellular service akin to how local and long distance are connected to the enterprise's PBX. The result is that enterprises can consume minutes of use from public cellular carriers and pay for those minutes at the end of a time period, for example at the end of the month. A single relationship can exist between the cellular carrier and the enterprise, rather than multiple individual subscriptions between the carrier and enterprise employees (where the carrier is forced to treat them as ordinary consumers). This embodiment of the invention also facilitates the situation in which a single service provider can provide local, long distance, cellular and internet service to an enterprise. Ultimately the enterprise can become its own service provider with its own Home Location Register (HLR) and Home Subscriber Server (HSS) operating on and interconnected with the public networks. Thus, employees making/receiving voice calls and data sessions can be roaming on cellular carrier networks, which will charge the enterprise based on their usage.
The voice gateway component in this embodiment of the invention comprises a hybrid gateway router, combining the traditional routing functionalities of a Wireless Gateway Mobile Switching Center (GMSC) with the admission control and routing functionalities of an IMS SIP Application Server proxy and/or H.323 gatekeeper in addition to functionality for call management and control in the enterprise space based on SIP and/or H.323.
All signaling is transported over IP instead of SS7 where possible using protocols, such as SIGTRAN. In cases where IP signaling is not available, SS7 may be required to connect with the public cellular and carrier networks. In addition, the invention supports functionality not traditionally associated with a Wireless GMSC. This includes support for 3GPP/2 SIP and/or H.323.
The present invention provides support for 3GPP/2 SIP, GSM MAP, CAP, ANSI-41/WIN and AIN protocols, converts between them and maps to individual SIP network elements in the enterprise network. Support for signaling is via SIGTRAN with high reliability over IP connections instead of traditional and expensive SS7 links.
Various embodiments of the invention provide technical advantages including:
Interconnection algorithms between carrier network telecom protocols and specific enterprise PBX services platforms, including enhancements to standard cellular network nodes including GMSC, SCP, GGSN:
Routing of dialed digits from carrier network to enterprise system without modifying carrier software, using existing intelligent network and/or IMS signaling and data messaging techniques.
Method for reducing/eliminating of PSTN interconnect charges between carrier and enterprise, enabling:
Methods for increasing enterprise-grade availability via a cellular interconnection gateway:
Enterprise MVNO Business framework
MVNO Infrastructure
Integrated Services Capabilities Framework
Intelligent Least cost routing techniques
Data Session Management
The present invention in one embodiment includes a software/server system that advantageously provides a cost effective and transparent means to connect enterprise employees' cellular phones to their corporation's PBX. The solution provides corporations with the ability to achieve, with regular single-mode mobile phones used by employees without requiring any special dialing sequences, the same PBX based benefits now provided for fixed office landline phones. The solution creates a multi-dimensional paradigm shift in the enterprise telecommunications market that is expected to change the way enterprises purchase and integrate cellular service with their PBX as well as the way carriers compete for all phone services to the enterprise.
The solution provides a unique product and business concept that is highly strategic for enterprise customers and channel distribution partners. Mobile operators have the opportunity to benefit from enterprises' need for operational control, efficiency and flexibility. The solution drives competitive advantage, higher market share and increased revenues for network operators by extending the cellular network and its call control into the enterprise.
One implication of moving the call control into the enterprise is that the invention enables the enterprise to control their communications—enabling the enterprise to track, monitor and even record voice conversations that occur on public carrier networks. The enterprise will be able to enforce policy-based call routing for employees making and receiving calls on public cellular networks. This means they can allow/prevent calls based on specific criteria such as destinations, time of day, external stimuli (e.g. active employee badge), other circumstances. As a result, corporations submitting to control-procedure legislations such as Sarbanes-Oxley will now have the ability to manage and control cellular communications in line with their landline (PBX) and data networks (e.g. e-mail traffic).
The gateway server transparently extends the cellular network directly to the PBX in the enterprise, ultimately enabling the enterprise to equally ‘plug’ cellular service into their PBX from a choice of providers, alongside their local and long distance landline service. In the enterprise, the server according to one aspect of the present invention is a mobility gateway that enables the enterprise to manage its own cellular services and costs as well as to deploy customized mobility solutions to bridge their internal business applications and processes with mobile devices. The architecture addresses the extension of the PBX control over both cellular voice and data systems, in addition to the current PBX control over land line voice. The approach of the present invention is a networking solution versus a device-centric solution, and does not require the enterprise to deploy and manage complex RF (radio frequency) components or purchase specialized mobile devices.
For the enterprise, the solution enables them to manage and control their cellular services & costs by routing all employees' cellular voice and data calls through their corporate PBX network, while simultaneously enabling them to deploy customized and secure mobility solutions integrated with their internal IT systems. For the mobile operator, the solution enables them to capture market share, grow revenues, reduce operational expenses and reduce churn in the highly profitable enterprise segment.
Referring now to
The gateway server:
The gateway server 10 leverages the benefits of Voice over IP with cellular to extend the cellular network into the enterprise. The gateway server 10 addresses both cellular voice and data, and is a networking solution that works together with the enterprise's existing PBX, performing mobile call control functions (routing and services).
Additionally, the gateway server 10:
The gateway server may be software-only solution that can execute on standard, inexpensive Linux platforms. The gateway server may consist of a mobile core network (for call handling and routing) and services network (voice and data services such as PBX-based short code dialing, voicemail, conference calling, VPN, etc.) components. It may be appropriately scaled down to the smaller subscriber base of a decentralized large enterprise, in the order of hundreds to several thousand subscribers, compared with carrier systems that manage many millions of “centralized” subscribers. The gateway server is designed to be managed and maintained by the same IT group that currently manages the enterprise's PBX system.
The gateway server in some aspects is a cellular system which does not require or include any radio frequency network components—which are highly complicated and expensive to deploy and manage. Campus radio networks, whether cellular, Wi-Fi or other, require highly skilled and dedicated resources to maintain and ensure network stability for the enterprise's critical voice and data communications, while simultaneously managing their spatial co-existence with live public carrier radio networks overlapping the enterprise campus.
Instead, the invention includes a method for combining the technology for enabling enterprises to integrate its call control and services with a proven business model (MVNOs) that further enables the enterprise to negotiate with carriers for a reasonable discounted price to use the carrier's professional nationwide cellular network. To the carrier, this maintains large numbers of high-value enterprise customers locked in on their networks, while reducing their costs of acquiring and maintaining individual subscribers.
One network architecture implementing an aspect of the present invention is shown in
The gateway server 10 includes the network functions for both voice (gateway MSC) and data (gateway GPRS Support Node or Home Agent), VoIP capability for interconnecting the mobile network with the enterprise thereby eliminating PSTN interconnect charges, a billing gateway, and a next-generation Network Services gateway (platform enabling third party value added services for the enterprise (e.g. mobile phone activation/de-activation, corporate directory integration) based on IMS (IP Multimedia Subsystem). It also includes the element management subsystem (EMS) and a service management subsystem (SMS) for the operational support system (OSS). The following Legend identified some of the terms used in
Configurations: The solution enables various configurations to be deployed.
The following description is based on
Current enterprise PBX systems are developed to be ‘enterprise grade’ in terms of their reliability and availability, compared with carrier network systems which are ‘carrier grade’ with failover solutions to prevent or minimize interruption of service. Enterprise PBX systems are by design not as reliable as carrier networks. With the gateway server solution of the present invention, overall system availability is increased as the gateway server intermediates between the carrier and enterprise networks. If the PBX goes down, the gateway server 10 can instruct the carrier to route calls on behalf of the enterprise until the PBX is back in service. In the event that the gateway server 10 should go out of service, the architecture of the invention is such that the carrier network will automatically take over the calls, with only nominal delays in routing (for example, a timeout event may occur in the MSC, after which the MSC will continue).
Many cellular carriers today allow free calling between subscribers on the same networks (e.g. Verizon to Verizon, T-Mobile to T-Mobile). This is partly because the call is maintained within the cellular carrier's own network, thus no PSTN (Public Switched Telephone Network) interconnect charges apply to the carrier. In addition, to call from a cellular phone on one carrier to a cellular phone on another carrier, or from a cellular phone to a landline phone requires the call be routed through the PSTN, thus incurring PSTN interconnect charges to the carrier.
One architecture of the present invention as shown in
Similarly, cellular calls from enterprise users to landline phones are also transitioned from the cellular network to the enterprise over VoIP, and are connected with the PSTN at the enterprise's PBX instead of being connected to the PSTN from the cellular network. Again, this reduces the cost for the cellular carrier to service enterprise calls.
For the enterprise, PSTN interconnect charges are included as part of the landline subscription. North American landline calling plans are typically ‘all-you-can-eat’, with no per-minute charges for local PSTN interconnection. In Europe and other parts of the world, landline calls are charged per time interval (e.g. per minute, or per 6-second interval), however at a substantially lower connection charge than for cellular calls.
The diagram of
One preferred call flow for Call origination is shown in
One preferred call flow for effecting Call Delivery using VoIP is shown in
One preferred call flow for effecting Mobile termination using VoIP is shown in
The invention enables a multi-dimensional paradigm change that has profound effects on the overall industry, as it will not only change how enterprises purchase and use cellular service—but will ultimately impact the entire value chain for wireless and wireline service providers and manufacturers.
The gateway server 10 architecture enables the migration of centralized call control from the cellular carrier networks to distributed call control throughout individual enterprise networks. The gateway server 10 enables cellular service to effectively be “plugged-in” to the PBX, similar to how local and long distance service are connected to current PBXs.
As a result of gateway server 10 capability, enterprises are equipped for carriers to compete for the enterprise's cellular PBX service as they do today for local and long distance interconnection with the PBX. By winning the business, carriers will benefit from locking in large numbers of users while significantly reducing its sales, marketing, and acquisition costs since service minutes will be sold bulk to the enterprise as a whole, no longer to individual employees. Though the invention has been described with respect to a specific preferred embodiment, many variations and modifications will become apparent to those skilled in the art upon reading the present application. It is therefore the intention that the appended claims be interpreted as broadly as possible in view of the prior art to include all such variations and modifications.
Advantages of the gateway architecture are shown in Table 2.
Existing platforms for detecting DTMF digit events fall into one of the following two categories:
Category I) Required to be a terminating end-point for a call session
Category II) Expensive hardware-based solution
Category I) solutions do not allow the call server to provide mid-call services during an active two party call session and therefore do not provide the necessary functionality. Category II) solutions provide the necessary functionality but are too expensive and increase the hardware footprint too much to be viable solutions.
One preferred embodiment of the invention includes a new mechanism whereby a VoIP call server can detect Dual Tone Multi Frequency (DTMF) digit events within the bearer stream of a VoIP call session. A call server is defined as being an intermediate node on the signaling path of a call (e.g. a routing proxy) rather than an endpoint such as an Interactive Voice Response (IVR) system. This embodiment of the invention allows the call server to cost effectively provide mid-call services to end clients based on DTMF digit events originated by a client.
This preferred embodiment of the invention, herein as the Packet Engine and shown in
The Packet Engine can be advantageously deployed on a separate hardware platform from the call server, on the same hardware platform, or even statically linked into the call server process itself in order to provide both flexibility and scalability. The Packet Engine supports control by multiple call servers in the network. Likewise, a single call server can control multiple Packet Engines providing for a many-to-many relationship.
In one preferred embodiment, the Packet Engine consists of two parts: a user space process as shown in
The second part of the Packet Engine, the kernel module, allows the Packet Engine to determine which packets being forwarded by the IP stack contain DTMF digits. The kernel module examines the headers of each RTP packet being forwarded and checks the Payload Type field. If the Payload Type field indicates the packet contains a DTMF event (encoded as per IETF RFC 2833) then the kernel module sends the packet up to the user space process for further application level processing. The kernel module advantageously operates as an extension (plugin) to the Linux kernel and therefore allows incoming packets to be examined in a highly efficient manner since the packet never leaves the kernel.
Once in the user space, the DTMF events are reported up to the call server in order to enable feature invocation. The Packet Engine can be supervised by the call server to only look for specific DTMF digit patterns and report them to the call server or it can be supervised to look for and report all DTMF digit events. The Packet Engine utilizes a buffer and an inter-digit timer to determine the start and stop of digit patterns (e.g. *97) in order to differentiate a feature invocation digit pattern from standard DTMF digits being sent to end client application such as an IVR.
The invention also advantageously provides a network-based architecture that enables the support for existing standard cellular handsets, without modifications or client software on the devices. Next generation specialized Wi-Fi and client-based handsets are also supported. By comparison, alternative solutions may require specific expensive specialized handsets with downloadable software clients that need to be managed by the enterprise IT department. The usability of these services is often not as intuitive and simple as using the standard phone capability for making calls, since the software is downloaded onto the device and subject to the device's capabilities and restrictions such as window screen size and soft & hard key programming. In addition, because the client is itself is an application running on the device, the client has to be activated, or ‘turned-on’ to run the application to integrate with the enterprise network. This means it may be possible that the employee chooses not to activate the feature, and thereby continue to make calls on the cellular network that are not tracked, managed, monitored or routed over the corporate network (for least cost routing) by the enterprise's PBX.
Because the described solution is network-based, the employee cannot circumvent the enterprise integration. At the discretion of the enterprise, employees may be permitted to use the cellular phone for personal use, for example on weekends or after work, by tracking these calls and charging them to the employee or deducting directly from their paycheck. The cost of the personal calls may still be at the corporate discounted rates which would thereby benefit the employee.
The gateway server 10 is based on the next generation IMS (IP Multimedia Subsystem) architecture as shown in
Current competing solutions are designed using legacy network architecture only, with no support for IMS. Effectively, the gateway server IMS solution adds modules for supporting ANSI-41/WIN and GSM-MAP/CAMEL and AIN protocols to achieve backward compatibility with legacy networks, as shown in
The invention also advantageously provides a network-based architecture that enables the support for existing standard cellular handsets, without modifications or client software on the devices. Next generation specialized Wi-Fi and client-based handsets are also supported. By comparison, alternative solutions may require specific expensive specialized handsets with downloadable software clients that need to be managed by the enterprise IT department. The usability of these services is often not as intuitive and simple as using the standard phone capability for making calls, since the software is downloaded onto the device and subject to the device's capabilities and restrictions such as window screen size and soft & hard key programming. In addition, because the client is itself is an application running on the device, the client has to be activated, or ‘turned-on’ to run the application to integrate with the enterprise network. This means it may be possible that the employee chooses not to activate the feature, and thereby continue to make calls on the cellular network that are not tracked, managed, monitored or routed over the corporate network (for least cost routing) by the enterprise's PBX.
Because the described solution is network-based, the employee cannot circumvent the enterprise integration. At the discretion of the enterprise, employees may be permitted to use the cellular phone for personal use, for example on weekends or after work, by tracking these calls and charging them to the employee or deducting directly from their paycheck. The cost of the personal calls may still be at the corporate discounted rates which would thereby benefit the employee.
The invention describes a system and method for executing originating services in a terminating IP Multimedia Subsystem (IMS) network in which a triggered application may or may not support IMS.
One of the benefits of such an invention is to enable an IMS network to interface with a non-IMS network. Another benefit is to enable an IMS network to interface with a second IMS network supporting a non-IMS application. A third benefit is that an originating IMS network need not have to support all originating services for the originator as the invention enables a second network to offer originating services for an originator in a first network.
A Gateway Server acting as an IMS standard-compliant SIP Application Server in a first IMS network can communicate with a corresponding GS in the terminating network to enable origination services to be executed in the terminating network even if the terminating network is not IMS-compliant. The GS-C is typically located in the wireless carrier network which may be IMS-compliant, while the GS-E is typically located in the enterprise network which may or may not be IMS-compliant. This application server in the enterprise could be a PBX which effectively serves subscribers in a manner similar to an IMS Serving-CSCF, however does not support IMS interfaces.
Irrespective of whether the terminating network is IMS-compliant or not, the described architecture in which a GS is acting as an IMS-compliant SIP-AS within the IMS network interfacing with a GS in another network enables this second network to offer origination services separately from the first network.
For this to occur, the session, when passed to the GS-C application server, is redirected into the terminating network, which could be an enterprise. This is performed by resetting the destination address to an enterprise specific address and instructing the wireless network route that session into the foreign domain of the enterprise network. GS-C may communicate with the GS-E directly outside the IMS network, or through the stand IMS network messaging.
To enable the execution of originating services within the terminating network, the GS solution enables the enterprise network to provide those services by passing the session to a PBX as if it were a request for originating services. Therefore two types of originating services can be executed—those in the wireless carrier network (the originating network) and those of the enterprise (the terminating network).
In a similar manner, termination services are executed in the terminating network. When a session is terminated to an enterprise user, the GS solution enables the PBX to execute its terminating services for that user, and then pass the session to the IMS network as a termination such that the terminating wireless carrier may also apply terminating services for the terminating mobile subscriber.
The S-CSCF then triggers on the IFC to one or many SIP-AS which perform the terminating services for User B (8)-(9) prior to terminating the session through the data gateway (11) to user B.
The FE may convert the terminating services request to an originating services request prior to communicating with the terminating service (11). This allows the terminating service to invoke services as if it were an originating node. For example, the PBX can perform originating services such as invoking call policy (restrict user A from dialing international) prior to routing the call.
Once the originating services are executed, the non-IMS application can then perform terminating services. For example, the PBX could invoke destination services for user B to route calls from user A to voicemail.
In the case where the terminating network application were IMS-compliant (e.g. an IMS-compliant PBX), the FE would convert the terminating services request to an originating services request prior to communicating with the IMS-compliant application (11), and once the originating service has been performed, the application would return control to the FE which would then invoke another service request back to the IMS-compliant application to perform terminating services.
System and Method for Enabling Multi-Line Mobile Telephone Service on a Single-Line Mobile Telephone
Another embodiment of the invention includes a system and method for enabling a multi-line mobile telephone service using a single-line mobile telephone. The embodiment of invention applies to various network architectures used in communications systems including legacy mobile network architecture based on SS7, GSM-MAP and/or ANSI-41, as well as the next generation IP Multimedia Subsystem (IMS) network architecture.
One of the benefits of this embodiment is enabling a subscriber to manipulate the outgoing caller identification information when originating a call, such that the called party will see the identity (including the phone number and name information) that was selected by the calling party.
An example of this embodiment of the usage of the invention might be a doctor whose patients are directed to call a special phone number to reach the doctor after hours. The doctor can set the special after-hours phone number to forward to their mobile phone using existing solutions that exist today. This way the doctor need not give out their personal mobile phone information. When a patient calls the special after-hours phone number, the call is forwarded to the doctor's mobile phone without revealing the doctor's mobile phone number to the patient.
However in the reverse case, this embodiment of the invention enables the doctor to call a patient from their mobile phone without revealing their mobile phone number. This is done by enabling the doctor to select a specific outgoing line from which to originate the call on their mobile phone. The patient will see the calling party identification information of the outgoing line selected by the doctor, which could be the special after-hours phone number, not be the doctor's mobile phone number.
The function of this embodiment of the invention is described below. This feature can operate in a legacy mobile network architecture such as GSM-MAP or ANSI-41, or in a next generation architecture such as IMS.
Prior to originating an outgoing call the calling party can identify the outgoing line information using various means such as:
Referring to
Once the trigger is received in the GS-C containing the digits dialed by the subscriber, the GS-C can then invoke the service whereby it can communicate with a Gateway Server Enterprise (GS-E) located in an enterprise. The GS-E can then originate an outgoing call to the intended destination using the outgoing line including the appropriate calling line information selected by the subscriber, and then connect that outgoing call leg to the originating call leg from the subscriber.
In the case of a per-call invocation of the multi-line service, subsequent calls made from the mobile phone would have the line selection default back to either a primary line, or to the last line selected in a previous call. For example, if a user's primary line is 212-814-4490, and they originate a call with digits *542-212-481-2813 indicating to use line 2 to call to destination 212-481-2813, then if the same subscriber subsequently dials another number such as 212-777-2222, this call would originate from either the primary line 212-814-4490 or from the previously selected line 2 from the previous per-call invocation of *542-212-481-2813. Thus the called party (212-777-2222) would see the calling party information as either the primary line 212-814-4490, or the previously per-call selected line 212-481-2813. The preference of whether subsequent calls should default back to the primary line or to the last line selected in a previous call can be defined by either the service provider, the system administrator or the user if permitted.
In the case of a permanent invocation of the multi-line service, all subsequent calls to the feature invocation (i.e. following the dialing of *542 indicating the selection of line 2), would continue to use line 2 until changed by the user, the system administrator or a function such as a timer or external application. For example, a calendar event could automatically reset a doctor's outgoing mobile phone line back to the daytime office number beginning each morning.
Additionally, a user may select a personality or profile based on various criteria (such as the user being at work, in a meeting, at home outside of work hours, etc.). The personality or profile can be selected manually or automatically set based on criteria such as whether the employee has badged into the office or has logged into their work computer, Time-of-Day or Day-of-Week information, or other criteria. The personality or profile would determine the outgoing line to be used—such as a personal line when after six in the evening, or when the user has badged out of the office or has logged out of their work computer. Additionally the personality or profile could determine which voicemail system to use, in addition to the customizing and tailoring of other services.
Referring now to
Note in some cases replacing the first set of digits (such as the area code digits) with the line information may be preferred instead of prefixing the line information to the full digits in order to preserve the display formatting on certain mobile phones. This is because certain mobile phones support only ten digits in the display, therefore if line information is prefixed to the digits, the ending digits would not appear in the display.
Incoming calls on various lines that are intended to be routed to the subscriber's mobile phone terminate at the GS-E. The GS-E identifies the destination mobile phone to which the incoming call should be routed based on various criteria such as time-of-day, day-of-week, permanent settings, or other user/administrator settings for determining call routing.
If the GS-C has the ability to originate outgoing calls then the GS-E orders the GS-C to originate a call to the subscriber's mobile phone with the calling name and number information of the calling party prefixed with supplementary information to indicate which line was called, and/or with a distinctive ring indicator. Once the outgoing leg is established, the GS-C connects the outgoing leg to the incoming call leg in the control of the GS-E.
If the GS-C does not have the ability to originate calls then the GS-E originates the outgoing call to the subscriber's mobile phone with the calling name and number information of the calling party prefixed with supplementary information to indicate which line was called, and/or with a distinctive ring indicator. Once the outgoing leg is established, the GS-E connects the outgoing leg to the incoming call leg.
Technical Advantages
1. Provisioning: The gateway server may also support a provisioning engine for provisioning the functions of the server itself, as well as provisioning external nodes including the enterprise PBX and the public carrier cellular network nodes. It may be possible that the gateway server provisioning engine (GSPE) front-end the entire PBX and be used to provision all data in the PBX. Alternatively the GSPE may be used to provision all functions in the PBX related to a cellular subscriber including their landline information, or it may be used to provision only the cellular portion of PBX subscriber information. In the cellular network, the GSPE may be used to provision the HLR/HSS of the carrier to modify existing service profiles for employees that are currently subscribers of the operator's network and are being transferred to the new service plan for enabling this service. The GSPE may also be used for provisioning new subscribers to the service that were previously not subscribers of that operator. The GSPE may also be used for provisioning other nodes in the cellular network such as a Foreign Agent, Home Agent, soft-switch, MSC, SGSN or GGSN. These functions would typically be provisioned with routing information used for enabling the service.
2. Method for speeding up call originations/terminations by using predictive techniques for routing half call, using intelligence to decide when to route calls to different devices based on presence, routes, TOD, distance. Calls routed to/from a subscriber of this service typically occurs in two stages, e.g. from the cellular network to the enterprise, and from the enterprise to the destination. Since the gateway server is notified in the first stage of the originator and the desired destination, it is possible for the GS to begin routing the second leg prior to the first leg's bearer being established. Using intelligence of the destination route combined with knowledge from past experience in the time it may take to route to a certain destination using a particular method or link, the GS may predict the moment at which it should begin routing the second leg of the call in anticipation of receiving the indication that the bearer for the first leg being established such that the two legs can be connected together with no delays. This technique can be used to minimize the chances that the second leg will be established and answered by the destination party before the first leg is setup. Conversely, this technique may minimize the wait of the originating party for the second leg to be established since the first leg need not be completely established to the enterprise before routing of the second leg is started. The GS may continuously update its information with intelligence about the routing times for specific destinations, and use this information in deciding the timing of setting up the call legs in order to minimize the end-to-end call establishment time.
3. Enterprise Call presence for mobile phones: Because the GS is located in the call path, the GS maintains knowledge of when a subscriber is active and available for calls, and also when a subscriber is currently in an active call. The GS can share this information with applications that may be used to, for example, indicate to other users that the subscriber is currently busy in a call. When the subscriber terminates the call, this information can be used to inform another user that the subscriber is available to receive a call. This presence information can also be provided to other presence servers that may be outside the enterprise site including with the carrier.
4. Enterprise HLR/HSS: The invention enables the distribution of HLR/HSS subscriber information among multiple sites within the enterprise. For example, the HLR/HSS information may be distributed according to the various PBXs in the enterprise network such that cellular information is stored at the site where the subscriber has a PBX subscription. The location of this information within the enterprise can be hidden from an outside entity such as the public carrier network such that an outside entity need not have to know where it is stored in order to access it. Any point of entry to the enterprise network may be able to locate the information of a particular subscriber.
5. Data—VPN-less session setup for enterprise. The invention enables a GGSN or HA to be including in the GS in the enterprise such that a secure data session can be established automatically between a device on the cellular network and the enterprise network by establishing a GTP tunnel between the carrier-hosted SGSN and the enterprise-hosted GGSN. In addition, in the case where there is a GS-C located in the carrier network that interfaces with GS-Es in the enterprise network, it is possible for the invention to add additional security and encryption specific to the enterprise's needs between the carrier's network and the enterprise. In this configuration, the function of the GGSN can be split between the GS-C and the GS-E such that the carrier network interfaces with the GS-C hosted within the carrier site, while the GTP tunnel and secure encrypted data session can be drawn out to the GS-E hosted within the enterprise. All data traffic to/from the mobile device will traverse the enterprise and its associated secure firewall. Billing for the wireless carrier can be supported within the carrier's network via charging records being generated from the GS-C. Enterprise charging records can equally be generated within the enterprise from the GS-E in order to enable the enterprise to keep track of usage and be able to compare with service bills from the carrier received at the end of a billing cycle.
6. Alternative methods for handling call originations: Using SMS and Hotline for call originations: Alternative solutions can be used in place of Intelligent Network triggers such as WIN or CAMEL for communicating with an SCP function in the enterprise. One technique is to use a method such as Short Message Service (SMS) to send the origination information from a mobile to an application server in the enterprise, and then to enable a “hotline” feature in the subscriber profile that forces the mobile to route to a specified destination no matter what is dialed. The hotline feature is often used to route to customer service when a new phone is being setup. In this case the hotline feature would route all calls to a destination that would ultimately route into the enterprise network, either using VoIP or PSTN. By sending the origination information including the originating subscriber number and the destination digits to the application server in advance of the hotline call, this information can be used to identify the incoming hotline call, and re-route it to the desired destination. In order to be able to use SMS in this manner, it may be required to have a special client on the device that captures the digits and sends them in an SMS to a specific server. Alternatively this functionality could be built into the device natively thus not requiring a software client. Note in this case that the destination SMSC may also be the GS instead of the carrier's SMSC since it is important that this information be delivered in real time, and not delayed through store-and-forward in the carrier's SMSC. Otherwise the routing of the call could be delayed. An alternative routing method does not require the hotline feature to be activated. Instead, when the SMS message is received at the application server, the application server can originate calls to the destination and to the originator's device. The originator would answer the phone and be connected with the second leg. If a client is on the device, the client may automatically answer the incoming call from the application server without ringing so as to appear as if the call was established by the originator's device when the SMS was sent. Other methods other than SMS for delivering the origination message may be used such as over-the-air messages and/or Unstructured Supplementary Service Data (USSD). Another alternative provides that originating calls are routed based on the subscriber profile to specific routes or trunk groups within the MSC. The destination routes to the GS which captures the original calling and called party information. The GS can analyze the routes and re-route the call accordingly, for example into the enterprise using VoIP. This solution also enables the GS to manipulate call legs to be able to perform handovers (or handoffs) between, for example, a wi-fi network and a cellular network by enabling the GS to establish a new call leg for a call in progress and join or switch the failing call leg to the new leg. Similarly this kind of call leg manipulation can be used to maintain or reconnect a call that has been lost—for example if a subscriber enters a tunnel where there is no cellular coverage and therefore the call leg is lost, the GS can decide to maintain the other call leg up and potentially treat the leg by playing a message to inform the party that the call is being reconnected. The GS can then proceed to re-establish the call leg by establishing an outbound call to the device once they exit the tunnel, or having the device originate a call back to the GS if the device has a software client—and then the GS can reconnect the legs together, or the user manually originates a call back to the GS.
7. The combining of cellular nodal functions in a single functional entity: GMSC, GGSN, SCP, IMS SIP Application Server, Call Server. The invention combines the functionality of multiple cellular network nodes into a single entity that is scaled down to support in the order of thousands of subscribers compared with individual cellular nodes supporting millions of subscribers. The invention supports a GMSC for enabling call originations to an enterprise number to be redirected to a cellular phone number and routed using least cost routing techniques whereby the GS discovers the location of the terminating subscriber and can route the call to that serving MSC over alternate routes such as a public or private VoIP network. This reduces or eliminates transport costs to the public carrier since the call is routed over lower cost routes using VoIP, or completely outside the carrier's network. The interconnection to the carrier's network can be using VoIP which avoids any PSTN interconnect charges. The SCP function enables originating and terminating calls to be routed according to instructions from the enterprise in the GS which interacts with the enterprise PBX system. Similarly this is achieved with the IMS SIP Application server function in the case of an IMS network architecture. The Call Server enables the carrier to route calls to and from their network using a distributed soft-switch and media gateway architecture that enables the bearer to be transmitted over VoIP instead of traditional trunks. Thus the carrier can route calls into and out of the enterprise over VoIP thereby avoiding PSTN interconnection and associated charges. The GGSN function onboard the GS enables the enterprise to route data sessions in a similar manner to how the invention describes the routing of voice calls. By including a GGSN function within the enterprise and connected with the cellular carrier's SGSN, a secure tunnel can be established between the carrier and the enterprise networks. Similarly this can be achieved with a Home Agent function located within the enterprise and connected with the carrier's Foreign Agent for CDMA networks. As such, the invention:
8. Least cost routing for mobile originations to bypass long distance in control of enterprise: The invention describes how to bypass long distance for cellular subscribers for both international and national long distance, by routing the calls from the serving MSC into the closest point of entry into the enterprise network. This connection can be using traditional trunks which incur costs but is reduced since the call may be routed from the serving MSC to a local point of attachment to the enterprise network, or the connection can be using VoIP from the carrier network to the enterprise, which avoids any PSTN interconnect charges and also enables the call to be considered a local call even if the closest point of attachment is not local—the cost is according to VoIP tariffing which may include free nationwide as well as to Canada, western Europe and parts of Latin America. The invention also describes the concept of Tail-End-Hop-Off (TEHO). TEHO enables an employee dialing long distance to route the call as far as possible via least cost routing, and route the last leg from the least expensive point. For example, if an employee in the US dials a local telephone number in London, UK, the GS could detect this and decide to route the call from the US to the corporation's office in London, and from there initiate a local call to the destination. The invention would then enable all the legs of the call to be connected together. The end-to-end call would be routed from the originator in the cellular network into the enterprise network via a local connection, across the corporation's least cost routing (possibly VoIP) network to the London office, and connected with the local call from the London office to the final destination. The invention also stipulates that TEHO could be disallowed based on various criteria, such as destination (e.g. if such a solution were not allowed for connecting to certain countries), Time of Day/Day of Week or other criteria such as subscriber profile or policies.
9. PBX feature transparency: The invention describes how to enable PBX services from a desk phone be executed on a standard cellular phone with no special clients. The GS is configurable specific to the enterprise. Therefore the feature codes used on a deskphone in a particular enterprise can be programmed to be the same or similar on the cellular phone. The GS enables the use of “7” or “9” to be dialed in order to get an outside line, just like on a PBX. On the cellular phone, the employee would dial 9 followed by the destination digits, followed by the TALK button. If the employee dials destination digits without a “7” or “9”, the GS would consider them as internal PBX digits, such as a local 4 or 5-digit extension, or a 7-digit internal network destination. It is possible for the GS to suppress the use of “7” or “9” when using a cellular phone. The GS would analyze if the digits are internal or external and route accordingly. For example if the user dialed only 4 digits, the GS would treat as an internal extension. If the user dialed 10 digits, the GS would analyze the digits and if not associated with an internal extension, would consider it an external call and add the “7” or “9” prior to routing to the PBX. By enabling the suppression of the “7” or “9” for an outside line, the invention enables the employee to use the phone numbers stored in their device as they are—without modification. An employee can select a person's name and which number they wish to connect with (office, home, cellular) in their directory in the phone and dial, and the GS will determine automatically if it is an external or internal number, and route accordingly. Advanced PBX features such as Call Forward, Call Park, Call Pickup, Conference, Transfer, Do Not Disturb, Exclusive Hold, Consultative Hold, Last Number Redial, Link, Page, etc. that are available on the deskphone by pressing a “Feature” button followed by a code (e.g. Feature 74 to invoke Call Park, or Feature 85 to invoke Do Not Disturb), can be executed in a similar manner on the cellular phone by pressing an alternative button to “Feature” such as “*” or “#” followed by the same feature code. This is completely configurable and can be changed to suit the desire of the end user. If the user cannot recall what codes to use, the invention describes that the user can press a code such as “**”, “##” or “4HELP” (44357) which would connect the user with an Interactive Voice Response System (IVR). The IVR would prompt the user with information such as “Press *74 for Call Park, Press *85 for Do Not Disturb”. The user could enter the digits at anytime and the feature would be invoked. If the user remembers the code, they can avoid using the IVR on subsequent feature invocations. The invention describes the invocation of features at the beginning of a call, and during a call. Mid-call triggers can be used by the system to inform the GS. For example if a user wishes to bridge in a third party, they could press TALK followed by the destination digits followed by TALK. A cellular system supporting mid-call triggers would send this information to the GS which would originate a call to the third party from the PBX, bridge the third part at the PBX, and enable the single voice path back to the cellular switch. The GS would respond to the midcall trigger with a message indicating to continue the call as normal. The result is that the original two parties would be connected with the third party through the PBX, and not through the cellular MSC—only a single voice path connection from the cellular MSC is required back to the PBX. Using the same concept, it is possible to link in multiple parties into a large conference call using the PBX and conference bridges in the enterprise, and only a single voice path connection to the cellular user. If the cellular system does not support mid-call triggers, DTMF tones can be collected on the voice path using a code receiver placed in the voice path typically onboard a media gateway or subscribing to a media gateway for tone detection service. If a code receiver is used, it could be located in the enterprise, or at the carrier. As such, the user would not press the TALK button. Instead they would invoke features while in a call by pressing a designated code such as “*”, “#”, or alternatively “**” or “##” to invoke the IVR system to assist the user in invoking the services.
10. Monitoring and controlling of calls (voice and data) from enterprise mobiles. The invention previously described how all voice calls and data sessions from the cellular network are routed through the enterprise, enabling the enterprise to control, manage, subject to policy and even record the bearer information. The implications of this invention are consistent with what are considered “best practices” among corporations that must comply with regulations such as Sarbanes-Oxley for control procedures, similar to how corporations manage and control e-mail traffic or PBX voice communications that can be tracked and recorded. While the invention enables an enterprise to gain control of voice and data calls, the design of invention also continues to enable federal legal requirements for monitoring calls on public cellular networks in compliance with regulations such as CALEA. Because the invention routes all calls through the serving MSC before they are routed to the enterprise, the serving MSC can still invoke wiretapping in accordance with federal law. Similarly the invention design fully supports emergency call handling in that a subscriber that dials 911 will have the call immediately routed in accordance with emergency call handing procedures via the serving MSC which will override any triggers to route the call to the enterprise. As the invention uses standard cellular handsets, there E-911 location features operate as designed. Thus the architecture of the invention fully complies with emergency call handling regulations.
11. Identity manipulation for outgoing and incoming calls: The invention enables either the enterprise PBX landline phone number or the cellular phone number to be used as the single number. If the landline is used as primary and if the cellular number is called, the call can be allowed, or the call can be diverted to a voice recording that states the landline number to call. The call can then be routed, or it can hang up and require the originator to re-dial the new digits. Similarly this can be done with the cellular number as primary. If the landline is primary and the user originates a call from their cellular phone, the GS can manipulate the outgoing callerid information to be the landline number instead of the cellular number. If the terminator decides to call back the originator, they can select the callerid which will be the landline number. Similarly this can be done with the cellular number as the primary. SMS message originations from the mobile user are triggered to the GS which converts the originator's cellular phone number to the landline number. The SMS can then be redirected back to the MSC for sending to the SMSC, or the GS can instruct the MSC to cancel the message, after which the GS originates a new SMS directly to the SMSC containing the landline origination number and the original destination. Similarly when an SMS is sent to a subscriber using their landline number, the MSC will trigger to the GS based on the terminating number. The GS will convert the destination number from the landline to the cellular number and return it to the MSC for routing to the subscriber or SMSC. In this case it may be required that the HLR be provisioned with a subscriber profile for the landline number to trigger to the GS. In the case where the GS also contains an SMSC on the SS7 network, the originating MSC would route the SMS to the GS-SMSC which would in turn convert the landline number to the cellular number and originate a new SMS to the cellular network for termination.
12. Enhanced services
13. Billing
14. IMS-Legacy Interaction
15. Configurations: The solution enables various configurations to be deployed.
16. Availability: PBX systems are by nature designed to be enterprise-grade, which implies they may go out of service more frequently than carrier systems which must comply with strict minimum downtime requirements. The architecture of the invention increases the effective availability of a PBX system for routing calls since the GS (GS-E or GS-C) can instruct the cellular network to route the call (with same or modified dialing instructions) in the event that the PBX has gone out of service. The GS can store the call information and report it to the PBX when it is back online. In the event that the GS should go out of service, the architecture of the invention enables the cellular network to be configured such that if its communication with the GS times out, the cellular network can take alternate action, for example to route the call on its own, send to treatment (e.g. play a message), redirect to an alternative GS, or other call handling.
17. MVNO infrastructure: The invention is effectively a wireless core network that could alternatively be packaged and sold to MVNOs to enable them to operate their own core networks and host their own advanced services, while connecting to public cellular carrier networks for radio access.
18. Call Leg Manipulation and handling—In addition to using originating and terminating triggers to transfer call control from the carrier network to the enterprise via the GS, the solution also enables advanced services to be executed mid-call using mid-call triggers or in-line code receivers. When a user wishes to invoke a mid-call service such to invoke a multi-party call using an external conference bridge that resides in the enterprise network, the user can press digits on the device to invoke the service, and then press the TALK or SEND button to invoke a flash. The flash message is sent to the GS using mid-call triggers with the information of what was dialed. The GS can then respond to proceed with the call as normal, so that the voice conversation can continue, and then the GS can invoke the service, in this case to bridge in other users to the call, from the enterprise side. Thus for a multi-party call, only one voice leg is required from the user to the enterprise. Alternatively to the use of mid-call triggers, the solution can use an code receiver in the line that captures DTMF tones throughout the call. In this case the user could press a series of digits followed by, for example, # (instead of TALK or SEND). The code receiver or media gateway can then send a message to the GS to perform the service. In this case there is no interruption in the voice session. In this case the media gateway can block the transmission of the tones to other parties on the call such that the other parties will not hear them as they are being pressed. This section is in addition to what is described in section “Alternative methods for handling call originations”.
19. Corporate Calling Name: Calling name display is based on the carrier network database. This information does not contain calling name information for internal enterprise numbers. The invention enables the redirection of the GR-1188 or IS41 based query in the terminating switch to point to the GS. The GS will access the calling name information from the corporate directory. The GS can also obtain calling name information from a carrier database or other source, and decide which information (or both) to provide to the terminator depending on various factors such as completeness, originator's preferences, etc.
20. IMS Handover/Handoff: The invention enables handoff to occur between a voice conversation on a Wi-Fi network and a cellular network. Signaling between the Wi-Fi network and the cellular network is transited through the GS which converts the messaging between SIP call leg manipulation and ANSI-41 or GSM cellular signaling protocols for invoking a handoff. The solution can support the equivalent of an inter-MSC handoff as is done today in the cellular network, or alternatively a Call Redirection pseudo handoff in which a through-connected call is redirected. The latter uses messages such as SIP JOIN to connect the calls. In the case where the cellular network supports IMS, the GS acts as a SIP AS to perform the application function, and can also act as a peer IMS network including P-CSCF, I-CSCF and S-CSCF. In this case, the GS acting in these functions enables the PBX or IP-PBX that is controlling the user in Wi-Fi mode to be abstracted from having to support IMS to the cellular network, as the PBX/IP-PBX interfaces with the GS which interfaces with the IMS network.
Data—VPN-less session setup for enterprise. The invention enables a GGSN or HA to be including in the GS in the enterprise such that a secure data session can be established automatically between a device on the cellular network and the enterprise network by establishing a GTP tunnel between the carrier-hosted SGSN and the enterprise-hosted GGSN. In addition, in the case where there is a GS-C located in the carrier network that interfaces with GS-Es in the enterprise network, it is possible for the invention to add additional security and encryption specific to the enterprise's needs between the carrier's network and the enterprise. In this configuration, the function of the GGSN can be split between the GS-C and the GS-E such that the carrier network interfaces with the GS-C hosted within the carrier site, while the GTP tunnel and secure encrypted data session can be drawn out to the GS-E hosted within the enterprise. All data traffic to/from the mobile device will traverse the enterprise and its associated secure firewall.
This application is a continuation of U.S. Ser. No. 12/961,834, entitled “ALL FLOW SYSTEM AND METHOD FOR USE IN A VOIP TELECOMMUNICATION SYSTEM” filed Dec. 7, 2010, now issued U.S. Pat. No. 8,488,598 issued on Jul. 16, 2013, which is a continuation of U.S. Ser. No. 11/509,260, entitled “CALL FLOW SYSTEM AND METHO USE IN VOIP TELECOMMUNICATION SYSTEM” filed Aug. 24, 2006. Now issued U.S. Pat. No. 7,873,032 issued on Jan. 18, 2011; which claims priority of U.S. Provisional Ser. No. 60/778,252, entitled “MOBILE APPLICATION GATEWAY FOR CONNECTING DEVICES ON A CELLULAR NETWORK WITH INDIVIDUAL ENTERPRISE AND DATA NETWORKS” filed Mar. 2, 2006; U.S. Provisional Ser. No. 60/778,276, entitled “CALL FLOW SYSTEM AND METHOD USE IN LEGACY TELECOMMUNICATION SYSTEM” filed Mar. 2, 2006; U.S. Provisional Ser. No. 60/778,443, entitled “CALL FLOW SYSTEM AND METHOD USE IN VOIP TELECOMMUNICATION SYSTEM” filed Mar. 2, 2006; and U.S. Provisional Ser. No. 60/797,724, entitled “SYSTEM AND METHOD FOR EXECUTING ORIGINATING SERVICES IN A TERMINATING NETWORK FOR IMS AND NON-IMS APPLICATIONS” filed May 4, 2006 incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| 60797724 | May 2006 | US | |
| 60778276 | Mar 2006 | US | |
| 60778443 | Mar 2006 | US | |
| 60778252 | Mar 2006 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12961834 | Dec 2010 | US |
| Child | 13938797 | US | |
| Parent | 11509260 | Aug 2006 | US |
| Child | 12961834 | US |
