EP1938193A2 - Systeme et procede de gestion des recettes - Google Patents

Systeme et procede de gestion des recettes

Info

Publication number
EP1938193A2
EP1938193A2 EP06788883A EP06788883A EP1938193A2 EP 1938193 A2 EP1938193 A2 EP 1938193A2 EP 06788883 A EP06788883 A EP 06788883A EP 06788883 A EP06788883 A EP 06788883A EP 1938193 A2 EP1938193 A2 EP 1938193A2
Authority
EP
European Patent Office
Prior art keywords
memory
data
request
manager
data manager
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.)
Ceased
Application number
EP06788883A
Other languages
German (de)
English (en)
Other versions
EP1938193A4 (fr
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 EP1938193A2 publication Critical patent/EP1938193A2/fr
Publication of EP1938193A4 publication Critical patent/EP1938193A4/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION 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/00—Commerce
    • G06Q30/04—Billing or invoicing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION 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/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION 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/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION 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/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION 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/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12—Accounting
    • G06Q50/60—

Definitions

  • This invention relates to a revenue management system that has an in-memory write-through cache.
  • Prepaid phone accounts are tracked in real-time by billing and time management hardware and software architectures in communication with the phone 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 prepaid account during a call, the architecture acts to terminate the call.
  • CRM systems are known as customer relation management (CRM) systems. CRM systems are also used for non-prepaid scenarios, such as for generating bills. CRM systems are also used for other telecommunications, and other network management scenarios.
  • Prepaid account CRM systems need to have the ability to track accounts in real-time.
  • Available real-time architectures for managing prepaid customer accounts have some existing limitations.
  • First, the available architectures require high performance and data throughput, thereby leading to relatively high hardware requirements. These architectures, along with their storage and maintenance can be expensive and time- consuming.
  • Second, requirements for very low system response latencies are difficult to achieve. Transactions in existing architectures involve several round-trips to the disk- based storage subsystem. The data must be processed by a comparatively large software stack to transform from a relational representation into a physical storage format.
  • the data is transferred several times from component to component of the system to retrieve the data, map it from a relational format to an object format, process it with the desired business logic, and then transfer the response to the client.
  • currently available architectures can not provide desired levels of data 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 requirements. Being part of the public network, some parts of the system need to have carrier-grade availability.
  • no single product accomplished both batch processing and real-time processing for telecommunications CRM (e.g., billing) purposes.
  • a system and method for managing any numerical account information is disclosed.
  • the system and method can be used for managing revenue for telecommunications system.
  • the system and method can be used to manage account balances, such as user accounts for the telecommunications system.
  • Management of account balances can include altering the balance of the 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 statement or perform other accounting features, and/or querying the account to determine whether to authorize use of the account.
  • the system can be used with an account with an existing balance (e.g., prepaid), an account with a maximum use limit (e.g., capped), a current payment account (e.g., now-pay, for example through the use of a credit card), other types of balance management accounts, or combinations thereof.
  • the system architecture can be configured to increase performance, and availability and decrease latency.
  • the system and method can manage accounts, for example, for the prepaid wireless markets handling services such as GSM, GPRS and SMS.
  • 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 be a virtual database cache.
  • the first memory can be a typical on-board RAM storage location.
  • the first memory can be a smart cache.
  • the smart cache can treat different object types different ways. For example, the smart cache can treat reference objects, database-only objects, and transient object differently.
  • 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 balance) that change each call, and static reference objects (e.g., the billing rate for different types of calls) that never or rarely change.
  • Database-only objects can be objects that change one-time or rarely during the call and are not referred to by the connection manager.
  • Transient objects can exist, for example, only in-memory (e.g., in TIMOS).
  • Transient objects can be unwritten to the database. Transient objects can be written to the database, for example, at the end of the call (e.g., credit balance).
  • the database can have a data dictionary.
  • the data dictionary can by written by the users.
  • the data dictionary can define an object type and what type of object each other is. Customers can edit the data dictionary if so desired.
  • the new revenue management system can have a high availability.
  • the system can have a warm standby operation by referring to any data remaining in TIMOS. During warm standby, in the case of a loss of data, the system can recreate data from the switch and/or TIMOS when the switch sends re-authorization data (e.g., during long calls) or end-of-call data.
  • a known failure protection scheme with a high availability (monitor) regularly checking the status of the control manager, TIMOS, data manager, the database manager, and the database is also disclosed.
  • a self-container failure protection system is disclosed. Each component of the 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 further downstream component failure, the system can take appropriate action, including alerting a user.
  • Figure 1 illustrates a variation of the revenue management system architecture connected to a switch over a network.
  • Figure 2 illustrates a variation of the revenue management system architecture connected to a switch over a public network.
  • Figures 3 through 5 illustrate variations of the revenue management system architecture.
  • Figure 6 illustrates a variation for a method for using the revenue management system.
  • Figure 7 illustrates process flows for variations for methods for using the revenue management system.
  • Figure 8 illustrates a variation for a method for using the revenue management system.
  • Figure 9 illustrates process flows for variations for methods for using the revenue management system.
  • Figure 10 illustrates a variation for a method for using the revenue management system.
  • Figure 11 illustrates process flows for variations for methods for using the revenue management system.
  • Figures 12a through 14 illustrate variations of the revenue management system.
  • a computer-based system and method for managing any numerical account information is disclosed.
  • the system and method can be used for managing revenue for telecommunications system.
  • the system and method can be used to manage account balances, such as user accounts for the telecommunications system.
  • the management of account balances can include altering the balance of the 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 statement or perform other accounting features, and/or querying the account to determine whether to authorize use of the account.
  • FIG. 1 illustrates a telecommunication device 2, such as a phone, computer, 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 telecommunication device through the switch 6.
  • the switch 6 can communicate across a network and through a gateway 8 (e.g., having a protocol translator) to the revenue management system 100.
  • the gateway 8 can communicate directly with a business logic module 10 or business logic application (e.g., Portal Infranet, Portal Software, Inc. Cupertino, CA).
  • the business logic module 10 can communicate with a database system 12 to determine whether the telecommunication device 2 connected to the switch 6 has permission to connect and/or stay on the line.
  • the database system 12 can have a highly-available Oracle RAC database cluster.
  • the system 100 can utilize Oracle transaction management functionality.
  • Figure 2 illustrates that the gateway 8 can be a part of the revenue management system 100.
  • the gateway 8 can interface between the business logic module 10 and an intelligent network (IN) service control point system (SCP) 14.
  • 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 database within the network that receives queries, for example from service switching points (SSP), in order to process applications, such as 800 and LNP number lookups and calling card verification.
  • the SCP system 14 can process the applications 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 system 100.
  • Figure 3 illustrates that the business logic module 10 can have one or more rating connection managers (CM) 16a and 16b, a first memory data manager 18 (e.g., TBvIOS 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 second memory data managers 20a and 20b can communicate with the database system 12 or other second memory system.
  • the database system 12 can have one or more database clusters 22a and 22b (e.g., Oracle Real Application Clusters), for 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.
  • the business logic module can be accessed via the gateway 8 and/or via a manual access application 26.
  • the manual access application 26 can be operated manually or automatically.
  • the manual access application 26 can be configured, for 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 check account status.
  • the revenue management system 100 can have a first memory (e.g., TIMOS) and a second memory (e.g., database).
  • the first memory can be, for example, in and/or in communication with the first memory data manager 18.
  • the first memory can be configured to have faster, slower, and/or the same read, and/or write, and/or re- write speeds (e.g., access speeds) as the second memory.
  • the first memory can be an in-memory data store and database cache dedicated to high-speed rating and authorization requirements.
  • the first memory can be solid state memory, such as system memory (e.g., RAM) or one or more hard drives, for example with fast access speeds. Requests for data in the first memory can be processed faster than requests for data in a second memory.
  • 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 Intranet, Portal Software, Inc.).
  • the first data can be left untranslated before storage in the first memory.
  • the internal search and storage algorithms can be optimized for in-first-memory data. Storing the first data in the first memory can, for example, eliminate the round trip to 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 creation or updates for the first data objects can require no access of the second memory. Updates for the first data objects can be performed in the first memory.
  • the system can have, for example, a reduced throughput and/or latency.
  • the first memory data objects e.g., transient objects
  • the first memory data objects can be stored in the first memory and/or the second memory.
  • the first memory data objects can be stored not in the database and not be persisted in the first memory.
  • the first memory objects can, for example, exist only in the process heap memory of the first memory.
  • the first memory objects can be, for example, managed in a transactional manner (e.g., like the other memory objects).
  • First memory data objects can be removed from the first memory by shutdown of the first memory or the business logic executing a delete operation on the first memory data object.
  • the store for first memory data objects can be a fixed size, for example, determined during startup of the first memory process.
  • 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 objects.
  • the second memory can be in and/or in communication with the second memory data manager 20. Requests for second memory data objects can be sent to the second memory data manager 20.
  • the second memory for example, can be a disk-based (e.g., on one or more hard drives) database.
  • the database can be a relational database (RDBMS).
  • RDBMS relational database
  • the system can have low access second memory data objects (e.g., database- 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 access second memory data objects can be stored in the first memory none of the time, or some of the time.
  • the first memory data manager can access the low access second memory data object type via a pass-through mode.
  • requests can be forwarded to the second memory data manager (e.g., DM_Oracle), and responses can be forwarded back to the first memory data manager.
  • the high access second memory data objects e.g., reference objects
  • the high access second memory data objects can be updated seldom and not during high-speed session processing.
  • the high access 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 relation to growth in the subscriber base.
  • the high access second memory data objects can exist in the first memory an equal amount of time as length of the first memory process. A newly started first memory instance can contain no high access second memory data objects.
  • Updating and creating high access second memory data objects can be performed in the second memory and in the first memory, in the high access second memory data objects can be updated or created asynchronously or synchronously in the second memory and the first memory.
  • 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 deleted at irregular intervals.
  • the static high access second memory data objects can be, for example, subscriber information such as the list of subscribed services and the chosen tariff plans.
  • 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 high access second memory data objects can be, for example, the monetary and non- monetary balances belonging to a subscriber account.
  • a standby-first memory e.g., for a high availability variation that can have an active first memory and a backup, standby first memory
  • Changes of static reference objects can be propagated from the active first memory to the standby first memory.
  • the gateway 8 can directly communicate with the business logic module 10. For example, during a customer's use of the telecommunication network, the gateway 8 can communicate with a first connection manager (CM) 16a.
  • CM connection manager
  • the gateway 8 can pass requests to the CM 16a, for example, calling the appropriate business logic routines depending on the type of request that is indicated from the IN SCP 14.
  • the gateway 8 can be nearly stateless.
  • the gateway 8 can provide fast failover 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 authentication, authorization and accounting procedures.
  • Events received by the CM can be rated via an embedded rating engine using the data provided from the first memory data manager 18 (e.g., DM TIMOS cache) 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 day, day of week, network used).
  • the rating engine can cache pricing objects itself, for example, in order to reduce the number of network roundtrips necessary to complete the rating phase.
  • the rating engine can perform zoning and discounting rating.
  • the first memory data manager 18 can pass the request to the database system 12, query the first memory data manager 18 reference object cache or accesses the first memory (e.g., in-memory store) for transient objects.
  • the object types and their locations can be defined in a business logic database (e.g., Infranet 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 accessing the database manager 20, for example, in the same way a commonly used system without the first data manager would be configured.
  • the data integrity of the first memory can be ensured by a platform-managed synchronization mechanism that can propagate the necessary updates to the first memory.
  • the first memory can have one or more caches.
  • Figures 4a and 4b illustrate variations of the revenue management system 100.
  • the gateway 8 can act as a high-speed protocol translator as well as an SLA monitor with fallback capabilities.
  • the CM 16 can receive requests from the gateway 8.
  • the CM 16 can have the authorization, authentication and accounting business logic (e.g., for delivery to the gateway 8).
  • the CM 16 can call operational codes on the first data manager 18.
  • the CM 16 can be replaced with another client, such as a migration tool.
  • the CM 16 can have a realtime pipeline (RTP) 28.
  • RTP realtime pipeline
  • the RTP 28 can be configured to adjust the rating, for example by discounting and zoning the rate.
  • the RTP 28 can be optionally used by the CM 16 while rating.
  • the first data manager 18 can have a data migratory subsystem 30.
  • the data manager subsystem 30 can be used to fill the high access second memory object cache after start or fail over.
  • 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 combinations in scaled scenarios with more second memory instances than first memory instances or more first memory instances than second memory instances.
  • the directory server 32 can enable the gateway instances and CM instances to be independent of the number of first memory instances.
  • FIG. 4a shows that the elements of the architecture of the business logic module can all be standalone.
  • Figure 4b illustrates that the numerous elements of the architecture can be integrated.
  • Figure 5 illustrates that the first memory 102 can have a reference object cache (ROC) 34 and a transient object store (TOC) 36.
  • the ROC 34 can be managed by a separate set of rules than the TOC 36.
  • the ROC 34 and the TOC 36 can be in the same or different parts of the first memory 102.
  • the first memory 102 can be part of, 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., reference objects).
  • the TOC 36 can be configured to store first memory data objects (e.g., transient objects).
  • Figure 6 illustrates a method for accessing a first memory data in the TOC 36.
  • 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 request 38.
  • the first data manager 18 can conclude that the request applies to the first memory.
  • the first data manager 18 can apply or execute the request on the TOC 36.
  • the first data manager 18 can generate a reply and send, shown by arrow 40, the reply to the CM 16.
  • Figure 7 illustrates flows of various requests from the CM 16 and the replies to the requests.
  • the instructions are shown as create, update, delete and search/read (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 data object, and search/read the first data object.
  • the numbers of the requests and replies illustrate an exemplary chronological order.
  • the first data manager 18 can convert or otherwise translate the request from the CM 16 to a first data manager instruction, such as add the first data object, change the first data object, remove the first data object, and find the first data 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 reply.
  • Figure 8 illustrates a method for accessing high access memory data in the 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 memory data.
  • the first data manager 18 can analyze the request 38.
  • the first data manager 18 can conclude that the request applies to the high access second memory data.
  • the first data manager 18 can determine whether the high access second memory data is in the ROC 34. Ifthe 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 execute the request on the high access second data in the ROC 34.
  • the first data manager 18 can send the request to the second data manager 20.
  • the second data manager 20 can apply or execute the request on the high access second data in the 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 sent, shown by arrow 40, directly or via the first data manager 18 to the CM 16.
  • Figure 9 illustrates flows of various requests from the CM and the replies to the requests.
  • the exemplary instructions are shown as create, update, delete, simple 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 data object, and search/read the first data object.
  • the numbers of the requests and replies illustrate an exemplary chronological order.
  • the first data manager 20 can convert or otherwise translate the request from the CM 16 to a first data manager instruction, such as add the first data object, change the first data object, remove the first data object, and find the first data object, respectively.
  • the first data manager can then apply or execute the translated request on the high access second data in the ROC 34.
  • 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 second data manager 20 can convert or otherwise translate the request to a second data manager instruction, such as insert the row of data, update the row of data, delete the row of data, and select the row or rows of data, respectively (with no response 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 access second data in the database system 12.
  • the second data manager 20, and/or the database system 12 and/or the first data manager 20 can then return a reply.
  • 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.
  • Figure 10 illustrates a method for accessing low access memory data in the database system 12.
  • the CM 16 can send, shown by arrow 38, a request to the first data manager 18, and/or directly to the second data manager 18.
  • the request can apply to the high access second memory data.
  • the first data manager 18 can analyze 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 the second data manager 20.
  • the second data manager 20 can apply or execute the request on the high access second data in the database system 12.
  • the database system 12 and/or the second data manager 20 can generate one or more replies.
  • the replies can be sent, shown by arrow 40, directly or via the first data manager 18 to the CM 16.
  • Figure 11 illustrates flows of various requests from the CM and the replies to the requests.
  • the exemplary instructions are shown as create, update, delete, and searches/read (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 data object, and search/read the first data object.
  • the numbers of the requests and replies illustrate an exemplary chronological order.
  • the first data manager 18 can send the request to the second data manager 20.
  • the second data manager 20 can convert or otherwise translate the request to a second data manager instruction, such as insert the row of data, update the row of data, delete the row of data, and select the row or rows of data, respectively.
  • the second data manager 20 can apply or execute the request on the high access second data in the database system 12.
  • the second data manager 20, and/or the database system 12 and/or the first data manager 20 can then return a reply.
  • 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.
  • the CM 16 can send requests directly to the desired data manager 18 or 20 and/or the CM 16 can tag the request and the first data manager 18 can analyze the tag to determine whether to apply and/or execute the request and/or whether to send the 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 location of the request.
  • the first memory data objects of this category can be created, updated or deleted in the high-speed access path of the revenue management system 100.
  • the first memory data objects include active session objects and resource reservation obj ects.
  • the first memory data objects can be analyzed using, for example, logical predicates (e.g., equals, not equals). Queries executed on first memory data can specify an index to use to satisfy the query.
  • the index can be a hash to enable fast 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.
  • Requests for the first memory data objects can be passed to a standard heap memory area. The requests can be created, changed and deleted within transactions.
  • the first memory data objects can be limited to particular object, such as business object types.
  • the high access second memory data objects can be accessed only in a read- only mode in the high-speed access path.
  • An example of the high access second memory data objects is customer account information.
  • the ROC 34 can be filled on demand. This means that requests can be 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 be filled or cached by the reply (e.g., as the reply passes through the first data manger 18 on the reply's route back to the CM 16 from the second data manager 20). Partial object requests ('read_fields') of the high access second memory data objects can be cached in a similar manner to that performed for the entire object.
  • the high access second memory data objects can be folly queried. Simple queries involving basic logical operators (e.g., equals, not equals) can be performed by the first data manager 18 on the high access second memory data objects in the 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 second memory data objects in the database system 12.
  • the dynamic high access second memory data objects can be loaded by the data migrator 30 after a failover.
  • 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 static high access second memory data objects can be synchronized with the database via the first memory synchronization system.
  • the low access second memory data objects can be absent from the first 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 second memory data obj ects can be folly queried.
  • the first data manager can allow reading of the first data values during a write operation.
  • the first data manager can have the write operation take place on a 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 commit time.
  • the first data manager can have a read committed isolation.
  • the read committed isolation makes all committed updates available to transactions even if the 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 for reading during pending changes to the first data value).
  • the first data manager can support or not support statement or transaction level consistent reads.
  • 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 data manager 18.
  • a synchronization system can be used to send updates to the first memory data manager 18.
  • the synchronization system can automatically propagate changes affecting objects stored in the first memory to all the first memory instances caching the particular obj ect or obj ect type.
  • the revenue management system 100 can have a convergence system.
  • the convergence system can load batch data via the first data manager 18 into the revenue management system 100, for example, to share any data of batch origin, such as balances between prepaid and postpaid accounts.
  • the data capacity of a first memory instance can be lower than data the capacity of a second memory (e.g., database) instance.
  • One second memory instance can support several shared-nothing instances of the first memory. (The commonly used term is m:n (m - first memory instances / n - second memory instances)).
  • 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 of the system 100.
  • first memory data manager 18 For installation of first memory data manager 18, the first memory data manager 18 can be configured to be inserted between the CM 16 component and 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- existing revenue management system that did not have the first memory data manager 18. Installation of the first memory data manager 18 can be configured to be transparent (e.g., not change object types). The system 100 can be configured so that 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 memory data manager 18. These changes can be ignored by the system 100 if the first memory data manager 18 is not present. [0085] The first memory data manager 18 can be installed in an existing revenue management system.
  • the first memory data manager 18 can be physically installed (e.g., mounting hardware and/or loading software onto the appropriate computer-readable medium) and the base software can be configured. [0086] After the installation of the base software, the first data can then be migrated into the first memory data manager 18.
  • the first memory data object residencies 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 module 10 installation (having no effect when the first memory data manager 18 is not present) or can be loaded onto the business logic module 10 during the installation of the first memory data manager 18.
  • Reference objects can be migrated by loading into the first data manager 18 when accessed for the first time and/or pushed into the first memory data manager 18 by the data migratory 30.
  • 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 mechanism, and then updating the residency type in the data dictionary.
  • the first memory data manager 18 can have an empty ROC 34.
  • a separate data migration thread can push all high access second memory data in the ROC 34.
  • the static high access second memory data objects can be loaded into the ROC 34.
  • a first memory data manager 18 in backup mode can load only the static high access second memory data objects into the ROC 34.
  • the revenue management system 100 can provide hooks to verify and monitor performance.
  • the revenue management system 100 can log performance data on a 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 some parts of the system).
  • the revenue management system 100 can create system logs that can monitor operation of the revenue management system 100.
  • a log monitoring GUI e.g., Pipeline log viewer
  • Business logic style pin-logging can, for example, aid debugging and diagnosis.
  • the first memory data manager 18 can have a pipeline framework tracing model. Additional trace information can be collected from subsystems of the revenue management system 100 on a case by case basis.
  • Figures 12a, 12b and 12c illustrate that the revenue management system 100 can be scalable to large scale expansion.
  • the revenue management system 100 can have multiple second memory 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 memory data manager 20a-20l. Pairs of sets of first memory data managers and second memory data manager, for example, 18a, 18b, 20a, and 20b can be formed into high availability (HA) pairs 42.
  • the HA pairs 42 can have active and backup first data managers 18a and 18b, respectively, for example, and active and backup second data managers 20a and 20b, respectively, for example.
  • the revenue management system 100 can have a capacity partitioning scheme.
  • Each second memory (e.g., database 24) instance can be associated (i.e., in communication) with one or more first memory data manager 18 instances.
  • the revenue management system can be configured so no data is stored in overlapping second memory instances (n Timos instances : 1 database).
  • the business logic module can have several, independent databases (m).
  • the combination of TIMOS/databases can be referred to as m:n configuration.
  • the CM 16a-l 6e can lookup in the directory server 32 to identify the first memory data manager 18 and second memory data manager 20 (or database 24) combination applicable for a certain object.
  • the revenue management system 100 can have account migration tools.
  • the account migration tools can move subscriber data from one first and/or second memory location (e.g., database 24 and/or first memory data manager 18) to another first and/or second memory location.
  • Multiple second memory data managers 20 can communicate with the same database clusters 22. All the databases can be managed with one database cluster 22 (e.g., one RAC cluster) (not shown).
  • the SCPs 14, gateways 8 and CMs 16 can each be associated to multiple first 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 correct first memory data managers 18.
  • the database system 12 can run multiple database schemes in one RAC cluster 22.
  • the revenue management system 100 can be configured to associate a dedicated set of resources to just one SCP 14 or group of SCPs 14.
  • Figure 12b illustrates that the first memory data managers 18c and 18d can communicate directly with the database system 12, for example with the database clusters 22a and 22b.
  • Figure 12c illustrates that the revenue management system can have two or more database systems 12a and 12b.
  • Figure 13 illustrates a failure protection scheme with a high availability monitor 44 regularly checking the status of the control manager, the first memory in the first memory data manager 18, the second memory data manager 20, the database cluster , and the database 24.
  • Figure 14 illustrates a self-contained failure protection system.
  • Each component of the revenue management system 100 can check on the status of its immediately downstream component (e.g., the second memory data manager 20 is immediately downstream of the first memory data manager 18). If the immediately downstream component has failed, or is sending a failure message regarding a further downstream component failure, the revenue management system can take appropriate action, including alerting a user that a failure has occurred.
  • the revenue management system 100 can be absent of a separate monitor component checking for system failures.
  • the revenue management system 100 can have a high availability.
  • the revenue management system 100 can have a warm standby operation by referring to any data remaining in the first memory (e.g., TIMOS).
  • the revenue management system 100 can recreate data from the switch 6 and/or the first memory when the switch 6 sends re-authorization data (e.g., during long calls) or end-of-call data.
  • the database system 24 can store the latest static high access second memory data before a loss of data.
  • the static high access second memory data can be recovered to the first memory from the database system 24 after a loss of data in the first memory.
  • higher layers i.e., more stable during a system failure, such as the database
  • lower layers i.e., less stable during a system failure, such as a solid state RAM variation of the first memory
  • the revenue management system 100 can have spare, unused hardware and software such as backup data managers in the high availability pairs 42, as shown in Figures 12a through 12c.
  • the high availability pair 42 can have active and a backup 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 a period of no other activity with the active data manager and/or from a sketchpad, and/or the last available data from the active data manager. In case of failure of an element, the backup or other inactive elements will be able to restore data and/or take over the additional load.
  • Accessing can include querying, updating, creating, deleting and combinations thereof. Querying, updating, creating, and deleting for any data can be interchanged with each other as disclosed.

Abstract

La présente invention se rapporte à un système de gestion des relations clientèle en temps réel. Le système selon l'invention peut permettre d'augmenter la disponibilité, de réduire les temps d'attente internes, ainsi que le traitement et le transfert de données. Le système selon l'invention assure un traitement en temps réel et un traitement par lots. L'architecture de système peut posséder une mémoire cache à écriture immédiate intégrée à la mémoire. Ladite mémoire cache peut stocker des données qui auraient été sinon envoyées dans une base de données. Le système selon l'invention peut être doté d'une mémoire cache à écriture immédiate intégrée à la mémoire de sauvegarde. Le système peut faire appel à un secours semi-automatique de sauvegarde, par exemple, afin d'améliorer l'efficacité de sauvegarde des données.
EP06788883A 2005-07-28 2006-07-28 Systeme et procede de gestion des recettes Ceased EP1938193A4 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US70368705P 2005-07-28 2005-07-28
PCT/US2006/029571 WO2007016412A2 (fr) 2005-07-28 2006-07-28 Systeme et procede de gestion des recettes

Publications (2)

Publication Number Publication Date
EP1938193A2 true EP1938193A2 (fr) 2008-07-02
EP1938193A4 EP1938193A4 (fr) 2010-08-04

Family

ID=37709236

Family Applications (1)

Application Number Title Priority Date Filing Date
EP06788883A Ceased EP1938193A4 (fr) 2005-07-28 2006-07-28 Systeme et procede de gestion des recettes

Country Status (7)

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

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
US8116326B2 (en) 2005-06-28 2012-02-14 Oracle International Corporation Revenue management system and method
CA2616194C (fr) 2005-07-28 2015-02-17 Oracle International Corporation Systeme et procede de gestion des recettes
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 (ko) * 2006-12-04 2010-06-21 한국전자통신연구원 소프트웨어 및 파일 포맷의 관계 정보를 제공하는 소프트웨어 포탈 시스템 및 그의 동작 방법
JP4585540B2 (ja) * 2007-05-01 2010-11-24 株式会社東芝 Ｗｅｂアプリケーションシステム、装置及びプログラム
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
US20100228707A1 (en) * 2009-03-05 2010-09-09 Buddha Software Inc. System for rating a service
CN102347950B (zh) * 2011-09-29 2018-02-06 中兴通讯股份有限公司 电信网络向互联网提供会话服务的方法及系统
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.
US20150381520A1 (en) * 2013-02-04 2015-12-31 Nec Corporation Data set multiplicity change device, server, data set multiplicity change method and computer redable medium
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 (fr) * 2016-01-30 2017-08-03 Entit Software Llc Gestion analytique de grappe d'évènements de journal

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
EP0377684A1 (fr) 1988-03-25 1990-07-18 Ncr International Inc. Systeme de point de vente
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
DE69132600T2 (de) 1990-10-01 2002-02-07 Thomas A Bush Transaktionsverarbeitungssystem
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 (fr) 1991-10-31 1998-08-18 Brenda B. Amarant Surveillance des frais debites a un compte a limite fixee
US5499367A (en) * 1991-11-15 1996-03-12 Oracle Corporation System for database integrity with multiple logs assigned to client subsets
WO1993012606A1 (fr) 1991-12-12 1993-06-24 Cellular Technical Services Company, Inc. Systeme d'information en temps reel destine a des telephones cellulaires
JP3130609B2 (ja) 1991-12-17 2001-01-31 日本電気株式会社 オンライン情報処理装置
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 (de) 1992-05-21 1994-08-18 Dornier Gmbh Verfahren zur Erdbeobachtung
AU5364794A (en) 1992-10-22 1994-05-09 American Express Travel Related Services Company, Inc. Automated billing consolidation system and method
JPH0820982B2 (ja) 1992-11-12 1996-03-04 インターナショナル・ビジネス・マシーンズ・コーポレイション コンピュータ・アプリケーションプログラム収納体の項目をフィルタ処理する方法
FI96655C (fi) 1992-12-17 1996-07-25 Nokia Telecommunications Oy Menetelmä ryhmäpuhelun ylläpitämiseksi radiopuhelinjärjestelmässä ja radiopuhelinjärjestelmän järjestelmäohjain sekä tilaaja-asema
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
MX9404062A (es) 1993-06-03 1995-01-31 Ericsson Telefon Ab L M Transferencia de llamada dentro del sistema de comunicaciones celulares.
US5544302A (en) 1993-06-03 1996-08-06 Taligent, Inc. Object-oriented framework for creating and using container objects with built-in properties
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 (ja) 1993-07-08 2004-03-29 富士通株式会社 チェックイン・チェックアウトモデルにおける施錠方式
US6684261B1 (en) 1993-07-19 2004-01-27 Object Technology Licensing Corporation Object-oriented operating system
WO1995003586A1 (fr) 1993-07-21 1995-02-02 Persistence Software, Inc. Procede et appareil de generation du code de mise en correspondance de donnees relationnelles avec des objets
WO1995004960A2 (fr) 1993-08-02 1995-02-16 Persistence Software, Inc. Procede et dispositif permettant de gerer des donnees relationnelles dans une antememoire d'objets
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
CA2200955A1 (fr) 1994-09-28 1996-04-04 Gordon T. Brown Systeme comptable informatise
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
WO1996034350A1 (fr) 1995-04-24 1996-10-31 Aspect Development, Inc. Modelage de structures de base de donnees orientees objet, traduction en structures de base de donnees relationnelles et recherches dynamiques sur celles-ci
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
WO1996037848A1 (fr) 1995-05-24 1996-11-28 Walker Asset Management Limited Partnership Systeme de facturation et de recouvrement par le numero 900 et procede de services informatiques en ligne
US5644736A (en) 1995-05-25 1997-07-01 International Business Machines Corporation System and method for selecting components of a hierarchical file structure
US5677945A (en) 1995-06-06 1997-10-14 Mci Corporation Account balancing and monitoring system for a telecommunications network
US5829006A (en) 1995-06-06 1998-10-27 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
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 (ja) 1996-04-17 2000-12-04 インターナショナル・ビジネス・マシーンズ・コーポレ−ション 情報検索方法及び情報検索装置
JP3636399B2 (ja) 1996-05-29 2005-04-06 富士通株式会社 プロトコル変換システム及びプロトコル変換方法
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
US5974506A (en) * 1996-06-28 1999-10-26 Digital Equipment Corporation Enabling mirror, nonmirror and partial mirror cache modes in a dual cache system
US5864863A (en) 1996-08-09 1999-01-26 Digital Equipment Corporation Method for parsing, indexing and searching world-wide-web pages
US5852820A (en) 1996-08-09 1998-12-22 Digital Equipment Corporation Method for optimizing entries for searching an index
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 (ko) 1996-10-21 1999-11-15 윤종용 경영관리 자동화 시스템의 회계처리장치 및 방법
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
US5960416A (en) 1997-02-27 1999-09-28 Block; Robert S. Real time subscriber billing at a subscriber location in an unstructured communication network
US6377938B1 (en) 1997-02-27 2002-04-23 Real-Time Billing, Inc. Real time subscriber billing system and method
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
AU7687498A (en) 1997-05-14 1998-12-08 Portal Information Network Method and apparatus for object oriented storage and retrieval of data from a relational database to implement real time billing 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
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
KR100571059B1 (ko) 1997-08-06 2006-04-14 태크욘 인코포레이티드 예비 페칭을 위한 분산된 시스템 및 방법
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 (ja) 1998-03-20 2003-11-10 富士通株式会社 プロトコル変換システム
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
WO2000079379A1 (fr) 1999-06-19 2000-12-28 Kent Ridge Digital Labs Systeme d'organisation de donnees de catalogue aux fins de recherche et reperage
WO2001001366A2 (fr) 1999-06-25 2001-01-04 Telemonitor, Inc. Procede et systeme de surveillance intelligent a distance
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 (fr) * 1999-07-30 2005-07-27 Intertrust Technologies Corp. Procédés et systèmes de fourniture de données de transactions enregistrées au moyen de seuils et de protocole à plusieurs étages
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
AU1431201A (en) 1999-10-15 2001-04-30 Ajit K. Zacharias Secure multi-application card system
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 (fi) 2000-05-15 2003-02-28 Nokia Corp Puhelun muodostamisen ja jatkumisen ohjaaminen
AU2001273079A1 (en) 2000-06-26 2002-01-08 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
DE50106580D1 (de) 2001-04-12 2005-07-28 Siemens Ag Verfahren zum Abrechnen von Leistungen in einem Kommunikationsnetz
WO2002091726A1 (fr) * 2001-04-18 2002-11-14 Yozan Inc. Systeme de communication et procede de selection de ligne
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 (ja) 2001-12-17 2003-07-04 Fujitsu Ltd ゲートウェイ装置
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 (sv) 2002-02-28 2003-12-16 Ericsson Telefon Ab L M En metod och ett distribuerat tariffberäkningssystem för att bestämma tariffdata i ett debiteringssystem
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
AU2002358741A1 (en) 2002-12-16 2004-07-09 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 (fr) 2003-05-07 2006-02-01 Nokia Corporation Taxation basee sur le flux d'acces pour les services ims/poc
DE50301192D1 (de) 2003-05-27 2005-10-20 Siemens Ag Verfahren zum paketorientierten Übertragen von Daten in Telekommunikationsnetzen mittels Umsetzung in einem Zwischenknoten von einem verbindungslosen zu einem verbindungsorientierten Übertragungsprotokoll und umgekehrt
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
US7418252B2 (en) 2003-08-15 2008-08-26 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
US20050187830A1 (en) 2004-02-24 2005-08-25 First Data Corporation System for maintaining product 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
ATE382238T1 (de) 2004-06-03 2008-01-15 Ericsson Telefon Ab L M Gebührenberechnungsmechanismen für ip-multimedia- dienste
JP4668998B2 (ja) 2004-06-08 2011-04-13 テレフオンアクチーボラゲット エル エム エリクソン（パブル） Ｉｐマルチメディアサービスフレキシブル課金メカニズム
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 (fi) 2004-08-16 2004-08-16 Nokia Corp Mediapalvelun reititys
JP2006067124A (ja) * 2004-08-25 2006-03-09 Nec Corp 画像符号化データの切り替え方法および装置、システムならびにプログラム
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
US8116326B2 (en) 2005-06-28 2012-02-14 Oracle International Corporation Revenue management system and method
CA2616194C (fr) 2005-07-28 2015-02-17 Oracle International Corporation Systeme et procede de gestion des recettes
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

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"STATEMENT IN ACCORDANCE WITH THE NOTICE FROM THE EUROPEAN PATENT OFFICE DATED 1 OCTOBER 2007 CONCERNING BUSINESS METHODS - EPC / ERKLAERUNG GEMAESS DER MITTEILUNG DES EUROPAEISCHEN PATENTAMTS VOM 1.OKTOBER 2007 UEBER GESCHAEFTSMETHODEN - EPU / DECLARATION CONFORMEMENT AU COMMUNIQUE DE L'OFFICE EUROP" JOURNAL OFFICIEL DE L'OFFICE EUROPEEN DES BREVETS.OFFICIAL JOURNAL OF THE EUROPEAN PATENT OFFICE.AMTSBLATTT DES EUROPAEISCHEN PATENTAMTS, OEB, MUNCHEN, DE, 1 November 2007 (2007-11-01), pages 592-593, XP002456252 ISSN: 0170-9291 *
See also references of WO2007016412A2 *

Also Published As

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

Similar Documents

Publication Publication Date Title
US8117358B2 (en) Revenue management system and method utilizing database backup
CN107563887B (zh) 基于as400银行核心账务系统零停机日切方法
US10360563B1 (en) Architecture for a system and method for work and revenue management
US8489742B2 (en) System and method for work management
JP6181290B2 (ja) トランザクションの順序付け
US10642840B1 (en) Filtered hash table generation for performing hash joins
US6829623B2 (en) Method and system for managing multiple database storage units
US7043444B2 (en) Synchronization of planning information in a high availability planning and scheduling architecture
US10949413B2 (en) Method and system for supporting data consistency on an active standby database after DML redirection to a primary database
CN104813276A (zh) 从备份系统流式恢复数据库
CN101410836A (zh) 向应用提供对存储在数据库中的数据的访问的方法
CN110191168A (zh) 在线业务数据的处理方法、装置、计算机设备和存储介质
CN106649530B (zh) 云详单查询管理系统及方法
KR20150075407A (ko) 데이터를 저장하고 검색하는 방법 및 시스템
US20060031122A1 (en) Determining the configuration of a data processing system existing at the time a transaction was processed
CN112131305A (zh) 账户处理系统
US11256695B1 (en) Hybrid query execution engine using transaction and analytical engines
CN101364224A (zh) 用于信息管理的系统和方法
US20070038598A1 (en) Method and system for asynchronous data query and storage media storing a computer program for executing the method
US11914571B1 (en) Optimistic concurrency for a multi-writer database
Jagadish et al. SUNRISE II: A Scalable and Timely Billing Architecture
CN117172897A (zh) 一种生命周期的管理方法、装置、电子设备及存储介质
CN115700489A (zh) 应急切换方法、装置、电子设备及存储介质
CN117474386A (zh) 一种快递行业奖罚工单结算方法、装置、终端及存储介质
CN115080609A (zh) 一种高性能高可靠业务流程引擎实现方法和系统

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20080331

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1121253

Country of ref document: HK

R17P Request for examination filed (corrected)

Effective date: 20080331

A4 Supplementary search report drawn up and despatched

Effective date: 20100707

RIC1 Information provided on ipc code assigned before grant

Ipc: H04K 1/00 20060101AFI20100701BHEP

Ipc: G06Q 50/00 20060101ALI20100701BHEP

Ipc: G06Q 30/00 20060101ALI20100701BHEP

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20170119

APBK Appeal reference recorded

Free format text: ORIGINAL CODE: EPIDOSNREFNE

APBN Date of receipt of notice of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA2E

APBR Date of receipt of statement of grounds of appeal recorded

Free format text: ORIGINAL CODE: EPIDOSNNOA3E

APAF Appeal reference modified

Free format text: ORIGINAL CODE: EPIDOSCREFNE

APBT Appeal procedure closed

Free format text: ORIGINAL CODE: EPIDOSNNOA9E

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20201103