CA2616194C - Revenue management system and method - Google Patents

Revenue management system and method Download PDF

Info

Publication number
CA2616194C
CA2616194C CA2616194A CA2616194A CA2616194C CA 2616194 C CA2616194 C CA 2616194C CA 2616194 A CA2616194 A CA 2616194A CA 2616194 A CA2616194 A CA 2616194A CA 2616194 C CA2616194 C CA 2616194C
Authority
CA
Canada
Prior art keywords
memory
data
request
manager
objects
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CA2616194A
Other languages
French (fr)
Other versions
CA2616194A1 (en
Inventor
David Scott Labuda
Jayaprakash Krishnamoorthy
James R. Haddock
Alexander Rockel
Keith M. Brefczynski
Giles Douglas
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Oracle International Corp
Original Assignee
Oracle International Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oracle International Corp filed Critical Oracle International Corp
Publication of CA2616194A1 publication Critical patent/CA2616194A1/en
Application granted granted Critical
Publication of CA2616194C publication Critical patent/CA2616194C/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/04Billing or invoicing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12Accounting
    • G06Q50/60

Abstract

A real-time customer relation management system is disclosed. The system can provide increased availability, reduced internal latencies, and reduced data processing and transfer. The system can provide real time processing and batch processing. The system architecture can have an in-memory write-through cache. The cache can store data that would have otherwise been sent to a database. The system can have a backup in-memory write-through cache. The system can use a warm standby, for example, to enhance data backup efficiency.

Description

REVENUE MANAGEMENT SYSTEM AND METHOD
[0002] This invention relates to a revenue management system that has an in-memory 11 write-through cache.
12 [0003] Prepaid phone accounts are tracked in real-time by billing and time 13 management hardware and software architectures in communication with the phone 14 network switch. The architecture approves the customer's call if there are sufficient funds in the customer's prepaid account. If the customer runs out of time on his 16 prepaid account during a call, the architecture acts to terminate the call.
17 [0004] These architectures are known as customer relation management (CRM) 18 systems. CRM systems are also used for non-prepaid scenarios, such as for 19 generating bills. CRM systems are also used for other telecommunications, and other network management scenarios.
21 [0005] Prepaid account CRM systems need to have the ability to track accounts in 22 real-time. Available real-time architectures for managing prepaid customer accounts 23 have some existing limitations.
24 [0006] First, the available architectures require high performance and data throughput, thereby leading to relatively high hardware requirements. These 26 architectures, along with their storage and maintenance can be expensive and time-27 consuming.
28 [0007] Second, requirements for very low system response latencies are difficult to 29 achieve. Transactions in existing architectures involve several round-trips to the disk-based storage subsystem. The data must be processed by a comparatively large 31 software stack to transform from a relational representation into a physical storage 32 format.
33 [0008] Third, in an available architecture, the data is transferred several times from 34 component to component of the system to retrieve the data, map it from a relational 1 format to an object format, process it with the desired business logic, and then transfer 2 the response to the client.
3 [0009] Fourth, currently available architectures can not provide desired levels of data 4 availability to the public phone network (e.g., the switch). The close connection of a prepaid CRM system to the public network increases the data availability 6 requirements. Being part of the public network, some parts of the system need to 7 have carrier-grade availability.
8 [0010] Also, no single product accomplished both batch processing and real-time 9 processing for telecommunications CRM (e.g., billing) purposes.

12 [0011] A system and method for managing any numerical account information is 13 disclosed. For example, the system and method can be used for managing revenue for 14 telecommunications system. The system and method can be used to manage account balances, such as user accounts for the telecommunications system. Management of 16 account balances can include altering the balance of the account during use, and/or 17 querying the account (e.g., by the account holder or a customer service 18 representative), and/or querying the account to produce a billing statement or perform 19 other accounting features, and/or querying the account to determine whether to authorize use of the account.
21 [0012] The system can be used with an account with an existing balance (e.g., 22 prepaid), an account with a maximum use limit (e.g., capped), a current payment 23 account (e.g., now-pay, for example through the use of a credit card), other types of 24 balance management accounts, or combinations thereof.
[0013] The system architecture can be configured to increase performance, and 26 availability and decrease latency. The system and method can manage accounts, for 27 example, for the prepaid wireless markets handling services such as GSM, GPRS and 28 SMS.
29 [0014] The system can have a rating engine, a billing engine, and a first, high-speed, memory (e.g., transaction in memory object store (TIMOS)). The first memory can 31 be a virtual database cache. The first memory can be a typical on-board RAM storage 32 location.

1 [0015] The first memory can be a smart cache. The smart cache can treat different 2 object types different ways. For example, the smart cache can treat reference objects, 3 database-only objects, and transient object differently.
4 [0016] Reference objects can be owned by the database and never updated by the first memory. Reference objects can include dynamic reference objects (e.g., an account 6 balance) that change each call, and static reference objects (e.g., the billing rate for 7 different types of calls) that never or rarely change. Database-only objects can be 8 objects that change one-time or rarely during the call and are not referred to by the 9 connection manager. Transient objects can exist, for example, only in-memory (e.g., in T11\40S). Transient objects can be unwritten to the database. Transient objects can 11 be written to the database, for example, at the end of the call (e.g., credit balance).
12 [0017] The database can have a data dictionary. The data dictionary can by written 13 by the users. The data dictionary can define an object type and what type of object 14 each other is. Customers can edit the data dictionary if so desired.
[0018] The new revenue management system can have a high availability. The 16 system can have a warm standby operation by referring to any data remaining in 17 TIMOS. During warm standby, in the case of a loss of data, the system can recreate 18 data from the switch and/or TIMOS when the switch sends re-authorization data (e.g., 19 during long calls) or end-of-call data.
[0019] A known failure protection scheme with a high availability (monitor) regularly 21 checking the status of the control manager, TIMOS, data manager, the database 22 manager, and the database is also disclosed.
23 [0020] A self-container failure protection system is disclosed. Each component of the 24 system can check on the status of its immediately downstream component.
If the downstream component has failed, or is passing along a failure message regarding a 26 further downstream component failure, the system can take appropriate action, 27 including alerting a user.

[0021] Figure 1 illustrates a variation of the revenue management system architecture 31 connected to a switch over a network.
32 [0022] Figure 2 illustrates a variation of the revenue management system architecture 33 connected to a switch over a public network.

1 [0023] Figures 3 through 5 illustrate variations of the revenue management system 2 architecture.
3 [0024] Figure 6 illustrates a variation for a method for using the revenue management 4 system.
[0025] Figure 7 illustrates process flows for variations for methods for using the 6 revenue management system.
7 [0026] Figure 8 illustrates a variation for a method for using the revenue management 8 system.
9 [0027] Figure 9 illustrates process flows for variations for methods for using the revenue management system.
11 [0028] Figure 10 illustrates a variation for a method for using the revenue 12 management system.
13 [0029] Figure 11 illustrates process flows for variations for methods for using the 14 revenue management system.
[0030] Figures 12a through 14 illustrate variations of the revenue management 16 system.

19 [0031] A computer-based system and method for managing any numerical account information is disclosed. For example, the system and method can be used for 21 managing revenue for telecommunications system. The system and method can be 22 used to manage account balances, such as user accounts for the telecommunications 23 system. The management of account balances can include altering the balance of the 24 account during use, and/or querying the account (e.g., by the account holder or a customer service representative), and/or querying the account to produce a billing 26 statement or perform other accounting features, and/or querying the account to 27 determine whether to authorize use of the account.
28 [0032] Figure 1 illustrates a telecommunication device 2, such as a phone, computer, 29 or fax machine, that can be connected through a public telephone network 4 to a switch 6. The telecommunication device 2 can be communicating with a second 31 telecommunication device through the switch 6. The switch 6 can communicate 32 across a network and through a gateway 8 (e.g., having a protocol translator) to the 33 revenue management system 100. The gateway 8 can communicate directly with a 34 business logic module 10 or business logic application (e.g., Portal Infranet, Portal 1 Software, Inc. Cupertino, CA). The business logic module 10 can communicate with 2 a database system 12 to determine whether the telecommunication device 2 connected 3 to the switch 6 has permission to connect and/or stay on the line. The database 4 system 12 can have a highly-available Oracle RAC database cluster. The system 100 can utilize Oracle transaction management functionality.
6 [0033] Figure 2 illustrates that the gateway 8 can be a part of the revenue 7 management system 100. The gateway 8 can interface between the business logic 8 module 10 and an intelligent network (IN) service control point system (SCP) 14.
9 The service control point system 14 can facilitate communication between the switch 6 and the gateway 8. The SCP system 14 can be software or a remote computer 11 database within the network that receives queries, for example from service switching 12 points (SSP), in order to process applications, such as 800 and LNP
number lookups 13 and calling card verification. The SCP system 14 can process the applications 14 utilizing the customer management system 100. The gateway 8 can be a high-speed protocol translator from the IN SCP to the remainder of the revenue management 16 system 100.
17 [0034] Figure 3 illustrates that the business logic module 10 can have one or more 18 rating connection managers (CM) 16a and 16b, a first memory data manager 18 (e.g., 19 TIMOS Data Manager (DMT) from Portal Software, Inc.), and one or more second memory data managers 20a and 20b (e.g., Oracle Data Manager (DM Oracle). The 21 second memory data managers 20a and 20b can communicate with the database 22 system 12 or other second memory system. The database system 12 can have one or 23 more database clusters 22a and 22b (e.g., Oracle Real Application Clusters), for 24 example, providing high availability and scalability for databases running on the cluster. The database clusters 22a and 22b can support one or more databases 24.
26 [0035] The business logic module can be accessed via the gateway 8 and/or via a 27 manual access application 26. The manual access application 26 can be operated 28 manually or automatically. The manual access application 26 can be configured, for 29 example, to be used by billing software to generate invoices, and/or by a customer service representative to check on account status, and/or by the account-holder to 31 check account status.
32 [0036] The revenue management system 100 can have a first memory (e.g., TIMOS) 33 and a second memory (e.g., database). The first memory can be, for example, in 34 and/or in communication with the first memory data manager 18. The first memory 1 can be configured to have faster, slower, and/or the same read, and/or write, and/or re-2 write speeds (e.g., access speeds) as the second memory. The first memory can be an 3 in-memory data store and database cache dedicated to high-speed rating and 4 authorization requirements.
[0037] The first memory can be solid state memory, such as system memory (e.g., 6 RAM) or one or more hard drives, for example with fast access speeds.
Requests for 7 data in the first memory can be processed faster than requests for data in a second 8 memory.
9 [0038] The first data in a first data object can be stored in the first memory in the format used by the business logic module 10 (e.g., Portal Infranet, Portal Software, 11 Inc.). The first data can be left untranslated before storage in the first memory. The 12 internal search and storage algorithms can be optimized for in-first-memory data.
13 Storing the first data in the first memory can, for example, eliminate the round trip to 14 the second memory (e.g., one or more databases, such as on database servers), and can speed the process of storing, editing and/or querying the first data.
Object 16 creation or updates for the first data objects can require no access of the second 17 memory. Updates for the first data objects can be performed in the first memory. The 18 system can have, for example, a reduced throughput and/or latency.
19 [0039] The first memory data objects (e.g., transient objects) can be stored in the first memory and/or the second memory. For example, the first memory data objects can 21 be stored not in the database and not be persisted in the first memory.
The first 22 memory objects can, for example, exist only in the process heap memory of the first 23 memory. The first memory objects can be, for example, managed in a transactional 24 manner (e.g., like the other memory objects).
[0040] First memory data objects can be removed from the first memory by shutdown 26 of the first memory or the business logic executing a delete operation on the first 27 memory data object. The store for first memory data objects can be a fixed size, for 28 example, determined during startup of the first memory process.
29 [0041] The first memory data manager 18 can be configured to improve access times and latency on moving and/or writing and/or editing and/or deleting and/or querying 31 objects.
32 [0042] The second memory can be in and/or in communication with the second 33 memory data manager 20. Requests for second memory data objects can be sent to 34 the second memory data manager 20. The second memory, for example, can be a 1 disk-based (e.g., on one or more hard drives) database. The database can be a 2 relational database (RDBMS).
3 [0043] The system can have low access second memory data objects (e.g., database-4 only objects). The low access second memory data objects can be stored primarily and/or exclusively in the second memory (e.g., one or more databases). The low 6 access second memory data objects can be stored in the first memory none of the 7 time, or some of the time.
8 [0044] The first memory data manager can access the low access second memory data 9 object type via a pass-through mode. For example, requests can be forwarded to the second memory data manager (e.g., DM Oracle), and responses can be forwarded 11 back to the first memory data manager.
12 [0045] The high access second memory data objects (e.g., reference objects) can be 13 updated seldom and not during high-speed session processing. The high access 14 second memory data objects can be stored (cached) in a first memory reference object cache (ROC). The high access second memory data objects can grow in number in 16 relation to growth in the subscriber base.
17 [0046] The high access second memory data objects can exist in the first memory an 18 equal amount of time as length of the first memory process. A newly started first 19 memory instance can contain no high access second memory data objects.
[0047] Updating and creating high access second memory data objects can be 21 performed in the second memory and in the first memory. in the high access second 22 memory data objects can be updated or created asynchronously or synchronously in 23 the second memory and the first memory.
24 [0048] The high access second memory data objects can be static or dynamic. The static high access second memory data objects can be queried, updated, created, or 26 deleted at irregular intervals. The static high access second memory data objects can 27 be, for example, subscriber information such as the list of subscribed services and the 28 chosen tariff plans.
29 [0049] The dynamic high access second memory data objects can be touched (e.g., queried, updated, created, deleted) after the completion of each session. The dynamic 31 high access second memory data objects can be, for example, the monetary and non-32 monetary balances belonging to a subscriber account.
33 [0050] A standby-first memory (e.g., for a high availability variation that can have an 34 active first memory and a backup, standby first memory) can preload the static high 1 access second memory data objects. Changes of static reference objects can be 2 propagated from the active first memory to the standby first memory.
3 [0051] The gateway 8 can directly communicate with the business logic module 10.
4 For example, during a customer's use of the telecommunication network, the gateway 8 can communicate with a first connection manager (CM) 16a. The gateway 8 can 6 pass requests to the CM 16a, for example, calling the appropriate business logic 7 routines depending on the type of request that is indicated from the IN
SCP 14. The 8 gateway 8 can be nearly stateless. The gateway 8 can provide fast failover 9 capabilities, for example, accompanied by a degraded mode of operation that is used when the lower architecture layers become unavailable. The gateway 8 can perform 11 authentication, authorization and accounting procedures.
12 [0052] Events received by the CM can be rated via an embedded rating engine using 13 the data provided from the first memory data manager 18 (e.g., DM TIMOS
cache) 14 and the database system 12. The rating engine can produce rates for customer use of the telecommunications network under the specific conditions that apply (e.g., time of 16 day, day of week, network used). The rating engine can cache pricing objects itself, 17 for example, in order to reduce the number of network roundfrips necessary to 18 complete the rating phase. The rating engine can perform zoning and discounting 19 rating.
[0053] Based on the object type, the first memory data manager 18 can pass the 21 request to the database system 12, query the first memory data manager 18 reference 22 object cache or accesses the first memory (e.g., in-memory store) for transient objects.
23 The object types and their locations can be defined in a business logic database (e.g., 24 Intranet Data Dictionary by Portal Software, Inc.), which can be in the database system 12. Traffic for objects not in the first memory can be allowed to bypass the by 26 accessing the database manager 20, for example, in the same way a commonly used 27 system without the first data manager would be configured. The data integrity of the 28 first memory can be ensured by a platform-managed synchronization mechanism that 29 can propagate the necessary updates to the first memory. The first memory can have one or more caches.
31 [0054] Figures 4a and 4b illustrate variations of the revenue management system 100.
32 The gateway 8 can act as a high-speed protocol translator as well as an SLA monitor 33 with fallback capabilities. The CM 16 can receive requests from the gateway 8. The 34 CM 16 can have the authorization, authentication and accounting business logic (e.g., 1 for delivery to the gateway 8). The CM 16 can call operational codes on the first data 2 manager 18. The CM 16 can be replaced with another client, such as a migration tool.
3 The CM 16 can have a realtime pipeline (RTP) 28. The RTP 28 can be configured to 4 adjust the rating, for example by discounting and zoning the rate. The RTP 28 can be optionally used by the CM 16 while rating.
6 [0055] The first data manager 18 can have a data migratory subsystem 30.
The data 7 manager subsystem 30 can be used to fill the high access second memory object cache 8 after start or fail over.
9 [0056] The first data manager 18 can have a directory server 32. The directory server 32 can be configured to identify the correct first memory/second memory 11 combinations in scaled scenarios with more second memory instances than first 12 memory instances or more first memory instances than second memory instances.
13 The directory server 32 can enable the gateway instances and CM
instances to be 14 independent of the number of first memory instances. The number and location of gateway and CM processes can be flexibility and scalability with respect to the 16 number and location of first memory instances.
17 [0057] Figure 4a shows that the elements of the architecture of the business logic 18 module can all be standalone. Figure 4b illustrates that the numerous elements of the 19 architecture can be integrated.
[0058] Figure 5 illustrates that the first memory 102 can have a reference object cache 21 (ROC) 34 and a transient object store (TOC) 36. The ROC 34 can be managed by a 22 separate set of rules than the TOC 36. The ROC 34 and the TOC 36 can be in the 23 same or different parts of the first memory 102. The first memory 102 can be part of, 24 or separate but in communication with, the first memory data manager 18.
The ROC
34 can be configured to cache high access second memory data objects (e.g., 26 reference objects). The TOC 36 can be configured to store first memory data objects 27 (e.g., transient objects).
28 [0059] Figure 6 illustrates a method for accessing a first memory data in the TOC 36.
29 The CM 16 can send, shown by arrow 38, a request to the first data manager 18. The request can apply to the first memory data. The first data manager 18 can analyze the 31 request 38. The first data manager 18 can conclude that the request applies to the first 32 memory. The first data manager 18 can apply or execute the request on the TOC 36.
33 The first data manager 18 can generate a reply and send, shown by arrow 40, the reply 34 to the CM 16.

1 [00601 Figure 7 illustrates flows of various requests from the CM 16 and the replies to 2 the requests. The instructions are shown as create, update, delete and search/read 3 (i.e., query). The request from the CM 16 can be, respectively, create the first data 4 object, update the first data object, delete the first data object, and search/read the first data object. (The numbers of the requests and replies illustrate an exemplary 6 chronological order.) The first data manager 18 can convert or otherwise translate the 7 request from the CM 16 to a first data manager instruction, such as add the first data 8 object, change the first data object, remove the first data object, and find the first data 9 object, respectively. The first data manager 18 can apply or execute the first data manager instruction on the TOC 36. The first data manager 18 can then return a 11 reply. The replies can include the data searched, and/or confirmation that the task was 12 completed successfully, and/or an error code and or error explanation.
13 [0061] Figure 8 illustrates a method for accessing high access memory data in the 14 ROC 34 and in the database system 12. The CM 16 can send, shown by arrow 38, a request to the first data manager 18. The request can apply to the high access second 16 memory data. The first data manager 18 can analyze the request 38. The first data 17 manager 18 can conclude that the request applies to the high access second memory 18 data. The first data manager 18 can determine whether the high access second 19 memory data is in the ROC 34. If the first data manager 34 determines that the high access second memory data is in the ROC 34, the first data manager 18 can apply or 21 execute the request on the high access second data in the ROC 34. The first data 22 manager 18 can send the request to the second data manager 20. The second data 23 manager 20 can apply or execute the request on the high access second data in the 24 database system 12. The database system 12 and/or the second data manager 20 and/or the first data manager 18 can generate one or more replies. The replies can be 26 sent, shown by arrow 40, directly or via the first data manager 18 to the CM 16.
27 [0062] Figure 9 illustrates flows of various requests from the CM and the replies to 28 the requests. The exemplary instructions are shown as create, update, delete, simple 29 and complex searches/reads (i.e., query). The request from the CM 16 can be, respectively, create the first data object, update the first data object, delete the first 31 data object, and search/read the first data object. (The numbers of the requests and 32 replies illustrate an exemplary chronological order.) The first data manager 20 can 33 convert or otherwise translate the request from the CM 16 to a first data manager 34 instruction, such as add the first data object, change the first data object, remove the 1 first data object, and find the first data object, respectively. The first data manager 2 can then apply or execute the translated request on the high access second data in the 3 ROC 34.
4 [0063] The first data manager 18 can send the request to the second data manager 20 and/or the CM 16 can send the request directly to the second data manager 20.
The 6 second data manager 20 can convert or otherwise translate the request to a second 7 data manager instruction, such as insert the row of data, update the row of data, delete 8 the row of data, and select the row or rows of data, respectively (with no response 9 shown for a simple search/read, although the second data manager can perform simple searching). The second data manager 20 can apply or execute the request on the high 11 access second data in the database system 12. The second data manager 20, and/or 12 the database system 12 and/or the first data manager 20 can then return a reply. The 13 replies can include the data searched, and/or confirmation that the task was completed 14 successfully, and/or an error code and or error explanation.
[0064] Figure 10 illustrates a method for accessing low access memory data in the 16 database system 12. The CM 16 can send, shown by arrow 38, a request to the first 17 data manager 18, and/or directly to the second data manager 18. The request can 18 apply to the high access second memory data. The first data manager 18 can analyze 19 the request 38. The first data manager 18 can conclude that the request applies to the low access second memory data. The first data manager 18 can send the request to 21 the second data manager 20. The second data manager 20 can apply or execute the 22 request on the high access second data in the database system 12. The database 23 system 12 and/or the second data manager 20 can generate one or more replies. The 24 replies can be sent, shown by arrow 40, directly or via the first data manager 18 to the CM 16.
26 [0065] Figure 11 illustrates flows of various requests from the CM and the replies to 27 the requests. The exemplary instructions are shown as create, update, delete, and 28 searches/read (i.e., query). The request from the CM 16 can be, respectively, create 29 the first data object, update the first data object, delete the first data object, and search/read the first data object. (The numbers of the requests and replies illustrate an 31 exemplary chronological order.) The first data manager 18 can send the request to the 32 second data manager 20. The second data manager 20 can convert or otherwise 33 translate the request to a second data manager instruction, such as insert the row of 34 data, update the row of data, delete the row of data, and select the row or rows of data, 1 respectively. The second data manager 20 can apply or execute the request on the 2 high access second data in the database system 12. The second data manager 20, 3 and/or the database system 12 and/or the first data manager 20 can then return a reply.
4 The replies can include the data searched, and/or confirmation that the task was completed successfully, and/or an error code and or error explanation.
6 [0066] The CM 16 can send requests directly to the desired data manager 18 or 20 7 and/or the CM 16 can tag the request and the first data manager 18 can analyze the tag 8 to determine whether to apply and/or execute the request and/or whether to send the 9 request to the second data manager. The tag can be the substance of the request (i.e., the requested action) and/or additional data solely to communicate the desired final 11 location of the request.
12 [0067] The first memory data objects of this category can be created, updated or 13 deleted in the high-speed access path of the revenue management system 100.
14 Examples of the first memory data objects include active session objects and resource reservation objects.
16 [0068] The first memory data objects can be analyzed using, for example, logical 17 predicates (e.g., equals, not equals). Queries executed on first memory data can 18 specify an index to use to satisfy the query. The index can be a hash to enable fast 19 value lookup. The index can be a single column index. Predicates on other columns can be supported by filtering the result set to find matches.
21 [0069] Requests for the first memory data objects can be passed to a standard heap 22 memory area. The requests can be created, changed and deleted within transactions.
23 [0070] The first memory data objects can be limited to particular object, such as 24 business object types.
[0071] The high access second memory data objects can be accessed only in a read-26 only mode in the high-speed access path. An example of the high access second 27 memory data objects is customer account information.
28 [0072] The ROC 34 can be filled on demand. This means that requests can be 29 redirected to the database system 12 if the high access second memory data object is not found in the ROC 34. If the request is a read of an entire object, the ROC
34 can 31 be filled or cached by the reply (e.g., as the reply passes through the first data manger 32 18 on the reply's route back to the CM 16 from the second data manager 20). Partial 33 object requests ('read _fields') of the high access second memory data objects can be 34 cached in a similar manner to that performed for the entire object.

1 [0073] The high access second memory data objects can be fully queried.
Simple 2 queries involving basic logical operators (e.g., equals, not equals) can be performed 3 by the first data manager 18 on the high access second memory data objects in the 4 ROC 34. Complex queries (e.g., involving joins to other objects, or operators such as 'like' or 'in') can be performed by the second data manager 20 on the high access 6 second memory data objects in the database system 12.
7 [0074] The dynamic high access second memory data objects can be loaded by the 8 data migrator 30 after a failover.
9 [0075] The static high access second memory data objects can be loaded by the data migrator 30 immediately after the backup first memory system has been started.
The 11 static high access second memory data objects can be synchronized with the database 12 via the first memory synchronization system.
13 [0076] The low access second memory data objects can be absent from the first 14 memory. Requests for the low access second memory data objects can be routed directly from first data manager 18 to the second data manager 20. The low access 16 second memory data objects can be fully queried.
17 [0077] The first data manager can allow reading of the first data values during a write 18 operation. The first data manager can have the write operation take place on a 19 scratchpad of data that is only visible to the writing transaction. The first data manager can serialize the first data while the update is moved to main memory at the 21 commit time.
22 [0078] The first data manager can have a read committed isolation. The read 23 committed isolation makes all committed updates available to transactions even if the 24 commit takes place after the transaction is started. Read committed isolation can prevent "dirty" reads (i.e., the first data manager preserves the earlier first data value 26 for reading during pending changes to the first data value).
27 [0079] The first data manager can support or not support statement or transaction 28 level consistent reads.
29 [0080] The revenue management system 100 can be configured to route any traffic not related to session handling can be routed to and/or away from the first memory 31 data manager 18. A synchronization system can be used to send updates to the first 32 memory data manager 18. The synchronization system can automatically propagate 33 changes affecting objects stored in the first memory to all the first memory instances 34 caching the particular object or object type.

1 [0081] The revenue management system 100 can have a convergence system.
The 2 convergence system can load batch data via the first data manager 18 into the revenue 3 management system 100, for example, to share any data of batch origin, such as 4 balances between prepaid and postpaid accounts.
[0082] The data capacity of a first memory instance can be lower than data the 6 capacity of a second memory (e.g., database) instance. One second memory instance 7 can support several shared-nothing instances of the first memory. (The commonly 8 used term is m:n (m ¨ first memory instances / n ¨ second memory instances)).
9 [0083] The first memory data manager 18 can reduce the latency for objects first memory data manager 18 handles, and at the same time enabling increased throughput 11 of the system 100.
12 [0084] For installation of first memory data manager 18, the first memory data 13 manager 18 can be configured to be inserted between the CM 16 component and 14 second memory data manager 20 component. The introduction of the first memory data manager 18 can change the access characteristics of some object types for a pre-16 existing revenue management system that did not have the first memory data manager 17 18. Installation of the first memory data manager 18 can be configured to be 18 transparent (e.g., not change object types). The system 100 can be configured so that 19 the higher-level business logic architecture layers cannot tell first memory data manager 18 is present. However, the business logic can be changed to utilize the first 21 memory data manager 18. These changes can be ignored by the system 100 if the 22 first memory data manager 18 is not present.
23 [0085] The first memory data manager 18 can be installed in an existing revenue 24 management system. For example, the first memory data manager 18 can be physically installed (e.g., mounting hardware and/or loading software onto the 26 appropriate computer-readable medium) and the base software can be configured.
27 [0086] After the installation of the base software, the first data can then be migrated 28 into the first memory data manager 18. The first memory data object residencies 29 stored in the data dictionary can take effect, loading the first data onto the first data manager 18 during use. The residencies can be part of the default business logic 31 module 10 installation (having no effect when the first memory data manager 18 is 32 not present) or can be loaded onto the business logic module 10 during the installation 33 of the first memory data manager 18.

1 [0087] Reference objects can be migrated by loading into the first data manager 18 2 when accessed for the first time and/or pushed into the first memory data manager 18 3 by the data migratory 30.
4 [0088] Data objects can be redefined as first memory data objects (or low access or high access second memory data objects) by deploying the data object via the normal 6 mechanism, and then updating the residency type in the data dictionary.
7 [0089] After a process startup, the first memory data manager 18 can have an empty 8 ROC 34. A separate data migration thread can push all high access second memory 9 data in the ROC 34. The static high access second memory data objects can be loaded into the ROC 34. For example, a first memory data manager 18 in backup mode can 11 load only the static high access second memory data objects into the ROC
34.
12 [0090] The data migrator 30 can provide a notification hook to signal the end of the 13 migration and/or startup phase to other processes. The first memory data manager 18 14 can be operational immediately after start (e.g., before the migratory tool sends the notification hook), for example, with an empty cache. The first request after startup 16 for a specific first data object can trigger that first data object to be loaded into the 17 cache (e.g., if the data migrator 30 has not yet loaded the desired first data object 18 already).
19 [0091] Upon a system shutdown, the first data manager 18 can close the process log file, and release used memory. The high access second memory data objects can be 21 unaffected by shutdown (e.g., remaining stored on the second memory).
22 [0092] The revenue management system 100 can provide hooks to verify and monitor 23 performance. The revenue management system 100 can log performance data on a 24 regular basis and/or make performance data available via an embedded web server. A
signal can be sent to the second memory data manager to collect desired data (e.g., for 26 some parts of the system).
27 [0093] The revenue management system 100 can create system logs that can monitor 28 operation of the revenue management system 100. A log monitoring GUI
(e.g., 29 Pipeline log viewer) can be used. Business logic style pin-logging can, for example, aid debugging and diagnosis.
31 [0094] The first memory data manager 18 can have a pipeline framework tracing 32 model. Additional trace information can be collected from subsystems of the revenue 33 management system 100 on a case by case basis.

1 [0095] Figures 12a, 12b and 12c illustrate that the revenue management system 100 2 can be scalable to large scale expansion.
3 [0096] The revenue management system 100 can have multiple second memory 4 locations (e.g., databases 24a, 24b and 24c). The revenue management system 100 can have separate instances of the first memory data manager 18a-18i, and the second 6 memory data manager 20a-201. Pairs of sets of first memory data managers and 7 second memory data manager, for example, 18a, 18b, 20a, and 20b can be formed 8 into high availability (HA) pairs 42. The HA pairs 42 can have active and backup 9 first data managers 18a and 18b, respectively, for example, and active and backup second data managers 20a and 20b, respectively, for example.
11 [0097] The revenue management system 100 can have a capacity partitioning scheme.
12 [0098] Each second memory (e.g., database 24) instance can be associated (i.e., in 13 communication) with one or more first memory data manager 18 instances.
The 14 revenue management system can be configured so no data is stored in overlapping second memory instances (n Timos instances : 1 database). The business logic 16 module can have several, independent databases (m) . The combination of 17 TIMOS/databases can be referred to as m : n configuration.
18 [0099] The CM 16a-16e can lookup in the directory server 32 to identify the first 19 memory data manager 18 and second memory data manager 20 (or database 24) combination applicable for a certain object.
21 [0100] The revenue management system 100 can have account migration tools. The 22 account migration tools can move subscriber data from one first and/or second 23 memory location (e.g., database 24 and/or first memory data manager 18) to another 24 first and/or second memory location.
[0101] Multiple second memory data managers 20 can communicate with the same 26 database clusters 22. All the databases can be managed with one database cluster 22 27 (e.g., one RAC cluster) (not shown).
28 [0102] The SCPs 14, gateways 8 and CMs 16 can each be associated to multiple first 29 memory data managers 18. The gateway 8 can support load balancing over several CMs 16. The CMs 16 can use the directory server 32 to route the requests to the 31 correct first memory data managers 18.
32 [0103] The database system 12 can run multiple database schemes in one RAC cluster 33 22. The revenue management system 100 can be configured to associate a dedicated 34 set of resources to just one SCP 14 or group of SCPs 14.

1 [0104] Figure 12b illustrates that the first memory data managers 18c and 18d can 2 communicate directly with the database system 12, for example with the database 3 clusters 22a and 22b.
4 [0105] Figure 12c illustrates that the revenue management system can have two or more database systems 12a and 12b.
6 [0106] Figure 13 illustrates a failure protection scheme with a high availability 7 monitor 44 regularly checking the status of the control manager, the first memory in 8 the first memory data manager 18, the second memory data manager 20, the database 9 cluster, and the database 24.
[0107] Figure 14 illustrates a self-contained failure protection system. Each 11 component of the revenue management system 100 can check on the status of its 12 immediately downstream component (e.g., the second memory data manager 20 is 13 immediately downstream of the first memory data manager 18). If the immediately 14 downstream component has failed, or is sending a failure message regarding a further downstream component failure, the revenue management system can take appropriate 16 action, including alerting a user that a failure has occurred. The revenue management 17 system 100 can be absent of a separate monitor component checking for system 18 failures.
19 [0108] The revenue management system 100 can have a high availability.
The revenue management system 100 can have a warm standby operation by referring to 21 any data remaining in the first memory (e.g., TIMOS). During warm standby, in the 22 case of a loss of data (e.g., during a system failure), the revenue management system 23 100 can recreate data from the switch 6 and/or the first memory when the switch 6 24 sends re-authorization data (e.g., during long calls) or end-of-call data.
[0109] The database system 24 can store the latest static high access second memory 26 data before a loss of data. The static high access second memory data can be 27 recovered to the first memory from the database system 24 after a loss of data in the 28 first memory.
29 [0110] In the revenue management system 100, higher layers (i.e., more stable during a system failure, such as the database) of architecture with very high availabilities can 31 partially or completely backup lower layers (i.e., less stable during a system failure, 32 such as a solid state RAM variation of the first memory) with lesser availabilities in 33 case of failures.

1 [0111] The revenue management system 100 can have spare, unused hardware and 2 software such as backup data managers in the high availability pairs 42, as shown in 3 Figures 12a through 12c. The high availability pair 42 can have active and a backup 4 first data managers 18 and active and backup second data managers 20. The backup data managers can copy from the respective active data managers, for example during 6 a period of no other activity with the active data manager and/or from a sketchpad, 7 and/or the last available data from the active data manager. In case of failure of an 8 element, the backup or other inactive elements will be able to restore data and/or take 9 over the additional load.

12 [0113] Accessing can include querying, updating, creating, deleting and combinations 13 thereof. Querying, updating, creating, and deleting for any data can be interchanged 14 with each other as disclosed.
[0114] It is apparent to one skilled in the art that various changes and modifications 16 can be made to this disclosure, and equivalents employed, without departing from the 17 scope of the invention. System and architecture are used as interchangeable 18 terms, both referring to one or more hardware and software components in 19 communication. All elements shown herein can be software and/or hardware components. Elements shown with any embodiment are exemplary for the specific 21 embodiment and can be used on other embodiments within this disclosure.

Claims (32)

CLAIMS:
1. A computer-based telecommunications network account management system comprising:
a first memory having a first memory access speed and storing one or more transient objects related to a communication on the telecommunications network, wherein the first memory manages the transient objects per communication and wherein the transient objects are not persisted;
a second memory having a second memory access speed and storing one or more reference objects related to the communication, wherein the second memory persists the reference objects; and a first memory manager configured to route a first request for a first object to the first memory, and configured to route a second request for a second object not to the first memory, wherein the first memory has a faster access speed than the second memory, wherein routing the first request for the first object to the first memory and routing the second request for the second object to the second memory are performed based on an object type for each of the first object and the second object and wherein the object types for the first object and the second object are defined in a user defined data dictionary stored in the second memory and wherein the data dictionary stores a user defined object type for the first object and a user defined object type for the second object.
2. The system of claim 1, further comprising a second memory manager configured to route the second object to the second memory.
3. The system of claim 1, wherein the second memory comprises a hard drive.
4. The system of claim 1, wherein the first memory comprises solid state memory.
5. The system of claim 1, wherein the first memory comprises Random Access Memory (RAM).
6. The system of claim 1, wherein the second memory comprises a relational database.
7. The system of claim 1, further comprising a database cluster.
8. The system of claim 1, further comprising a gateway configured to interface with a telecommunications network.
9. The system of claim 1, wherein the first request comprises a query.
10. The system of claim 9, wherein the second request comprises a query.
11. The system of claim 1, wherein the first request comprises a request to write.
12. The system of claim 11, wherein the second request comprises a request to write.
13. The system of claim 1, wherein the object type for the first object comprises a transient object.
14. The system of claim 13, wherein the object type for the second object comprises a reference object.
15. A method for managing a telecommunications network account, the method comprising:
storing in a first memory having a first memory access speed one or more transient objects related to a communication on the telecommunications network, wherein the first memory manages the transient objects per communication and wherein the transient objects are not persisted;
storing in a second memory having a second memory access speed one or more reference objects related to the communication, wherein the second memory persists the reference objects;
routing by a first memory manager a first request for a first object to the first memory; and routing by the first memory manager a second request for a second object not to the first memory, wherein the first memory has a faster access speed than the second memory, wherein routing the first request for the first object to the first memory and routing the second request for the second object to the second memory are performed based on an object type for each of the first object and the second object and wherein the object types for the first object and the second object are defined in a user defined data dictionary stored in the second memory and wherein the data dictionary stores a user defined object type for the first object and a user defined object type for the second object.
16. The method of claim 15, further comprising routing by a second memory manager the second object to the second memory.
17. The method of claim 15, wherein the second memory comprises a hard drive.
18. The method of claim 15, wherein the first memory comprises solid state memory.
19. The method of claim 15, wherein the first memory comprises Random Access Memory (RAM).
20. The method of claim 15, wherein the second memory comprises a relational database.
21. The method of claim 15, wherein the first request comprises a query.
22. The method of claim 21, wherein the second request comprises a query.
23. The method of claim 15, wherein the first request comprises a request to write.
24. The method of claim 23, wherein the second request comprises a request to write.
25. The method of claim 15, wherein the object type for the first object comprises a transient object.
26. The method of claim 25, wherein the object type for the second object comprises a reference object.
27. A computer-readable storage medium having stored thereon a sequence of instruction which, when executed by a processor, cause the processor to manage a telecommunications network account by:
storing in a first memory having a first memory access speed one or more transient objects related to a communication on the telecommunications network, wherein the first memory manages the transient objects per communication and wherein the transient objects are not persisted;
storing in a second memory having a second memory access speed one or more reference objects related to the communication, wherein the second memory persists the reference objects;
routing by a first memory manager a first request for a first object to the first memory; and routing by the first memory manager a second request for a second object not to the first memory, wherein the first memory has a faster access speed than the second memory, wherein routing the first request for the first object to the first memory and routing the second request for the second object to the second memory are performed based on an object type for each of the first object and the second object and wherein the object types for the first object and the second object are defined in a user defined data dictionary stored in the second memory and wherein the data dictionary stores a user defined object type for the first object and a user defined object type for the second object.
28. The computer-readable storage medium of claim 27, further comprising routing by a second memory manager the second object to the second memory.
29. The computer-readable storage medium of claim 27, wherein the second memory comprises a hard drive.
30. The computer-readable storage medium of claim 27, wherein the first memory comprises solid state memory.
31. The computer-readable storage medium of claim 27, wherein the first memory comprises Random Access Memory (RAM).
32. The computer-readable storage medium of claim 27, wherein the second memory comprises a relational database.
CA2616194A 2005-07-28 2006-07-28 Revenue management system and method Active CA2616194C (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US70368705P 2005-07-28 2005-07-28
US60/703,687 2005-07-28
PCT/US2006/029571 WO2007016412A2 (en) 2005-07-28 2006-07-28 Revenue management system and method

Publications (2)

Publication Number Publication Date
CA2616194A1 CA2616194A1 (en) 2007-02-08
CA2616194C true CA2616194C (en) 2015-02-17

Family

ID=37709236

Family Applications (1)

Application Number Title Priority Date Filing Date
CA2616194A Active CA2616194C (en) 2005-07-28 2006-07-28 Revenue management system and method

Country Status (7)

Country Link
US (1) US8117358B2 (en)
EP (1) EP1938193A4 (en)
JP (1) JP2009504030A (en)
CN (1) CN101233497B (en)
AU (1) AU2006275665A1 (en)
CA (1) CA2616194C (en)
WO (1) WO2007016412A2 (en)

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6047284A (en) 1997-05-14 2000-04-04 Portal Software, Inc. Method and apparatus for object oriented storage and retrieval of data from a relational database
US8099393B2 (en) 2002-03-22 2012-01-17 Oracle International Corporation Transaction in memory object store
US8223935B2 (en) 2005-04-30 2012-07-17 Oracle International Corporation Revenue management systems and methods
EP1935152A4 (en) 2005-06-28 2010-08-04 Oracle Int Corp Revenue management system and method
CN101233497B (en) 2005-07-28 2013-01-30 甲骨文国际公司 Revenue management system and method
US8874477B2 (en) 2005-10-04 2014-10-28 Steven Mark Hoffberg Multifactorial optimization system and method
US8223777B2 (en) 2005-11-15 2012-07-17 Oracle International Corporation Gateway for achieving low latency and high availability in a real time event processing system
KR100964969B1 (en) * 2006-12-04 2010-06-21 한국전자통신연구원 Software Portal System for providing the relation information of software and data format and operating method thereof
JP4585540B2 (en) * 2007-05-01 2010-11-24 株式会社東芝 Web application system, apparatus and program
US20100228707A1 (en) * 2009-03-05 2010-09-09 Buddha Software Inc. System for rating a service
US8504538B2 (en) 2009-03-05 2013-08-06 Matrixx Software, Inc. Dependent commit queue for a database
US8321391B2 (en) 2009-03-05 2012-11-27 Matrixx Software, Inc. Conditional commit for data in a database
CN102347950B (en) * 2011-09-29 2018-02-06 中兴通讯股份有限公司 Communication network provides the method and system of conversational services to internet
US9594536B2 (en) * 2011-12-29 2017-03-14 Ati Technologies Ulc Method and apparatus for electronic device communication
US9043274B1 (en) 2012-05-22 2015-05-26 Shoretel, Inc. Updating local database and central database
GB2505185A (en) 2012-08-21 2014-02-26 Ibm Creating a backup image of a first memory space in a second memory space.
JP6115575B2 (en) * 2013-02-04 2017-04-19 日本電気株式会社 Data set multiplicity changing device, server, data set multiplicity changing method, and computer program
US9298769B1 (en) * 2014-09-05 2016-03-29 Futurewei Technologies, Inc. Method and apparatus to facilitate discrete-device accelertaion of queries on structured data
WO2017131791A1 (en) * 2016-01-30 2017-08-03 Entit Software Llc Log event cluster analytics management

Family Cites Families (241)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4814979A (en) * 1981-04-01 1989-03-21 Teradata Corporation Network to transmit prioritized subtask pockets to dedicated processors
US4430530A (en) * 1981-08-24 1984-02-07 Stromberg-Carlson Corporation Telephony system with automatic test call generator for remote port groups
US5898762A (en) * 1985-07-10 1999-04-27 Ronald A. Katz Technology Licensing, L.P. Telephonic-interface statistical analysis system
US4849884A (en) 1986-09-05 1989-07-18 Pitney Bowes Inc. Mailing and accounting system
US4831582A (en) * 1986-11-07 1989-05-16 Allen-Bradley Company, Inc. Database access machine for factory automation network
US4868743A (en) 1986-11-25 1989-09-19 Hitachi, Ltd. Traversal method of processing tree structure information and apparatus using the same
US4918593A (en) * 1987-01-08 1990-04-17 Wang Laboratories, Inc. Relational database system
US4968873A (en) 1987-09-08 1990-11-06 Juergen Dethloff Smart card issuing and receiving apparatus
WO1989009452A1 (en) * 1988-03-25 1989-10-05 Ncr Corporation Point of sale system
US5043872A (en) 1988-07-15 1991-08-27 International Business Machines Corporation Access path optimization using degrees of clustering
US5345587A (en) 1988-09-14 1994-09-06 Digital Equipment Corporation Extensible entity management system including a dispatching kernel and modules which independently interpret and execute commands
US5010485A (en) * 1989-01-31 1991-04-23 Jbh Ventures Apparatus, system and method for creating credit vouchers usable at point of purchase stations
US5452451A (en) 1989-06-15 1995-09-19 Hitachi, Ltd. System for plural-string search with a parallel collation of a first partition of each string followed by finite automata matching of second partitions
US5036389A (en) 1989-07-14 1991-07-30 Magus, Ltd. Satellite controlled audience polling system
US5163148A (en) 1989-08-11 1992-11-10 Digital Equipment Corporation File backup system for producing a backup copy of a file which may be updated during backup
US5220501A (en) 1989-12-08 1993-06-15 Online Resources, Ltd. Method and system for remote delivery of retail banking services
US5870724A (en) * 1989-12-08 1999-02-09 Online Resources & Communications Corporation Targeting advertising in a home retail banking delivery service
AU656542B2 (en) 1990-10-01 1995-02-09 Thomas A. Bush Transactional processing system
US5291583A (en) * 1990-12-14 1994-03-01 Racal-Datacom, Inc. Automatic storage of persistent ASN.1 objects in a relational schema
US5295256A (en) * 1990-12-14 1994-03-15 Racal-Datacom, Inc. Automatic storage of persistent objects in a relational schema
US5224034A (en) 1990-12-21 1993-06-29 Bell Communications Research, Inc. Automated system for generating procurement lists
US5212787A (en) * 1991-03-12 1993-05-18 International Business Machines Corporation Method and apparatus for accessing a relational database without exiting an object-oriented environment
US5448727A (en) 1991-04-30 1995-09-05 Hewlett-Packard Company Domain based partitioning and reclustering of relations in object-oriented relational database management systems
US5305389A (en) * 1991-08-30 1994-04-19 Digital Equipment Corporation Predictive cache system
US5526404A (en) 1991-10-10 1996-06-11 Space Systems/Loral, Inc. Worldwide satellite telephone system and a network coordinating gateway for allocating satellite and terrestrial gateway resources
CA2076433C (en) 1991-10-31 1998-08-18 Brenda B. Amarant Monitoring of charges debited to an account having an assigned limit
US5499367A (en) * 1991-11-15 1996-03-12 Oracle Corporation System for database integrity with multiple logs assigned to client subsets
AU3238793A (en) * 1991-12-12 1993-07-19 Cellular Technical Services Company, Inc. Real-time information system for cellular telephones
JP3130609B2 (en) * 1991-12-17 2001-01-31 日本電気株式会社 Online information processing equipment
GB9204450D0 (en) * 1992-03-02 1992-04-15 Ibm Concurrent access to indexed data files
US5426780A (en) 1992-02-28 1995-06-20 Intergraph Corporation System for dynamic segmentation analysis using conversion of relational data into object-oriented data
US5241670A (en) 1992-04-20 1993-08-31 International Business Machines Corporation Method and system for automated backup copy ordering in a time zero backup copy session
DE4216828C2 (en) * 1992-05-21 1994-08-18 Dornier Gmbh Earth observation procedures
EP0692119A1 (en) 1992-10-22 1996-01-17 American Express Travel Related Services Company, Inc. Automated billing consolidation system and method
JPH0820982B2 (en) 1992-11-12 1996-03-04 インターナショナル・ビジネス・マシーンズ・コーポレイション How to filter items in a computer application program enclosure
FI96655C (en) 1992-12-17 1996-07-25 Nokia Telecommunications Oy Procedure for Maintaining a Group Call in a Radio Telephone System and System Controller and Subscriber Terminal for the Radio Telephone System
US5469497A (en) 1993-01-19 1995-11-21 Teledebit Networked interactive call management subsystems with prevention of simultaneous use of a single account number
US5386413A (en) * 1993-03-19 1995-01-31 Bell Communications Research, Inc. Fast multilevel hierarchical routing table lookup using content addressable memory
US5544302A (en) 1993-06-03 1996-08-06 Taligent, Inc. Object-oriented framework for creating and using container objects with built-in properties
MX9404062A (en) 1993-06-03 1995-01-31 Ericsson Telefon Ab L M CALL TRANSFER WITHIN THE CELLULAR COMMUNICATIONS SYSTEM.
US5504885A (en) * 1993-06-29 1996-04-02 Texas Instruments Incorporated O-R gateway: a system for connecting object-oriented application programs and relational databases
JP3512439B2 (en) 1993-07-08 2004-03-29 富士通株式会社 Locking method in check-in / check-out model
US6684261B1 (en) * 1993-07-19 2004-01-27 Object Technology Licensing Corporation Object-oriented operating system
WO1995003586A1 (en) * 1993-07-21 1995-02-02 Persistence Software, Inc. Method and apparatus for generation of code for mapping relational data to objects
WO1995004960A2 (en) 1993-08-02 1995-02-16 Persistence Software, Inc. Method and apparatus for managing relational data in an object cache
US5649118A (en) 1993-08-27 1997-07-15 Lucent Technologies Inc. Smart card with multiple charge accounts and product item tables designating the account to debit
US6643362B2 (en) 1998-11-19 2003-11-04 Global Crossing, Ltd. Call-processing system and method
US5548749A (en) 1993-10-29 1996-08-20 Wall Data Incorporated Semantic orbject modeling system for creating relational database schemas
US5666648A (en) 1993-11-09 1997-09-09 Leo One Ip, L.L.C. Polar relay system for satellite communication
US5590395A (en) 1993-11-10 1996-12-31 Motorola, Inc. Satellite cellular network resource management method and apparatus
US5560005A (en) 1994-02-25 1996-09-24 Actamed Corp. Methods and systems for object-based relational distributed databases
US5555444A (en) 1994-03-11 1996-09-10 Motorola, Inc. Method and apparatus for predictive operation of a communication system
SG43130A1 (en) 1994-03-30 1997-10-17 British Telecomm Data processing
US5523942A (en) 1994-03-31 1996-06-04 New England Mutual Life Insurance Company Design grid for inputting insurance and investment product information in a computer system
US5799087A (en) 1994-04-28 1998-08-25 Citibank, N.A. Electronic-monetary system
US5832068A (en) 1994-06-01 1998-11-03 Davox Corporation Data processing system with real time priority updating of data records and dynamic record exclusion
US5680573A (en) * 1994-07-12 1997-10-21 Sybase, Inc. Method of buffering data objects in a database
US5627979A (en) * 1994-07-18 1997-05-06 International Business Machines Corporation System and method for providing a graphical user interface for mapping and accessing objects in data stores
EP0789883A4 (en) * 1994-09-28 2002-07-31 Gordon T Brown Automated accounting system
US6005926A (en) 1997-08-29 1999-12-21 Anip, Inc. Method and system for global communications network management
US5694598A (en) 1994-10-12 1997-12-02 U S West Technologies, Inc. Method for mapping data between a relational format and an object-oriented format
US5613012A (en) * 1994-11-28 1997-03-18 Smarttouch, Llc. Tokenless identification system for authorization of electronic transactions and electronic transmissions
US5615249A (en) * 1994-11-30 1997-03-25 Lucent Technologies Inc. Service prioritization in a cellular telephone system
US5873093A (en) * 1994-12-07 1999-02-16 Next Software, Inc. Method and apparatus for mapping objects to a data source
US5799309A (en) 1994-12-29 1998-08-25 International Business Machines Corporation Generating an optimized set of relational queries fetching data in an object-relational database
US5893108A (en) * 1994-12-29 1999-04-06 International Business Machines Corporation System, method, and computer program product for efficiently translating relational tuples to object-oriented objects
US5732400A (en) * 1995-01-04 1998-03-24 Citibank N.A. System and method for a risk-based purchase of goods
US5706516A (en) * 1995-01-23 1998-01-06 International Business Machines Corporation System for communicating messages among agent processes
US5787403A (en) * 1995-03-08 1998-07-28 Huntington Bancshares, Inc. Bank-centric service platform, network and system
US6016341A (en) * 1995-03-22 2000-01-18 Cybiotronics, Ltd. Telephone with data acquisition means
US5845206A (en) 1995-03-24 1998-12-01 Virtual Geosatellite Holdings, Inc. Elliptical satellite system which emulates the characteristics of geosynchronous satellites
EP0823092A1 (en) 1995-04-24 1998-02-11 Aspect Development, Inc. Modeling of object-oriented database structures, translation to relational database structures, and dynamic searches thereon
US5748952A (en) 1995-05-10 1998-05-05 International Business Machines Corporation System and method for avoiding complete index tree traversals in sequential and almost sequential index probes
US5615109A (en) * 1995-05-24 1997-03-25 Eder; Jeff Method of and system for generating feasible, profit maximizing requisition sets
MX9700655A (en) * 1995-05-24 1998-01-31 Walker Asset Man Ltd Partnersh Readily openable pop-up dispenser.
US5644736A (en) 1995-05-25 1997-07-01 International Business Machines Corporation System and method for selecting components of a hierarchical file structure
US5850544A (en) 1995-06-06 1998-12-15 International Business Machines Corporation System and method for efficient relational query generation and tuple-to-object translation in an object-relational gateway supporting class inheritance
US5677945A (en) 1995-06-06 1997-10-14 Mci Corporation Account balancing and monitoring system for a telecommunications network
US5745754A (en) * 1995-06-07 1998-04-28 International Business Machines Corporation Sub-agent for fulfilling requests of a web browser using an intelligent agent and providing a report
US5701451A (en) 1995-06-07 1997-12-23 International Business Machines Corporation Method for fulfilling requests of a web browser
US5717924A (en) * 1995-07-07 1998-02-10 Wall Data Incorporated Method and apparatus for modifying existing relational database schemas to reflect changes made in a corresponding object model
US5799072A (en) 1995-07-21 1998-08-25 Callmanage Telecommunications call management system
US6321205B1 (en) 1995-10-03 2001-11-20 Value Miner, Inc. Method of and system for modeling and analyzing business improvement programs
US5913164A (en) 1995-11-30 1999-06-15 Amsc Subsidiary Corporation Conversion system used in billing system for mobile satellite system
US5870473A (en) * 1995-12-14 1999-02-09 Cybercash, Inc. Electronic transfer system and method
US5809120A (en) 1996-02-09 1998-09-15 Bell Atlantic Network Services, Inc. Telecommunications network circuit usage measurement
US5797137A (en) 1996-03-26 1998-08-18 Golshani; Forouzan Method for converting a database schema in relational form to a schema in object-oriented form
JP3113814B2 (en) * 1996-04-17 2000-12-04 インターナショナル・ビジネス・マシーンズ・コーポレ−ション Information search method and information search device
JP3636399B2 (en) 1996-05-29 2005-04-06 富士通株式会社 Protocol conversion system and protocol conversion method
US5974506A (en) * 1996-06-28 1999-10-26 Digital Equipment Corporation Enabling mirror, nonmirror and partial mirror cache modes in a dual cache system
US5864845A (en) * 1996-06-28 1999-01-26 Siemens Corporate Research, Inc. Facilitating world wide web searches utilizing a multiple search engine query clustering fusion strategy
US5852820A (en) 1996-08-09 1998-12-22 Digital Equipment Corporation Method for optimizing entries for searching an index
US5864863A (en) * 1996-08-09 1999-01-26 Digital Equipment Corporation Method for parsing, indexing and searching world-wide-web pages
US5822747A (en) 1996-08-23 1998-10-13 Tandem Computers, Inc. System and method for optimizing database queries
US5966649A (en) 1996-09-06 1999-10-12 Phoenix Wireless, Inc. Cellular-telephone central call-processing system utilizing object-oriented software in adjunct personal computer for generating billing records
US6108672A (en) 1996-10-07 2000-08-22 Moore Business Forms, Inc. Multiple company integrated documents production
KR100230455B1 (en) * 1996-10-21 1999-11-15 윤종용 Accounting apparatus and method of management automation system
US5884290A (en) * 1996-10-22 1999-03-16 Unisys Corporation Method of transferring funds employing a three-node real-time electronic interlock
US5924094A (en) 1996-11-01 1999-07-13 Current Network Technologies Corporation Independent distributed database system
GB9624180D0 (en) * 1996-11-21 1997-01-08 Plessey Telecomm Telecommunication equipment
US5915253A (en) 1996-12-13 1999-06-22 Novell, Inc. Method and system for implementing objects in a storage system
US5909440A (en) 1996-12-16 1999-06-01 Juniper Networks High speed variable length best match look-up in a switching device
US5937406A (en) 1997-01-31 1999-08-10 Informix Software, Inc. File system interface to a database
US6377938B1 (en) * 1997-02-27 2002-04-23 Real-Time Billing, Inc. Real time subscriber billing system and method
US5960416A (en) 1997-02-27 1999-09-28 Block; Robert S. Real time subscriber billing at a subscriber location in an unstructured communication network
US6075796A (en) 1997-03-17 2000-06-13 At&T Methods and apparatus for providing improved quality of packet transmission in applications such as internet telephony
US6011795A (en) * 1997-03-20 2000-01-04 Washington University Method and apparatus for fast hierarchical address lookup using controlled expansion of prefixes
US5842220A (en) 1997-05-02 1998-11-24 Oracle Corporation Methods and apparatus for exposing members of an object class through class signature interfaces
US5983223A (en) 1997-05-06 1999-11-09 Novell, Inc. Method and apparatus for determining a longest matching prefix from a dictionary of prefixes
US6035326A (en) * 1997-05-07 2000-03-07 International Business Machines Corporation Mapping table lookup optimization system
US6047284A (en) 1997-05-14 2000-04-04 Portal Software, Inc. Method and apparatus for object oriented storage and retrieval of data from a relational database
US6092055A (en) 1997-05-14 2000-07-18 Portal Software, Inc. Method and apparatus for providing a clean accounting close for a real time billing system
US6047267A (en) * 1997-05-14 2000-04-04 Portal Software, Inc. Method and apparatus for tracking multiple payment resources and charging transactions to payment resources in on line transaction processing system
WO1998052131A1 (en) 1997-05-14 1998-11-19 Portal Information Network Method and apparatus for object oriented storage and retrieval of data from a relational database to implement a real time billing system
US5806061A (en) 1997-05-20 1998-09-08 Hewlett-Packard Company Method for cost-based optimization over multimeida repositories
US6243760B1 (en) 1997-06-24 2001-06-05 Vistar Telecommunications Inc. Information dissemination system with central and distributed caches
US6012057A (en) * 1997-07-30 2000-01-04 Quarterdeck Corporation High speed data searching for information in a computer system
EP1002410B1 (en) 1997-08-06 2004-11-17 Tachyon, Inc. A distributed system and method for prefetching objects
US6112190A (en) 1997-08-19 2000-08-29 Citibank, N.A. Method and system for commercial credit analysis
US6112304A (en) 1997-08-27 2000-08-29 Zipsoft, Inc. Distributed computing architecture
GB2329044B (en) 1997-09-05 2002-10-09 Ibm Data retrieval system
US5974407A (en) 1997-09-29 1999-10-26 Sacks; Jerome E. Method and apparatus for implementing a hierarchical database management system (HDBMS) using a relational database management system (RDBMS) as the implementing apparatus
US6311185B1 (en) 1997-10-30 2001-10-30 At&T Corp. Method and apparatus for modifying an information page transmitted in a communications network
US6223172B1 (en) * 1997-10-31 2001-04-24 Nortel Networks Limited Address routing using address-sensitive mask decimation scheme
US6070051A (en) 1997-11-03 2000-05-30 Motorola, Inc. Method and apparatus for predicting service availability for a ground-to-satellite radio of a communication system
US6061679A (en) * 1997-11-25 2000-05-09 International Business Machines Corporation Creating and searching a data structure ordered by ranges of key masks associated with the data structure
US6141759A (en) 1997-12-10 2000-10-31 Bmc Software, Inc. System and architecture for distributing, monitoring, and managing information requests on a computer network
US20010025273A1 (en) * 1997-12-22 2001-09-27 Jay Walker Parallel data network billing and collection system
US6252544B1 (en) 1998-01-27 2001-06-26 Steven M. Hoffberg Mobile communication device
US6078897A (en) 1998-02-02 2000-06-20 Intraware, Inc. Method and apparatus for optimizing orders for goods or services to increase a discount
US6735631B1 (en) 1998-02-10 2004-05-11 Sprint Communications Company, L.P. Method and system for networking redirecting
US6058173A (en) * 1998-02-19 2000-05-02 Lhs Group Inc. Real-time call rating and debiting system
US6311186B1 (en) 1998-02-20 2001-10-30 Priority Call Management, Inc. Telecommunications switching system utilizing a channelized database access mechanism
US5987233A (en) 1998-03-16 1999-11-16 Skycache Inc. Comprehensive global information network broadcasting system and implementation thereof
US6154765A (en) 1998-03-18 2000-11-28 Pasocs Llc Distributed digital rule processor for single system image on a clustered network and method
JP3464907B2 (en) 1998-03-20 2003-11-10 富士通株式会社 Protocol conversion system
US6170014B1 (en) * 1998-03-25 2001-01-02 Community Learning And Information Network Computer architecture for managing courseware in a shared use operating environment
US6067574A (en) * 1998-05-18 2000-05-23 Lucent Technologies Inc High speed routing using compressed tree process
US6032132A (en) * 1998-06-12 2000-02-29 Csg Systems, Inc. Telecommunications access cost management system
US6112209A (en) * 1998-06-17 2000-08-29 Gusack; Mark David Associative database model for electronic-based informational assemblies
US20010056362A1 (en) 1998-07-29 2001-12-27 Mike Hanagan Modular, convergent customer care and billing system
US6185557B1 (en) * 1998-07-31 2001-02-06 Unisys Corporation Merge join process
US6266660B1 (en) 1998-07-31 2001-07-24 Unisys Corporation Secondary index search
US6999569B2 (en) * 1998-10-28 2006-02-14 Mastercard International Incorporated System and method for using a prepaid card
US6584183B2 (en) * 1998-11-17 2003-06-24 Charles L. Manto System and method for providing sponsored of universal telecommunications service and third party payer services
US6260024B1 (en) 1998-12-02 2001-07-10 Gary Shkedy Method and apparatus for facilitating buyer-driven purchase orders on a commercial network system
US6377957B1 (en) * 1998-12-29 2002-04-23 Sun Microsystems, Inc. Propogating updates efficiently in hierarchically structured date
US6477651B1 (en) 1999-01-08 2002-11-05 Cisco Technology, Inc. Intrusion detection system and method having dynamically loaded signatures
US6381228B1 (en) * 1999-01-15 2002-04-30 Trw Inc. Onboard control of demand assigned multiple access protocol for satellite ATM networks
US6973057B1 (en) 1999-01-29 2005-12-06 Telefonaktiebolaget L M Ericsson (Publ) Public mobile data communications network
US6567408B1 (en) 1999-02-01 2003-05-20 Redback Networks Inc. Methods and apparatus for packet classification with multi-level data structure
US6400925B1 (en) 1999-02-25 2002-06-04 Trw Inc. Packet switch control with layered software
US6662180B1 (en) 1999-05-12 2003-12-09 Matsushita Electric Industrial Co., Ltd. Method for searching in large databases of automatically recognized text
US6381605B1 (en) * 1999-05-29 2002-04-30 Oracle Corporation Heirarchical indexing of multi-attribute data by sorting, dividing and storing subsets
US6658463B1 (en) 1999-06-10 2003-12-02 Hughes Electronics Corporation Satellite multicast performance enhancing multicast HTTP proxy system and method
US6381607B1 (en) * 1999-06-19 2002-04-30 Kent Ridge Digital Labs System of organizing catalog data for searching and retrieval
WO2001001366A2 (en) * 1999-06-25 2001-01-04 Telemonitor, Inc. Smart remote monitoring system and method
US6404746B1 (en) 1999-07-13 2002-06-11 Intervoice Limited Partnership System and method for packet network media redirection
US6401098B1 (en) 1999-07-15 2002-06-04 American Management Systems, Inc. System for database creation, maintenance and access using event marking and two-dimensional partitioning
US7653614B2 (en) 1999-07-15 2010-01-26 Spotware Technologies, Inc. Method of searching across media and source types
US6427172B1 (en) 1999-07-20 2002-07-30 Cyberstar, L.P. Method and apparatus for internet cache content delivery via a data distribution system
EP1526435A3 (en) * 1999-07-30 2005-07-27 Intertrust Technologies Corp. Methods and systems for transaction record delivery using thresholds and multi-stage protocol
US6415323B1 (en) 1999-09-03 2002-07-02 Fastforward Networks Proximity-based redirection system for robust and scalable service-node location in an internetwork
US6442652B1 (en) 1999-09-07 2002-08-27 Motorola, Inc. Load based cache control for satellite based CPUs
US20030202521A1 (en) 1999-09-10 2003-10-30 Theodore Havinis System and method for negotiation of multi-media capabilities across networks
US6662184B1 (en) 1999-09-23 2003-12-09 International Business Machines Corporation Lock-free wild card search data structure and method
US6700869B1 (en) * 1999-10-01 2004-03-02 Lucent Technologies Inc. Method for controlling data flow associated with a communications node
ATE244430T1 (en) 1999-10-15 2003-07-15 Ajit K Zacharias SECURE CARD SYSTEM FOR MULTIPLE USE
US6563800B1 (en) 1999-11-10 2003-05-13 Qualcomm, Inc. Data center for providing subscriber access to data maintained on an enterprise network
US6446068B1 (en) 1999-11-15 2002-09-03 Chris Alan Kortge System and method of finding near neighbors in large metric space databases
US6564247B1 (en) 1999-11-18 2003-05-13 International Business Machines Corporation System and method for registering user identifiers
US6725052B1 (en) * 1999-12-20 2004-04-20 Ericsson Inc. Cell assignment method during group calls
US6490592B1 (en) 1999-12-30 2002-12-03 Nortel Networks Limited Method of and apparatus for generating a tree data structure supporting longest match lookup
US6314365B1 (en) 2000-01-18 2001-11-06 Navigation Technologies Corp. Method and system of providing navigation services to cellular phone devices from a server
US20080215474A1 (en) * 2000-01-19 2008-09-04 Innovation International Americas, Inc. Systems and methods for management of intangible assets
US6947440B2 (en) 2000-02-15 2005-09-20 Gilat Satellite Networks, Ltd. System and method for internet page acceleration including multicast transmissions
US6347340B1 (en) * 2000-02-18 2002-02-12 Mobilesys, Inc. Apparatus and method for converting a network message to a wireless transport message using a modular architecture
US7792745B2 (en) 2000-02-25 2010-09-07 Ipass Inc. Method and system to facilitate financial settlement of service access transactions between multiple parties
US6678675B1 (en) 2000-03-30 2004-01-13 Portal Software, Inc. Techniques for searching for best matches in tables of information
US7257611B1 (en) 2000-04-12 2007-08-14 Oracle International Corporation Distributed nonstop architecture for an event processing system
US6658415B1 (en) 2000-04-28 2003-12-02 International Business Machines Corporation Monitoring and managing user access to content via a universally accessible database
FI110656B (en) 2000-05-15 2003-02-28 Nokia Corp Control the making and continuing of a call
WO2002001838A2 (en) 2000-06-26 2002-01-03 Kpmg Consulting, Inc. Using a pseudo-clec to test operational support systems of an incumbent local exchange carrier
US7233918B1 (en) 2000-07-18 2007-06-19 Oracle International Corporation Rating billing events in real time according to account usage information
US6564047B1 (en) 2000-08-28 2003-05-13 Motorola Inc. Advanced air time management
US6532283B1 (en) * 2000-09-11 2003-03-11 Isaac J. Ingram Method and apparatus for viewing real time telephone charges
US7406471B1 (en) 2000-09-28 2008-07-29 Oracle International Corporation Scalable multi-database event processing system using universal subscriber-specific data and universal global data
US20020082881A1 (en) 2000-10-20 2002-06-27 Price Marc Steven System providing event pricing for on-line exchanges
US20020068545A1 (en) 2000-11-06 2002-06-06 Johnson Oyama Method and apparatus for coordinating charging for services provided in a multimedia session
US7146332B2 (en) * 2000-12-01 2006-12-05 Bellsouth Intellectual Property Corporation Methods and systems for automatic tracking and balancing billing data
US7729925B2 (en) * 2000-12-08 2010-06-01 Sony Corporation System and method for facilitating real time transactions between a user and multiple entities
US20020073082A1 (en) * 2000-12-12 2002-06-13 Edouard Duvillier System modification processing technique implemented on an information storage and retrieval system
US20020087469A1 (en) 2000-12-28 2002-07-04 Ravi Ganesan Technique of registration for and direction of electronic payments in real-time
ES2244549T3 (en) * 2001-04-12 2005-12-16 Siemens Aktiengesellschaft PROCEDURE FOR BILLING SERVICES IN A COMMUNICATIONS NETWORK.
US20030078056A1 (en) * 2001-04-18 2003-04-24 Sunao Takatori Communication system and line selecting method
US7146637B2 (en) * 2001-06-29 2006-12-05 International Business Machines Corporation User registry adapter framework
US7305421B2 (en) * 2001-07-16 2007-12-04 Sap Ag Parallelized redo-only logging and recovery for highly available main memory database systems
US20030133552A1 (en) 2001-08-07 2003-07-17 Shyam Pillai Method and apparatus for integrating disparate telecommunication operational support systems (OSS) and streamlining business processes using a software platform
AU2002341768A1 (en) * 2001-09-20 2003-04-01 Adc Telecommunications, Inc. Balance management for pre-paid services
US20030069780A1 (en) * 2001-10-05 2003-04-10 Hailwood John W. Customer relationship management
US6901507B2 (en) 2001-11-19 2005-05-31 Intel Corporation Context scheduling
US20030105799A1 (en) 2001-12-03 2003-06-05 Avaz Networks, Inc. Distributed processing architecture with scalable processing layers
JP2003188986A (en) 2001-12-17 2003-07-04 Fujitsu Ltd Gateway apparatus
US7246102B2 (en) 2001-12-21 2007-07-17 Agere Systems Inc. Method of improving the lookup performance of three-type knowledge base searches
US7792714B1 (en) 2001-12-28 2010-09-07 Fannie Mae System and method for providing a common data and analytic framework for valuating financial instruments and portfolios
SE521896C2 (en) 2002-02-28 2003-12-16 Ericsson Telefon Ab L M A method and a distributed tariff calculation system for determining tariff data in a billing system
US9087319B2 (en) 2002-03-11 2015-07-21 Oracle America, Inc. System and method for designing, developing and implementing internet service provider architectures
US7421506B2 (en) 2002-06-12 2008-09-02 Nokia Corporation Load balancer for multiprocessor platforms
US7558758B2 (en) * 2002-06-26 2009-07-07 International Business Machines Corporation Business event triggered, policy-driven payment management
US6829473B2 (en) * 2002-07-25 2004-12-07 Utstarcom, Inc. Roaming and hand-off support for prepaid billing for wireless data networks
US7203691B2 (en) * 2002-09-27 2007-04-10 Ncr Corp. System and method for retrieving information from a database
US7480915B2 (en) * 2002-10-03 2009-01-20 Nokia Corporation WV-IMS relay and interoperability methods
US8577795B2 (en) * 2002-10-10 2013-11-05 Convergys Information Management Group, Inc. System and method for revenue and authorization management
US7221929B2 (en) 2002-10-12 2007-05-22 Lg Electronics Inc. Handling charging information in interworking structure of mobile communication and wireless local area networks
WO2004056079A1 (en) * 2002-12-16 2004-07-01 Telefonaktiebolaget Lm Ericsson (Publ) Cost negotiation for communication sessions
US7391784B1 (en) 2002-12-30 2008-06-24 3Com Corporation Method and system for communicating state information between devices of a communications network
US7058773B1 (en) * 2003-01-16 2006-06-06 Cisco Technology, Inc. System and method for managing data in a distributed system
EP1620995A1 (en) * 2003-05-07 2006-02-01 Nokia Corporation Access flow based charging for ims/poc services
EP1482701B1 (en) * 2003-05-27 2005-09-14 Siemens Aktiengesellschaft Method for transmitting packet-oriented data in a telecommunication network by converting in a proxy a connectionless transport protocol into a connection-oriented transport protocol and vice versa
US8032593B2 (en) * 2003-08-07 2011-10-04 Teamon Systems, Inc. Communications system providing reduced access latency and related methods
US7376087B2 (en) * 2003-08-13 2008-05-20 Tropos Networks, Inc. Method and apparatus for monitoring and displaying routing metrics of a network
MXPA06001678A (en) 2003-08-15 2006-05-19 Boston Communications Group Inc Subscriber management and accounting using event detection in a wireless device.
US7660755B2 (en) * 2003-09-18 2010-02-09 At&T Intellectual Property I, L.P. Methods, systems, and computer-readable-mediums for managing rollover usage units of communication services
US7003280B2 (en) * 2003-11-20 2006-02-21 Lucent Technologies Inc. Method and system for processing adjustments to the type and quality of multimedia communication sessions
US7203478B2 (en) 2003-12-08 2007-04-10 Lucent Technologies Inc. Network support for mobile service plan minute exchange by category
US20050144099A1 (en) 2003-12-24 2005-06-30 Indrojit Deb Threshold billing
US20050185774A1 (en) 2004-02-24 2005-08-25 First Data Corporation System for maintaining communication point data
US9014355B2 (en) 2004-04-27 2015-04-21 Value-Added Communications, Inc. Telecommunication revenue management system
US8209250B2 (en) * 2004-05-10 2012-06-26 Morgan Stanley Systems and methods for conducting an interactive financial simulation
EP1751966B1 (en) 2004-06-03 2007-12-26 TELEFONAKTIEBOLAGET LM ERICSSON (publ) Charging mechanisms for ip multimedia services
CN101006681B (en) 2004-06-08 2010-10-27 艾利森电话股份有限公司 Flexible charging mechanisms for IP multimeda services
US20060015363A1 (en) 2004-07-12 2006-01-19 United Parcel Service Of America, Inc. Systems and methods for processing invoices based on a minimum invoice amount
FI20045298A0 (en) * 2004-08-16 2004-08-16 Nokia Corp Directing media communication service
JP2006067124A (en) * 2004-08-25 2006-03-09 Nec Corp Method and device for switching image encoded data, system, and program
US7010104B1 (en) * 2004-08-26 2006-03-07 Lucent Technologies Inc. Pre-biller capability in enhanced charging collection function (CCF) applications
US20070100981A1 (en) 2005-04-08 2007-05-03 Maria Adamczyk Application services infrastructure for next generation networks including one or more IP multimedia subsystem elements and methods of providing the same
US8223935B2 (en) * 2005-04-30 2012-07-17 Oracle International Corporation Revenue management systems and methods
EP1935152A4 (en) * 2005-06-28 2010-08-04 Oracle Int Corp Revenue management system and method
CN101233497B (en) 2005-07-28 2013-01-30 甲骨文国际公司 Revenue management system and method
US8223777B2 (en) 2005-11-15 2012-07-17 Oracle International Corporation Gateway for achieving low latency and high availability in a real time event processing system
US8228925B2 (en) 2005-12-14 2012-07-24 Alcatel Lucent Interactive voice response system for online and offline charging and for multiple networks

Also Published As

Publication number Publication date
CN101233497A (en) 2008-07-30
US8117358B2 (en) 2012-02-14
EP1938193A4 (en) 2010-08-04
WO2007016412A3 (en) 2007-07-12
CA2616194A1 (en) 2007-02-08
CN101233497B (en) 2013-01-30
JP2009504030A (en) 2009-01-29
WO2007016412A2 (en) 2007-02-08
US20070198283A1 (en) 2007-08-23
AU2006275665A1 (en) 2007-02-08
EP1938193A2 (en) 2008-07-02

Similar Documents

Publication Publication Date Title
CA2616194C (en) Revenue management system and method
US10360563B1 (en) Architecture for a system and method for work and revenue management
CN107563887B (en) AS 400-based zero-halt daily cutting method for bank core accounting system
US8489742B2 (en) System and method for work management
US10642840B1 (en) Filtered hash table generation for performing hash joins
US6829623B2 (en) Method and system for managing multiple database storage units
US8090751B2 (en) Operational data store
US20140337393A1 (en) Transaction ordering
EP2169909A1 (en) System and method to maintain coherence of cache contents in a multi-tier software system aimed at interfacing large databases
US20220114064A1 (en) Online restore for database engines
US10949413B2 (en) Method and system for supporting data consistency on an active standby database after DML redirection to a primary database
CN102158540A (en) System and method for realizing distributed database
CN106886371A (en) caching data processing method and device
CN106649530B (en) Cloud detail query management system and method
CN112835917A (en) Data caching method and system based on blood relationship distribution
CN112131305A (en) Account processing system
US11256695B1 (en) Hybrid query execution engine using transaction and analytical engines
CN114547108A (en) Data processing method, device, equipment and medium
US11914571B1 (en) Optimistic concurrency for a multi-writer database
Jagadish et al. SUNRISE II: A Scalable and Timely Billing Architecture
CN117172897A (en) Life cycle management method and device, electronic equipment and storage medium
CN115080609A (en) Method and system for realizing high-performance and high-reliability business process engine
CN117131080A (en) Data processing platform based on stream processing and message queue
CN111475740A (en) Disaster tolerance processing method and equipment for service cluster

Legal Events

Date Code Title Description
EEER Examination request