AU2012241129B2

AU2012241129B2 - Tariff management test automation

Info

Publication number: AU2012241129B2
Application number: AU2012241129A
Authority: AU
Inventors: Adrian Envin How; Jasmine Mei Ping Kua; Kin Yip Lau; Ming Hon Wong
Original assignee: Accenture Global Services Ltd
Current assignee: Accenture Global Services Ltd
Priority date: 2008-09-05
Filing date: 2012-10-16
Publication date: 2015-07-02
Anticipated expiration: 2029-09-04
Also published as: AU2012241129A1

Abstract

A method for an operator to test tariff and/or billing configurations using a computer based system, the method being effected by a user interface, 5 said method including the steps of creating through said computer based system one or more accounts from a selection of a first set of options by the operator from the user interface, allocating a service or services to each account from a selection of a second set of options by the operator from the user interface said allocated services being assigned to said 10 accounts by said computer based system, adding at least one package or component to each account from a selection of a third set of options by the operator from the user interface said packages or components services being assigned to said accounts by said computer based system, associating at least one usage file to each account from a 15 selection of a fourth set of options by the operator from the user interface said usage files being assigned to said accounts by said computer based system thereby providing bulk test data; and simulating operation of the accounts with said bulk test data using said computer based system to provide the operator with information on the cost of the usage defined in 20 the at least one usage file according to the services and component and/or package associated with said accounts which define the tariff and/or billing configuration.

Description

Editorial Note 2012241129 Please note description pages begin with page 2 -2 TARIFF MANAGEMENT TEST AUTOMATION FIELD OF THE INVENTION The present invention relates to a system and method of testing data 5 relating to products and/or services. The invention is particularly useful for testing configuration data relating to proposed tariff and/or billing plans for products and/or services for a telecommunication service provider thus allowing the creation and execution of test data with respect to proposed tariff and/or billing plans. 10 BACKGROUND OF THE INVENTION The telecommunications industry is highly competitive and this has resulted generally from regulatory changes in most countries around the world seeking to deregulate the provision of telecommunication services. As 15 the reform of the telecommunication services industries has evolved, consumers have been provided with an increasing number of products and services at a lower cost. At the present time, the telecommunications industry worldwide is 20 facing four major trends. Firstly, changing consumer requirements are evolving towards more personalized on-demand content and services. In the past, highly regulated telecommunications industries provided relatively few alternatives with respect to the packaging of products and/or services and consumers were required to select the most appropriate products and/or 25 services from the relatively few offerings. However, with deregulation, the number of products and/or services has increased dramatically and consumers are displaying an increasing preference to group products and/or services according to their personal preferences. In this respect, the consumers preferences include both the products and/or services that the 30 consumer requires and the preferred billing arrangements for those products and/or services. ct. 18175.Specification as filed.3-Sep-09 -3 Secondly, with the increased competition in the industry, individual telecommunication service providers are competing for the available revenue of consumers. In addition to the telecommunication service providers competing with each other, increasingly these providers are required to 5 compete for revenue with alternative business models such as Mobile Virtual Network Operators (MVNO's). Thirdly, the rapid pace of developments in information technology and telecommunications technology is enabling telecommunication service 10 providers to develop a common platform for building and integrating real time, converged IP (Internet Protocol) and legacy services. As a result, telecommunication service providers increasingly need to take advantage of the developments in information technology in order to obtain increased efficiency with respect to the delivery of their products and/or services in 15 order to remain competitive. Fourthly, as the reform of telecommunications industries around the world continues, present "barriers to entry" to specific consumer markets will most likely not exist in the future. For example, cell phone number portability 20 between telecommunication service providers is being mandated in various countries around the world to prevent consumers from being "locked-in" to a particular telecommunication service provider. This particular reform will allow a consumer to change telecommunication service provider without the loss of their cell phone number. Whilst the introduction of this 25 reform may vary from country to country, there is a clear intention in most countries with well developed telecommunications services to provide consumers with portability such that they can elect to choose a new telecommunication service provider without the loss of their cell phone number (sometimes referred to as mobile number or handset number). 30 Presently many consumers are discouraged from selecting a new telecommunication service provider, despite a new provider's efforts to offer less costly services, as the transition will require them to abandon their old ct. 18175.Specification as filed.3-Sep-09 -4 cell phone number with the consequent requirement to advise all their contacts (family, friends and business associates) of their new cell phone number. 5 In any event, due to constantly changing consumer trends, regulatory shifts and intense competition, there is a need to frequently introduce new and innovative bill plans and promotions and to reduce the time-to-market for these services. 10 In view of the aforementioned emerging trends, telecommunication service providers must take action to preserve or increase the competitiveness of their offerings. Presently, reacting to changing consumer requirements is particularly 15 difficult for telecommunication service providers. The generation of configurations for new tariff and/or billing plans for products and/or services presents a difficult problem as it is necessary for a telecommunications service provider to fully test a configuration for any new proposed tariff and/or billing plan before offering same to consumers. Having devised a new tariff 20 and/or billing plan for products and/or services, it is necessary for the telecommunication service provider to deploy the proposed new plan configuration into multiple data bases. Further, having deployed newly devised configurations, it is necessary to fully test the new configurations across different accounts and service instances (for example, cell telephony, 25 fixed line telephony and/or provision of an internet service) to ensure the configured tariffs and/or billing plans operate correctly and, if implemented, will invoice consumers accurately according to the published tariff and/or billing plan details. 30 Presently, the process of generating a configuration for a new tariff or billing plan, deploying and testing same is predominantly a manual process requiring operators of a high skill level. In particular, it is usual when ct. 181 75.Specification as filed.3-Sep-09 -5 configuring, deploying and testing a configuration for a new tariff and/or billing plan to require skilled staff to construct database scripts manually for the purpose of deploying and testing the plans. Of course, the use of highly skilled personnel performing operations manually not only increases the cost 5 associated with the development, deployment and testing of new tariff configurations but also causes the process to require a substantial period of time in which to fully test any proposed tariff and/or billing configuration. The problems associated with developing and deploying new tariff 10 and/or billing configurations is further exacerbated by the extent to which steps within the process are performed manually. Despite requiring operators to have a high level of skill and understanding with respect to the information technology systems and the test environments in which new tariff and billing plan configurations are tested, the performance of operations 15 manually gives rise to a high degree of human error which in turn delays the progress of testing a configuration for a new tariff and/or billing plan. For example, having devised a configuration for a new tariff and/or billing plan, which is usually embodied in the form of computer program code, it is generally necessary to deploy the program code representing the new tariff 20 and/or billing across all active data bases in a telecommunications system in order to maintain consistency with the existing configuration in the production environment. Generally, a telecommunications service provider will have established several environments for performing necessary functions such as a reporting environment, a testing environment and a back up environment 25 for disaster recovery. For some systems it can be necessary to generate, deploy and test a configuration for a new tariff and/or billing plan which is configured across more than twenty (20) database tables the database table being in different 30 databases and the databases being on different platforms. In testing such a system, the operator(s) would require an in-depth knowledge of databases, including tables and their relationships. ct. I 1 75.Specification as filed.3-Sep-09 -6 As the timeframe for generation, deployment and testing of a configuration for a tariff and/or billing plan can span several weeks, any such failures can be both time consuming and costly. 5 Having devised a new tariff or billing plan, it is necessary to test the new configuration for the plan in a test environment before implementing same in a production environment. When operating within the test environment, deploying the computer program code to effect a configuration for a new tariff or billing plan generally requires an operator to deploy the 10 computer program code to individual data bases in the test environment in a particular order to avoid errors. Further, these functions are generally performed by an operator executing detailed instructions from a UNIX server and hand keying text commands in order to execute the computer program code in the respective databases. Of course, such activities necessarily 15 incur a degree of human error particularly in relation to ensuring that computer program code representing the new tariff or configuration plan is executed in the correct order and in relation to the correct databases. Accordingly, in view of the previously mentioned emerging market 20 trends there is a need for telecommunication service providers to reduce the time required to configure, deploy and test configurations for new tariff plans in order to facilitate the implementation of new tariff or billing arrangements. In turn, any improvement to the efficiency of this process will facilitate the attraction of new and/or existing consumers to a newly devised tariff or billing 25 plan. Testing is an essential phase before rolling out any new configurations of new bill plans or products. The testing process often requires an exhaustive array of test criteria to ensure all areas related to a new tariff 30 and/or billing plan or product launch have been covered. Currently, testers are required to carry out tests based on supplied test criteria and in order to ot. 18175.Specification as filed.3-Sep-09 -7 perform these tests, the testers need to create test data for execution in the test environment. Test data for functions such as accounts, services, packages and 5 components are required to be created by the tester. Currently, testers generally use the available Customer Relationship Management (CRM) software of which the well known CustomerCentre is typical. CustomerCentre is the same application that customer service representatives use over the counter in service centres to create and 10 maintain customer accounts. However, the test data creation process is often the longest process in the entire flow of testing and use of a CRM software application such as CustomerCentre represents a significant delay as it can only create one account, service, add package(s) and component(s) at any one time. The process of creating an account with service and 15 packages/components typically takes an average of 5 minutes. To create multiple sets of accounts and services with packages/components using a CRM application such as CustomerCentre would require the process to be repeated i.e. 100 accounts = 100 x 5 minutes = 500 minutes. 20 Upon creating test data, the testers can verify that tariff and/or billing plans and products provisioned to an account are displayed correctly via CustomerCentre. Certain transactions such as change of bill plans, service transfer, etc can be performed on these test accounts to ensure that the newly configured tariff and/or billing plans and promotions are working as 25 expected. Another aspect of testing is to ensure that usages are rated and processed accurately and that bills can be generated for these accounts without errors. 30 Usage files contain call records which are not rated (i.e. no dollar amount is associated with any of the calls). A significant component of ctj 18175.Specification as filed.3-Sep-09 -8 testing a tariff and/or billing plan is to ensure that calls made by the account which is provisioned to a particular bill plan is rated based on the bill plans configured rates e.g. a bill plan may define a 1min local call as 30c hence one would expect to see 30c for every minute of local call made for an 5 account with this bill plan. Billing plan configuration is generally a difficult task as the rating engine is very complicated and there can be many permutations to rating a call (e.g. if off peak and non adjacent call and <30 seconds and is made to favourite 5 numbers, then amount = $x) 10 Currently, usage files are created by the testers manually. The end product is typically a flat text file having a complex file format convention in which to store details of call records. This manual way of creating a usage file is highly prone to human error and hence requires a lot of time as testers seek to minimise errors. 15 Once usage files are created, they are stored in a specific directory in the server. To execute usage processing, a tester must key in a text based command from a UNIX server to initiate the process. The usage file is then identified and processed, rated, and the rated call records are written to the 20 database. The bill generation process is similar to usage processing. In order to generate bills, the tester keys in a text based command from the UNIX server to initiate the process. 25 Accordingly, in the context of the overall requirements there is a specific need to reduce the time presently required to test new tariff and/or billing configurations. 30 The reference to any prior art in this specification is not, and should not be taken as, an acknowledgement or any form or suggestion that the prior art ct. 18175.Specification as filed,3-Sep-09 -9 forms part of the common general knowledge to those skilled in the relevant field of technology at the priority date of the claims herein. SUMMARY OF THE INVENTION 5 In one aspect, the present invention provides a computer-implemented method including receiving data specifying a proposed billing plan for users of telecommunications services, wherein the proposed billing plan is proposed for testing as a candidate billing plan prior to being implemented for the 10 telecommunications services and prior to being offered to users of the telecommunications services receiving data specifying a type, a quantity, and attributes of simulated user accounts to be generated, wherein the simulated user accounts correspond to non-actual users and are generated for testing, generating, in bulk, the specified type and quantity of simulated user accounts 15 that have the specified attributes, receiving data identifying the telecommunications services to be attached to each of the simulated user accounts, then attaching the identified telecommunications services to each of the simulated user accounts, receiving data identifying telecommunications units to be added to one or more of the telecommunications services that are 20 attached to each of the simulated user accounts, then adding the telecommunications units to the one or more of the telecommunications services that are attached to each of the simulated user accounts, receiving data identifying pre-defined, simulated usage data, then applying portions of the simulated usage data to each of the simulated user accounts, wherein the 25 simulated usage data corresponds to non-actual users, after applying the portions of the simulated usage data to each of the simulated user accounts, receiving data indicative of an instruction selected by an operator to test the proposed billing plan on the simulated user accounts, then testing the proposed billing plan on the simulated user accounts, and generating, based on results of 30 the testing of the proposed billing plan on the simulated user accounts, a respective test bill for each simulated user account.

-10 In a further aspect, the present invention provides a system including one or more computers, and a computer-readable medium coupled to the one or more computers having instructions stored thereon which, when executed by the one or more computers, cause the one or more computers to perform 5 operations including receiving data specifying a proposed billing plan for users of telecommunications services, wherein the proposed billing plan is proposed for testing as a candidate billing plan prior to being implemented for the telecommunications services and prior to being offered to the users of the telecommunications services, receiving data specifying a type, a quantity, and 10 attributes of simulated user accounts to be generated, wherein the simulated user accounts correspond to non-actual users and are to be generated for testing, generating, in bulk, the specified type and quantity of simulated user accounts that have the specified attributes, receiving data identifying the telecommunications services to be attached to each of the simulated user 15 accounts, then attaching the identified telecommunications services to each of the simulated user accounts, receiving data identifying telecommunications units to be added to one or more of the telecommunications services that are attached to each of the simulated user accounts, then adding the telecommunications units to the one or more of the telecommunications 20 services that are attached to each of the simulated user accounts, receiving data identifying pre-defined, simulated usage data, then applying portions of the simulated usage data to each of the simulated user accounts, after applying the portions of the simulated usage data to each of the simulated user accounts, receiving data indicative of an instruction selected by an operator to test the 25 proposed billing plan on the simulated user accounts, then testing the proposed billing plan on the simulated user accounts, and generating, based on results of the testing of the proposed billing plan on the simulated user accounts, a respective test bill for each simulated user account. 30 In yet a further aspect, the present invention provides a computer readable medium coupled to one or more computers having instructions stored thereon which, when executed by the one or more computers, cause the one or more computers to perform operations including receiving data specifying a proposed billing plan for users of telecommunications services, wherein the 35 proposed billing plan is proposed for testing as a candidate billing plan prior to -11 being implemented for the telecommunications services and prior to being offered to the users of the telecommunications services, receiving data specifying a type, a quantity, and attributes of simulated user accounts to be generated, wherein the simulated user accounts correspond to non-actual 5 users and are to be generated for testing, generating, in bulk, the specified type and quantity of simulated user accounts that have the specified attributes, receiving data identifying the telecommunications services to be attached to each of the simulated user accounts, then attaching the identified telecommunications services to each of the simulated user accounts, receiving 10 data identifying telecommunications units to be added to one or more of the telecommunications services that are attached to each of the simulated user accounts, then adding the telecommunications units to the one or more of the telecommunications services that are attached to each of the simulated user accounts, receiving data identifying pre-defined, simulated usage data, then 15 applying portions of the simulated usage data to each of the simulated user accounts, after applying the portions of the simulated usage data to each of the simulated user accounts, receiving data indicative of an instruction selected by an operator to test the proposed billing plan on the simulated user accounts, then testing the proposed billing plan on the simulated user accounts, and 20 generating, based on results of the testing of the proposed billing plan on the simulated user accounts, a respective test bill for each simulated user account.

-12 Having created accounts, allocated services thereto, added packages and/or components to the accounts and associated usage files, the operation of the accounts is simulated on the test system. This provides the operator with an indication of the cost that would be incurred 5 in each account in the event that the usage as defined in the usage files were to occur. In one embodiment, the reported costs are compared with the known cost that should arise from the usage for a particular tariff configuration thereby enabling the validation of the configuration. In the event that the reported cost is the same as the cost that should result from 10 the usage according to the usage file, the configuration is validated. Alternatively, in the event that the reported cost differs, then an error or conflict has occurred and operators may then attempt to locate the source of the error or conflict. 15 The user interface may be provided in the form of a graphical user interface with the various objects such as accounts, services, packages and/or components represented as graphical objects, In one embodiment, operators may allocate services to accounts by selecting the object representing a service and "dragging and dropping" the graphical object 20 representing the service over the graphical object representing one or more accounts. Other associations and or assignments between objects may be similarly effected. In another embodiment, the user interface is implemented by the 25 use of a tabbed menu arrangement. The techniques described herein may be embodied by stored, executable instructions that are executed by one or more suitable processing devices such as personal or server computers. The executable 30 instructions may result in computer instructions that are implemented integrally to a - 13 computer or over a network using separate software segments. The executable instructions may also include segments of existing software that effect functions in cooperation with dedicated segments of computer instruction code developed specifically for the present invention. 5 In an exemplary embodiment, the interface with an operator is a web enabled interface that is implemented on a device connected to a data communications network such as the internet. BRIEF DESCRIPTION OF THE DRAWINGS 10 One or more embodiments of the present invention are described below with reference to the accompanying figures in which: Figure 1 is a block diagram detailing the conceptual layers of a proposed solution architecture according to one embodiment of the invention; and 15 Figure 2 is a flow chart providing a greater level of detail with respect to the individual steps involved in the testing of a newly configured tariff plan. DESCRIPTION OF EMBODIMENTS OF THE INVENTION With reference to Figure 1, a block diagram detailing the conceptual 20 layers of a proposed solution architecture is provided. In this solution architecture, the primary conceptual layers include a presentation layer (10), a functional services layer (20), a platform services layer (30) and an integration adapters layer (40). The tariff management automation suite including these layers interfaces with a range of existing business 25 applications (50). The presentation layer (10) includes a personalization application (12) and user interface (UI) templates (14). 30 The functional services layer (20) includes software for performing the functions of Configuration Automation (22), Deployment Automation (24) et. 8175.Specification as filed.3-Sep-09 -14 and Test Automation (26). The user interface templates (14) and personalization application (12) provided in the presentation layer (10) interface with each of the automation functional services (22, 24 and 26) as defined in the functional services layer (20) thus affording operators a 5 consistent user interface experience when invoking functions from any of the automation components in the functional services layer (20). The tariff management automation suite as depicted in Figure 1 also includes a platform services layer (30) which includes system administration 10 components (32), a security access component (34), audit trail and logging component (36) and an exception handling component (38). Software components residing in the integration adapters layer (40) enable the functional components of the tariff management automation suite 15 to interface with existing business applications of the telecommunications service provider. As an example, in Figure 1, the business applications layer (50) includes a functional software component (52) in the form of a billing management software program. 20 Figure 2 provides a summary level flow chart of the primary steps involved in the testing of proposed tariff and/or billing configurations depicted as test automation (26) in Figure 1. The flow chart does not illustrate the operational aspects which are generally effected by relational data bases that are managed by the execution of SQL (Structured Query Language) scripts. 25 These scripts perform actions such as inserting, updating and/or deleting entries from data bases. In addition to these basic functions, scripts can be used to perform complex logical functions such as searching and sorting. The test automation flow chart depicts a graphical user interface 30 (GUI) browser based front end and presents a "tabbed" interface to the user. Each tab represents a working module and contains a form which requires completion by the user. The form will allow data to be inserted directly or by ct.18175.Specification as filed.3-Sep-09 - 15 invoking "drop down boxes". There are five (5) tabs which include the following tabs in order: Account creation (100), Service creation (102), Add Package/component (104), Usage (106) and Billing (108). 5 The first module 100 will now be described. All modules require a user to logon onto the system. At 110 a user enters their name and password to open the test automation system. Account creation (100) allows the user to create test accounts in bulk mode. The user can create accounts with a particular set of attributes. At step (112) the "Account Creation" screen 10 is opened to initiate the process. The user will need to know the types of accounts to be created and the number of accounts. In contrast to the prior art, the user is not limited to the creation of one account but can create a number of accounts simultaneously. The form to select the criteria for the accounts is completed at step (114). Once the criteria for the accounts are 15 completed then the accounts are created at step (116) by accessing the various databases. The selected number of accounts is created with the set of attributes which have been selected. Each account will contain name and address details together with billing cycle period, market code, discounts, etc. The accounts generated would be tested at step (118) for any errors and 20 confirmation is provided that the accounts should be saved. Once complete, this module will allow access through step (120) to the service creation module (102) and is directed to the enter "Service Creation" screen at step (122). 25 The service creation module (102) allows the user to attach a service, or multiple services, to one or more accounts. Services are predefined and could be mobile, fixed line or ISP. At step (122) the "Service Creation" screen is opened to initiate this process. In contrast to the prior art, the user is not limited to the creation of one service at a time for a single 30 account. A form is completed at step (124). The form would include selections for mobile, fixed line and ISP services which can be attached to one or more accounts as required. Drop down choices and range boxes ct. 18175.Specification as filed.3-Sep-09 -16 would be able to assist in this selection together with "drag and drop" options at step 126. Once the selections have been made each account is populated with the defined service or services at step (128). Validation for each account occurs at step (130). Once complete, this module will allow access 5 through step (132) to the add package/component module (104) and is directed to the Enter "Add Package/Component" Screen at step (134). The add package/component module (104) allows the user to add packages or components to accounts and services. The packages or 10 components are predefined. Packages could include data, special promotions, 3G, etc. Components may include call waiting, SMS, WAP, international roaming, etc. At step (134) the "Add Package/Component" screen is opened to initiate this process. in contrast to the prior art, the user is not limited to the creation of one component or package at a time to a 15 single account. A form is opened at step (136). The form at step (138) allows the components or packages to be associated with multiple accounts as required. Once the selections have been made, each account is populated with the defined components or packages at step (140). Validation for each account occurs at step (142). Once complete, this module will allow 20 access through step (144) to the usage module (106) and is directed to the Enter "Usage" Screen at step (146). The usage module (106) allows the user to process default usage files or to create custom usage files to generate call transactions for an 25 account or multiple accounts. At step (146) the "Usage" screen is opened to initiate this process. In contrast to the prior art, the user does not need to know the construction of a usage file nor does he need to spend time creating one. Analysis of the file format or validation of the usage file is not required. The user at step (148) has the option of selecting one or more 30 predefined default usage files or can create a custom usage file. If a default usage file or files is required, then the user will proceed to step (150) where the selection is made from the predefined default usage files. If a default c. IS 175.Specification as filed.3-Sep-09 - 17 usage file or files is not applicable, then the user completes the fields on the form at step (152) to specify the usage criteria required. Once the criteria has been selected, step (154) will generate the required custom usage files which will be stored on the server. Custom usage files constructed by hand 5 using prior art techniques would require highly skilled operators and would require a substantial amount of time as compared with a system generating these files. The usage files are allocated to respective accounts as required. From either step (150) or step (154) the allocated usage files are processed at step (156) to generate the costs from the usage files. Validation for each 10 account occurs at step (158). Once complete, this module will allow access through step (160) to the billing module (108). The billing module (108) allows the user to execute the billing process on one or more accounts to check whether the tariff and/or billing 15 configuration would be suitable. At step (162) the "Billing" screen is opened to initiate this process. Previously, in accordance with prior art techniques, a user would be required to manually insert a list of accounts into a database table. The process would require a text based command from the UNIX command line to be executed to start the bill process. In the present 20 embodiment, a form is completed at step (164). The form specifies the mode of billing and the accounts to be billed. The bills are then processed under step (166). Validation for each account occurs at step (168). Once validation is complete this module will produce the required bills and summary reports on the operation of the test automation (26). The results can then be 25 analyzed to determine whether the billing plan could be rolled out and the consequences of such a roll out. The invention is not limited to the configuration discussed in the preferred embodiment. The database implementations and tabbed user 30 interface can be substituted by equivalents. A browser based interface is preferred for ease of use but a menu driven interface may also be used. ct. 18175.Specification as filed.3-Scp-09 - 18 To assist the understanding of this invention the following terms are used in this specification. Account: an entity in the billing system which holds all customer 5 information including personal details and billing information. Service: an entity attached to an account e.g. mobile, fixed line, broadband. Inventory such as phone number, SIM, IP addresses are tied to a service. Package: the bill plan which the account subscribes to based on its 10 service e.g. a mobile plan with $75 monthly access fee and 30 minutes of free calls. Component: subset entity contained within a package in which a customer has the option to add to a package e.g. voicemail, call forwarding, missed call notification. 15 Usage: calls (e.g. local calls, IDD calls, SMS, GPRS, roaming inbound/outbound calls) Rate: All usages are stored in the usage file with details of the transaction such as start and end time of call, origin and target location, type of call, rate period e.g. peak/off peak and other details. The billing system will 20 process these individual records (calls) in the usage file to identify which configured rate the combination of details match and then assign it a rate i.e. the price for that call. This is the basis of usage processing - to rate the call and then to insert the record of the rated call into the database. Bills: Generated by the system when the bill generation process is 25 executed. The process involves a complex logic of steps taken by the system to accumulate all monthly and one time charges, as well as call amounts within the billing period (e.g. monthly, quarterly, yearly). It will then apply any discounts or credits where applicable. 30 It will be appreciated by persons skilled in the relevant field of technology that numerous variations and/or modifications may be made to the invention as detailed in the embodiments without departing from the spirit ct. 18175.Specification as filed.3-Sep-09 -19 of the scope of the invention as broadly described. The present embodiments are, therefore, to be considered in all aspects as illustrative and not restrictive. 5 For the purposes of this specification and claims the terms "tariff' and "billing" should be considered to have the same meaning. ct 18175.Specification as filed.3-Sep-09

Claims

1. A computer-implemented method including: receiving data specifying a proposed billing plan for users of 5 telecommunications services, wherein the proposed billing plan is proposed for testing as a candidate billing plan prior to being implemented for the telecommunications services and prior to being offered to users of the telecommunications services; receiving data specifying a type, a quantity, and attributes of simulated 10 user accounts to be generated, wherein the simulated user accounts correspond to non-actual users and are generated for testing; generating, in bulk, the specified type and quantity of simulated user accounts that have the specified attributes; receiving data identifying the telecommunications services to be attached 15 to each of the simulated user accounts, then attaching the identified telecommunications services to each of the simulated user accounts; receiving data identifying telecommunications units to be added to one or more of the telecommunications services that are attached to each of the simulated user accounts, then adding the telecommunications units to the one or 20 more of the telecommunications services that are attached to each of the simulated user accounts; receiving data identifying pre-defined, simulated usage data, then applying portions of the simulated usage data to each of the simulated user accounts, wherein the simulated usage data corresponds to non-actual users; 25 after applying the portions of the simulated usage data to each of the simulated user accounts, receiving data indicative of an instruction selected by an operator to test the proposed billing plan on the simulated user accounts, then testing the proposed billing plan on the simulated user accounts; and generating, based on results of the testing of the proposed billing plan on 30 the simulated user accounts, a respective test bill for each simulated user account.

2. A method according to claim 1, wherein the pre-defined, simulated usage data is received from one or more default usage files selected by the operator. -21

3. A method according to claim 1, wherein the pre-defined, simulated usage data is received from one or more generated custom usage files that include usage data specified by the operator. 5

4. A method according to claim 3, wherein the operator specifies the usage data by selecting options provided to the operator by a user interface.

5. A method according to any one of the preceding claims, wherein the 10 telecommunications units include pre-defined packages and components, wherein: the pre-defined packages include data packages, special promotions packages, and third generation (3G) packages; and the pre-defined components include call waiting components, short 15 message service (SMS) components, wireless application protocol (WAP) components and international roaming components.

6. A method according to any one of the preceding claims, wherein generating, as a result of the testing of the proposed billing plan on the simulated 20 customer accounts, further includes: generating one or more summary reports for the test.

7. A method according to any one of the preceding claims, further including: analyzing each respective test bill for each simulated customer account; 25 and implementing the proposed billing plan for the telecommunications services based on the analysis.

8. A method according to any one of the preceding claims, further including 30 testing each of the generated simulated user accounts for errors, and based on determining that a simulated user account is free of errors, saving the respective simulated user account. -22

9. A method according to any one of the preceding claims, wherein the telecommunications services include mobile services, fixed line services and internet service provider (ISP) services. 5

10. A method according to any one of the preceding claims, further including: validating each of the simulated user accounts after attaching the identified telecommunications services to each of the simulated user accounts and before adding the telecommunications units to one or more of the telecommunications services; 10 validating each of the simulated user accounts after adding the telecommunications units to the one or more of the telecommunications services and before applying portions of the simulated usage data to each of the simulated user accounts; and validating each of the simulated user accounts after applying portions of 15 the simulatedusage data to each of the simulated user accounts and before generating a respective test bill for each simulated user account.

11. A system including: one or more computers; and 20 a computer-readable medium coupled to the one or more computers having instructions stored thereon which, when executed by the one or more computers, cause the one or more computers to perform operations including: receiving data specifying a proposed billing plan for users of telecommunications services, wherein the proposed billing plan is 25 proposed for testing as a candidate billing plan prior to being implemented for the telecommunications services and prior to being offered to the users of the telecommunications services; receiving data specifying a type, a quantity, and attributes of simulated user accounts to be generated, wherein the simulated user 30 accounts correspond to non-actual users and are to be generated for testing; generating, in bulk, the specified type and quantity of simulated user accounts that have the specified attributes; -23 receiving data identifying the telecommunications services to be attached to each of the simulated user accounts, then attaching the identified telecommunications services to each of the simulated user accounts; 5 receiving data identifying telecommunications units to be added to one or more of the telecommunications services that are attached to each of the simulated user accounts, then adding the telecommunications units to the one or more of the telecommunications services that are attached to each of the simulated user accounts; 10 receiving data identifying pre-defined, simulated usage data, then applying portions of the simulated usage data to each of the simulated user accounts; after applying the portions of the simulated usage data to each of the simulated user accounts, receiving data indicative of an 15 instruction selected by an operator to test the proposed billing plan on the simulated user accounts, then testing the proposed billing plan on the simulated user accounts; and generating, based on results of the testing of the proposed billing plan on the simulated user accounts, a respective test bill for each 20 simulated user account.

12. A system according to claim 11, wherein the pre-defined, simulated usage data is received from one or more default usage files selected by the operator. 25

13. A system according to claim 11, wherein the pre-defined, simulated usage data is received from one or more generated custom usage files that include usage data specified by the operator.

14. A system according to claim 13, wherein the operator specifies the usage 30 data by selecting options provided to the operator by a user interface.

15. A system according to any one of claims 11 to 14, wherein the telecommunications units include pre-defined packages and components, wherein: -24 the pre-defined packages include data packages, special promotions packages, and third generation (3G) packages; and the pre-defined components include call waiting components, short message service (SMS) components, wireless application protocol (WAP) 5 components and international roaming components.

16. A system according to any one of claims 11 to 15, wherein the operation of generating, as a result of the testing of the proposed billing plan on the simulated customer accounts, further includes: 10 generating one or more summary reports for the test.

17. A system according to any one of claims 11 to 16, the operations further including: analyzing each respective test bill for each simulated customer account; 15 and implementing the proposed billing plan for the telecommunications services based on the analysis.

18. A system according to any one of claims 11 to 17, the operations further including testing each of the generated simulated user accounts for errors, and 20 based on determining that a simulated user account is free of errors, saving the respective simulated user account.

19. A system according to any one of claims 11 to 18, wherein the telecommunications services include mobile services, fixed line services and 25 internet service provider (ISP) services.

20. A system according to any one of claims 11 to 19, the operations further including: validating each of the simulated user accounts after attaching the identified 30 telecommunications services to each of the simulated user accounts and before adding the telecommunications units to one or more of the telecommunications services; validating each of the simulated user accounts after adding the telecommunications units to the one or more of the telecommunications services -25 and before applying portions of the simulated usage data to each of the simulated user accounts; and validating each of the simulated user accounts after applying portions of the simulated usage data to each of the simulated user accounts and before 5 generating a respective test bill for each simulated user account.

21. A computer-readable medium coupled to one or more computers having instructions stored thereon which, when executed by the one or more computers, cause the one or more computers to perform operations including: 10 receiving data specifying a proposed billing plan for users of telecommunications services, wherein the proposed billing plan is proposed for testing as a candidate billing plan prior to being implemented for the telecommunications services and prior to being offered to the users of the telecommunications services; 15 receiving data specifying a type, a quantity, and attributes of simulated user accounts to be generated, wherein the simulated user accounts correspond to non-actual users and are to be generated for testing; generating, in bulk, the specified type and quantity of simulated user accounts that have the specified attributes; 20 receiving data identifying the telecommunications services to be attached to each of the simulated user accounts, then attaching the identified telecommunications services to each of the simulated user accounts; receiving data identifying telecommunications units to be added to one or more of the telecommunications services that are attached to each of the 25 simulated user accounts, then adding the telecommunications units to the one or more of the telecommunications services that are attached to each of the simulated user accounts; receiving data identifying pre-defined, simulated usage data, then applying portions of the simulated usage data to each of the simulated user accounts; 30 after applying the portions of the simulated usage data to each of the simulated user accounts, receiving data indicative of an instruction selected by an operator to test the proposed billing plan on the simulated user accounts, then testing the proposed billing plan on the simulated user accounts; and -26 generating, based on results of the testing of the proposed billing plan on the simulated user accounts, a respective test bill for each simulated user account. 5

22. A computer-implemented method according to claim 1, or a system according to claim 11, or a computer-readable medium according to claim 21, substantially as hereinbefore described with reference to the accompany Figures.