EP2997495A1

EP2997495A1 - Interfacing multiple retailer systems and multiple carrier systems in the requisition of telecommunication products

Info

Publication number: EP2997495A1
Application number: EP13773167.5A
Authority: EP
Inventors: Micheal Youssef
Original assignee: Iris Solutions International Inc
Current assignee: Iris Solutions International Inc
Priority date: 2013-10-11
Filing date: 2013-10-11
Publication date: 2016-03-23
Also published as: CA2833699A1; WO2015053783A1

Abstract

A system, method and apparatus for interfacing a plurality of retailers with a plurality of carriers for requisitioning a telecommunication product for a customer from any one of the retailers and with any one of the carriers. According to an embodiment, the system comprises a processing module or hub, a plurality of retailer interface components, and a plurality of carrier interface components. The processing module includes a retailer communication interface for operatively coupling to the plurality of retailer interface components, for example, through a network, and a carrier communication interface for operatively coupling to the plurality of carrier interface components, for example, through a network. The processing module further includes a transaction module configured to execute the requisitioning of the telecommunication product with one of the carriers based on retailer process information received from one of the retailers.

Description

TITLE:

INTERFACING MULTIPLE RETAILER SYSTEMS AND MULTIPLE CARRIER SYSTEMS IN THE REQUISITION OF TELECOMMUNICATION PRODUCTS

FIELD OF THE INVENTION

[0001] The present invention relates to computer systems, and more particularly to a networked system for connecting or integrating one or more retailer systems with one or more carrier systems in the requisitioning of products and services offered by the one or more carriers to one or more clients of the retailers.

BACKGROUND OF THE INVENTION

[0002] Consumers are relying more and more on retailers for the purchase or upgrade of mobile communication devices. Traditional systems utilized by retailers comprise a point- to-point configuration between the retailer system and the carrier system. Point-to-point integration between each retailer and the carrier partners of the retailer requires a substantial investment both in the system infrastructure for connecting with each carrier and also in the ongoing support including training, maintenance, upgrade and testing of each point-to-point connection. With the plethora of retailers offering mobile communication devices and the numerous carriers providing mobile telecommunication services, the investment and ongoing costs and resources required to maintain the system is effectively multiplied by the number of carriers partnered with a retailer and the number of retailers supported by the carrier. It will be appreciated that the direct and associated costs can be quite substantial.

[0003] Accordingly, there remains a need for a scalable system and/or a system that allows multiple retailer systems to connect with multiple carrier systems in the requisitioning of services. BRIEF SUMMARY OF THE INVENTION

[0004] The present invention provides a networked system for connecting one or more retailer systems to one or more carrier systems in the requisitioning of telecommunication products including devices and services offered by the one or more carriers to one or more clients of the retailer.

[0005] According to one aspect, the system provides a single integration point for a carrier to connect to a plurality of retailers.

[0006] According to another aspect, the system provides a single integration point for a retailer to connect to a plurality of carriers.

[0007] According to another aspect, the system is configured to isolate the retailers and the carriers from their respective development, test, release and support schedules or requirements and/or infrastructure.

[0008] According to another aspect, the system is configured to be scalable and comprises a multi-tenant arrangement for retailers and carriers.

[0009] In accordance with an embodiment, the present invention comprises a system for connecting a plurality of retailer systems with a plurality of carrier systems for requisitioning a telecommunication product for a customer, the system comprises: a network; each of the plurality of retailer systems having a retailer network interface configured to operatively couple the retailer system to the network; each of the plurality of carrier systems having a carrier network interface configured to operatively couple the carrier partner system to the network; a processing module having a retailer communication interface operatively coupled to the network and configured to receive and transmit retailer process information for requisitioning the communication device for the customer through one of the retailer systems; the processing module having a carrier communication interface operatively coupled to the network and configured to receive carrier process information with any one of the plurality of carrier systems; and the processing module having a transaction module configured to execute a requisitioning procedure utilizing the retailer process information and any required carrier process information for requisitioning the telecommunication product between one of the plurality of retailer systems and one of the carrier systems, wherein the carrier system is selected by a user. [00010] In accordance with another embodiment, the present invention comprises a computer-implemented method for requisitioning a telecommunication product for a customer at a retailer with one of a plurality of carrier systems, the computer-implemented method comprising: generating a requisitioning request at a retailer system, and transmitting the requisitioning request to a telecom processing hub, wherein the telecom processing hub is operatively coupled to the retailer system in a network configuration; transforming the requisitioning request into a corresponding common object according to a common object model at the telecom processing hub; selecting one of the plurality of carrier systems for requisitioning the telecommunication product, and the selection being based on a user input; transforming the common object request into a carrier request operation having a form compatible with the selected carrier system; invoking the selected carrier system based on the carrier request operation; receiving carrier request response from the selected carrier system; transforming the carrier request response into a common object response; transforming the common object response into a corresponding retailer response object; transmitting the retailer response object to the retailer system; and completing the requisitioning of the communication device at the retailer system.

[00011] In accordance with a further embodiment, the present invention comprises a computing apparatus for performing a requisitioning operation for a telecommunication product between one of a plurality of retailers and one of a plurality of carriers, the computing apparatus comprises: a processing module comprising a common retailer interface configured for each of the plurality of retailers, and the common retailer interface being configured to receive request from one of the plurality of retailers; the processing module comprising a common carrier interface configured for each the plurality of carriers; the processing module comprising a common model, and the common retailer interface being configured to receive a request from one of the plurality of retailers and transform the request into a common object according to the common model; the common carrier interface being configured to transform the common object into a carrier request; and the processing module being configured to provide the carrier request to one of the plurality of carriers as part of the requisitioning operation.

[00012] In accordance with another embodiment, the present invention comprises a computing apparatus for requisitioning a telecommunication product for a customer at one of a plurality of retailers from one of a plurality of carriers, the computing apparatus comprises: a processing module comprising a common retailer interface configured for each of the plurality of retailers; the processing module comprising a common carrier interface configured for each the plurality of carriers; the processing module further including a graphical user interface comprising a common functional configuration for the plurality of retailers, and the graphical user interface having one or more inputs responsive to user inputs for defining a transaction for requisitioning the telecommunication product at the retailer and wherein one of the inputs comprises a carrier selection input for selecting one of the plurality of carriers; and the common carrier interface being configured to transform the requisitioning transaction into a carrier requisition operation for performing the requisitioning of the telecommunication product at the selected carrier.

[00013] In accordance with yet another embodiment, the present invention comprises a network based system for requisitioning a customer with a telecommunication product, the network based system comprises: one or more retailers and each of the one or more retailers having a retailer adapter operatively coupled to the network; one or more carriers and each of the one or more carriers having a carrier adapter operatively coupled to the network; a hub having a retailer interface for coupling to the retailer adapter of each of said one or more retailers for transferring retailer information over the network between the hub and any one of the retailers, and further including a carrier interface for coupling to the carrier adapter of each of the one or more carrier partners for transferring carrier information over the network between the hub and any one of the carrier partners; the hub including a component configured to transform the retailer information into retailer common objects according to a common object model, and another component configured to transform the carrier information into carrier common objects according to the common object model; and the hub being configured to execute a telecom transaction based on the retailer common objects and the carrier common objects for requisitioning the customer at one of the one or more retailers with the telecommunication product selected from the of said one or more carriers.

[00014] Other aspects and features of the present invention will become apparent to those ordinarily skilled in the art upon review of the following description of specific embodiments of the invention in conjunction with the accompanying figures. BRIEF DESCRIPTION OF THE DRAWINGS

[00015] Reference will now be made to the accompanying drawings, which show, by way of example, embodiments of the present invention, and in which:

[00016] Fig. 1 shows in diagrammatic form a networked system for requisitioning telecommunication products according to an embodiment of the present invention;

[00017] Fig. 2 shows in diagrammatic form an exemplary architecture for the networked system for requisitioning telecommunication products of Fig. 1 and in accordance with an embodiment of the present invention;

[00018] Fig. 3 shows in schematic form a logical data model for the networked system for requisitioning telecommunication products according to an embodiment of the present invention;

[00019] Fig. 4 shows in flowchart form processing steps for conducting telecom or wireless transactions according to an embodiment of the present invention;

[00020] Fig. 5 is a process flow diagram showing processing steps executed in the networked system for requisitioning telecommunication products of Fig. 1, according to an embodiment of the present invention;

[00021] Fig. 6(a) is a screenshot of a landing page according to an embodiment of the present invention;

[00022] Fig. 6(b) is a screenshot of a customer authentication page according to an embodiment of the present invention;

[00023] Fig. 7 is a screenshot of a customer authentication page according to an embodiment of the present invention;

[00024] Figs. 8(a) and 8(b) are screenshots of a create new customer page according to an embodiment of the present invention;

[00025] Fig. 9 is a screenshot of a select device page according to an embodiment of the present invention; [00026] Fig. 10 is a screenshot of a customer conditions and restrictions page according to an embodiment of the present invention;

[00027] Fig. 11 is a screenshot of a select phone number page according to an embodiment of the present invention;

[00028] Fig. 12 is a screenshot of a select promotion page according to an embodiment of the present invention;

[00029] Fig. 13 is a screenshot of a select plan & features page according to an embodiment of the present invention;

[00030] Fig. 14 is a screenshot of a review page according to an embodiment of the present invention;

[00031] Fig. 15 is a screenshot of a customer agreement page according to an embodiment of the present invention;

[00032] Fig. 16 is a screenshot of an order confirmation page according to an embodiment of the present invention;

[00033] Fig. 17 shows in diagrammatic form an exemplary "cloud based" implementation or deployment of the networked system for requisitioning telecommunication products of Fig. 1 ;

[00034] Fig. 18 shows in diagrammatic form an exemplary redundant system deployment for the networked system for requisitioning communication devices of Fig. 1 according to an embodiment of the present invention;

[00035] Fig. 19 is a process flow diagram showing processing steps for a data upload and data cache procedure according to an embodiment of the present invention; and

[00036] Fig. 20 is a block diagram showing an exemplary implementation for a computer system suitable for the requisitioning system of Fig. 1. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

[00037] Reference is first made to Fig. 1, which shows in diagrammatic form a networked system for requisitioning telecommunication products by integrating one or more retailers with one or more carriers according to the present invention and indicated by reference 100. Embodiments according to the present invention are described in the context of one or more retailers providing customers of the retailer with activation, renewal, upgrade, exchange, return, migration, subscriber identity module (SIM) replacement, and the like services for telecommunication products, such as mobile communication devices (for example, smart phones), for one or more carriers based on services provided by the carrier, for example, cellular service, data service and other value added services. It will however be appreciated that embodiments according to the present invention may be used in other applications where a customer purchases or subscribes to services through one or more retailers and the services are made available from one or more service providers.

[00038] As shown in Fig. 1, the networked system for requisitioning telecommunication products 100 comprises a hub module 110. The hub module 110 comprises a processing module and is configured to connect or integrate one or more carrier adapter modules 120, indicated individually by references 120a, 120b...120m with one or more retailer adapter modules 130, indicated individually by references 130a, 130b,...130n in Fig. 1. Each of the carrier adapter modules 120 is associated with or deployed with a carrier or carrier partner 122, indicated individually by references 122a, 122b,...122m. Each of the retailer adapter modules 130 is associated with or deployed with a retailer or retail partner 132, indicated individually by references 132a, 132b, ...132n. According to an exemplary implementation, each of the plurality of retailers 132 may be an independently operated retail store not associated with any of the plurality of the carrier partners 122. According to another aspect, each of the plurality of retailers, i.e. retail partners, 132 may have a partnership or relationship with one or more of the plurality of carrier partners 122. According to another exemplary implementation, each partnership between one of the plurality of retail partners 132 and one of the plurality of carrier partners 122 may provide for the sale of portable electronic devices, among other things, by the retail partners 132 and/or the sale of telecommunications services provided by the carrier partners 122.

[00039] In one example, the retail partner 132b may sell portable electronic devices together with a wireless telecommunications service plan, both provided by the carrier partner 122a. The purchase price of the portable electronic device may be subsidized by the carrier partner 122a in some instances. The portable electronic device sold by the retail partner 132b may have been provided to the retail partner 132b by the carrier partner 122a in some examples, in which case the sale of the portable electronic device and the wireless telecommunications service plan both may need to be coordinated with the carrier partner 122a. In other examples, the retail partner 132b may have obtained the portable electronic device directly from the manufacturer of the portable electronic device, in which case the retail partner 132b may not need to coordinate the sale of the device itself with the carrier 122a, but will still need to coordinate the sale of the telecommunications service plan (including any subsidy for the device paid for by the carrier 122a, if applicable). In either example, the retail partner 132b may also need to coordinate the activation of the portable electronic device on the carrier's telecommunications network, the enrollment of the customer into the telecommunications service plan, the association between the portable electronic device and the purchased telecommunications service plan, and so forth. In general, any sale by the retailer partner 132b may involve one or more transactions with the carrier partner 122a. The transactions may include various requests and responses to those requests, as described in more detail below.

[00040] As will be described in more detail below, the hub module 110 is configured to execute a layer of services and modules that are common to the retail partners 132 and to the carrier partners 122. The retail partners 132 provide the details of transaction requests to the hub module 110 through their own instance on the retail adapter module, and are unaffected by any changes or operations performed by the carrier partner(s) 122 until the retail partner 132 so chooses, as described in more detail below. Similarly, if the retail partner(s) 132 make changes to their connection or integration with the hub module 110 that do not necessarily require any change for the carrier partner 122, the changes can be implemented and tested without involvement by the carrier partner(s) 122, as described in more detail below. The carrier adapter modules 120 are configured to provide the services and functions required for a telecom transaction with one of the retail partners 132 and transform them into a common model for processing by the hub model 110, as described in more detail below. Similarly, the retailer adapter modules 130 are configured to provide the services and functions required for a telecom transaction with one of the retail partners 132 and transform them into a common model for processing by the hub model 110, as described in more detail below. [00041] According to an embodiment, the hub module 110 comprises a "cloud-based" implementation, and is configured to couple through the Internet to the carrier adapter modules 120 and to the retailer adapter modules 130. In the context of the present description, the carrier adapter modules 120 comprise an interface and control module that couples each carrier requisitioning system with the hub module 110 and is configured provide customer functions (e.g. activations, port-in activation, upgrades, renewals, migrations and swaps, multi-unit transactions, future dated transactions, exchanges, returns, and related functions), integration, testing and other support functions, as will be described in more detail below. The retailer adapter modules 130 comprise an interface and control module that couples each of the retail partners 132 (i.e. retailer activation system 230 (Fig. 2)) with the hub module 110, and is configured to provide the retail partner or retailer activation system 230 (Fig. 2) with functions, such as, new customer activation and/or upgrade functions, and the like, with a selected carrier 220 (Fig. 2). In addition, the retailer adapter module 130 is configured to provide the retail partner 132 with integration, testing and other support functions, as will be described in more detail below. According to another aspect, the hub module 110 is configured to allow one of the retail partners 132, for example, a retailer of mobile phones (e.g. BestBuy or Future Shop), to integrate the retailer's computer system with the hub module 110 and then be configured to conduct business and transactions through the hub module 110 with the one or more carrier partners 122 (e.g. Bell, Rogers) who are also integrated with the hub module 110, as will be described in more detail below. Similarly, the hub module 110 is configured to allow the carrier partner 122, for example, a cellular service provider (e.g. ATT, Verizon), to integrate the carrier's requisitioning system with the hub module 110 through the carrier adapter module 120 and then be configured to provide through the hub module 110 requisitioning and/or upgrade, and other related transactions, of the carrier's services to customers of any one of the retail partners 132, as will be described in more detail below.

[00042] Reference is next made to Fig. 2, which shows an architecture comprising logical and functional modules for the networked system for requisitioning telecommunication products according to an embodiment of the present invention and indicated generally by reference 200. As shown in Fig. 2, each of the retailer adapter modules 130 comprises a retailer adapter 231, indicated individually references 23 la,...23 In, and a retailer bridge 232, indicated individually by reference 232a...232n. The retailer adapter 231 is configured to provide an interface between the retail partner 132 and the hub or processing module 110. According to another aspect, the retailer adapter 231 may be configured to provide a graphical user interface (GUI) comprising one or more windows or pages, for example, as described in more detail below. The retailer bridge 232 is configured to transform data flow or retailer process information, e.g. control commands, status requests, customer information and requisitioning data, to and from the retailer specific interface (as configured in the retailer adapter module 130) into a form or format suitable for input/processing by a common model module in the hub module 110. According to an embodiment, the retailer adapter module 130 is configured to provide the following functionality and/or features:

(1) sales management flow, e.g. sale, activation, upgrade of mobile communication devices to customers of the retail partner

(2) point of sale (POS) functions

(3) inventory management

(4) document management - documents generated during a telecom transaction are sent from the hub module 110 to the retail partner through the retailer adapter module 130 and the retailer bridge 232

(5) data warehouse - data feeds and other information is pushed by the retailer adapter module 130 through the retailer bridge 232 and stored by the retail partner, e.g. in a data warehouse

[00043] According to another aspect, the retailer adapter modules 130 are configured in a multi-tenant arrangement and each retail partner is provided with the capability to configure the user interface for the retailer adapter module 130 to satisfy requirements of the retailer. According to an embodiment, the retailer adapter modules 130 may be configured with one or more of the following functions or features:

(1) branding - configured according to corporate identity, retailer styles, images and/or fonts

(2) pages layout - configurable header, footer, menu and/or body

(3) business rules - configurable utilizing scripted rules and/or decision tables (4) configuration parameters - static configuration and/or real-time configuration

(5) Web content - configurable images, text, messages, email/notification templates, documents and/or campaigns

[00044] As also shown in Fig. 2, each of the carrier adapter modules 120a to 120m comprises an associated carrier bridge 221, indicated individually by references 221a to 221m, and an associated carrier adapter 223, indicated individually by references 223 a to 223m. The carrier bridge 221 is configured to transform data flow or carrier process information, e.g. control commands, status requests, customer and requisitioning data and information, to and from the carrier partner interface (as configured in the carrier adapter module 120) into a form or format suitable for input/processing by the common model module in the hub module 110 in the upstream direction, and in the downstream direction into form or format suitable for input or processing by the requisitioning system utilized by or resident at the carrier partner 120.

[00045] According to an exemplary embodiment, the retailer adapter module 130 comprising both the retailer adapter 231 and the retailer bridge 232 is configured or deployed at the retail partner 132, for example, on the retail computer system and operatively coupled to the processing module 110 through a network, e.g. the "cloud". Similarly, according to an exemplary embodiment, the carrier adapter module 120 comprising both the carrier adapter 223 and the carrier bridge 221 is configured or deployed at the carrier partner 120, for example, on the carrier computer system(s) and operatively coupled to the processing module 110 through the network, e.g. the "cloud". According to another exemplary embodiment, the retailer adapter module 130 comprising both the retailer adapter 231 and the retailer bridge 232 are configured or deployed at the hub or processing module 110 and operatively coupled to the respective retail partners 132 via the network or cloud. Similarly, according to another exemplary embodiment, the carrier adapter module 120 comprising both the carrier adapter 223 and the carrier bridge 221 are configured or deployed at the hub or processing module 110 and operatively coupled to the respective carrier partners 122 via the network or cloud. According to another exemplary embodiment or implementation, the retailer adapter 231 is configured or deployed at the retail partner 132 and the retailer bridge 232 is configured or deployed at the hub module 110 and operatively coupled through the network or cloud. Similarly and according to another exemplary embodiment or implementation, the carrier adapter 223 is configured or deployed at the carrier partner 120 and the carrier bridge 221 is configured or deployed at the hub module 110 and operatively coupled through the network or cloud.

[00046] According to an embodiment and as shown in Fig. 2, the hub module 110 comprises a sales common model module 240 and a carrier specific VAS (Value Added Services) module 250, which are configured to implement processing operations associated with the requisitioning of a telecommunication product. In the context of the present description, a telecommunication product comprises wireless devices and services. However, the telecommunication products may also include other devices and/or services offered by a carrier partner, for example, Internet devices and services, landline devices and services, and TV/cable devices and services. Further, the requisitioning of a wireless telecommunication product comprises one or more of the following requisitioning transactions or operations, acquisition (activation) of a new device, for example, a wireless telecommunication device, or a SIM card, renewal, upgrade, exchange, return, SIM card replacement and migration. The sales common model module 240 is configured to provide the functions associated with the requisitioning of a telecommunication product for the carrier partners 220 and the retailer partners 230.

[00047] According to an exemplary implementation, the sales common model module 240 comprises a sales flow management module 242, a sales information management module 244, and a sales virtualization module 246. The sales common model module 240 may also include another functional module indicated generally by reference 248 which is configured to provide other or future functions associated with telecommunication products.

[00048] The sales flow management module 242 is configured to support the processing performed or executed in a retailer telecom sales flow process, e.g. the purchase and activation of a new mobile communication device by a customer at one of the retailer partners 230. According to an exemplary implementation, the retailer telecom sales flow process comprises the following operations or processes:

(1) Customer Management comprising: creation of an account/subscriber; modification of an account/subscriber; cancellation of an account/subscriber; authentication of an account/subscriber; credit check of an account; and an account/subscriber eligibility check. These processes are managed through the requisitioning system of the selected or associated carrier partner 220. (2) Customer Selection Management comprising: device, network area code, rate plan, feature(s) and/or promotions, as selected by the customer at the retailer partner. These processes or operations are managed through the operation of the sales information management module 244.

(3) Telecom Functions comprising: reserve and release phone number; special promotion retrieval; customer selection validated against customer profile; price calculation; order submission; and/or service agreement creation. These processes or operations are managed through the requisitioning system of the selected or associated carrier partner 220.

In addition, the system 100 can be configured to provide additional features or services, such as electronic or digital signature capture and final service agreement generation, subscriber address validation, subscriber device trade-in and/or service transitional data management, as will be described in more detail below.

[00049] Referring again to Fig. 2, the sales information management module 244 is configured to manage sales reference information associated with a telecom transaction. According to an exemplary implementation, the sales reference information comprises: account type/sub-type as defined in the carrier system; network area codes; country/province (state); device; rate plan; feature(s); and/or promotions. Since the sales reference information is relatively stable and maintained in the carrier system, the sales reference information can be uploaded by the carrier partner and maintained in a database as will be described in more detail below.

[00050] The sales virtualization module 246 is configured to provide support for any one of the retailer partners 132, such as testing and integration. According to an embodiment, the virtualization module 246 is configured to generate a virtual model or "virtualization" of one or more of the carrier systems. According to an exemplary implementation, the sales virtualization module 246 is configured to allow the retailer partner 132 to test the retailer's system in a "non-production" environment, for example, if the carrier system is down or offline. According to an embodiment, the hub module 110 receives a web service request containing a virtualization indicator from the retail adapter module 130 for one or more of the retailer partners 132. The hub module 110 generates a web service response and the virtualization module 246 is invoked and a "virtual carrier" is generated and made available to the retail partner 132, for example, comprising a test structure for testing changes (e.g. new services or functions) that the retail partner 132 has implemented in their system and/or the retail adapter module 130. It will be appreciated that this allows a retail partner to test their system independently of the carrier partner

[00051] According to an embodiment, the hub module 110 may include the carrier specific VAS (Value Added Services) module as introduced above and indicated by reference 250 in Fig. 2. The carrier specific VAS module 250 is configured to provide value added services that are specific or associated with a specific carrier partner or a third party vendor 225, indicated individually by references 225a, 225b in Fig. 2. The third party vendor 225 interfaces to the hub module 110 through a vendor interface module indicated by reference 223 in Fig. 2. The vendor interface module 223 is configured to provide the capability to transmit and/or receive information (e.g. data, transaction requests, transaction responses) between the third party vendor 225 and the hub module 110. According to an embodiment, the carrier specific VAS module 250 comprises a postal code/zip code lookup module 252 and a credit check module 254. According to an exemplary implementation, the third party vendor 225 provides a postal code/zip code lookup service. According to another exemplary implementation, the third party vender 225 provides a credit check service. According to an embodiment, the value added services are provided to support the sales flow of devices for a carrier partner, and invoked internally by the hub module 110 without direct intervention by the retail partner 132. For example, in the processing of a new activation request from one of the retail partners 132, the hub module 110 activates the carrier specific VAS module 250 and the postal code/zip lookup module 252 is invoked to confirm the postal code of a customer purchasing a mobile phone (e.g. based on the residential address of the customer) through the third party vender 225, and/or the credit check module 254 is invoked to perform a credit check on the customer through another third party vendor. The outcomes of the VAS services are then passed to the retail partner 132 (and the carrier partner 122) as part of the processing of the telecom transaction.

[00052] According to an embodiment, the retailer adapter module 130 is implemented as a Web service API (Application Program Interface). The retail adapter module 130 comprises a set of telecom sales Web services that allow the retail partner to fulfill an end-to- end telecom transaction between the retailer and one of the carriers. According to another aspect, each Web service API is further customizable for each retailer. According to another aspect, the Web services may be implemented utilizing RESTful style or SOAP style, as will be understood by one skilled in the art. According to another embodiment, the retailer adapter may be implemented as a retailer web application 235 with a GUI (Graphical User Interface) and a retailer bridge 232 as also shown in Fig. 2. According to an exemplary implementation or embodiment, the graphical user interface or GUI for the retailer web application 235 includes one or more pages or screens as described in more detail below. According to an exemplary implementation, the retailer web application 235 is configured to execute on a web browser platform, such as Internet Explorer™ or Safari™ browsers, and provide a retailer with the functions required to perform a telecom transaction as described below.

[00053] According to another embodiment, the retailer adapter module 130 may be integrated with other retailer systems, such as, point of sale, inventory, document and web content management, reporting, and/or human resources. Referring back to Fig. 2, the networked system for requisitioning telecommunication products 100 may include a retail system integration module according to an embodiment and indicated generally by reference 222. The retail system integration module 222 may be configured in the hub or processing module 110 and comprises a POS (Point Of Sale) integration module 224 and a retailer inventory integration module 226. According to an embodiment, the POS integration module 224 is configured to function with the retailer adapter module 130 and transfer initial transaction and subscriber information or data. The retail adapter module 130 communicates with the POS integration module 224 and transfers sales process information back to the POS integration module 224. The retailer inventory integration module 226 is configured to communicate with the retail adapter module 130 (i.e. through the retailer bridge 232) for performing inventory functions, such as, inventory lookup, inventory validation and adjustments in the retail partner's inventory system.

[00054] According to an embodiment, the networked system for requisitioning telecommunication products 100 may include (e.g. as part of the hub module) a Value Added Services (VAS) integration module as shown in Fig. 2 and indicated generally by reference 201. The VAS integration module 201 is configured as a service, which is provided, e.g. based on a subscription, to one or more of the retail partners 230. According to an exemplary implementation, the VAS integration module 201 comprises a Value Added Services (VAS) interface 260 and a retailer specific VAS model or module 261. The retailer specific VAS module 261 is configured to provide services or functionality that gives a retailer alternate or extended capabilities. According to an embodiment, the retailer specific VAS module 261 comprises a digital signature module 262 configured to provide a digital signature service, a messaging module 264 configured to provide messaging and bulletin services for a retailer, and a device trade-in program module 266. The device trade-in program module 266 is configured to provide a retailer with the capability to secure a trade-in value or credit for the customer's old phone or device.

[00055] According to an embodiment, the networked system for requisitioning telecommunication products 100 may include an administrative processing module as shown in Fig. 2 and indicated generally by reference 202. The administrative process module 202 is configured to provide one or more of the retailers or retail partners 132 and/or one or more of the carrier partners 220 with administrative functions. As shown in Fig. 2, the administrative processing module 202 comprises a retailer interface 270, a carrier interface 272 and an administrative functions module 274. According to an exemplary implementation, the administrative functions module 274 is configured provide the following administrative functions/features: retailer and carrier subscriptions, subscription billing information, retailer on-boarding for sales representatives, product and release information, report generation, and issue management. According to an embodiment, the administrative functions module 274 comprises the following functional modules: a customer relationship management module 276, a customer order management module 278, a product management module 280, a report management module 282, an issue management module 284, and an "other" module 286 (configured to provide miscellaneous or additional administration functions). Each of the modules is configured to implement the particular administrative functions described above. According to an embodiment, the retailer interface 270 comprises two interface options: a retailer admin (GUI based) portal 271a and a retailer admin web service API module 271b. Similarly, the carrier interface 272 comprises two interface options: a carrier admin (GUI based) portal 273a and a carrier admin web service API module 273b. According to an exemplary implementation, the administrative functions are implemented as web services in the retailer admin web service API module 271b for the retail partners 132 (and for the carrier partners 122 in the carrier admin web service API module 273b). The web services may be implemented in a RESTful style or in a SOAP style, and the particular implementation details will be within the understanding of one skilled in the art. [00056] According to an embodiment, the networked system for requisitioning telecommunication products 100 may include a data loading and database module as shown in Fig. 2 and indicated generally by reference 204. The data loading module 204 is configured to upload reference data from the retailers or retail partners 132 and the carrier partners 122 and transform or restructure the uploaded data into a reference data structure that is stored locally. As shown in Fig. 2, the data loading module 204 comprises a data load ETL (Extract, Transform and Load) module 290 for loading data from the retail partners 132, a data load ETL module 291 for loading data from the carrier partners 122 and a database module 292. The ETL modules 290, 291 are invoked through a data upload web service or process in the retailer adapter module 130 (Fig. 2) and the carrier adapter module 120 (Fig. 2). The database module 292 is configured to store the data uploaded from the retail partners 132 and the carrier partners 122, and according to an embodiment comprises a database 294 and a content manager 296. The database 294 may also comprise a data cache as described in more detail below. The data loaded into the database module 292 includes customer account categorization/classification information (e.g. consumer, small business or corporate), mobile devices data, rate plans data, features data, contract terms information, promotions information, and/or network area code data. According to an embodiment the data is stored in data schema or model as shown in Fig. 3 and indicated generally by reference 300. The data schema 300 comprises static data 310, cache data 320, transaction data 330, and synchronization tables 340.

[00057] According to an exemplary implementation, the static data 310 comprises data that doesn't change, i.e. is relatively static or persistent, and comprises the following data structures or modules: a retailer data structure 311 having a "retailerlD" parameter; a retailer/carrier data structure 312 having a "retailerCarrierld" parameter and fields for "carrierld", "retailerld" and "transactionTypeld"; a carrier data structure 313 having a "carrierld" parameter; a sales representative data structure 314 having a "salesRepresentativeld" parameter and a "retailerld" field; a transaction type data structure 315 having a "transactionTypeld" parameter; a contract term data structure 316 having a "contractTermld" parameter and a "carrierld" field; a store data structure 317 having a "storeld" parameter, a "retailerld" field and an "addressld" field; and an address data structure 318 having an "addressld" parameter. [00058] According to an exemplary implementation, the cache data 320 comprises data that is uploaded from the retail partner(s) 230 and/or the carrier partner(s) 220 and utilized in a telecom transaction or other processing to achieve improved performance by eliminating the need to upload or reload the data from the retail partner or carrier partner. The cache data 320 comprises a device data structure 321 having a "deviceld" parameter and a "carrierld" field; a rate plan data structure 322 having a "ratePlanld" parameter and a "carrierld" field; a feature data structure 324 having a "featureld" parameter and a "carrierld" field; an availability rule data structure. As shown, the availability rule is linked to the device 321 and the rate plan 322 and contains rules that determine the availability of the device and/or the rate plan. According to another aspect, the data stored in the data cache 320 can be utilized in the execution of a telecom transaction. It will be appreciated that by utilizing cached data improved transaction performance can be achieved because all or some of the required transaction data does not need to be provided or retrieved downstream from the carrier partner system. According to another aspect, the respective carrier adapter modules 120 and retail adapter modules 130 are configured to synchronize and upload the reference data for the data cache 320, for example, as described below with reference to Fig. 18.

[00059] According to an exemplary implementation, the transaction data 330 comprises data this is utilized in a telecom transaction or other processing operations and does not necessarily need to be retained or stored in the database 294 (Fig. 2) after the processing or transaction is completed. The transaction data 330 comprises a transaction data structure 331 having a "transactionld" parameter, a "transactionTypeld" field, a "carrierld" field, a "salesRepresentativeld" field, a "storeld" field and a "customerld" field; a transaction item data structure 332 having a "transactionltemld" parameter, a "transactionld" field, a "customerld" field, a "deviceld" field, a "ratePlanld" field and a "contractTermld" field; a customer data structure 334 having a "customerld" parameter; an added feature data structure 336 having an "addedFeatureld" field with a "featureld" parameter and a "transactionltemld" parameter; and a port in detail data structure 338 having a "portlnltemld" parameter and a "transactionltemld" parameter. As shown, the transaction item data structure 332 is linked to the cached data in the device data structure 321 and the rate plan data structure 322 and also to static or persistent data in the contract term data structure 316, and the added feature data structure 336 is linked to feature data structure 324 in the cached data. [00060] According to an exemplary implementation, the synchronization tables 340 comprise an audit data table 342 and a metrics data table 344.

[00061] Reference is next made to Fig. 4, which shows in flowchart form processing steps for performing wireless transactions according to an embodiment of the present invention and indicated generally by reference by 400, and with reference to Figs. 6 to 16 which show screenshots of selected pages or screens generated by the system and the embedded logic flow for the wireless transaction in the form a graphical user interface or GUI according to an exemplary implementation. A wireless transaction comprises a login and authentication procedure indicated generally by reference 410, a new customer activation 420, an add new line procedure 422, a subscriber upgrade procedure 430, a device migration procedure 440, a device return procedure 460 and a device exchange procedure 470. The login and authentication procedure 410 starts at 411 and comprises invoking a Login Page in 412 and downloading a login page configured to allow a user, for example, a sales representative, to logon onto the system. In 413, a landing page is invoked and a selection is made of one the carrier partners 122 or a telecommunication product brand. According to an exemplary embodiment, the landing page comprises an input that is responsive to a user (for example, a sales representative at the retailer) for selecting one of the available carrier partners. An exemplary landing page is depicted in Fig. 6(a) and indicated by reference 650, and includes a user responsive input 660 configured to select one of the carriers, the available carriers being indicated individually by references 660a, 660b and 660c in Fig. 6(a). From the landing page 413, a determination is made whether the customer is a new customer or an existing customer 414, for example, utilizing a customer authentication page as shown in Fig. 6(b) and indicated by reference 600, which is configured with a "New Customer" selection input 610 and an "Existing Customer" selection input 620. If an existing customer, then a customer authentication operation in 416 is performed and an operation or transaction type is selected for the authenticated customer in 418, for example, utilizing a customer authenticated page 700 configured as shown in Fig. 7. (As will be described in more detail below, wireless or telecom transactions for an existing customer include, for example, a device upgrade, migration to a new device, device exchange, device return, SIM replacement or swap, and add a new line.) For a new customer, the new customer activation procedure 420 is invoked. [00062] As described above, the system 100 is configured to provide the capability for a retail partner to perform new customer activations on the multiple carrier networks. The new customer activation procedure 420 comprises creating a new customer page in 421, for example, utilizing an account type and customer information page 800 as depicted in Fig. 8. As shown in Fig. 8, the account and customer page 800 includes inputs 810 for selecting the "ACCOUNT TYPE" as "Postpaid" or "Prepaid" and as "Consumer" or "Business". The account and customer page 800 also includes "CUSTOMER INFO" fields 820, which are populated with the relevant customer information or data. According to another aspect, the account and customer page 800 may be configured to generate an "ADDRESS SELECTION" pop-up window as shown in Fig. 8(b) and indicated by reference 820. The address selection pop-up window 820 is generated in response to the input of the customer's postal code (for example, through the postal code lookup module 252 in the hub module 110, as described above with reference to Fig. 2), and presents the addresses associated with the postal code. The processing then proceeds to a common flow procedure indicated generally by reference 423 and according to exemplary implementation comprises processes or functions that are common to more than one procedure, for example, the common flow procedure 423 is common to the new customer activation procedure 420, the add new line procedure 422, the subscriber upgrade procedure 430, and the device migration procedure 440. In 431, the system is configured to generate a select device page 900 for example as shown in Fig. 9. The select device page 900 is configured to allow selection of a new device, or a SIM card only, as depicted in Fig. 9. If the customer is buying a new device, then the new device is selected from one of the devices presented on the page 900. According to another aspect, the select device page 900 is configured to show customer information, for example, customer account # and/or customer name, and the system can be configured to persist the customer information on one or more of the other pages. The system may also be configured to a customer conditions page as shown in Fig. 10 and indicated by reference 1000. The customer conditions page 1000 is configured to present additional restrictions on a customer (for example, based on a credit check executed by the credit check module 254 in the hub module 110, as shown in Fig. 2 and described above). According to an exemplary implementation, a security deposit may be required as indicated by reference 1010 and/or a monthly spending limit as indicated by reference 1020. If the customer is an existing customer (as determined in 418) who wants to add a new line, then processing flow or execution moves to the common flow procedure 423, and a device is selected in 431 (for example, using the page and GUI as depicted in Fig. 9), and then a choose/change phone number page is generated in 432, for example, having a form as shown in Fig. 11 and indicated by reference 1100. The select phone number page 1100 is configured to generate a new phone number for the customer as indicated by input selection 1110, or assign a phone number that is "ported" in as indicated by input selection 1120.

[00063] As shown in Fig. 4, the common flow procedure 423 comprises selecting a promotion (if available or applicable) in 450 and selecting a plan & features in 452. According to an embodiment, the system is configured to generate a select promotion page 1200 having a form as shown in Fig. 12, and a select plan and features page 1300 as shown in Fig. 13. The select promotion page 1200 is configured to display the available promotions (based on term, promotional code, etc.), for example, "UNLIMITED CHAT & DATA" 1210, "LOTS OF DATA" 1220 or "TALK TEXT & DATA" 1230, and is responsive to a user input for selecting one (or more) of the available promotions. The select plan and features page 1300 is configured to allow selection of a rate plan 1310 and additional features 1320. Once the plan and features have been selected (and any promotions applied), the system generates a review page in 453 and having a form, for example, as shown in Fig. 14 and indicated by reference 1400. The review page 1400 is configured to display the particulars of the selected device, the plan and any selected features, and a user responsive input for acceptance of the contract indicated by reference 1410. If acceptable to the customer, then the contract is presented to the customer for review and acceptance in 454, for example, utilizing a customer agreement page as depicted in Fig. 15 and indicated generally by reference 1500. According to an exemplary embodiment, the contract (i.e. the customer agreement) is displayed or presented in a window (which is configured to be scrollable) as indicated by reference 1510 in Fig. 15. According to an embodiment, the system is configured to allow the contract to be electronically (e.g. digitally) signed, for example, by activating a user input or control indicated by reference 1520 in Fig. 15. A confirmation page, for example, as shown in Fig. 16 and indicated by reference 1600, is generated in 456 and an email receipt is also sent to the customer in 458.

[00064] Referring to Fig. 4, if an existing customer is upgrading their device (as determined in 418), for example, based on upgrade eligibility, pricing and/or promotion, then the upgrade device procedure 430 is executed. As shown, the upgrade device procedure 430 comprises selecting a new device in 431. According to an exemplary embodiment, the upgrade device procedure 430 follows the common flow procedure 423 as described above, and involves upgrading the device and/or plan and/or features, for example, as described above with reference to 431, 452. If the existing customer is migrating (e.g. from a prepaid service to a postpaid service/from a postpaid service to a prepaid service, from one network type to another network type, or from one billing system to another billing system), then the migration flow procedure 440 is invoked. The migration flow procedure 440 follows the common flow procedure 423 as described above. If the migration involves a new device, then a device is selected in 431, and processing continues according to the common flow procedure 450, as described above. According to another aspect, the system is configured to provide multi-unit transactions for activations, upgrades and migrations.

[00065] Referring again to Fig. 4, if an existing customer is returning their device (as determined in 418), the return flow procedure 460 is executed. According to an embodiment, the system is configured to provide retail partners with the capability to perform device returns on multiple carrier networks. As shown, the return procedure 460 comprises determining if the subscriber is eligible for a return in 461, for example, based on return period and/or on the condition of the device being returned. If eligible, the device return is processed in 462 and a confirmation page is generated in 463. If the return involves cancellation of a contract, then a cancel contract operation is executed in 464. The system generates an email receipt in 465.

[00066] Referring back to Fig. 4, if an existing customer is exchanging a device (as determined in 418), then the exchange device flow procedure 470 is executed. According to an embodiment, the system is configured to provide retail partners with the capability to perform device exchanges on multiple carrier networks. The exchange flow procedure 470 comprises determining if the subscriber is eligible to exchange, for example, based on exchange period and/or device condition rules in 471. In 472, a determination is made whether the exchange is for a new device 474, for a new or different phone number 473, for a new promotion 486, for a plan or term change 489, or for a SIM card replacement or "swap" 490. If the SIM card is being replaced, then operation for selecting or generating a new SIM card is performed in 490, followed by generating a confirmation page in 484 and an email receipt in 492. If the exchange involves a new device, then a new device is selected in 474. In 476, a promotion is selected (if available or applicable) and then a plan & features are selected in 478. A page is then presented for review in 480, and if acceptable, a contract is accepted (e.g. electronically signed) in 482. The system generates a confirmation page in 484 and an email receipt sent to the customer in 492. If the exchange involves, a phone number, then a new phone number is selected in 473, and a confirmation page in 484 and an email receipt in 492 are generated. If the exchange comprises a new promotion, then the promotion is selected in 486. If the promotion includes a new device, then a new device is selected in 488 and further processing is executed according to 478, 480, 482, 484 and 492, as described above. If the exchange involves a change in the plan and/or terms, then the change is made in 489, and further processing is executed according to 478, 480, 482, 484 and 492, as described above.

[00067] Reference is next made to Fig. 5, which shows the process flow in a telecom transaction executed in accordance with an embodiment of the present invention. In the downstream direction, i.e. from the retail partner 230 to the carrier partner 220, the telecom transaction is commenced at one of the retail partners 230 (e.g. by a sales representative) by initiating a request (e.g. get a rate plan from the selected carrier partner 220) through the retailer adapter module 130 as indicated by reference 501. The system is configured to validate the request in 502 and transmit the request to the retailer bridge 232 in 504. The retailer bridge 232 transforms or translates the request into a common object form, i.e. a common object request, based on the hub module 110 as indicated by reference 506, and the common object request is passed to the hub module 110 for processing in 508. According to an embodiment, the hub module 110 is configured to determine if the information contained in the common object request is available in the data cache (i.e. stored in the database 294 as shown in Fig. 2). If the requested data is available in the data cache, then hub module 110 is configured with a process or function to retrieve the reference data (e.g. the rate plan) from the database 294 as indicated by reference 510 in Fig. 5. The reference data is returned to the hub module 110 as indicated by reference 512, and processed for the retail partner 230 as described below with reference to process flow steps 538 to 546. If the request cannot be fulfilled with data from the data cache in the database 294, then the hub module 110 is configured to generate a carrier operation from the common object request in 506 as indicated by reference 520, and the carrier operation is passed to the carrier bridge 221. The carrier bridge 221 is configured to transform or translate the carrier operation into a carrier operation request object as indicated by reference 522 and the carrier adapter module 120 is invoked for the carrier operation in 524, which is passed to the carrier partner 220 for processing in 526. In the upstream direction, i.e. from the carrier partner 220 to the retail partner 230, the carrier partner 220 invokes the carrier adapter module 120 in 530, and the response to the request, i.e. the request response, (e.g. rate plan or other carrier specific information or data) is passed to the carrier bridge 221 as indicated by reference 532. The carrier bridge 221 is configured to transform or convert the request response into a common object for processing/handling by the hub module 110 in 534 and the common object is passed to the hub module as indicated by reference 536. The processing at the hub module 110 may comprise applying logic and other operations to the common object as indicated by reference 538. The common object is then passed to the retailer bridge 232 in 540 and transformed or converted into a retailer response object as indicated by reference 542. The retailer bridge 232 passes the retailer response object to the retail adapter module 130 in 544. The retailer adapter module 130 incorporates the retailer response object into the telecom transaction being performed by the sales representative at the retail partner 230 as indicated by reference 546. If the request was fulfilled by retrieving data from the data cache 294 in 512 (as described above), then the process flow in steps 538, 540, 542, 544 and 546 are performed.

[00068] According to another aspect, the retailer bridge 271 (Fig. 2) is configured to execute administrative functions, such as collecting audit information and/or other types of persistent data, as indicated by reference 550, as shown in Fig. 5. The hub module 110 is configured to store some or all of the collected data in the database module 292 (Fig. 2) as indicated by reference 552.

[00069] Reference is next made to Fig. 17, which shows an exemplary deployment or implementation of the software -based systems or components comprising the networked system for requisitioning telecommunication products 100 according to an embodiment of the present invention. The deployment is "cloud-based" and indicated generally by reference 1700. The hub module 110 (as described above with references to Figs. 1 to 3) is implemented on a cloud based platform, for example, through a cloud provider, indicated generally by reference 1710. The cloud based platform 1710 couples through the cloud (i.e. the Internet) 1701 to computers 1720 associated with the carrier partners and to computers 1730 associated with each of the retail partners. According to an exemplary implementation, secure channels or protocols, such as, SSL, TLS and/or VPN are utilized. As shown in Fig. 17, the cloud based platform comprises a UI (User Interface) application server 1740 and a web content manager 1742, which are configured to provide the web services, web pages (including branding and page layouts), data upload/download operations associated with the retail adapter modules and the carrier adapter modules. According to an exemplary implementation, the cloud based platform 1710 includes a CDN (Content Delivery Network) component 1744 and a security component 1746. As shown in Fig. 17, the cloud platform 1710 may include a load balancer indicated generally by reference 1748 and configured to balance the flow of data between the UI application server 1740, the content delivery network 1764 and the computers or computing systems 1730 associated with the retail partners. The security component 1746 is configured to provide identity management, authentication/recovery of credentials for users associated with the system and other associated encryption/decryption and security functions. The cloud platform 1710 includes an integration services application server 1750, a database 1760 and a data cache 1770. The integration services application server 1750 interfaces with the UI application server 1740 and the carrier partner computer systems 1720 and is configured or implemented to execute the functions and features associated with the hub module 110, the VAS integration module 201, the administrative processing module 202 and/or the data loading module 204, as described above with reference to Fig. 2. The data cache 1770 is configured to cache data associated with a telecom transaction as described above with reference to Fig. 3. To facilitate the transfer of data between the database 1760 and the carrier computer systems 1720, the cloud platform 1710 includes a data loader, for example, implemented as batch ETL (Extract, Transform and Load) process, and indicated generally by reference 1762. As shown in Fig. 1, the cloud platform may also include a mail server 1780 and a reporting server 1782. The email server 1780 is configured to generate emails, for example, the email receipts 458, 492 described above with reference to Fig. 4. The reporting server 1782 is configured to generate reports, including, for example, reports generated based on the audit information asynchronously captured by the retailer bridge 232 as described above with reference to Fig. 5.

[00070] According to an embodiment, the integration services application server 1750 is configured with a data upload process for uploading selected data from one or more of the carrier partners 220 as shown in Fig. 19 and indicated generally by reference 1900. The data upload process 1900 is configured to upload selected data from the carrier partner 220 comprising reference data (i.e. rate plan information) as indicated by reference 1910. The reference data is uploaded to the database 1660 as indicated by reference 1920, and according to another aspect, some or all of the reference data is uploaded to the data cache 1670, as indicated by reference 1930. As described above with reference to Fig. 3, cache data may be utilized in a telecom transaction to achieve improved performance by eliminating the need to upload data (e.g. rate plan data) from the selected carrier partner 220 on a per transaction basis. In addition to the rate plan data (i.e. rate plan data 322 in Fig. 3), the reference data uploaded and stored in the data cache 1670 includes device data (i.e. device data 321 in Fig. 3) and/or features data (i.e. feature data 324 in Fig. 3).

[00071] Reference is next made to Fig. 18, which shows in diagrammatic form a redundant deployment 1800 of the networked system for requisitioning telecommunication products 100 according to an embodiment of the present invention. The redundant deployment 1800 comprises a master networked system 1810, a slave networked system 1820 and a load balancer 1830. The master networked system 1810 and the slave networked system 1820 each comprise a cloud based deployment 1700 as described above in Fig. 17. The master networked system 1810 and the slave networked system 1820 are each located in separate geographical regions, e.g. Region 1 and Region 2, and according to another aspect run on different cloud service providers. The load balancer 1830 is configured to balance the load across the two systems under normal operating conditions. In the event that one of the systems is not available, the other system is configured to continue operation for both regions.

[00072] The functionality and features associated with the cloud platform 1710 (Fig. 17), the hub module 110 (Figs. 1 and 2), the carrier adapter module 120 (Figs. 1 and 2) and the carrier bridge 221 (Fig. 2), the retailer adapter module 130 (Figs. 1 and 2) and the retailer bridge 232 (Fig. 2), and the associated application components or modules and other functional components or modules of the networked system for requisitioning telecommunication products 100 (Figs. 1 and 2), and/or the user interface screens or pages, for a telecom transactions indicated generally by references 600 to 1600 (in Figs. 6 to 16) as described above and in accordance with the embodiments may be implemented in the form of one or more software objects, code components, executable statements and machine readable code, computer programs or program modules in the server and/or the partner machines or computers. Further, at least some or all of the software objects, executable statements, machine readable computer code, components or modules can be hard-coded into processing units and/or read only memories or stored or embedded on computer readable media, storage media, or other digital storage media or non- volatile storage media in the computers, computer systems, servers and/or other components or modules depicted in the drawings. The specific implementation details and coding details for the computer programs, software objects and/or program modules will be within the knowledge and understanding of one skilled in the art.

[00073] Reference is next made to Fig. 20, which shows an exemplary implementation of a computer system 2000 according to an embodiment and suitable for the processing or hub module 110 (Fig. 1).

[00074] As shown, the computer system 2000 comprises a processor 2010 and a keyboard 2012 and mouse 2014 coupled to the processor 2010 via a system bus 2016. The keyboard 2012 and the mouse 2014, in one example, allow a user to introduce or provide inputs to computer system 2000 and the processor 2010. It will be appreciated that other suitable input devices may be used in addition to, or in place of, the mouse 2014 and/or the keyboard 2012. The computer system 2000 may be configured with other input/output (I/O) devices 2018 coupled to the system bus 2016, for example, a printer, audio/video (A/V) I/O, etc.

[00075] According to another aspect, the computer system 2000 may include a video memory module 2020, a main memory module 2022 and a mass storage device 2024, which are coupled to the system bus 2016. The mass storage device 2024 may include both fixed and removable media, such as magnetic, optical or magnetic optical storage systems and any other available mass storage technology. The system bus 2016 may be configured, for example, with address lines for addressing the video memory 2020 and/or the main memory 2024.

[00076] According to another aspect, the system bus 2016 may include a data bus for transferring data between and among the components, such as the processor 2010, the main memory 2022, the video memory 2020 and/or the mass storage device 2024. The video memory 844 may be a dual-ported video random access memory. One port of the video memory 2020, in one example, is coupled to a video amplifier 2026, which is used to drive one or more monitor(s) indicated generally by reference 2028. The monitor(s) 2028 may be any type of monitor suitable for displaying graphic images, such as a cathode ray tube monitor (CRT), flat panel, or liquid crystal display (LCD) monitor or any other suitable data presentation device. The processor 2010 may be implemented utilizing any suitable microprocessor or microcomputer.

[00077] According to another aspect, the computer system 2000 may include a communication interface 2030 which is coupled to the system bus 2016. The communication interface 2030 provides a two-way data communication coupling via a network link. For example, the communication interface 2030 may be a satellite link, a local area network (LAN) card, a cable modem, and/or wireless interface. In any such implementation, the communication interface 2030 is configured to send and/or receive electrical, electromagnetic or optical signals that carry digital data representing various types of information.

[00078] According to another aspect, code received by the computer system 2000 may be executed by the processor 2010 as the code is received, and/or stored in the mass storage 2024, or other non-volatile storage for later execution. In this manner, the computer system 2000 may obtain program code in a variety of forms. Program code may be embodied in any form of computer program product such as a medium configured to store or transport computer readable code or data, or in which computer readable code or data may be embedded. Examples of computer program products include CD-ROM discs, ROM cards, floppy disks, magnetic tapes, computer hard drives, servers on a network, and solid state memory devices. Regardless of the actual implementation of the computer system 2000, the data processing system may execute operations that allow for facilitating transactions between disparate retailers and disparate telecommunications carriers as described herein.

[00079] The present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. Certain adaptations and modifications of the invention will be obvious to those skilled in the art. Therefore, the presently discussed embodiments are considered to be illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.

Claims

WHAT IS CLAIMED IS:

1. A system for interfacing a plurality of retailer systems with a plurality of carrier systems for requisitioning a telecommunication product for a customer, said system comprising:

a network;

each of said plurality of retailer systems having a retailer interface component configured to operatively couple said retailer system to said network;

each of said plurality of carrier systems having a carrier interface component configured to operatively couple said carrier partner system to said network;

a processing module having a retailer communication interface operatively coupled to said network and configured to receive and transmit retailer process information for requisitioning the telecommunication product for the customer through one of the retailer systems;

said processing module having a carrier communication interface operatively coupled to said network and configured to receive carrier process information with any one of said plurality of carrier systems; and

said processing module having a transaction module configured to execute a requisitioning procedure utilizing said retailer process information and any carrier process information required for requisitioning the telecommunication product between one of said plurality of retailer systems and one of said with one of said carrier systems, wherein said carrier system is selected by a user.

2. The system as claimed in claim 1, further including a data cache, and said data cache being configured to store at least some of said carrier process information, and said transaction module being configured to utilize said carrier process information on as required basis from said data cache in the execution of said procedure for requisitioning the telecommunication product.

3. The system as claimed in claim 1, wherein said processing module includes a virtualization module configured to generate a virtual carrier partner based on one of said plurality of carrier systems, said virtual carrier partner being responsive to retailer process information received from one or more of said retailer systems, and said virtualization module being configured to generate a virtual response to said retailer process information based on characteristics of said carrier partner system.

4. The system as claimed in claim 1, wherein said processing module includes a value added services module configured to provide a service from a third party and said service being associated with the execution of said requisitioning procedure.

5. The system as claimed in claim 4, wherein said service comprises one of a customer address lookup and a customer credit check.

6. The system as claimed in claim 1 , wherein said retailer interface component for each of said plurality of retailer systems comprises a retail bridge module configured to convert said retailer process information into retailer common objects according to a common object model for processing by said processing module, and said carrier interface component for each of said plurality of carrier systems comprises a carrier bridge module configured to convert said carrier process information into carrier common objects according to said common object model for processing by said processing module.

7. The system as claimed in claim 6, wherein said retailer process information comprises one or more of data and an operation including a create operation, a read operation, an update operation and a delete operation.

8. The system as claimed in claim 7, wherein said carrier process information comprises one or more of data and an operation including a create operation, a read operation, an update operation and a delete operation.

9. The system as claimed in claim 6, wherein said processing module includes a component configured to convert one or more of said retailer common objects into corresponding carrier operation request objects, and said carrier bridge module being configured to invoke a carrier operation response from one of said plurality of carrier systems based on said carrier operation request object and said carrier object response being utilized in said requisitioning procedure initiated by one of said plurality of retailer systems.

10. The system as claimed in claim 9, wherein said processing module includes a data cache and a component configured determine if said carrier operation request object is available in said data cache, and configured to retrieve said carrier operation request directly from said data cache without invoking said carrier system.

11. The system as claimed in claim 10, wherein said carrier operation request objects comprise reference data associated with a telecom transaction for the requisitioning procedure.

12. The system as claimed in claim 10, wherein carrier operation request objects stored in said data cache comprise one or more of communication device data, rate plan data, feature data and availability data.

13. A computer- implemented method for requisitioning a telecommunication product for a customer at a retailer with one of a plurality of carrier systems, said computer-implemented method comprising:

generating a requisitioning request at a retailer system, and transmitting said requisitioning request to a processing hub, wherein said processing hub is operatively coupled to said retailer system in a network configuration;

transforming said requisitioning request into a corresponding common object according to a common object model at said processing hub;

selecting one of said plurality of carrier systems for requisitioning the telecommunication product;

transforming said common object request into a carrier request operation having a form compatible with said selected earner system;

invoking said selected carrier system based on said carrier request operation;

receiving a carrier request response from said selected carrier system;

transforming said carrier request response into a common object response;

transforming said common object response into a corresponding retailer response object;

transmitting said retailer response object to said retailer system; and

completing the requisitioning of the telecommunication product at said retailer system.

14. The computer-implemented method as claimed in claim 13, further including the step of determining if said common object request is available in a data cache at said processing hub, and retrieving said available common object request from said data cache without invoking said selected carrier system.

15. The computer- implemented method as claimed in claim 14, further comprising populating said data cache with a plurality of common object requests associated with at least one of said plurality of carrier systems.

16. The computer-implemented method as claimed in claim 13, further including the step of accessing a third party for obtaining a credit check associated with the customer.

17. A computing apparatus for performing a requisitioning operation for a telecommunication product between one of a plurality of retailers and one of a plurality of carriers, said computing apparatus comprising:

a processing module comprising a common retailer interface configured for each of the plurality of retailers, and said common retailer interface being configured to receive a request from one of the plurality of retailers;

said processing module comprising a common carrier interface configured for each the plurality of carriers;

said processing module comprising a common model, and said common retailer interface being configured to receive a request from one of the plurality of retailers and transform said request into a common object according to said common model;

said common carrier interface being configured to transform said common object into a carrier request; and

said processing module being configured to provide said carrier request to one of the plurality of carriers as part of the requisitioning operation.

18. The computing apparatus as claimed in claim 17, further including a cache, said cache being configured to store at least some of said carrier requests, and said processing module being configured to utilize said carrier requests from said cache in the requisitioning operation for the telecommunication product.

19. A computing apparatus for requisitioning a telecommunication product for a customer at one of a plurality of retailers from one of a plurality of carriers, said computing apparatus comprising:

a processing module comprising a common retailer interface configured for each of the plurality of retailers;

said processing module further including a graphical user interface comprising a common functional configuration for the plurality of retailers, and said graphical user interface having one or more inputs responsive to user inputs for defining a transaction for requisitioning the telecommunication product at the retailer and wherein one of said inputs comprises a carrier selection input for selecting one of the plurality of carriers; and

said common carrier interface being configured to transform said requisitioning transaction into a carrier requisition operation for performing the requisitioning of the telecommunication product at the selected carrier.

20. The computing apparatus for requisitioning a telecommunication product as claimed in claim 19, wherein said requisitioning transaction comprises one or more of an acquisition of a telecommunication product, a renewal of a telecommunication product, an upgrade of a telecommunication product, an exchange of a telecommunication product, a return of a telecommunication product, a migration of a telecommunication product, and a replacement of a telecommunication product.

21. The computing apparatus for requisitioning a telecommunication product as claimed in claim 20, wherein said telecommunication product comprises one or more of a device and a service.

22. A network based system for requisitioning a customer with a telecommunication product, said network based system comprising:

one or more retailers and each of said one or more retailers having a retailer adapter operatively coupled to the network;

one or more carriers and each of said one or more carriers having a carrier adapter operatively coupled to the network;

a hub having a retailer interface for coupling to said retailer adapter of each of said one or more retailers for transferring retailer process information over the network between said hub and any one of said retail partners, and further including a carrier interface for coupling to said carrier adapter of each of said one or more carrier partners for transferring carrier process information over the network between said hub and any one of said carriers; said hub including a component configured to transform said retailer process information into retailer common objects according to a common object model, and another component configured to transform said carrier process information into carrier common objects according to said common object model; and

said hub being configured to execute a telecom transaction based on said retailer common objects and said carrier common objects for requisitioning the customer at one of said one or more retailers with the telecommunication product selected from one of said one or more carriers.