WO2009137882A1

WO2009137882A1 - Internet telephone network and mobile telephone network integration

Info

Publication number: WO2009137882A1
Application number: PCT/AU2009/000605
Authority: WO
Inventors: Michael Carew; John P Mcmullan; Daniel Trembath
Original assignee: Freshtel R & D Pty Ltd
Priority date: 2008-05-14
Filing date: 2009-05-14
Publication date: 2009-11-19

Abstract

A method of providing telecommunications through a Mobile Internet Phone Virtual Network Enabler (MIPVNE) application to a Mobile Internet Phone Virtual Network Operator (MIPVNO) is described which enables subscribers to the MIPVNO to have access to an IP network and a mobile communications network. The method comprises providing Internet Phone Virtual Network Enabler (IPVNE) services for use by the MIPVNE application and further providing Mobile Virtual Network Enabler (MVNE) services for use by the MIPVNE application. The method is operable such that seamless connection is made over the IP network or the mobile communications network when a subscriber initiates a call or data session

Description

"Internet telephone network and mobile telephone network integration"

Cross-Reference to Related Applications

The present application claims priority from Australian Provisional Patent Application No 2008902364 filed on 14 May 2008, the content of which is incorporated herein by reference.

Field of the Invention

This invention relates to a method and system for integrating a mobile virtual telephone network with an internet telephone virtual network. More particularly, it relates to a method and system that allows virtual telephone network operators to offer mobile telecommunication services and internet telephone services to customers as a single integrated service.

Background of the Invention

With more and more telecommunication customers using the internet for communications, including voice and data communications, as well as using mobile telecommunications, there is a need to provide such customers and operators of telecommunications networks the choice of using either mobile telecommunications or internet telephone communications dependent on geography, cost or other requirements. Virtual network operators are now creating branded telecommunication services for their customers, such as organisations that are in the business of customer service. Mobile virtual network operators (MVNO) provide re-branded consumer mobile telecommunication services that are provided through a retail offering. Such MVNOs do not have wireless telecommunication networks over which to operate. Instead the MVNOs rely on mobile network operators (MNO) to provide underlying equipment and communication infrastructure that interface the MVNO systems with the systems of the mobile network operators. Thus, each MVNO offers a wireless service under a different brand. The MNOs control and own the infrastructure and service operation which may or may not be utilised by an MVNO. MVNOs need to provide subscriber interfaces and technology for customer management, administration management and billing management. These requirements are provided by an MVNE (Mobile Virtual Network Enabler).

The MVNE deploys and manages a consumer mobile telecommunication offering by leveraging infrastructure and systems that are provided by an MNO or a telecommunications operator as a re-branded consumer mobile offering. Also, existing to a lesser extent are internet phone virtual network operators (IPVNO) that is a re-branded consumer VoIP telecommunications solution provided through a retail offering by an internet phone virtual network enabler (IPVNE). The IPVNE deploys and manages a consumer VoIP offering by leveraging infrastructure in the systems provided by an internet phone network operator (IPNO) or other telecommunications operator as a re-branded consumer VoIP solution. The IPNO controls and owns the infrastructure and service operation which may or may not be utilised by the IPVNO in order to deliver a consumer VoIP offering.

The IPVNOs offer a branded internet phone service but do not actually have the telecommunication infrastructure for operating over the internet. Instead, the IPVNOs rely on IPNOs to provide the underlying equipment and communication services to interface their systems with the systems of the IPNO. This is assisted through the IPVNE which acts as an intermediary between the branded system of the IPVNO and the IPNO. Thus the IPVNOs are able to provide customer systems and management, administrative systems and management and billing systems and management through the IPVNE.

However, with the convergence of internet phones and mobile phones, such as phones that provide WiFi access, there is a need to provide a system to enable seamless use of either the internet or the mobile network through the one handset. It is known that a telecommunications carrier has used Unlicensed Mobile

Access (UMA) to enable better telecommunication coverage, for example, at the home of a customer. This was done to prevent churning, where a customer is dissatisfied with one telecommunications carrier and subscribes to another telecommunications carrier because there has been poor network coverage at, for example, a home location of the user. UMA enables a handset having WiFi capability to connect to a local WiFi hotspot which is provided through a GSM network of the same carrier. Thus, where, for example, the GSM mobile coverage is unsatisfactory the user will be able to connect to the internet through the WiFi hotspot and when the GSM coverage is satisfactory in a particular region would be able to switch back to the GSM network through the same carrier. Incentives have been provided to customers to prevent churning by making the WiFi connectability more attractive to customers, for example, by providing more connection time on the WiFi network.

A particular problem with this scenario is that the mobile network and the internet phone network are owned and managed by a particular mobile carrier. Thus, each user has to subscribe to both networks to obtain the benefits of those networks. This restricts the choice or availability to different and preferably cheaper rates that can be provided through IPVNOs and MVNOs.

Another problem with the carriers that are using UMA is that the handsets are often tied in to or manufactured by companies that own the specific IP and mobile networks.

Thus, with handsets that have WiFi with VoIP capability the present invention makes it possible to use such handsets and subscribe to virtual network operators that use the equipment and services provided by mobile network operators and IP network operators. Further problems with existing arrangements is that there is no back end and front end support for virtual network operators that attempt to provide internet phone and mobile phone capabilities on the one handset. This is provided specifically for individual IPVNOs and specifically for individual MVNOs but not together such that back end support is provided in terms of business support systems and operation supports systems such as billing, rating, least cost routing and customer care management all in the one system. Thus, it enables such virtual network operators to offer to their customers the use of internet phone communications or mobile phone communications and has support for the back end functions that are necessary in such an offering or system to consumers. Any discussion of documents, acts, materials, devices, articles or the like which has been included in the present specification is solely for the purpose of providing a context for the present invention. It is not to be taken as an admission that any or all of these matters form part of the prior art base or were common general knowledge in the field relevant to the present invention as it existed before the priority date of each claim of this application.

Throughout this specification the word "comprise", or variations such as "comprises" or "comprising", will be understood to imply the inclusion of a stated element, integer or step, or group of elements, integers or steps, but not the exclusion of any other element, integer or step, or group of elements, integers or steps.

Summary of the Invention

According to a first aspect of the invention there is provided a method of providing telecommunications, through a MIPVNE application, to an MIPVNO to selectively enable subscribers to the MIPVNO to have access to an IP network or a mobile communications network comprising: providing IPVNE services for use by the MIPVNE application; providing MVNE services for use by the MIPVNE application; such that seamless connection is made over the IP network or the mobile communications network when a subscriber initiates a call or data session.

Preferably the MIPVNE application interfaces to the IPVNE and the MVNE through the Simple Object Access Protocol (SOAP) or a Web Service contract interface. The MIPVNE application preferably contains exposed services of the IPVNE and exposed services of the MVNE.

The MIPVNE application may further contain application specific services, such as device management service, process management service, additional subscriber data service, least cost routing service, service access management service, service delivery manager service, network selection manager service and account closure service. Each of the application specific services and the exposed services contained in the MIPVNE are accessible through the SOAP interface. The IPVNE and MVNE exposed services and the MIPVNE application specific services register with a SOAP end point where synchronous and asynchronous messages can trigger requests for such exposed services. The service requests and application delivery to and from a subscriber handset may be performed through Workflow, and preferably through PNML or BPEL.

The exposed services are preferably performed using the Parlay X Web

Services. The MIPVNE application is preferably used by a plurality of MIPVNOs, with the MIPVNE services specifically catering for each MIPVNO.

Access to the internet is available through a Wi-Fi hotspot, which can be provided through a Wireless Access System.

According to a second aspect of the invention there is provided an MIPVNE application for providing telecommunication services to an MIPVNO to selectively enable subscribers to the MIPVNO to have access to an IP network or a mobile communications network using a single mobile handset, the MIPVNE application comprising:

IPVNE services available in connection with use of the IP network by the subscribers;

MVNE services available in connection with use of the mobile communications network by the subscribers; such that seamless connection is selectively made over the IP network or the mobile communications network using the respective IPVNE services or the MVNE services when a subscriber initiates a call or data session. The MIPVNE application may further comprise a Workflow application, an interface, preferably SOAP, for interfacing to the MVNE and the IPVNE, and an Enterprise Messaging System.

According to a third aspect there is provided a system of providing telecommunications to subscribers over an IP network and a mobile communications network using a single mobile handset comprising: an MIPVNE linked to each of an MVNE and an IPVNE for accessing MVNE services and IPVNE services respectively; an MIPVNO linked to the MIPVNE, the MIPVNO linked to the internet and to a mobile communications network ; wherein the system is selectively operable to enable subscribers to communicate over the IP network through the MIPVNO using the IPVNE services or the mobile communications network through the MIPVNO using the MVNE services.

Brief Description of the Drawings

A preferred embodiment of the invention will hereinafter be described, by way of example only, with reference to the drawings in which:

Figure 1 is a block diagram of a system that enables communication over the internet or a mobile communications network; Figure 2 is a block diagram of the system of Figure 1 together with its interconnection to the internet and the mobile communications network;

Figure 3 is a more detailed block diagram of the components of the system of Figure 1;

Figure 4 shows the IPVNO and IPVNE services/applications; Figure 5 shows the MVNO and MVNE services/applications;

Figure 6 shows the MIPVNO and MIPVNE services/applications; and Figure 7 shows the services/applications of an MNO and examples of IPNOs such as an Operator and a Wireless Access Service Provider.

Detailed Description of the Preferred Embodiments

Referring to Fig 1 there is shown a system 100 that enables a virtual network operator to provide seamlessly integrated internet phone and mobile phone communications to its customers. A mobile internet phone virtual network enabler (MIPVNE) 105 is an application that is intermediate and in communication with a IPVNE 110 and a MVNE 115 through a SOAP interface 120. The MIPVNE 105 deploys and manages a converged mobile and VoIP offering through leveraging infrastructure and systems that are provided by a IPNO, MNO or a TO as a re-branded converged mobile and VoIP solution. Primarily but not exclusively the application allows the use of VoIP technology on mobile GSM telephone handsets. The MIPVNE 105 is also linked to a mobile internet phone virtual network operator (MIPVNO) 150 which is a re-branded converged mobile and VoIP solution that is provided through a retail offering by the MIPVNE 105. This service also allows the use of VoIP on mobile GSM handsets but is not necessarily limited to these types of handsets.

The MVNE 115 is linked the MVNO 140 and also the MNO 145. Similarly, the IPVNE 110 is linked to IPVNO 125 and also to a IPNO 155. The IPNO 155 can also be an operator (of telephony systems) 130, or a Wireless Access Service Provider (WASP) 135. A WASP can be, for example, a public WiFi hotspot provider, for example, any retail chain. After verification the user signs on, for example, by supplying a user name and password and uses a laptop or PDA to logon to the internet through that hotspot provider. Referring to the block diagram 200 of Fig 2 there is shown the various virtual network operators connected to either the internet 210 or a mobile network 220 or connected to both as is the case with the MIPVNO 150. Thus, each of the MVNO 140, MVNE 115 and MNO 145 are connected to mobile network 220. The IPVNO 125, IPVNE 110, IPNO 155 (or WASP 135 and network operator 130) are connected respectively to the internet 210. As with Fig 1 the IPVNE 110 and the MVNE 115 are connected to the MIPVNE application 105. The MIPVNO 150 uses the functionality of the MIPVNE 105 in order to provide its customers with connection either over the internet using VoIP or over a mobile network 220. In order for the MIPVNE 105 to provide this functionality it uses exposed services from each of the IPVNE 110 and the MVNE 115.

Although Figs 1 and 2 depict a single MIPVNO 150 the system 100 can have many MIPVNOs that use the same MIPVNE application 105. Thus, as many brand offerings that are available to use the MIPVNE 105 can be provided for. Thus, as an example it is a one-to-many provision of the MIPVNE services to as many wholesale providers as required. A combined retail offering is given whereby the MIPVNOs use the system and services such as one single billing application, least cost routing, ledger management and network intelligence across the IP network and the mobile network.

With reference to Fig 3 there is shown a block diagram 300 showing the various applications and systems in block form of each of the systems shown in Fig 1. Fig 3 is divided into three business units specifically customer systems, application systems and service providers. The MIPVNE 105 consists of the core components of Workflow 302, services 304 and MIPVNE systems 306. It also includes IPVNE exposed services 308 and MVNE exposed services 310. Each of the components of Workflow 302, services 304 and MIPVNE systems 306 communicate with the IPVNE 110 and the MVNE 115 through the SOAP interface 120. The MVNE exposed services 310 communicates with the MVNE 115 through the Enterprise Messaging System (EMS) 312. Similarly, the IPVNE exposed services 308 communicates with the IPVNE 110 through the EMS 312. The application 105 contains elements or systems and services that are delivered from each of the IPVNE 110 and the MVNE 115. These components are identified to operate the MIPVNE system successfully and are required to be exposed services that are accessible via the EMS 312. Thus, the services required from IPVNE 110 are present in the exposed services 308 and those that are required from the MVNE 115 are grouped together as exposed services 310. Thus, exposed services for the IPVNE 308 will be exposed to and accessible by a MIPVNO 150. Similarly, the MVNE exposed services 310 derived from the MVNE systems 115 will be accessible to the MIPVNO 150. It is to be noted that the IPVNE services 308 will be exposed to the MVNE 115/MNO 145 in order to accommodate IPVNO implementations that may not require full MIPVNO capability. These IPVNO implementations can be upgraded to deliver a converged mobile solution.

Each of the IPVNO 125, MIPVNO 150 and MVNO 140 have business support systems (BSS) and operational support systems (OSS). Additionally, the MVNE 115 has BSS and OSS. The MVNE 115 also has Workflow application 330 which is the same application as what the IPVNE application 105 uses. Essentially, the Workflow application uses Process Notation Markup Language (PNML) or alternatively BPEL (Business Process Extension Language). This software uses internet remote web server based architecture in the mobile environment in order to perform real time application delivery to the handset to perform certain functions like least cost routing (LCR) and real time rating. The MVNE 115 also uses the intelligent network 332 which includes a number of resources which will be described hereinafter.

The IPVNE architecture 110 has customer systems 334, administration systems 336 and billing systems 338. The IPNO 155 utilises a telecommunications network architecture 340 and application business logic 342. Alternatively the operator 130 uses telephony operator systems 344 whilst the wireless access module 135 utilises wireless access systems 346. Finally, the MNO 145 utilises MNO systems 348 to be hereinafter described. The exposed services 308 and 310 mentioned previously are essentially Parlay

X Web Services. This is a cut down or reduced version of Parlay which are standards that allow telecommunication providers to develop to and integrate with those standards. For example, implementing SMS, call rating and other telecommunication applications use Parlay. The cut down version or Parlay X Web Services are used by most telecommunication providers and therefore compatibility exists across most of those providers. Thus, the exposed services are essentially web based data services which use Parlay X web services that are a contract of functions requiring authentication. Thus, telecommunication operators would subscribe to such authentication and as an example the MIPVNO would be able to access call detail records (CDR) of a particular customer. This may be then returned in a data array of results. For example, the details on twelve calls by that customer may be returned and then this is stored in the EMS of the MIPVNE. This is transmitted over the SOAP 120. The MVNE 115 would expose end points, that is, turn on the Parlay X web service, for example, for call rating in real time. Thus, it would ascertain how much one particular call is costing per minute, what the charge is, whether there is multiple time billing, whether there is a start charge (or flag fall) and determine if there are different charging rates at different times of the day or week. As an example, a customer may dial the first four digits, then the MIPVNE 105 will know the prefix and from the MIPVNE 105 it would be possible to determine the cheapest route over which to send that call and over which network. The MIPVNE 105 determines this and transmits this information to the handset so that the handset can call over the indicated network at the cheapest rate. On the display of the mobile handset an indication of the charge for a particular call may be given to the subscriber.

The MVNE 115 will have a full contract, that is a web service contract, that aggregates specific elements from either the IP network or the MIPNE 110 that are returned to it once data is obtained on the MVNE 115 by the MIPVNE 105, through the exposed services. Thus, the exposed services of the MVNE 310, some or all of those can be returned after being exposed to the MIPVNE/MIPVNO.

The exposed services listed under 308 and 310 are not definitive and can change over time. The services are defined as industry standards where appropriate and the Parlay X web services are an example of industry standard that meets the specifications of the present system. As mentioned previously, the MIPVNE application 105 contains IPVNE and MVNE exposed services 308 and 310 with additional application specific services 306. All these services are accessibly by the MIPVNE web service contract interface (SOAP). Both IPVNE and MVNE systems will register to the SOAP end point where synchronous and asynchronous messages will trigger service requests. The MIPVNE system 306 can also be requested via the SOAP interface 120 as required. These services will be orchestrated via PNML compatible Workflow processes.

Referring to Fig 4, there is shown the IPVNO systems 125 and the IPVNE systems 110 and network in more detail. There are ten services and system architecture components that are exposed as shown in the exposed services 308 of Fig 3. These are from the IPVNE architecture and include (under customer systems 334) Registration, User Authentication and Account Closure. Under administration systems the Voucher Management is exposed and under billing systems the Retail Balance Management is exposed to the MIPVNE 105 and MVNE 115. From the actual network of the IPNO 155 there is exposed Real Time Rating, Real Time Promotion Rating and Presence and under the application business logic the Usage Detail Records and Number Allocation are exposed.

Firstly, with regard to the Registration component 402 this is in order to register an account for a particular subscriber and will be a single sign-on form so that it takes into account the registration details of the user for the mobile access, the wireless access (Wi-Fi) and the IP access. Thus, a part of the IP network is exposed and a part of the mobile network is exposed in order to get the registration details. This will also mean that there will a single account for the particular subscriber.

User Authentication component 404 is about establishing authentication of a particular subscriber when they want to logon to a WiFi network and therefore have access to the internet. Thus, access to the IP network is verified and the request actually arrives through the MIPVNE 105. The request through the MIPVNE 105 is answered by the IPVNE 115 and a response is given as to whether or not access is authorised to the subscriber to use the IP network. Regarding the Account Closure component 406 where a subscriber does not use their account for a certain predetermined time, for example, six months, then the MIPVNE 105 or MIPVNO 150 will contact the subscriber and let them know that fact. The subscriber is also notified that the account will be cancelled if it is not used within a certain period of time as this is required by regulation. Once the subscriber is notified and no use is made of the account within the period then the account is cancelled and that account number can be reallocated to another subscriber. Such an account number can be made available by either for use on the IP network and the mobile network at the same time.

In the administration systems under Voucher Management 408 this is essentially an amount of credit for a particular subscriber that is held on either or both the mobile network and the IP network and is particularly relevant to pre-paid users. This is particularly useful on a network such as the MIPVNO 150 as it will have access to ledgers which show how much call credit there is on both mobile calls and internet phone calls made by a particular user. Thus, the ledgers can be updated simultaneously and provide a single credit amount available. This would not be available to networks that simply use either IP services or mobile phone services where, for example, a charge for a particular call made on a mobile network would not appear on the ledger or the credit account for the same subscriber subscribing to an IP network. Thus, with the present invention or present system, calls that are made either through the internet or through a mobile network will be automatically deducted from the ledger so that the customer cannot run up a debt against the virtual network operators.

Under the billing systems there is the Retail Balance Management component 410 which is an exposed service and manages post-paid debt, that is customers that have used services and therefore accrued debt with the MIPVNO 150 that will allow a certain amount of credit for a particular customer based on past history payments and credit checks. Thus, the module 410 manages the post-paid debt associated with such customers.

A Real Time Rating Module 412 within the IP network undertakes to determine the rate of charge of a particular call or transfer of data using either the IP network or the mobile network and is able to route a user through either network depending on particular conditions, such as the cheapest possible rate at a particular time of day. The Real Time Promotion Rating module 414 determines promotional ratings that may be occurring at particular times or periods of a day or week. An example is the next thousand calls to land lines will be half price, and this module 414 facilitates a subscriber using the promotional rating for a particular call either through the IP network 210 or the mobile network 220. Where subscribers have already pre-paid for a particular service, and a promotional rating is available, this will be possible for the remaining unused portion of the pre-paid allocation for that particular subscriber. If a subscriber has two hours left of usage time over either network, then the promotional rating, for example, or further calls at half price can be implemented for the remaining time of the pre-paid user. Each of the modules 412 and 414 will update the counterpart real time rating module and real time promotion rating module in the mobile network (or IP network)to update the usage data for a particular call (at a particular rate or on a promotional rate) and to reflect how much time had been used, for example, on a recent call. Another exposed service available through the network is the Presence module

416 which is able to alert other subscribers to the system of the presence of a particular subscriber that they want to call or send a message to. For example, the subscriber they are wishing to call may be online in which case, to save costs, the subscribers wishing to get in contact with that particular subscriber will then get in contact online through the IP network. The presence feature is very useful in that it saves costs in this example, whereby communication is over the IP network for free. Ordinarily, if the subscriber was a mobile subscriber and other people where wishing to get in touch with that mobile subscriber, typically a call to that subscriber will be routed over a mobile network through the MVNE 115. The MVNE 115 recognises this as a mobile call and will switch the call back over the carrier network. Call switching is how each of the mobile networks are able to derive charges for such switching. However, with the present network the IPVNE 110, through the MIPVNE 105, SOAP 120 and EMS 312 is able to alert that initiating subscriber as to the presence of the intended recipient subscriber, for example, that they are logged onto the internet. This presence is signalled to the MVNO 140 so that the MVNO 140 is able to route the call over the internet and not through the mobile carrier.

Module 418 is Usage Detail Records where, for example, records of calls or internet sessions for subscribers is recorded and available when needed. Number Allocation module 420 enables a subscriber of, for example, a corporation to have a global presence whereby they can have a virtual account or real PSTN numbers. Thus, if the corporation is based globally then they may have local PSTN numbers in the countries where they are conducting business. Multiple number allocations are possible.

The systems previously mentioned and described are exposed systems and services. There are other available systems and services that can be exposed at any other time. Examples include, within the customer systems 334 of the IPVNE 110, such modules as Subscriber Data, Product Promotion, Sale Term Definition, Usage History. With administration systems 336 there are the modules Rate Management, Wholesale Vendor Management, Customer Care and Reporting. Within the billing systems 338 there are the modules Postpaid Billing, PAYG Billing, Invoice Compilation, Invoice Rendering, Automated Payment, Merchant Facilities and Bill Error Monitoring. Within the IPNO systems architecture (within the network) there includes the modules Wholesale Reconciliation and Revenue Assurance, Service Balance Management, Credit Control, Least Cost Routing (LCR), Contact Management, Service Provisioning, Interactive Voice Response (IVR), Voicemail, Value Added Services. Within the application business logic architecture (of the IPNO systems architecture) there include the modules Network Registration, CPE Management, Device Configuration Management and Service Usage Limitation.

Within the IPVNO 125 examples of business support systems including Cashier/Merchant Systems, the website (of the IPVNO) and Agency. Within the operational support systems there include the modules Stock Management Systems and Customer Care.

The IPVNO 125 can also detect when a subscriber's computer is turned on at 422 and turned off at 424. It also has online account facilities 426 and registration facilities 428.

With regard to Fig 5 there is shown the system architecture of each of the MVNO 140 and MVNE 115. Systems and services that are exposed and located in block 310 of Fig 3 include Voucher Management 502, Customer Care 504, Mobile Number Portability 506, Account Closure 508, Subscriber Data 510, Balance Management 512, SMSC 514, USSD 516 and Real Time Unified Rating 518.

Each of the exposed services are those services of the MVNE 115 that the MIPVNE 105 requires.

Regarding Voucher Management 502 this is similar to the discussion in relation to Voucher Management 408. Customer Care module 504 provides customers with information and assistance with their subscription to the MVNE 115 and also the MIPVNE 105. The Subscriber Data module 510 under Workflow is a module similar to the Usage Detail Records module 418 whereby data pertaining to subscribers such as details on calls and connections are stored. The Account Closure service 508 is another exposed service and is similar to Account Closure module 406. Within the intelligent network is the Balance Management Service 512 whereby such management ensures that the MIPVNE 105 or MVNE 115 is not exposed to debt through its subscribers. The SMSC module 514 is a short message service centre which manages the transmission of SMS messages through the MVNE 115 and manages billing, calls and connections as well as the delivery of the messages. The SMS calls can be routed through the MVNO 140 or the MIPVNO 150 or a wholesale delivery supplied where such services are cheaper. Module 516 is the USSD or Unstructured Supplementary Services Data whereby the call costs are determined by this module and delivered to the network and possibly displayed to the user after each call or connection. The Real Time Unified Rating module 518 is similar to module 412 in that it manages promotional rates for calls and particularly on the mobile network through which the MVNO is operating. Other systems architecture and service modules that can be exposed at other times to the MIPVNE 105 include, within the business support systems, the modules for Reporting and Invoice Printing and, within the presentation layer, modules for Point-of-Sale and Self Care. Under operational support systems there are the modules Inventory Management and Dealer Management. Underneath the Workflow architecture there are the modules for Postpaid Billing, Invoice Generation and Accounts Receivable. The Mobile Number Portability module 507 may be exposed and allows a subscriber to retain a mobile number when moving between different service providers. There is also a Credit Check module and a System Monitoring module.

Within the intelligent network there are modules for Wholesale Reconciliation and Revenue Assurance, Credit Control, RADIUS, IVR, MMSC, Data Charging Gateway, Voicemail and Value Added Services. There is also the Service Provisioning module, CDR Mediation and Service Signalling Layer module. Within the MVNO 140, under business support systems, there is Cashier

Systems and Website Management and, under operational support systems, there is Stock Management Systems and ERF Systems. The MVNO 140 also has online account system 520, a registration system 522 and enables connection to and from the mobile network for subscribers at 524. Shown in Fig 7 are the service providers being the IPNO or operator 130,

Wireless Access module for WiFi communications 135 and the Mobile Network Operator (MNO) 145. With regard to the IP network operator 130, under Telephony Operator Systems there are the modules for Provisioning Devices, Mediation Device, Mobile Number Portability, Wholesale Usage Data and the Telephony Network itself. For the Wireless Access networks 135, which relate to provision of WiFi services through the various hotspots by retail chain organisations, it includes the modules for Provisioning Device so that the various devices of the subscribers are configured to communication through WiFi hotspots when they are within such a hotspot and have signed on to use that access point. It also minimises exposure to possible hacking through the provisioning of such devices. MAC address signing can also be provided by the Wireless Access Service Providers in order minimise hacking. Aside from that module it has a Mediation Device Module, the RADIUS module, Data Access Network, Wholesale Usage Data and Roaming Access Management. The Wireless Access system also includes a WISPr Authentication module which is a protocol that is in a XML formatted message which can be sent to the MIPVNE 105 and is used for roaming purposes where roaming takes place from one WiFi network to another WiFi network or point. Thus, where the user is roaming between WiFi providers then the authentication protocol is used to enable communications to continue for that subscriber. Once authentication is made available, then session usage over the internet can be tracked using RADIUS which is the Remote Authentication Dial In User Service being an authentication, authorisation and account protocol for applications such as network access or IP mobility. It is intended to work in both local and roaming situations.

Regarding the MNO 145 it has within its systems modules for Provisioning Devices, Mediation Device, Mobile Number Portability, Home Location Register, Mobile Network, Voicemail, SMSC as well as protocols associated with a MNO such as MSC/STP, GGSN, SGSN and RADIUS.

Referring to Fig 6, there is shown the MIPVNE application 105 and its association with MIPVNO 150 and the interfaces of SOAP 120 and EMS 312.

Specifically within the IPVNE services 306 there are a number of service modules including RADIUS 602, website 604, Device Management 606, Registration 608, Process Management 610, Additional Subscriber Data 612, Service Access Management 614, Service Delivery Manager 616, Network Selection Manager 618, Least Cost Routing 620 and Account Closure 622.

The Device Management module 606 informs the mobile network that specific firmware is supported on the mobile network, it manages updates to be forwarded to the mobile network and to specific handsets, as the MIPVNE 105 provides additional services in the future. The module also is able to ascertain the state of each handset in terms of operational support systems. The data collected by the Device Management module 606 will also be used on WiFi access applications, for example, it is determined that a certain hardware device, system or software support is provided on a particular handset. The module 606 is a service that will also capture device hardware identification detail upon receipt of new inventory orders. Further responsibilities include "push" device configuration and account authentication in registration and other isolated requests. Device access destruction is also performed by this service. The Process Management Service module 610 manages the compatibility between the PNML and BPM formats. The status monitoring in customer account, administration and customer care interfaces is also managed via this service. The Additional Subscriber Data Service module 612 is used to model and encapsulate MIPVNE specific data requirements. An example of additional subscriber data will be future rich presence data. The Service Access Management Service module 614 aggregates the access or barring level activity occurring across an IPNO, MNO or other network to ensure user service is consistently maintained against specified business rules. Thus, as an example, access for a particular subscriber may allow that subscriber to make SMSs, have access to the internet through particular WiFi hotspot providers but they might be restricted to making such transmissions through video only or call only as an example. It also bars access to service if the subscriber has not paid off their current account.

The Service Delivery Manager module 616 maintains active service delivery methods across all available network delivery options. Thus, it will automatically select either the IP network or mobile network depending on the time of day and the call charge for a particular subscriber.

The Network Selection Manager module 618 provides direct input into the Service Delivery Manager 616 on health and congestion indicators and eventually selects the particular network through which a call or session is to be routed. The Least Cost Routing module 620 calculates the path of least cost for all services with multiple delivery options where costs vary. This service is also responsible for rule based routing decision management and rule import and compilation processes. The Account Closure module 622 aggregates the account closure activity across multiple networks with multiple products and/or services. It monitors time based activity events, service abuse complaints and network indicators and payment failure events in order to trigger closure of an account.

The MIPVNO 150 has BSS 318 and OSS 320. Within the BSS 318 are the Cashier/Merchant Systems, Website and Agency System. Within the OSS 320 are Stock Management Systems and Customer Care. The MIPVNO can detect the state of a subscriber's computer, for example whether it is turned on at 624 or turned off at 626. It has an online account facility 62, a registration facility 630 and enables connection through the mobile network at 632.

All of the modules 602 to 622 form part of the service layer which defines the jobs that software is supposed to do and directs the expressive domain objects to work out specific problems within a network. The layer is responsible for co-ordinating tasks and delegates work to collaborations of domain objects in the next layer down. It does not have a state reflecting the business situation but can have a state that reflects the progress of a task for the user or the program. The layer is typically kept thin in that it does not contain business rules or business knowledge. The tasks it performs are necessary for interaction with the application layers of other systems. A domain model is responsible for representing concepts of the business, information about the business situation and business rules. This layer is at the heart of business software.

A data access layer abstracts access to various data sources, including relational databases, legacy systems, message queues and directory services.

Apart from the service layer, domain model and data access layer forming part of the business logic as modular elements thereof there is the web services layer that provides a standards-based interface to the service layer for use by call switching, IPVNO websites, the administration system and wholesale billing system. Web services layer is provided by a number of web services using SOAP, WSDL, XML and related technologies. These web services are grouped by major class of consumer, there is one for use by white label websites, such as virtual network operators, and another used by the call switching portion of the network.

A call switching interface is the interface that the internal call switching and instant messaging application uses to communicate with the business logic block. This interface is responsible for providing call rating, call routing, call authentication and authorisation functionality to the application.

As mentioned previously, the exposed services use Parlay X web services which are powerful but simple telecommunications services that developers and IT users and administrators can quickly understand and use to develop new, innovative telecommunication applications. These services make it possible to introduce a wide variety of services and applications quickly with faster development cycles. They are built on open technologies that developers use, such as object-oriented programming, JavaR, and web services, as opposed to proprietary technologies. The SOAP interface 120 is the effective gateway that bridges the IPVNE system

110 and the MVNE system 115. Its maintenance, upgrade, regression testing and production availability is of critical importance and requires dedicated development and operational resources.

It will be appreciated by persons skilled in the art that numerous variations and/or modifications may be made to the invention as shown in the specific embodiments without departing from the spirit or scope of the invention as broadly described. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive.

Claims

CLAIMS:

1. A method of providing telecommunications, through a Mobile Internet Phone Virtual Network Enabler (MIPVNE) application to a Mobile Internet Phone Virtual Network Operator (MIPVNO)₅ to selectively enable subscribers to the MIPVNO to have access to an IP network or a mobile communications network, the method comprising: providing Internet Phone Virtual Network Enabler (IPVNE) services for use by the MIPVNE application; and providing Mobile Virtual Network Enabler (MVNE) services for use by the

MIPVNE application; such that seamless connection is made over the IP network or the mobile communications network when a subscriber initiates a call or data session.

2. A method according to claim I₅ further comprising: interfacing the MIPVNE application to the IPVNE and the MVNE through one of the Simple Object Access Protocol (SOAP) interface and a Web Service contract interface.

3. A method according to claim 1 or 2, where the MIPVNE application contains exposed services of the IPVNE and exposed services of the MVNE.

4. A method according to claim 3, where the MIPVNE application further contains at least one application specific service, the application specific service selected from: a device management service, a process management service, an additional subscriber data service, a least cost routing service, a service access management service, a service delivery manager service, a network selection manager service and an account closure service.

5. A method according to claim 4, further comprising: accessing the or each of the application specific services and the exposed services contained in the MIPVNE application via the SOAP interface.

6. A method according to claim 4 or 5, further comprising the exposed services of the IPVNE, the exposed services of the MVNE and the MIPVNE application specific services registering with a SOAP end point; where synchronous and asynchronous messages trigger requests for such exposed services.

7. A method according to claim 6, further comprising: performing such requests and application delivery to and from a subscriber handset through Workflow.

8. A method according to claim 7, where Workflow is one of PNML and BPEL.

9. A method according to any one of claims 3 to 8, further comprising: using Parlay X Web Services to perform the exposed services.

10. A method according to any one of the preceding claims, further comprising the MIPVNE services specifically catering for each of a plurality of MIPVNOs.

11. A method according to any one of the preceding claims, further comprising: providing a Wi-Fi hotspot through a Wireless Access System; and accessing the internet through a Wi-Fi hotspot.

12. A Mobile Internet Phone Virtual Network Enabler (MIPVNE) application for providing telecommunication services to a Mobile Internet Phone Virtual Network Operator (MIPVNO) to selectively enable subscribers to the MIPVNO to have access to an IP network or a mobile communications network using a single mobile handset, the MIPVNE application comprising:

Internet Phone Virtual Network Enabler (IPVNE) services available in connection with use of the IP network by the subscribers;

Mobile Virtual Network Enabler (MVNE) services available in connection with use of the mobile communications network by the subscribers; such that a seamless connection is selectively made over the IP network or the mobile communications network using the respective IPVNE services or the MVNE services when a subscriber initiates a call or data session.

13. An MIPVNE application according to claim 12, further comprising: a Workflow application; an interface for interfacing to the MVNE and the IPVNE; and an Enterprise Messaging System.

14. An MIPVNE application according to claim 13, wherein the interface for interfacing to the MVNE and the IPVNE is a SOAP interface.

15. A system of providing telecommunications to subscribers over an IP network and a mobile communications network using a single mobile handset comprising: a Mobile Internet Phone Virtual Network Enabler (MIPVNE) linked to each of a Mobile Virtual Network Enabler (MVNE) and an Internet Phone Virtual Network Enabler (IPVNE) for accessing MVNE services and IPVNE services respectively; a Mobile Internet Phone Virtual Network Operator (MIPVNO) linked to the MIPVNE, the MIPVNO linked to the internet and to a mobile communications network; wherein the system is selectively operable to enable subscribers to communicate over the IP network through the MIPVNO using the IPVNE services or the mobile communications network through the MIPVNO using the MVNE services.