<br/>- 30 -<br/>WHAT IS CLAIMED IS:<br/>1. A system for interfacing a plurality of retailer systems with a <br/>plurality of carrier systems <br/>for requisitioning a telecommunication product for a customer, said system <br/>comprising:<br/>a network;<br/>each of said plurality of retailer systems having a retailer interface <br/>component configured <br/>to operatively couple said retailer system to said network;<br/>each of said plurality of carrier systems having a carrier interface component <br/>configured <br/>to operatively couple said carrier partner system to said network;<br/>a processing module having a retailer communication interface operatively <br/>coupled to <br/>said network and configured to receive and transmit retailer process <br/>information for <br/>requisitioning the telecommunication product for the customer through one of <br/>the retailer <br/>systems;<br/>said processing module having a carrier communication interface operatively <br/>coupled to <br/>said network and configured to receive carrier process information with any <br/>one of said plurality <br/>of carrier systems; and<br/>said processing module having a transaction module configured to execute a <br/>requisitioning procedure utilizing said retailer process information and any <br/>carrier process <br/>information required for requisitioning the telecommunication product between <br/>one of said <br/>plurality of retailer systems and one of said with one of said carrier <br/>systems, wherein said carrier <br/>system is selected by a user.<br/>2. The system as claimed in claim 1, further including a data cache, and <br/>said data cache <br/>being configured to store at least some of said carrier process information, <br/>and said transaction <br/>module being configured to utilize said carrier process information on as <br/>required basis from said <br/>data cache in the execution of said procedure for requisitioning the <br/>telecommunication product.<br/>3. The system as claimed in claim 1, wherein said processing module <br/>includes a <br/>virtualization module configured to generate a virtual carrier partner based <br/>on one of said <br/>plurality of carrier systems, said virtual carrier partner being responsive to <br/>retailer process <br/>information received from one or more of said retailer systems, and said <br/>virtualization module<br/><br/>- 31 -<br/>being configured to generate a virtual response to said retailer process <br/>information based on <br/>characteristics of said carrier partner system.<br/>4. The system as claimed in claim 1, wherein said processing module <br/>includes a value <br/>added services module configured to provide a service from a third party and <br/>said service being <br/>associated with the execution of said requisitioning procedure.<br/>5. The system as claimed in claim 4, wherein said service comprises one of <br/>a customer <br/>address lookup and a customer credit check.<br/>6. The system as claimed in claim 1, wherein said retailer interface <br/>component for each of <br/>said plurality of retailer systems comprises a retail bridge module configured <br/>to convert said <br/>retailer process information into retailer common objects according to a <br/>common object model <br/>for processing by said processing module, and said carrier interface component <br/>for each of said <br/>plurality of carrier systems comprises a carrier bridge module configured to <br/>convert said carrier <br/>process information into carrier common objects according to said common <br/>object model for <br/>processing by said processing module.<br/>7. The system as claimed in claim 6, wherein said retailer process <br/>information comprises <br/>one or more of data and an operation including a create operation, a read <br/>operation, an update <br/>operation and a delete operation.<br/>8. The system as claimed in claim 7, wherein said carrier process <br/>information comprises one <br/>or more of data and an operation including a create operation, a read <br/>operation, an update <br/>operation and a delete operation.<br/>9. The system as claimed in claim 6, wherein said processing module <br/>includes a component <br/>configured to convert one or more of said retailer common objects into <br/>corresponding carrier <br/>operation request objects, and said carrier bridge module being configured to <br/>invoke a carrier <br/>operation response from one of said plurality of carrier systems based on said <br/>carrier operation<br/><br/> - 32 -<br/>request object and said carrier object response being utilized in said <br/>requisitioning procedure <br/>initiated by one of said plurality of retailer systems.<br/>10. The system as claimed in claim 9, wherein said processing module <br/>includes a data cache <br/>and a component configured determine if said carrier operation request object <br/>is available in said <br/>data cache, and configured to retrieve said carrier operation request directly <br/>from said data cache <br/>without invoking said carrier system.<br/>11. The system as claimed in claim 10, wherein said carrier operation <br/>request objects <br/>comprise reference data associated with a telecom transaction for the <br/>requisitioning procedure.<br/>12. The system as claimed in claim 10, wherein carrier operation request <br/>objects stored in <br/>said data cache comprise one or more of communication device data, rate plan <br/>data, feature data <br/>and availability data.<br/>13. A computer-implemented method for requisitioning a telecommunication <br/>product for a <br/>customer at a retailer with one of a plurality of carrier systems, said <br/>computer-implemented <br/>method comprising:<br/>generating a requisitioning request at a retailer system, and transmitting <br/>said <br/>requisitioning request to a processing hub, wherein said processing hub is <br/>operatively coupled to <br/>said retailer system in a network configuration;<br/>transforming said requisitioning request into a corresponding common object <br/>according <br/>to a common object model at said processing hub;<br/>selecting one of said plurality of carrier systems for requisitioning the <br/>telecommunication <br/>product;<br/>transforming said common object request into a carrier request operation <br/>having a form <br/>compatible with said selected carrier system;<br/>invoking said selected carrier system based on said carrier request operation;<br/>receiving a carrier request response from said selected carrier system;<br/>transforming said carrier request response into a common object response;<br/>transforming said common object response into a corresponding retailer <br/>response object;<br/><br/>-33-<br/>transmitting said retailer response object to said retailer system; and<br/>completing the requisitioning of the telecommunication product at said <br/>retailer system.<br/>12. The computer-implemented method as claimed in claim 11, further <br/>including the step of <br/>determining if said common object request is available in a data cache at said <br/>processing hub, <br/>and retrieving said available common object request from said data cache <br/>without invoking said <br/>selected carrier system.<br/>13. The computer-implemented method as claimed in claim 12, further <br/>comprising <br/>populating said data cache with a plurality of common object requests <br/>associated with at least <br/>one of said plurality of carrier systems.<br/>14. The computer-implemented method as claimed in claim 11, further <br/>including the step of <br/>accessing a third party for obtaining a credit check associated with the <br/>customer.<br/>15. A computing apparatus for performing a requisitioning operation for a <br/>telecommunication product between one of a plurality of retailers and one of a <br/>plurality of <br/>carriers, said computing apparatus comprising:<br/>a processing module comprising a common retailer interface configured for each <br/>of the <br/>plurality of retailers, and said common retailer interface being configured to <br/>receive a request <br/>from one of the plurality of retailers;<br/>said processing module comprising a common carrier interface configured for <br/>each the <br/>plurality of carriers;<br/>said processing module comprising a common model, and said common retailer <br/>interface <br/>being configured to receive a request from one of the plurality of retailers <br/>and transform said <br/>request into a common object according to said common model;<br/>said common carrier interface being configured to transform said common object <br/>into a <br/>carrier request; and<br/>said processing module being configured to provide said carrier request to one <br/>of the <br/>plurality of carriers as part of the requisitioning operation.<br/><br/>-34-<br/>16. The computing apparatus as claimed in claim 15, further including a <br/>cache, said cache <br/>being configured to store at least some of said carrier requests, and said <br/>processing module being <br/>configured to utilize said carrier requests from said cache in the <br/>requisitioning operation for the <br/>telecommunication product.<br/>17. A computing apparatus for requisitioning a telecommunication product <br/>for a customer at <br/>one of a plurality of retailers from one of a plurality of carriers, said <br/>computing apparatus <br/>comprising:<br/>a processing module comprising a common retailer interface configured for each <br/>of the <br/>plurality of retailers;<br/>said processing module comprising a common carrier interface configured for <br/>each the <br/>plurality of carriers;<br/>said processing module further including a graphical user interface comprising <br/>a common <br/>functional configuration for the plurality of retailers, and said graphical <br/>user interface having one <br/>or more inputs responsive to user inputs for defining a transaction for <br/>requisitioning the <br/>telecommunication product at the retailer and wherein one of said inputs <br/>comprises a carrier <br/>selection input for selecting one of the plurality of carriers; and<br/>said common carrier interface being configured to transform said <br/>requisitioning <br/>transaction into a carrier requisition operation for performing the <br/>requisitioning of the <br/>telecommunication product at the selected carrier.<br/>18. The computing apparatus for requisitioning a telecommunication product <br/>as claimed in <br/>claim 17, wherein said requisitioning transaction comprises one or more of an <br/>acquisition of a <br/>telecommunication product, a renewal of a telecommunication product, an <br/>upgrade of a <br/>telecommunication product, an exchange of a telecommunication product, a <br/>return of a <br/>telecommunication product, a migration of a telecommunication product, and a <br/>replacement of a <br/>telecommunication product.<br/>19. The computing apparatus for requisitioning a telecommunication product <br/>as claimed in <br/>claim 18, wherein said telecommunication product comprises one or more of a <br/>device and a <br/>service.<br/><br/>-35-<br/>20. A <br/>network based system for requisitioning a customer with a telecommunication <br/>product,<br/>said network based system comprising:<br/>one or more retailers and each of said one or more retailers having a retailer <br/>adapter <br/>operatively coupled to the network;<br/>one or more carriers and each of said one or more carriers having a carrier <br/>adapter <br/>operatively coupled to the network;<br/>a hub having a retailer interface for coupling to said retailer adapter of <br/>each of said one or <br/>more retailers for transferring retailer process information over the network <br/>between said hub <br/>and any one of said retail partners, and further including a carrier interface <br/>for coupling to said <br/>carrier adapter of each of said one or more carrier partners for transferring <br/>carrier process <br/>information over the network between said hub and any one of said carriers;<br/>said hub including a component configured to transform said retailer process <br/>information <br/>into retailer common objects according to a common object model, and another <br/>component <br/>configured to transform said carrier process information into carrier common <br/>objects according <br/>to said common object model; and<br/>said hub being configured to execute a telecom transaction based on said <br/>retailer common <br/>objects and said carrier common objects for requisitioning the customer at one <br/>of said one or <br/>more retailers with the telecommunication product selected from one of said <br/>one or more <br/>carriers.<br/>

<br/>CA 02833699 2013-10-11<br/>- -<br/>TITLE: METHOD <br/>AND SYSTEM FOR INTERFACING MULTIPLE RETAILER<br/>SYSTEMS AND MULTIPLE CARRIER SYSTEMS IN THE <br/>REQUISITION OF TELECOMMUNICATION PRODUCTS FOR <br/>CLIENTS OF THE RETAILERS<br/>FIELD OF THE INVENTION <br/>[0001] The <br/>present invention relates to computer systems, and more particularly to a<br/>networked system for connecting or integrating one or more retailer systems <br/>with one or more <br/>carrier systems in the requisitioning of products and services offered by the <br/>one or more carriers <br/>to one or more clients of the retailers.<br/>BACKGROUND OF THE INVENTION <br/>[0002] <br/>Consumers are relying more and more on retailers for the purchase or upgrade <br/>of<br/>mobile communication devices. Traditional systems utilized by retailers <br/>comprise a point-to-<br/>point configuration between the retailer system and the carrier system. Point-<br/>to-point integration <br/>between each retailer and the carrier partners of the retailer requires a <br/>substantial investment both <br/>in the system infrastructure for connecting with each carrier and also in the <br/>ongoing support <br/>including training, maintenance, upgrade and testing of each point-to-point <br/>connection. With the <br/>plethora of retailers offering mobile communication devices and the numerous <br/>carriers providing <br/>mobile telecommunication services, the investment and ongoing costs and <br/>resources required to <br/>maintain the system is effectively multiplied by the number of carriers <br/>partnered with a retailer <br/>and the number of retailers supported by the carrier. R will be appreciated <br/>that the direct and <br/>associated costs can be quite substantial.<br/>[0003] <br/>Accordingly, there remains a need for a scalable system and/or a system that<br/>allows multiple retailer systems to connect with multiple carrier systems in <br/>the requisitioning of <br/>services.<br/><br/>CA 02833699 2013-10-11<br/>- 2 -<br/>'<br/>BRIEF SUMMARY OF THE INVENTION<br/>[0004] The present invention provides a networked system for connecting one <br/>or more<br/>retailer systems to one or more carrier systems in the requisitioning of <br/>telecommunication <br/>products including devices and services offered by the one or more carriers to <br/>one or more <br/>clients of the retailer.<br/>100051 According to one aspect, the system provides a single integration <br/>point for a<br/>carrier to connect to a plurality of retailers.<br/>[0006] According to another aspect, the system provides a single <br/>integration point for a<br/>retailer to connect to a plurality of carriers.<br/>[0007] According to another aspect, the system is configured to isolate the <br/>retailers and<br/>the carriers from their respective development, test, release and support <br/>schedules or <br/>requirements and/or infrastructure.<br/>[0008] According to another aspect, the system is configured to be scalable <br/>and<br/>comprises a multi-tenant arrangement for retailers and carriers.<br/>[0009] In accordance with an embodiment, the present invention comprises a <br/>system for<br/>connecting a plurality of retailer systems with a plurality of carrier systems <br/>for requisitioning a <br/>telecommunication product for a customer, the system comprises: a network; <br/>each of the <br/>plurality of retailer systems having a retailer network interface configured <br/>to operatively couple <br/>the retailer system to the network; each of the plurality of carrier systems <br/>having a carrier <br/>network interface configured to operatively couple the carrier partner system <br/>to the network; a <br/>processing module having a retailer communication interface operatively <br/>coupled to the network <br/>and configured to receive and transmit retailer process information for <br/>requisitioning the <br/>communication device for the customer through one of the retailer systems; the <br/>processing <br/>module having a carrier communication interface operatively coupled to the <br/>network and <br/>configured to receive carrier process information with any one of the <br/>plurality of carrier systems; <br/>and the processing module having a transaction module configured to execute a <br/>requisitioning<br/><br/>CA 02833699 2013-10-11<br/>- 3 -<br/>procedure utilizing the retailer process information and any required carrier <br/>process information<br/>" for requisitioning the telecommunication product between one of the <br/>plurality of retailer systems<br/>and one of the carrier systems, wherein the carrier system is selected by a <br/>user.<br/>[000101 In accordance with another embodiment, the present invention <br/>comprises a<br/>computer-implemented method for requisitioning a telecommunication product for <br/>a customer at <br/>a retailer with one of a plurality of carrier systems, the computer-<br/>implemented method <br/>comprising: generating a requisitioning request at a retailer system, and <br/>transmitting the <br/>requisitioning request to a telecom processing hub, wherein the telecom <br/>processing hub is <br/>operatively coupled to the retailer system in a network configuration; <br/>transforming the <br/>requisitioning request into a corresponding common object according to a <br/>common object model <br/>at the telecom processing hub; selecting one of the plurality of carrier <br/>systems for requisitioning <br/>the telecommunication product, and the selection being based on a user input; <br/>transforming the <br/>common object request into a carrier request operation having a form <br/>compatible with the <br/>selected carrier system; invoking the selected carrier system based on the <br/>carrier request <br/>operation; receiving carrier request response from the selected carrier <br/>system; transforming the <br/>carrier request response into a common object response; transforming the <br/>common object <br/>response into a corresponding retailer response object; transmitting the <br/>retailer response object to <br/>the retailer system; and completing the requisitioning of the communication <br/>device at the retailer <br/>system.<br/>[000111 In accordance with a further embodiment, the present invention <br/>comprises a<br/>computing apparatus for performing a requisitioning operation for a <br/>telecommunication product <br/>between one of a plurality of retailers and one of a plurality of carriers, <br/>the computing apparatus <br/>comprises: a processing module comprising a common retailer interface <br/>configured for each of <br/>the plurality of retailers, and the common retailer interface being configured <br/>to receive request <br/>from one of the plurality of retailers; the processing module comprising a <br/>common carrier <br/>interface configured for each the plurality of carriers; the processing module <br/>comprising a <br/>common model, and the common retailer interface being configured to receive a <br/>request from <br/>one of the plurality of retailers and transform the request into a common <br/>object according to the <br/>common model; the common carrier interface being configured to transform the <br/>common object<br/><br/>CA 02833699 2013-10-11<br/>- 4 -<br/>into a carrier request; and the processing module being configured to provide <br/>the carrier request <br/>to one of the plurality of carriers as part of the requisitioning operation.<br/>[00012] In accordance with another embodiment, the present invention <br/>comprises a<br/>computing apparatus for requisitioning a telecommunication product for a <br/>customer at one of a <br/>plurality of retailers from one of a plurality of carriers, the computing <br/>apparatus comprises: a <br/>processing module comprising a common retailer interface configured for each <br/>of the plurality of <br/>retailers; the processing module comprising a common carrier interface <br/>configured for each the <br/>plurality of carriers; the processing module further including a graphical <br/>user interface <br/>comprising a common functional configuration for the plurality of retailers, <br/>and the graphical <br/>user interface having one or more inputs responsive to user inputs for <br/>defining a transaction for <br/>requisitioning the telecommunication product at the retailer and wherein one <br/>of the inputs <br/>comprises a carrier selection input for selecting one of the plurality of <br/>carriers; and the common <br/>carrier interface being configured to transform the requisitioning transaction <br/>into a carrier <br/>requisition operation for performing the requisitioning of the <br/>telecommunication product at the <br/>selected carrier.<br/>[00013] In accordance with yet another embodiment, the present invention <br/>comprises a<br/>network based system for requisitioning a customer with a telecommunication <br/>product, the <br/>network based system comprises: one or more retailers and each of the one or <br/>more retailers <br/>having a retailer adapter operatively coupled to the network; one or more <br/>carriers and each of the <br/>one or more carriers having a carrier adapter operatively coupled to the <br/>network; a hub having a <br/>retailer interface for coupling to the retailer adapter of each of said one or <br/>more retailers for <br/>transferring retailer information over the network between the hub and any one <br/>of the retailers, <br/>and further including a carrier interface for coupling to the carrier adapter <br/>of each of the one or <br/>more carrier partners for transferring carrier information over the network <br/>between the hub and <br/>any one of the carrier partners; the hub including a component configured to <br/>transform the <br/>retailer information into retailer common objects according to a common object <br/>model, and <br/>another component configured to transform the carrier information into carrier <br/>common objects <br/>according to the common object model; and the hub being configured to execute <br/>a telecom <br/>transaction based on the retailer common objects and the carrier common <br/>objects for<br/><br/>CA 02833699 2013-10-11<br/>- 5 -<br/>requisitioning the customer at one of the one or more retailers with the <br/>telecommunication <br/>product selected from the of said one or more carriers.<br/>[00014] Other aspects and features of the present invention will become <br/>apparent to those<br/>ordinarily skilled in the art upon review of the following description of <br/>specific embodiments of <br/>the invention in conjunction with the accompanying figures.<br/>BRIEF DESCRIPTION OF THE DRAWINGS <br/>[00015] Reference will now be made to the accompanying drawings, which <br/>show, by way<br/>of example, embodiments of the present invention, and in which:<br/>[00016] Fig. 1 shows in diagrammatic form a networked system for <br/>requisitioning<br/>telecommunication products according to an embodiment of the present <br/>invention;<br/>[00017] Fig. 2 shows in diagrammatic form an exemplary architecture for the <br/>networked<br/>system for requisitioning telecommunication products of Fig. 1 and in <br/>accordance with an <br/>embodiment of the present invention;<br/>[00018] Fig. 3 shows in schematic form a logical data model for the <br/>networked system for<br/>requisitioning telecommunication products according to an embodiment of the <br/>present invention;<br/>[00019] Fig. 4 shows in flowchart form processing steps for conducting <br/>telecom or<br/>wireless transactions according to an embodiment of the present invention;<br/>[00020] Fig. 5 is a process flow diagram showing processing steps executed <br/>in the<br/>networked system for requisitioning telecommunication products of Fig. 1, <br/>according to an <br/>embodiment of the present invention;<br/>[00021] Fig. 6(a) is a screenshot of a landing page according to an <br/>embodiment of the<br/>present invention;<br/>[000221 Fig. 6(b) is a screenshot of a customer authentication page <br/>according to an<br/>embodiment of the present invention;<br/><br/>CA 02833699 2013-10-11<br/>- 6 -<br/>[00023] Fig. 7 is a screenshot of a customer authentication page <br/>according to an<br/>" embodiment of the present invention;<br/>[00024] Figs. 8(a) and 8(b) are screenshots of a create new customer <br/>page according to an<br/>embodiment of the present invention;<br/>[00025] Fig. 9 is a screenshot of a select device page according to an <br/>embodiment of the<br/>present invention;<br/>[00026] Fig. 10 is a screenshot of a customer conditions and <br/>restrictions page according to<br/>an embodiment of the present invention;<br/>[00027] Fig. 11 is a screenshot of a select phone number page according <br/>to an<br/>embodiment of the present invention;<br/>[00028] Fig. 12 is a screenshot of a select promotion page according to <br/>an embodiment of<br/>the present invention;<br/>[00029] Fig. 13 is a screenshot of a select plan & features page <br/>according to an<br/>embodiment of the present invention;<br/>[00030] Fig. 14 is a screenshot of a review page according to an <br/>embodiment of the<br/>present invention;<br/>[00031] Fig. 15 is a screenshot of a customer agreement page according <br/>to an embodiment<br/>of the present invention;<br/>[00032] Fig. 16 is a screenshot of an order confirmation page according <br/>to an embodiment<br/>of the present invention;<br/>[00033] Fig. 17 shows in diagrammatic form an exemplary "cloud based" <br/>implementation<br/>or deployment of the networked system for requisitioning telecommunication <br/>products of Fig. 1;<br/>[00034] Fig. 18 shows in diagrammatic form an exemplary redundant <br/>system deployment<br/>for the networked system for requisitioning communication devices of Fig. 1 <br/>according to an <br/>embodiment of the present invention;<br/><br/>CA 02833699 2013-10-11<br/>- 7 -<br/>[00035] Fig. 19 is a process flow diagram showing processing steps for a <br/>data upload and<br/>data cache procedure according to an embodiment of the present invention; and<br/>[00036] Fig. 20 is a block diagram showing an exemplary implementation for <br/>a computer<br/>system suitable for the requisitioning system of Fig. 1.<br/>DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT<br/>[00037] Reference is first made to Fig. 1, which shows in diagrammatic form <br/>a networked<br/>system for requisitioning telecommunication products by integrating one or <br/>more retailers with <br/>one or more carriers according to the present invention and indicated by <br/>reference 100. <br/>Embodiments according to the present invention are described in the context of <br/>one or more <br/>retailers providing customers of the retailer with activation, renewal, <br/>upgrade, exchange, return, <br/>migration, subscriber identity module (SIM) replacement, and the like services <br/>for <br/>telecommunication products, such as mobile communication devices (for example, <br/>smart <br/>phones), for one or more carriers based on services provided by the carrier, <br/>for example, cellular <br/>service, data service and other value added services. It will however be <br/>appreciated that <br/>embodiments according to the present invention may be used in other <br/>applications where a <br/>customer purchases or subscribes to services through one or more retailers and <br/>the services are <br/>made available from one or more service providers.<br/>[00038] As shown in Fig. 1, the networked system for requisitioning <br/>telecommunication<br/>products 100 comprises a hub module 110. The hub module 110 comprises a <br/>processing module <br/>and is configured to connect or integrate one or more carrier adapter modules <br/>120, indicated <br/>individually by references 120a, 120b...120m with one or more retailer adapter <br/>modules 130, <br/>indicated individually by references 130a, 130b,...130n in Fig. 1. Each of the <br/>carrier adapter <br/>modules 120 is associated with or deployed with a carrier or carrier partner <br/>122, indicated <br/>individually by references 122a, 122b,...122m. Each of the retailer adapter <br/>modules 130 is <br/>associated with or deployed with a retailer or retail partner 132, indicated <br/>individually by <br/>references 132a, 132b,...132n. According to an exemplary implementation, each <br/>of the plurality <br/>of retailers 132 may be an independently operated retail store not associated <br/>with any of the <br/>plurality of the carrier partners 122. According to another aspect, each of <br/>the plurality of<br/><br/>CA 02833699 2013-10-11<br/>- 8 -<br/>=<br/>retailers, i.e. retail partners, 132 may have a partnership or relationship <br/>with one or more of the <br/>plurality of carrier partners 122. According to another exemplary <br/>implementation, each <br/>partnership between one of the plurality of retail partners 132 and one of the <br/>plurality of carrier <br/>partners 122 may provide for the sale of portable electronic devices, among <br/>other things, by the <br/>retail partners 132 and/or the sale of telecommunications services provided by <br/>the carrier <br/>partners 122.<br/>1000391 In one example, the retail partner 132b may sell portable <br/>electronic devices<br/>together with a wireless telecommunications service plan, both provided by the <br/>carrier partner <br/>122a. The purchase price of the portable electronic device may be subsidized <br/>by the carrier <br/>partner 122a in some instances. The portable electronic device sold by the <br/>retail partner 132b <br/>may have been provided to the retail partner 132b by the carrier partner 122a <br/>in some examples, <br/>in which case the sale of the portable electronic device and the wireless <br/>telecommunications <br/>service plan both may need to be coordinated with the carrier partner 122a. In <br/>other examples, <br/>the retail partner 132b may have obtained the portable electronic device <br/>directly from the <br/>manufacturer of the portable electronic device, in which case the retail <br/>partner 132b may not <br/>need to coordinate the sale of the device itself with the carrier 122a, but <br/>will still need to <br/>coordinate the sale of the telecommunications service plan (including any <br/>subsidy for the device <br/>paid for by the carrier 122a, if applicable). In either example, the retail <br/>partner 132b may also <br/>need to coordinate the activation of the portable electronic device on the <br/>carrier's <br/>telecommunications network, the enrollment of the customer into the <br/>telecommunications <br/>service plan, the association between the portable electronic device and the <br/>purchased <br/>telecommunications service plan, and so forth. In general, any sale by the <br/>retailer partner 132b <br/>may involve one or more transactions with the carrier partner 122a. The <br/>transactions may <br/>include various requests and responses to those requests, as described in more <br/>detail below.<br/>(000401 As will be described in more detail below, the hub module 110 is <br/>configured to<br/>execute a layer of services and modules that are common to the retail partners <br/>132 and to the <br/>carrier partners 122. The retail partners 132 provide the details of <br/>transaction requests to the hub <br/>module 110 through their own instance on the retail adapter module, and are <br/>unaffected by any <br/>changes or operations performed by the carrier partner(s) 122 until the retail <br/>partner 132 so <br/>chooses, as described in more detail below. Similarly, if the retail <br/>partner(s) 132 make changes to<br/><br/>CA 02833699 2013-10-11<br/>- 9 -<br/>their connection or integration with the hub module 110 that do not <br/>necessarily require any <br/>change for the carrier partner 122, the changes can be implemented and tested <br/>without <br/>involvement by the carrier partner(s) 122, as described in more detail below. <br/>The carrier adapter <br/>modules 120 are configured to provide the services and functions required for <br/>a telecom <br/>transaction with one of the retail partners 132 and transform them into a <br/>common model for <br/>processing by the hub model 110, as described in more detail below. Similarly, <br/>the retailer <br/>adapter modules 130 are configured to provide the services and functions <br/>required for a telecom <br/>transaction with one of the retail partners 132 and transform them into a <br/>common model for <br/>processing by the hub model 110, as described in more detail below.<br/>[00041] <br/>According to an embodiment, the hub module 110 comprises a "cloud-based"<br/>implementation, and is configured to couple through the Internet to the <br/>carrier adapter modules <br/>120 and to the retailer adapter modules 130. In the context of the present <br/>description, the carrier <br/>adapter modules 120 comprise an interface and control module that couples each <br/>carrier <br/>requisitioning system with the hub module 110 and is configured provide <br/>customer functions <br/>(e.g. activations, port-in activation, upgrades, renewals, migrations and <br/>swaps, multi-unit <br/>transactions, future dated transactions, exchanges, returns, and related <br/>functions), integration, <br/>testing and other support functions, as will be described in more detail <br/>below. The retailer <br/>adapter modules 130 comprise an interface and control module that couples each <br/>of the retail <br/>partners 132 (i.e. retailer activation system 230 (Fig. 2)) with the hub <br/>module 110, and is <br/>configured to provide the retail partner or retailer activation system 230 <br/>(Fig. 2) with functions, <br/>such as, new customer activation and/or upgrade functions, and the like, with <br/>a selected carrier <br/>220 (Fig. 2). In addition, the retailer adapter module 130 is configured to <br/>provide the retail <br/>partner 132 with integration, testing and other support functions, as will be <br/>described in more <br/>detail below. According to another aspect, the hub module 110 is configured to <br/>allow one of the <br/>retail partners 132, for example, a retailer of mobile phones (e.g. BestBuy or <br/>Future Shop), to <br/>integrate the retailer's computer system with the hub module 110 and then be <br/>configured to <br/>conduct business and transactions through the hub module 110 with the one or <br/>more carrier <br/>partners 122 (e.g. Bell, Rogers) who are also integrated with the hub module <br/>110, as will be <br/>described in more detail below. Similarly, the hub module 110 is configured to <br/>allow the carrier <br/>partner 122, for example, a cellular service provider (e.g. ATT, Verizon), to <br/>integrate the <br/>carrier's requisitioning system with the hub module 110 through the carrier <br/>adapter module 120<br/><br/>CA 02833699 2013-10-11<br/>- 10 -<br/>and then be configured to provide through the hub module 110 requisitioning <br/>and/or upgrade, <br/>and other related transactions, of the carrier's services to customers of any <br/>one of the retail <br/>partners 132, as will be described in more detail below.<br/>[00042] Reference is next made to Fig. 2, which shows an architecture <br/>comprising logical<br/>and functional modules for the networked system for requisitioning <br/>telecommunication products <br/>according to an embodiment of the present invention and indicated generally by <br/>reference 200. <br/>As shown in Fig. 2, each of the retailer adapter modules 130 comprises a <br/>retailer adapter 231, <br/>indicated individually references 231a,. ..231n, and a retailer bridge 232, <br/>indicated individually <br/>by reference 232a...232n. The retailer adapter 231 is configured to provide an <br/>interface between <br/>the retail partner 132 and the hub or processing module 110. According to <br/>another aspect, the <br/>retailer adapter 231 may be configured to provide a graphical user interface <br/>(GUI) comprising <br/>one or more windows or pages, for example, as described in more detail below. <br/>The retailer <br/>bridge 232 is configured to transform data flow or retailer process <br/>information, e.g. control <br/>commands, status requests, customer information and requisitioning data, to <br/>and from the retailer <br/>specific interface (as configured in the retailer adapter module 130) into a <br/>form or format <br/>suitable for input/processing by a common model module in the hub module 110. <br/>According to <br/>an embodiment, the retailer adapter module 130 is configured to provide the <br/>following <br/>functionality and/or features:<br/>(1) sales management flow, e.g. sale, activation, upgrade of mobile <br/>communication <br/>devices to customers of the retail partner<br/>(2) point of sale (POS) functions<br/>(3) inventory management<br/>(4) document management ¨ documents generated during a telecom transaction <br/>are <br/>sent from the hub module 110 to the retail partner through the retailer <br/>adapter <br/>module 130 and the retailer bridge 232<br/>(5) data warehouse ¨ data feeds and other information is pushed by the <br/>retailer <br/>adapter module 130 through the retailer bridge 232 and stored by the retail <br/>partner, e.g. in a data warehouse<br/><br/>CA 02833699 2013-10-11<br/>- 11 -<br/>[000431 According to another aspect, the retailer adapter modules 130 <br/>are configured in a<br/>' multi-tenant arrangement and each retail partner is provided with the <br/>capability to configure the<br/>user interface for the retailer adapter module 130 to satisfy requirements of <br/>the retailer. <br/>According to an embodiment, the retailer adapter modules 130 may be configured <br/>with one or <br/>more of the following functions or features:<br/>(1) branding ¨ configured according to corporate identity, retailer styles, <br/>images <br/>and/or fonts<br/>(2) pages layout ¨ configurable header, footer, menu and/or body<br/>(3) business rules ¨ configurable utilizing scripted rules and/or decision <br/>tables<br/>(4) configuration parameters ¨ static configuration and/or real-time <br/>configuration<br/>(5) Web content ¨ configurable images, text, messages, email/notification <br/>templates, <br/>documents and/or campaigns<br/>[000441 As also shown in Fig. 2, each of the carrier adapter modules <br/>120a to 120m<br/>comprises an associated carrier bridge 221, indicated individually by <br/>references 221a to 221m, <br/>and an associated carrier adapter 223, indicated individually by references <br/>223a to 223m. The <br/>carrier bridge 221 is configured to transform data flow or carrier process <br/>information, e.g. <br/>control commands, status requests, customer and requisitioning data and <br/>information, to and <br/>from the carrier partner interface (as configured in the carrier adapter <br/>module 120) into a form or <br/>format suitable for input/processing by the common model module in the hub <br/>module 110 in the <br/>upstream direction, and in the downstream direction into form or format <br/>suitable for input or <br/>processing by the requisitioning system utilized by or resident at the carrier <br/>partner 120.<br/>1000451 According to an exemplary embodiment, the retailer adapter <br/>module 130<br/>comprising both the retailer adapter 231 and the retailer bridge 232 is <br/>configured or deployed at <br/>the retail partner 132, for example, on the retail computer system and <br/>operatively coupled to the <br/>processing module 110 through a network, e.g. the "cloud". Similarly, <br/>according to an exemplary <br/>embodiment, the carrier adapter module 120 comprising both the carrier adapter <br/>223 and the <br/>carrier bridge 221 is configured or deployed at the carrier partner 120, for <br/>example, on the carrier<br/><br/>CA 02833699 2013-10-11<br/>- 12 -<br/>computer system(s) and operatively coupled to the processing module 110 <br/>through the network,<br/>' e.g. the "cloud". According to another exemplary embodiment, the retailer <br/>adapter module 130<br/>comprising both the retailer adapter 231 and the retailer bridge 232 are <br/>configured or deployed at <br/>the hub or processing module 110 and operatively coupled to the respective <br/>retail partners 132 <br/>via the network or cloud. Similarly, according to another exemplary <br/>embodiment, the carrier <br/>adapter module 120 comprising both the carrier adapter 223 and the carrier <br/>bridge 221 are <br/>configured or deployed at the hub or processing module 110 and operatively <br/>coupled to the <br/>respective carrier partners 122 via the network or cloud. According to another <br/>exemplary <br/>embodiment or implementation, the retailer adapter 231 is configured or <br/>deployed at the retail <br/>partner 132 and the retailer bridge 232 is configured or deployed at the hub <br/>module 110 and <br/>operatively coupled through the network or cloud. Similarly and according to <br/>another exemplary <br/>embodiment or implementation, the carrier adapter 223 is configured or <br/>deployed at the carrier <br/>partner 120 and the carrier bridge 221 is configured or deployed at the hub <br/>module 110 and <br/>operatively coupled through the network or cloud.<br/>1000461 According to an embodiment and as shown in Fig. 2, the hub <br/>module 110<br/>comprises a sales common model module 240 and a carrier specific VAS (Value <br/>Added <br/>Services) module 250, which arc configured to implement processing operations <br/>associated with <br/>the requisitioning of a telecommunication product. In the context of the <br/>present description, a <br/>telecommunication product comprises wireless devices and services. However, <br/>the <br/>telecommunication products may also include other devices and/or services <br/>offered by a carrier <br/>partner, for example, Internet devices and services, landline devices and <br/>services, and TV/cable <br/>devices and services. Further, the requisitioning of a wireless <br/>telecommunication product <br/>comprises one or more of the following requisitioning transactions or <br/>operations, acquisition <br/>(activation) of a new device, for example, a wireless telecommunication <br/>device, or a SIM card, <br/>renewal, upgrade, exchange, return, SIM card replacement and migration. The <br/>sales common <br/>model module 240 is configured to provide the functions associated with the <br/>requisitioning of a <br/>telecommunication product for the carrier partners 220 and the retailer <br/>partners 230.<br/>1000471 According to an exemplary implementation, the sales common <br/>model module 240<br/>comprises a sales flow management module 242, a sales information management <br/>module 244, <br/>and a sales virtualization module 246. The sales common model module 240 may <br/>also include<br/><br/>CA 02833699 2013-10-11<br/>- 13 -<br/>another functional module indicated generally by reference 248 which is <br/>configured to provide<br/>' other or future functions associated with telecommunication products.<br/>= [00048] The sales flow management module 242 is configured to <br/>support the processing<br/>performed or executed in a retailer telecom sales flow process, e.g. the <br/>purchase and activation of <br/>a new mobile communication device by a customer at one of the retailer <br/>partners 230. According <br/>to an exemplary implementation, the retailer telecom sales flow process <br/>comprises the following <br/>operations or processes:<br/>(1) Customer Management comprising: creation of an account/subscriber; <br/>modification of an account/subscriber; cancellation of an account/subscriber; <br/>authentication of an account/subscriber; credit check of an account; and an <br/>account/subscriber eligibility check. These processes are managed through the <br/>requisitioning system of the selected or associated carrier partner 220.<br/>(2) Customer Selection Management comprising: device, network area code, <br/>rate <br/>plan, feature(s) and/or promotions, as selected by the customer at the <br/>retailer <br/>partner. These processes or operations are managed through the operation of <br/>the <br/>sales information management module 244.<br/>(3) Telecom Functions comprising: reserve and release phone number; special <br/>promotion retrieval; customer selection validated against customer profile; <br/>price <br/>calculation; order submission; and/or service agreement creation. These <br/>processes <br/>or operations are managed through the requisitioning system of the selected or <br/>associated carrier partner 220.<br/>In addition, the system 100 can be configured to provide additional features <br/>or services, such as <br/>electronic or digital signature capture and final service agreement <br/>generation, subscriber address <br/>validation, subscriber device trade-in and/or service transitional data <br/>management, as will be <br/>described in more detail below.<br/>1000491 <br/>Referring again to Fig. 2, the sales information management module 244 is<br/>configured to manage sales reference information associated with a telecom <br/>transaction.<br/><br/>CA 02833699 2013-10-11<br/>- 14 -<br/>According to an exemplary implementation, the sales reference information <br/>comprises: account <br/>type/sub-type as defined in the carrier system; network area codes; <br/>country/province (state); <br/>device; rate plan; feature(s); and/or promotions. Since the sales reference <br/>information is <br/>relatively stable and maintained in the carrier system, the sales reference <br/>information can be <br/>uploaded by the carrier partner and maintained in a database as will be <br/>described in more detail <br/>below.<br/>[00050] The sales virtualization module 246 is configured to provide <br/>support for any one<br/>of the retailer partners 132, such as testing and integration. According to an <br/>embodiment, the <br/>virtualization module 246 is configured to generate a virtual model or <br/>"virtualization" of one or <br/>more of the carrier systems. According to an exemplary implementation, the <br/>sales virtualization <br/>module 246 is configured to allow the retailer partner 132 to test the <br/>retailer's system in a "non-<br/>production" environment, for example, if the carrier system is down or off-<br/>line. According to an <br/>embodiment, the hub module 110 receives a web service request containing a <br/>virtualization <br/>indicator from the retail adapter module 130 for one or more of the retailer <br/>partners 132. The hub <br/>module 110 generates a web service response and the virtualization module 246 <br/>is invoked and a <br/>"virtual carrier" is generated and made available to the retail partner 132, <br/>for example, <br/>comprising a test structure for testing changes (e.g. new services or <br/>functions) that the retail <br/>partner 132 has implemented in their system and/or the retail adapter module <br/>130. It will be <br/>appreciated that this allows a retail partner to test their system <br/>independently of the carrier <br/>partner<br/>[00051] According to an embodiment, the hub module 110 may include the <br/>carrier<br/>specific VAS (Value Added Services) module as introduced above and indicated <br/>by reference <br/>250 in Fig. 2. The carrier specific VAS module 250 is configured to provide <br/>value added services <br/>that are specific or associated with a specific carrier partner or a third <br/>party vendor 225, indicated <br/>individually by references 225a, 225b in Fig. 2. The third party vendor 225 <br/>interfaces to the hub <br/>module 110 through a vendor interface module indicated by reference 223 in <br/>Fig. 2. The vendor <br/>interface module 223 is configured to provide the capability to transmit <br/>and/or receive <br/>information (e.g. data, transaction requests, transaction responses) between <br/>the third party vendor <br/>225 and the hub module 110. According to an embodiment, the carrier specific <br/>VAS module 250 <br/>comprises a postal code/zip code lookup module 252 and a credit check module <br/>254. According<br/><br/>CA 02833699 2013-10-11<br/>- 15 -<br/>to an exemplary implementation, the third party vendor 225 provides a postal <br/>code/zip code <br/>lookup service. According to another exemplary implementation, the third party <br/>vender 225 <br/>provides a credit check service. According to an embodiment, the value added <br/>services are <br/>provided to support the sales flow of devices for a carrier partner, and <br/>invoked internally by the <br/>hub module 110 without direct intervention by the retail partner 132. For <br/>example, in the <br/>processing of a new activation request from one of the retail partners 132, <br/>the hub module 110 <br/>activates the carrier specific VAS module 250 and the postal code/zip lookup <br/>module 252 is <br/>invoked to confirm the postal code of a customer purchasing a mobile phone <br/>(e.g. based on the <br/>residential address of the customer) through the third party vender 225, <br/>and/or the credit check <br/>module 254 is invoked to perform a credit check on the customer through <br/>another third party <br/>vendor. The outcomes of the VAS services are then passed to the retail partner <br/>132 (and the <br/>carrier partner 122) as part of the processing of the telecom transaction.<br/>[000521 According to an embodiment, the retailer adapter module 130 is <br/>implemented as a<br/>Web service API (Application Program Interface). The retail adapter module 130 <br/>comprises a set <br/>of telecom sales Web services that allow the retail partner to fulfill an end-<br/>to-end telecom <br/>transaction between the retailer and one of the carriers. According to another <br/>aspect, each Web <br/>service API is further customizable for each retailer. According to another <br/>aspect, the Web <br/>services may be implemented utilizing RESTful style or SOAP style, as will be <br/>understood by <br/>one skilled in the art. According to another embodiment, the retailer adapter <br/>may be <br/>implemented as a retailer web application 235 with a GUI (Graphical User <br/>Interface) and a <br/>retailer bridge 232 as also shown in Fig. 2. According to an exemplary <br/>implementation or <br/>embodiment, the graphical user interface or GUI for the retailer web <br/>application 235 includes <br/>one or more pages or screens as described in more detail below. According to <br/>an exemplary <br/>implementation, the retailer web application 235 is configured to execute on a <br/>web browser <br/>platform, such as Internet ExplorerTM or SafariTM browsers, and provide a <br/>retailer with the <br/>functions required to perform a telecom transaction as described below.<br/>1000531 According to another embodiment, the retailer adapter module 130 <br/>may be<br/>integrated with other retailer systems, such as, point of sale, inventory, <br/>document and web <br/>content management, reporting, and/or human resources. Referring back to Fig. <br/>2, the networked <br/>system for requisitioning telecommunication products 100 may include a retail <br/>system<br/><br/>CA 02833699 2013-10-11<br/>- 16<br/>integration module according to an embodiment and indicated generally by <br/>reference 222. The <br/>retail system integration module 222 may be configured in the hub or <br/>processing module 110 and <br/>comprises a POS (Point Of Sale) integration module 224 and a retailer <br/>inventory integration <br/>module 226. According to an embodiment, the POS integration module 224 is <br/>configured to <br/>function with the retailer adapter module 130 and transfer initial transaction <br/>and subscriber <br/>information or data. The retail adapter module 130 communicates with the POS <br/>integration <br/>module 224 and transfers sales process information back to the POS integration <br/>module 224. The <br/>retailer inventory integration module 226 is configured to communicate with <br/>the retail adapter <br/>module 130 (i.e. through the retailer bridge 232) for performing inventory <br/>functions, such as, <br/>inventory lookup, inventory validation and adjustments in the retail partner's <br/>inventory system.<br/>[00054] According to an embodiment, the networked system for requisitioning<br/>telecommunication products 100 may include (e.g. as part of the hub module) a <br/>Value Added <br/>Services (VAS) integration module as shown in Fig. 2 and indicated generally <br/>by reference 201. <br/>The VAS integration module 201 is configured as a service, which is provided, <br/>e.g. based on a <br/>subscription, to one or more of the retail partners 230. According to an <br/>exemplary <br/>implementation, the VAS integration module 201 comprises a Value Added <br/>Services (VAS) <br/>interface 260 and a retailer specific VAS model or module 261. The retailer <br/>specific VAS <br/>module 261 is configured to provide services or functionality that gives a <br/>retailer alternate or <br/>extended capabilities. According to an embodiment, the retailer specific VAS <br/>module 261 <br/>comprises a digital signature module 262 configured to provide a digital <br/>signature service, a <br/>messaging module 264 configured to provide messaging and bulletin services for <br/>a retailer, and a <br/>device trade-in program module 266. The device trade-in program module 266 is <br/>configured to <br/>provide a retailer with the capability to secure a trade-in value or credit <br/>for the customer's old <br/>phone or device.<br/>[00055] According to an embodiment, the networked system for requisitioning<br/>telecommunication products 100 may include an administrative processing module <br/>as shown in <br/>Fig. 2 and indicated generally by reference 202. The administrative process <br/>module 202 is <br/>configured to provide one or more of the retailers or retail partners 132 <br/>and/or one or more of the <br/>carrier partners 220 with administrative functions. As shown in Fig. 2, the <br/>administrative <br/>processing module 202 comprises a retailer interface 270, a carrier interface <br/>272 and an<br/><br/>CA 02833699 2013-10-11<br/>- 17 -<br/>administrative functions module 274. According to an exemplary implementation, <br/>the<br/>administrative functions module 274 is configured provide the following <br/>administrative<br/>. functions/features: retailer and carrier subscriptions, subscription <br/>billing information, retailer on-<br/>boarding for sales representatives, product and release information, report <br/>generation, and issue <br/>management. According to an embodiment, the administrative functions module <br/>274 comprises <br/>the following functional modules: a customer relationship management module <br/>276, a customer <br/>order management module 278, a product management module 280, a report <br/>management <br/>module 282, an issue management module 284, and an "other" module 286 <br/>(configured to <br/>provide miscellaneous or additional administration functions). Each of the <br/>modules is configured <br/>to implement the particular administrative functions described above. <br/>According to an <br/>embodiment, the retailer interface 270 comprises two interface options: a <br/>retailer admin (GUI <br/>based) portal 271a and a retailer admin web service API module 271b. <br/>Similarly, the carrier <br/>interface 272 comprises two interface options: a carrier admin (GUI based) <br/>portal 273a and a <br/>carrier admin web service API module 273b. According to an exemplary <br/>implementation, the <br/>administrative functions are implemented as web services in the retailer admin <br/>web service API <br/>module 271b for the retail partners 132 (and for the carrier partners 122 in <br/>the carrier admin web <br/>service API module 273b). The web services may be implemented in a RESTful <br/>style or in a <br/>SOAP style, and the particular implementation details will be within the <br/>understanding of one <br/>skilled in the art.<br/>1000561 According to an embodiment, the networked system for <br/>requisitioning<br/>telecommunication products 100 may include a data loading and database module <br/>as shown in <br/>Fig. 2 and indicated generally by reference 204. The data loading module 204 <br/>is configured to <br/>upload reference data from the retailers or retail partners 132 and the <br/>carrier partners 122 and <br/>transform or restructure the uploaded data into a reference data structure <br/>that is stored locally. As <br/>shown in Fig. 2, the data loading module 204 comprises a data load ETL <br/>(Extract, Transform and <br/>Load) module 290 for loading data from the retail partners 132, a data load <br/>ETL module 291 for <br/>loading data from the carrier partners 122 and a database module 292. The ETL <br/>modules 290, <br/>291 are invoked through a data upload web service or process in the retailer <br/>adapter module 130 <br/>(Fig. 2) and the carrier adapter module 120 (Fig. 2). The database module 292 <br/>is configured to <br/>store the data uploaded from the retail partners 132 and the carrier partners <br/>122, and according to <br/>an embodiment comprises a database 294 and a content manager 296. The database <br/>294 may also<br/><br/>CA 02833699 2013-10-11<br/>- 18 -<br/>comprise a data cache as described in more detail below. The data loaded into <br/>the database <br/>module 292 includes customer account categorization/classification information <br/>(e.g. consumer, <br/>small business or corporate), mobile devices data, rate plans data, features <br/>data, contract terms <br/>information, promotions information, and/or network area code data. According <br/>to an <br/>embodiment the data is stored in data schema or model as shown in Fig. 3 and <br/>indicated <br/>generally by reference 300. The data schema 300 comprises static data 310, <br/>cache data 320, <br/>transaction data 330, and synchronization tables 340.<br/>[00057] According to an exemplary implementation, the static data 310 <br/>comprises data<br/>that doesn't change, i.e. is relatively static or persistent, and comprises <br/>the following data <br/>structures or modules: a retailer data structure 311 having a "retailerID" <br/>parameter; a <br/>retailer/carrier data structure 312 having a "retailerCarrierld" parameter and <br/>fields for <br/>"carrierId", "retailerId" and "transactionTypeId"; a carrier data structure <br/>313 having a "carrierId" <br/>parameter; a sales representative data structure 314 having a <br/>"salesRepresentativeId" parameter <br/>and a "retailerId" field; a transaction type data structure 315 having a <br/>"transactionTypeId" <br/>parameter; a contract term data structure 316 having a "contractTermId" <br/>parameter and a <br/>"carrierld" field; a store data structure 317 having a "storeId" parameter, a <br/>"retailerld" field and <br/>an "addressId" field; and an address data structure 318 having an "addressId" <br/>parameter.<br/>[00058] According to an exemplary implementation, the cache data 320 <br/>comprises data<br/>that is uploaded from the retail partner(s) 230 and/or the carrier partner(s) <br/>220 and utilized in a <br/>telecom transaction or other processing to achieve improved performance by <br/>eliminating the <br/>need to upload or reload the data from the retail partner or carrier partner. <br/>The cache data 320 <br/>comprises a device data structure 321 having a "deviceld" parameter and a <br/>"carrierId" field; a <br/>rate plan data structure 322 having a "ratePlanld" parameter and a "carrierId" <br/>field; a feature <br/>data structure 324 having a "featureld" parameter and a "carrierId" field; an <br/>availability rule data <br/>structure. As shown, the availability rule is linked to the device 321 and the <br/>rate plan 322 and <br/>contains rules that determine the availability of the device and/or the rate <br/>plan. According to <br/>another aspect, the data stored in the data cache 320 can be utilized in the <br/>execution of a telecom <br/>transaction. It will be appreciated that by utilizing cached data improved <br/>transaction performance <br/>can be achieved because all or some of the required transaction data does not <br/>need to be provided <br/>or retrieved downstream from the carrier partner system. According to another <br/>aspect, the<br/><br/>CA 02833699 2013-10-11<br/>- 19 -<br/>=<br/>respective carrier adapter modules 120 and retail adapter modules 130 are <br/>configured to <br/>synchronize and upload the reference data for the data cache 320, for example, <br/>as described <br/>below with reference to Fig. 18.<br/>[00059] According to an exemplary implementation, the transaction data 330 <br/>comprises<br/>data this is utilized in a telecom transaction or other processing operations <br/>and does not <br/>necessarily need to be retained or stored in the database 294 (Fig. 2) after <br/>the processing or <br/>transaction is completed. The transaction data 330 comprises a transaction <br/>data structure 331 <br/>having a "transactionId" parameter, a "transactionTypeId" field, a "carrierId" <br/>field, a <br/>"salesRepresentativeId" field, a "storeId" field and a "customerId" field; a <br/>transaction item data <br/>structure 332 having a "transactionItemId" parameter, a "transactionId" field, <br/>a "customerId" <br/>field, a "deviceId" field, a "ratePlanId" field and a "contractTermId" field; <br/>a customer data <br/>structure 334 having a -customerId" parameter; an added feature data structure <br/>336 having an <br/>"addedFeatureId" field with a "featureId" parameter and a "transactionItemId" <br/>parameter; and a <br/>port in detail data structure 338 having a "portInItemld" parameter and a <br/>"transactionitemId" <br/>parameter. As shown, the transaction item data structure 332 is linked to the <br/>cached data in the <br/>device data structure 321 and the rate plan data structure 322 and also to <br/>static or persistent data <br/>in the contract term data structure 316, and the added feature data structure <br/>336 is linked to <br/>feature data structure 324 in the cached data.<br/>[00060] According to an exemplary implementation, the synchronization <br/>tables 340<br/>comprise an audit data table 342 and a metrics data table 344.<br/>[00061] Reference is next made to Fig. 4, which shows in flowchart form <br/>processing steps<br/>for performing wireless transactions according to an embodiment of the present <br/>invention and <br/>indicated generally by reference by 400, and with reference to Figs. 6 to 16 <br/>which show <br/>screenshots of selected pages or screens generated by the system and the <br/>embedded logic flow <br/>for the wireless transaction in the form a graphical user interface or GUI <br/>according to an <br/>exemplary implementation. A wireless transaction comprises a login and <br/>authentication <br/>procedure indicated generally by reference 410, a new customer activation 420, <br/>an add new line <br/>procedure 422, a subscriber upgrade procedure 430, a device migration <br/>procedure 440, a device <br/>return procedure 460 and a device exchange procedure 470. The login and <br/>authentication<br/><br/>CA 02833699 2013-10-11<br/>- 20 -<br/>procedure 410 starts at 411 and comprises invoking a Login Page in 412 and <br/>downloading a <br/>login page configured to allow a user, for example, a sales representative, to <br/>logon onto the <br/>system. In 413, a landing page is invoked and a selection is made of one the <br/>carrier partners 122 <br/>or a telecommunication product brand. According to an exemplary embodiment, <br/>the landing <br/>page comprises an input that is responsive to a user (for example, a sales <br/>representative at the <br/>retailer) for selecting one of the available carrier partners. An exemplary <br/>landing page is depicted <br/>in Fig. 6(a) and indicated by reference 650, and includes a user responsive <br/>input 660 configured <br/>to select one of the carriers, the available carriers being indicated <br/>individually by references <br/>660a, 660b and 660c in Fig. 6(a). From the landing page 413, a determination <br/>is made whether <br/>the customer is a new customer or an existing customer 414, for example, <br/>utilizing a customer <br/>authentication page as shown in Fig. 6(b) and indicated by reference 600, <br/>which is configured <br/>with a "New Customer" selection input 610 and an "Existing Customer" selection <br/>input 620. If <br/>an existing customer, then a customer authentication operation in 416 is <br/>performed and an <br/>operation or transaction type is selected for the authenticated customer in <br/>418, for example, <br/>utilizing a customer authenticated page 700 configured as shown in Fig. 7. (As <br/>will be described <br/>in more detail below, wireless or telecom transactions for an existing <br/>customer include, for <br/>example, a device upgrade, migration to a new device, device exchange, device <br/>return, SIM <br/>replacement or swap, and add a new line.) For a new customer, the new customer <br/>activation <br/>procedure 420 is invoked.<br/>1000621 As <br/>described above, the system 100 is configured to provide the capability for a<br/>retail partner to perform new customer activations on the multiple carrier <br/>networks. The new <br/>customer activation procedure 420 comprises creating a new customer page in <br/>421, for example, <br/>utilizing an account type and customer information page 800 as depicted in <br/>Fig. 8. As shown in <br/>Fig. 8, the account and customer page 800 includes inputs 810 for selecting <br/>the "ACCOUNT <br/>TYPE" as "Postpaid" or "Prepaid" and as "Consumer" or "Business". The account <br/>and customer <br/>page 800 also includes "CUSTOMER INFO" fields 820, which are populated with <br/>the relevant <br/>customer information or data. According to another aspect, the account and <br/>customer page 800 <br/>may be configured to generate an "ADDRESS SELECTION" pop-up window as shown in <br/>Fig. <br/>8(b) and indicated by reference 820. The address selection pop-up window 820 <br/>is generated in <br/>response to the input of the customer's postal code (for example, through the <br/>postal code lookup <br/>module 252 in the hub module 110, as described above with reference to Fig. <br/>2), and presents the<br/><br/>CA 02833699 2013-10-11<br/>- 21 -<br/>=<br/>addresses associated with the postal code. The processing then proceeds to a <br/>common flow <br/>procedure indicated generally by reference 423 and according to exemplary <br/>implementation <br/>comprises processes or functions that are common to more than one procedure, <br/>for example, the <br/>common flow procedure 423 is common to the new customer activation procedure <br/>420, the add <br/>new line procedure 422, the subscriber upgrade procedure 430, and the device <br/>migration <br/>procedure 440. In 431, the system is configured to generate a select device <br/>page 900 for example <br/>as shown in Fig. 9. The select device page 900 is configured to allow <br/>selection of a new device, <br/>or a SIM card only, as depicted in Fig. 9. If the customer is buying a new <br/>device, then the new <br/>device is selected from one of the devices presented on the page 900. <br/>According to another <br/>aspect, the select device page 900 is configured to show customer information, <br/>for example, <br/>customer account # and/or customer name, and the system can be configured to <br/>persist the <br/>customer information on one or more of the other pages. The system may also be <br/>configured to a <br/>customer conditions page as shown in Fig. 10 and indicated by reference 1000. <br/>The customer <br/>conditions page 1000 is configured to present additional restrictions on a <br/>customer (for example, <br/>based on a credit check executed by the credit check module 254 in the hub <br/>module 110, as <br/>shown in Fig. 2 and described above). According to an exemplary <br/>implementation, a security <br/>deposit may be required as indicated by reference 1010 and/or a monthly <br/>spending limit as <br/>indicated by reference 1020. If the customer is an existing customer (as <br/>determined in 418) who <br/>wants to add a new line, then processing flow or execution moves to the common <br/>flow procedure <br/>423, and a device is selected in 431 (for example, using the page and GUI as <br/>depicted in Fig. 9), <br/>and then a choose/change phone number page is generated in 432, for example, <br/>having a form as <br/>shown in Fig. 11 and indicated by reference 1100. The select phone number page <br/>1100 is <br/>configured to generate a new phone number for the customer as indicated by <br/>input selection <br/>1110, or assign a phone number that is "ported" in as indicated by input <br/>selection 1120.<br/>[000631 As shown <br/>in Fig. 4, the common flow procedure 423 comprises selecting a<br/>promotion (if available or applicable) in 450 and selecting a plan & features <br/>in 452. According to <br/>an embodiment, the system is configured to generate a select promotion page <br/>1200 having a form <br/>as shown in Fig. 12, and a select plan and features page 1300 as shown in Fig. <br/>13. The select <br/>promotion page 1200 is configured to display the available promotions (based <br/>on term, <br/>promotional code, etc.), for example, "UNLIMITED CHAT & DATA" 1210, "LOTS OF <br/>DATA" 1220 or "TALK TEXT & DATA" 1230, and is responsive to a user input for <br/>selecting<br/><br/>CA 02833699 2013-10-11<br/>= - 22 -<br/>one (or more) of the available promotions. The select plan and features page <br/>1300 is configured <br/>to allow selection of a rate plan 1310 and additional features 1320. Once the <br/>plan and features<br/>. have been selected (and any promotions applied), the system generates a <br/>review page in 453 and<br/>having a form, for example, as shown in Fig. 14 and indicated by reference <br/>1400. The review <br/>page 1400 is configured to display the particulars of the selected device, the <br/>plan and any <br/>selected features, and a user responsive input for acceptance of the contract <br/>indicated by <br/>reference 1410. If acceptable to the customer, then the contract is presented <br/>to the customer for <br/>review and acceptance in 454, for example, utilizing a customer agreement page <br/>as depicted in <br/>Fig. 15 and indicated generally by reference 1500. According to an exemplary <br/>embodiment, the <br/>contract (i.e. the customer agreement) is displayed or presented in a window <br/>(which is <br/>configured to be scrollable) as indicated by reference 1510 in Fig. 15. <br/>According to an <br/>embodiment, the system is configured to allow the contract to be <br/>electronically (e.g. digitally) <br/>signed, for example, by activating a user input or control indicated by <br/>reference 1520 in Fig. 15. <br/>A confirmation page, for example, as shown in Fig. 16 and indicated by <br/>reference 1600, is <br/>generated in 456 and an email receipt is also sent to the customer in 458.<br/>[00064] Referring to Fig. 4, if an existing customer is upgrading their <br/>device (as<br/>determined in 418), for example, based on upgrade eligibility, pricing and/or <br/>promotion, then the <br/>upgrade device procedure 430 is executed. As shown, the upgrade device <br/>procedure 430 <br/>comprises selecting a new device in 431. According to an exemplary embodiment, <br/>the upgrade <br/>device procedure 430 follows the common flow procedure 423 as described above, <br/>and involves <br/>upgrading the device and/or plan and/or features, for example, as described <br/>above with reference <br/>to 431, 452. If the existing customer is migrating (e.g. from a prepaid <br/>service to a postpaid <br/>service/from a postpaid service to a prepaid service, from one network type to <br/>another network <br/>type, or from one billing system to another billing system), then the <br/>migration flow procedure <br/>440 is invoked. The migration flow procedure 440 follows the common flow <br/>procedure 423 as <br/>described above. If the migration involves a new device, then a device is <br/>selected in 431, and <br/>processing continues according to the common flow procedure 450, as described <br/>above. <br/>According to another aspect, the system is configured to provide multi-unit <br/>transactions for <br/>activations, upgrades and migrations.<br/><br/>CA 02833699 2013-10-11<br/>- 23 -<br/>[00065] Referring again to Fig. 4, if an existing customer is returning <br/>their device (as<br/>= determined in 418), the return flow procedure 460 is executed. According <br/>to an embodiment, the <br/>system is configured to provide retail partners with the capability to perform <br/>device returns on <br/>multiple carrier networks. As shown, the return procedure 460 comprises <br/>determining if the <br/>subscriber is eligible for a return in 461, for example, based on return <br/>period and/or on the <br/>condition of the device being returned. If eligible, the device return is <br/>processed in 462 and a <br/>confirmation page is generated in 463. If the return involves cancellation of <br/>a contract, then a <br/>cancel contract operation is executed in 464. The system generates an email <br/>receipt in 465.<br/>[00066] Referring back to Fig. 4, if an existing customer is exchanging <br/>a device (as<br/>determined in 418), then the exchange device flow procedure 470 is executed. <br/>According to an <br/>embodiment, the system is configured to provide retail partners with the <br/>capability to perform <br/>device exchanges on multiple carrier networks. The exchange flow procedure 470 <br/>comprises <br/>determining if the subscriber is eligible to exchange, for example, based on <br/>exchange period <br/>and/or device condition rules in 471. In 472, a determination is made whether <br/>the exchange is for <br/>a new device 474, for a new or different phone number 473, for a new promotion <br/>486, for a plan <br/>or term change 489, or for a SIM card replacement or "swap" 490. If the SIM <br/>card is being <br/>replaced, then operation for selecting or generating a new SIM card is <br/>performed in 490, <br/>followed by generating a confirmation page in 484 and an email receipt in 492. <br/>If the exchange <br/>involves a new device, then a new device is selected in 474. In 476, a <br/>promotion is selected (if <br/>available or applicable) and then a plan & features are selected in 478. A <br/>page is then presented <br/>for review in 480, and if acceptable, a contract is accepted (e.g. <br/>electronically signed) in 482. <br/>The system generates a confirmation page in 484 and an email receipt sent to <br/>the customer in <br/>492. If the exchange involves, a phone number, then a new phone number is <br/>selected in 473, and <br/>a confirmation page in 484 and an email receipt in 492 are generated. If the <br/>exchange comprises <br/>a new promotion, then the promotion is selected in 486. If the promotion <br/>includes a new device, <br/>then a new device is selected in 488 and further processing is executed <br/>according to 478, 480, <br/>482, 484 and 492, as described above. If the exchange involves a change in the <br/>plan and/or <br/>terms, then the change is made in 489, and further processing is executed <br/>according to 478, 480, <br/>482, 484 and 492, as described above.<br/><br/>CA 02833699 2013-10-11<br/>- 24 -<br/>[00067] <br/>Reference is next made to Fig. 5, which shows the process flow in a telecom<br/>transaction executed in accordance with an embodiment of the present <br/>invention. In the <br/>downstream direction, i.e. from the retail partner 230 to the carrier partner <br/>220, the telecom <br/>transaction is commenced at one of the retail partners 230 (e.g. by a sales <br/>representative) by <br/>initiating a request (e.g. get a rate plan from the selected carrier partner <br/>220) through the retailer <br/>adapter module 130 as indicated by reference 501. The system is configured to <br/>validate the <br/>request in 502 and transmit the request to the retailer bridge 232 in 504. The <br/>retailer bridge 232 <br/>transforms or translates the request into a common object form, i.e. a common <br/>object request, <br/>based on the hub module 110 as indicated by reference 506, and the common <br/>object request is <br/>passed to the hub module 110 for processing in 508. According to an <br/>embodiment, the hub <br/>module 110 is configured to determine if the information contained in the <br/>common object <br/>request is available in the data cache (i.e. stored in the database 294 as <br/>shown in Fig. 2). If the <br/>requested data is available in the data cache, then hub module 110 is <br/>configured with a process or <br/>function to retrieve the reference data (e.g. the rate plan) from the database <br/>294 as indicated by <br/>reference 510 in Fig. 5. The reference data is returned to the hub module 110 <br/>as indicated by <br/>reference 512, and processed for the retail partner 230 as described below <br/>with reference to <br/>process flow steps 538 to 546. If the request cannot be fulfilled with data <br/>from the data cache in <br/>the database 294, then the hub module 110 is configured to generate a carrier <br/>operation from the <br/>common object request in 506 as indicated by reference 520, and the carrier <br/>operation is passed <br/>to the carrier bridge 221. The carrier bridge 221 is configured to transform <br/>or translate the carrier <br/>operation into a carrier operation request object as indicated by reference <br/>522 and the carrier <br/>adapter module 120 is invoked for the carrier operation in 524, which is <br/>passed to the carrier <br/>partner 220 for processing in 526. In the upstream direction, i.e. from the <br/>carrier partner 220 to <br/>the retail partner 230, the carrier partner 220 invokes the carrier adapter <br/>module 120 in 530, and <br/>the response to the request, i.e. the request response, (e.g. rate plan or <br/>other carrier specific <br/>information or data) is passed to the carrier bridge 221 as indicated by <br/>reference 532. The carrier <br/>bridge 221 is configured to transform or convert the request response into a <br/>common object for <br/>processing/handling by the hub module 110 in 534 and the common object is <br/>passed to the hub <br/>module as indicated by reference 536. The processing at the hub module 110 may <br/>comprise <br/>applying logic and other operations to the common object as indicated by <br/>reference 538. The <br/>common object is then passed to the retailer bridge 232 in 540 and transformed <br/>or converted into<br/><br/>CA 02833699 2013-10-11<br/>- 25 -<br/>=<br/>a retailer response object as indicated by reference 542. The retailer bridge <br/>232 passes the retailer <br/>response object to the retail adapter module 130 in 544. The retailer adapter <br/>module 130 <br/>incorporates the retailer response object into the telecom transaction being <br/>performed by the <br/>sales representative at the retail partner 230 as indicated by reference 546. <br/>If the request was <br/>fulfilled by retrieving data from the data cache 294 in 512 (as described <br/>above), then the process <br/>flow in steps 538, 540, 542, 544 and 546 are performed.<br/>[00068] According to another aspect, the retailer bridge 271 (Fig. 2) is <br/>configured to<br/>execute administrative functions, such as collecting audit information and/or <br/>other types of <br/>persistent data, as indicated by reference 550, as shown in Fig. 5. The hub <br/>module 110 is <br/>configured to store some or all of the collected data in the database module <br/>292 (Fig. 2) as <br/>indicated by reference 552.<br/>[00069] Reference is next made to Fig. 17, which shows an exemplary <br/>deployment or<br/>implementation of the software-based systems or components comprising the <br/>networked system <br/>for requisitioning telecommunication products 100 according to an embodiment <br/>of the present <br/>invention. The deployment is "cloud-based" and indicated generally by <br/>reference 1700. The hub <br/>module 110 (as described above with references to Figs. 1 to 3) is implemented <br/>on a cloud based <br/>platform, for example, through a cloud provider, indicated generally by <br/>reference 1710. The <br/>cloud based platform 1710 couples through the cloud (i.e. the Internet) 1701 <br/>to computers 1720 <br/>associated with the carrier partners and to computers 1730 associated with <br/>each of the retail <br/>partners. According to an exemplary implementation, secure channels or <br/>protocols, such as, SSL, <br/>TLS and/or VPN are utilized. As shown in Fig. 17, the cloud based platform <br/>comprises a UI <br/>(User Interface) application server 1740 and a web content manager 1742, which <br/>are configured <br/>to provide the web services, web pages (including branding and page layouts), <br/>data <br/>upload/download operations associated with the retail adapter modules and the <br/>carrier adapter <br/>modules. According to an exemplary implementation, the cloud based platform <br/>1710 includes a <br/>CDN (Content Delivery Network) component 1744 and a security component 1746. <br/>As shown in <br/>Fig. 17, the cloud platform 1710 may include a load balancer indicated <br/>generally by reference <br/>1748 and configured to balance the flow of data between the UI application <br/>server 1740, the <br/>content delivery network 1764 and the computers or computing systems 1730 <br/>associated with the <br/>retail partners. The security component 1746 is configured to provide identity <br/>management,<br/><br/>CA 02833699 2013-10-11<br/>- 26 -<br/>authentication/recovery of credentials for users associated with the system <br/>and other associated <br/>encryption/decryption and security functions. The cloud platform 1710 includes <br/>an integration <br/>services application server 1750, a database 1760 and a data cache 1770. The <br/>integration services <br/>application server 1750 interfaces with the UI application server 1740 and the <br/>carrier partner <br/>computer systems 1720 and is configured or implemented to execute the <br/>functions and features <br/>associated with the hub module 110, the VAS integration module 201, the <br/>administrative <br/>processing module 202 and/or the data loading module 204, as described above <br/>with reference to <br/>Fig. 2. The data cache 1770 is configured to cache data associated with a <br/>telecom transaction as <br/>described above with reference to Fig. 3. To facilitate the transfer of data <br/>between the database <br/>1760 and the carrier computer systems 1720, the cloud platform 1710 includes a <br/>data loader, for <br/>example, implemented as batch ETL (Extract, Transform and Load) process, and <br/>indicated <br/>generally by reference 1762. As shown in Fig. 1, the cloud platform may also <br/>include a mail <br/>server 1780 and a reporting server 1782. The email server 1780 is configured <br/>to generate emails, <br/>for example, the email receipts 458, 492 described above with reference to <br/>Fig. 4. The reporting <br/>server 1782 is configured to generate reports, including, for example, reports <br/>generated based on <br/>the audit information asynchronously captured by the retailer bridge 232 as <br/>described above with <br/>reference to Fig. 5.<br/>1000701 According to an embodiment, the integration services application <br/>server 1750 is <br/>configured with a data upload process for uploading selected data from one or <br/>more of the carrier <br/>partners 220 as shown in Fig. 19 and indicated generally by reference 1900. <br/>The data upload <br/>process 1900 is configured to upload selected data from the carrier partner <br/>220 comprising <br/>reference data (i.e. rate plan information) as indicated by reference 1910. <br/>The reference data is <br/>uploaded to the database 1660 as indicated by reference 1920, and according to <br/>another aspect, <br/>some or all of the reference data is uploaded to the data cache 1670, as <br/>indicated by reference <br/>1930. As described above with reference to Fig. 3, cache data may be utilized <br/>in a telecom <br/>transaction to achieve improved performance by eliminating the need to upload <br/>data (e.g. rate <br/>plan data) from the selected carrier partner 220 on a per transaction basis. <br/>In addition to the rate <br/>plan data (i.e. rate plan data 322 in Fig. 3), the reference data uploaded and <br/>stored in the data <br/>cache 1670 includes device data (i.e. device data 321 in Fig. 3) and/or <br/>features data (i.e. feature <br/>data 324 in Fig. 3).<br/><br/>CA 02833699 2013-10-11<br/>= -27-<br/>1000711 Reference is next made to Fig. 18, which shows in diagrammatic form a <br/>redundant <br/>deployment 1800 of the networked system for requisitioning telecommunication <br/>products 100 <br/>according to an embodiment of the present invention. The redundant deployment <br/>1800 comprises <br/>a master networked system 1810, a slave networked system 1820 and a load <br/>balancer 1830. The <br/>master networked system 1810 and the slave networked system 1820 each comprise <br/>a cloud <br/>based deployment 1700 as described above in Fig. 17. The master networked <br/>system 1810 and <br/>thc slave networked system 1820 are each located in separate geographical <br/>regions, e.g. Region 1 <br/>and Region 2, and according to another aspect run on different cloud service <br/>providers. The load <br/>balancer 1830 is configured to balance the load across the two systems under <br/>normal operating <br/>conditions. In the event that one of the systems is not available, the other <br/>system is configured to <br/>continue operation for both regions.<br/>[00072] The functionality and features associated with the cloud platform 1710 <br/>(Fig. 17), the <br/>hub module 110 (Figs. 1 and 2), the carrier adapter module 120 (Figs. 1 and 2) <br/>and the carrier <br/>bridge 221 (Fig. 2), the retailer adapter module 130 (Figs. 1 and 2) and the <br/>retailer bridge 232 <br/>(Fig. 2), and the associated application components or modules and other <br/>functional components <br/>or modules of the networked system for requisitioning telecommunication <br/>products 100 (Figs. 1 <br/>and 2), and/or the user interface screens or pages, for a telecom transactions <br/>indicated generally <br/>by references 600 to 1600 (in Figs. 6 to 16) as described above and in <br/>accordance with the <br/>embodiments may be implemented in the form of one or more software objects, <br/>code <br/>components, executable statements and machine readable code, computer programs <br/>or program <br/>modules in the server and/or the partner machines or computers. Further, at <br/>least some or all of <br/>the software objects, executable statements, machine readable computer code, <br/>components or <br/>modules can be hard-coded into processing units and/or read only memories or <br/>stored or <br/>embedded on computer readable media, storage media, or other digital storage <br/>media or non-<br/>volatile storage media in the computers, computer systems, servers and/or <br/>other components or <br/>modules depicted in the drawings. The specific implementation details and <br/>coding details for the <br/>computer programs, software objects and/or program modules will be within the <br/>knowledge and <br/>understanding of one skilled in the art.<br/><br/>CA 02833699 2013-10-11<br/>= =<br/>-28-<br/>1000731 Reference is next made to Fig. 20, which shows an exemplary <br/>implementation of a <br/>computer system 2000 according to an embodiment and suitable for the <br/>processing or hub <br/>module 110 (Fig. 1).<br/>=<br/>[00074] As shown, the computer system 2000 comprises a processor 2010 and a <br/>keyboard <br/>2012 and mouse 2014 coupled to the processor 2010 via a system bus 2016. The <br/>keyboard 2012 <br/>and the mouse 2014, in one example, allow a user to introduce or provide <br/>inputs to computer <br/>system 2000 and the processor 2010. It will be appreciated that other suitable <br/>input devices may <br/>be used in addition to, or in place of, the mouse 2014 and/or the keyboard <br/>2012. The computer <br/>system 2000 may be configured with other input/output (I/O) devices 2018 <br/>coupled to the system <br/>bus 2016, for example, a printer, audio/video (AN) I/0, etc.<br/>[00075] According to another aspect, the computer system 2000 may include a <br/>video memory <br/>module 2020, a main memory module 2022 and a mass storage device 2024, which <br/>are coupled <br/>to the system bus 2016. The mass storage device 2024 may include both fixed <br/>and removable <br/>media, such as magnetic, optical or magnetic optical storage systems and any <br/>other available <br/>mass storage technology. The system bus 2016 may be configured, for example, <br/>with address <br/>lines for addressing the video memory 2020 and/or the main memory 2024.<br/>[00076] According to another aspect, the system bus 2016 may include a data <br/>bus for <br/>transferring data between and among the components, such as the processor <br/>2010, the main <br/>memory 2022, the video memory 2020 and/or the mass storage device 2024. The <br/>video memory <br/>844 may be a dual-ported video random access memory. One port of the video <br/>memory 2020, in <br/>one example, is coupled to a video amplifier 2026, which is used to drive one <br/>or more monitor(s) <br/>indicated generally by reference 2028. The monitor(s) 2028 may be any type of <br/>monitor suitable <br/>for displaying graphic images, such as a cathode ray tube monitor (CRT), flat <br/>panel, or liquid <br/>crystal display (LCD) monitor or any other suitable data presentation device. <br/>The processor 2010 <br/>may be implemented utilizing any suitable microprocessor or microcomputer.<br/>[00077] According to another aspect, the computer system 2000 may include a <br/>communication interface 2030 which is coupled to the system bus 2016. The <br/>communication <br/>interface 2030 provides a two-way data communication coupling via a network <br/>link. For <br/>example, the communication interface 2030 may be a satellite link, a local <br/>area network (LAN)<br/><br/>CA 02833699 2013-10-11<br/>- 29 -<br/>card, a cable modem, and/or wireless interface. In any such implementation, <br/>the communication <br/>interface 2030 is configured to send and/or receive electrical, <br/>electromagnetic or optical signals <br/>that carry digital data representing various types of information.<br/>[00078] According to another aspect, code received by the computer system 2000 <br/>may be <br/>executed by the processor 2010 as the code is received, and/or stored in the <br/>mass storage 2024, <br/>or other non-volatile storage for later execution. In this manner, the <br/>computer system 2000 may <br/>obtain program code in a variety of forms. Program code may be embodied in any <br/>form of <br/>computer program product such as a medium configured to store or transport <br/>computer readable <br/>code or data, or in which computer readable code or data may be embedded. <br/>Examples of <br/>computer program products include CD-ROM discs, ROM cards, floppy disks, <br/>magnetic tapes, <br/>computer hard drives, servers on a network, and solid state memory devices. <br/>Regardless of the <br/>actual implementation of the computer system 2000, the data processing system <br/>may execute <br/>operations that allow for facilitating transactions between disparate <br/>retailers and disparate <br/>telecommunications carriers as described herein.<br/>1000791 The <br/>present invention may be embodied in other specific forms without departing<br/>from the spirit or essential characteristics thereof. Certain adaptations and <br/>modifications of the <br/>invention will be obvious to those skilled in the art. Therefore, the <br/>presently discussed <br/>embodiments are considered to be illustrative and not restrictive, the scope <br/>of the invention being <br/>indicated by the appended claims rather than the foregoing description, and <br/>all changes which <br/>come within the meaning and range of equivalency of the claims are therefore <br/>intended to be <br/>embraced therein.<br/>

Past Owners that do not appear in the "Owners on Record" listing will appear in other documentation within the application.