WO2016101621A1 - 充值实现方法及系统 - Google Patents

充值实现方法及系统 Download PDF

Info

Publication number
WO2016101621A1
WO2016101621A1 PCT/CN2015/085628 CN2015085628W WO2016101621A1 WO 2016101621 A1 WO2016101621 A1 WO 2016101621A1 CN 2015085628 W CN2015085628 W CN 2015085628W WO 2016101621 A1 WO2016101621 A1 WO 2016101621A1
Authority
WO
WIPO (PCT)
Prior art keywords
card
recharge
node
type
data
Prior art date
Application number
PCT/CN2015/085628
Other languages
English (en)
French (fr)
Inventor
李小永
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016101621A1 publication Critical patent/WO2016101621A1/zh

Links

Images

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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/22—Payment schemes or models
    • G06Q20/28—Pre-payment schemes, e.g. "pay before"
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/16—Payments settled via telecommunication systems
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards

Definitions

  • the present invention relates to the field of communications, and in particular to a method and system for implementing recharge.
  • the prepaid card is a product of the operator, which provides the user with the recharge of the operator's paid service. Since the purchase and use of the prepaid card is convenient, it is widely used.
  • the Voucher Center (hereinafter referred to as VC) is a software system that manages the data of the recharge card. In some countries and regions, due to the small face value of recharge cards and high liquidity, the number of recharge cards that need to be managed in the recharge center system often reaches 10 million or even 100 million.
  • FIG. 1 is a card-centric structure diagram of a VC system in the related art.
  • the life cycle of a recharge card mainly includes: recharge card creation, recharge card issue, recharge card modification, unused card deletion, and recharge card recharge. And have been deleted with the card.
  • VC needs to use large database software, such as Oracle and Sybase.
  • the refill card creation refers to creating a new recharge card data in a VC database.
  • the state of the card at this time is called "unreleased", and the recharge card in this state cannot be recharged.
  • the physical operation is to create a number of card and password for the recharge card.
  • the recharge card is issued by changing the status of the recharge card from "unreleased” to "issued". Cards in this state can be used for card information inquiry and card recharge by card number and password.
  • the physical operation is to print the card number and password to print the recharge card.
  • the recharge card is modified, including the blockade card (the card is not allowed to recharge after the blockade), the card is unlocked (the previous blockade state is released, the card is allowed to recharge again), the expiration date is extended, the card face value is modified, and the card is deleted. According to the state of the card, it can be divided into two categories, one is the modification of the unissued card, and the other is the modification of the issuance card.
  • Unused card deletion means that for some reason, the operator needs to delete the created unused card (including the unreleased card and the issuance card) from the database.
  • Recharge card recharge means that the user recharges the amount in the recharge card to his account through the card number and password of the recharge card. After the recharge, the status of the recharge card changes to "Used" and the card cannot be recharged again.
  • the card has been deleted, which means that the card has been charged, after being stored in the database for a period of time, the card data is completely deleted from the database, reducing the amount of card data and improving database performance.
  • the process of operator management personnel participation is: recharge card creation, recharge card issuance, recharge card modification, unused card deletion, used card deletion, etc., which can be collectively referred to as card management process.
  • the process of the user's participation in the operator is only one of the "recharge card recharge", which can be called the card recharge process.
  • VC systems need to manage large amounts of data, so large database software is used to manage card data.
  • data storage and management are usually performed using two sets of unused card tables and used card tables.
  • the unused card table stores the card data that can be recharged. The user will use the data in this table to recharge the card number and password.
  • the card data that has been saved is the value of the card data.
  • the used card for one month is placed in a used card table, which is called the “used card month table”. Overcharged card data, its card status changed from "unused” to "used”, and its unused card table was transferred to the used card monthly table to reduce the amount of unused cards and reduce the query burden. .
  • attribute information such as management attribute information (such as batch number, creation time, operator, etc.), and one type of attribute information (card number, password, amount, etc.) used for recharge. ).
  • management attribute information such as batch number, creation time, operator, etc.
  • attribute information card number, password, amount, etc.
  • a node in the computer industry, usually refers to a separate piece of hardware; in this paper, a server that deploys a software system that performs a function.
  • the related technical solution is that the VC system adopts a set of database in the software, the card management process of the recharge card, and the logic implementation of the card recharge process are all completed in the set of databases; one server, database and VC system are used in the hardware. Both are deployed on this server, which has the following disadvantages:
  • the card management process is a process in which the management personnel participates, and implements related management of the card data, including “recharge card creation”, “recharge card issue”, “recharge card modification”, and “used card deletion”.
  • the card recharge process is performed by the user.
  • the recharge operation process has nothing to do with the management personnel.
  • the card management process and the card refilling process are implemented in a set of databases, and the two competing for limited database resources have an impact on each other. For example, the management personnel perform management operations—create a batch of 100,000 cards. At this time, the database needs to perform card-creating operations, and the database resources are consumed. At the same time, the user is recharging. At this time, the recharge CAPS will be affected and responded. Slower and less concurrency.
  • the embodiment of the invention provides a method and system for recharging to solve at least the low-per-second access times of the refill operation caused by the card management process and the card refilling process being completed in a set of databases. problem.
  • a replenishment implementation system comprising: a first type of node configured to manage a recharge card and synchronize the issue card data to a second type of node; the second type of node, Set to process the recharge card refill and synchronize the refill data to the first type of node.
  • the second type of node is further configured to save only the issuing card data in the database corresponding to the second type of node.
  • the second type of node is further configured to perform a table splitting the database single table corresponding to the second type of node according to a preset rule.
  • the preset rule includes at least one of the following: the single table is divided into the specified number according to the card number or the arrangement rule of the password.
  • the second type of node is only configured to store a field related to the refilling process in the card data table, wherein the field related to the refilling process includes at least one of the following: a recharge card number, a recharge card password, and a recharge card denomination. .
  • the second type of node is further configured to add at least one of the following information to a specified field in the card data table: dial the number of the recharge card, the recharged number, and the recharge serial number.
  • the second type of node is further configured to modify the card table status to the used card, and prohibit the generation of the independent refill record and the used card record.
  • a method for recharging implementation comprising: receiving, by a first type of node, a first request for managing a recharge card, and synchronizing the issuance card data to a second type of node; Description The second type of node receives a second request to process the refill card refill and synchronizes the refill data to the first type of node.
  • the method further includes: dividing, by the second type of node, a database single table corresponding to the second type of node according to a preset rule.
  • the preset rule includes at least one of the following: the single table is divided into the specified number according to the card number or the arrangement rule of the password.
  • the technical means for completing the card management process and the card refilling process function by using two kinds of nodes respectively are solved, and the recharging operation caused by the card management process and the card refilling process being completed in a set of databases is solved in the related technology.
  • the problem of low access times per second and card management and card replenishment competing for resources realizes that in the recharge system, the card management process and the card recharge process are completed by different nodes.
  • FIG. 1 is a structural diagram of a card system centered on a VC system in the related art
  • FIG. 3 is a structural block diagram of a refilling implementation system according to an embodiment of the present invention.
  • FIG. 4 is a block diagram of a VC system centered on a VC system according to an embodiment of the present invention
  • FIG. 5 is an overall structural diagram of a VC system according to an embodiment of the present invention.
  • FIG. 6 is another overall structural diagram of a VC system according to an embodiment of the present invention.
  • FIG. 7 is a flow chart centered on a VC system according to an embodiment of the present invention.
  • FIG. 8 is a flow chart of a method for implementing refilling according to an embodiment of the present invention.
  • FIG. 3 is a structural block diagram of a refilling implementation system according to an embodiment of the present invention. As shown in FIG. 3, the method includes:
  • a first type of node 30, configured to manage the recharge card, and synchronize the issue card data to the second type of node 32;
  • the second type of node 32 is configured to process the recharge card refill and synchronize the refill data to the first type of node.
  • the first type of node manages the management process of the recharge card
  • the second type of node manages the recharge process of the recharge card, that is, the management process and the recharge process are completed by different nodes, and the solution is solved.
  • the card management process and the card refilling process are completed in a set of databases, the number of accesses per second of the refilling operation is low, and the card management and the card refilling compete with each other for resources, thereby realizing the problem in the recharging system.
  • the card management process and card refilling process are completed by different nodes.
  • the second type of node 32 since the second type of node 32 is responsible for the recharge process of the recharge card, the recharge process needs to be fast, and the second type of node 32 can only set aspects closely related to the recharge process, mainly embodied in The following aspects:
  • the second type of node 32 is configured to save only the issuing card data in the database corresponding to the second type of node; the second type of node 32 is further configured to reduce the single database corresponding to the second type of node according to a preset rule.
  • the data amount of the table wherein the preset rule includes at least one of the following: the single table is divided into the specified number according to the card number or the password arrangement rule; the second type node is only set to store and recharge the process in the card data table.
  • the related field wherein the field related to the refilling process includes at least one of the following: a recharge card number, a recharge card password, and a recharge card denomination; and the second type of node is further configured to add at least one of the following information to the card data.
  • the specified field in the table dial the number of the above recharge card, the recharged number, and the recharged serial number; the second type of node is also set to prohibit the generation of the independent recharge record and the used card record, and modify the card table status to the used card. .
  • first type of nodes are one or more
  • second type of nodes are one or more
  • the management process of the recharge card includes at least one of the following: a card creation process, a management process of an unissued card, a card issuance process, a management process of the issuance card, and a deletion process of the used card;
  • the above second type of node is also set to be responsible for the management process of the issuance card and the card refilling process.
  • the process participants are different, the card recharge process only the user participates, and the card management process only the management personnel participate;
  • the card data attributes used in the process are different, the card recharge process
  • the only use of recharge related attributes, such as card number, password, face value, the number is small; and the card management process uses all the attributes, including not only the recharge related attributes, but also the attributes used for management, such as batch, creation date , modification date, operator and other attributes, the number is large;
  • the process efficiency requirements are different, the card recharge process requires the corresponding speed as fast as possible, the speed is slow to accept; and the management process does not have the card recharge process high efficiency, slow speed
  • the process can handle different data, the card management process is to process all card data, including unreleased cards, issued cards, used cards; and the recharge process only needs to process the issued cards .
  • the amount of data between the two is very different.
  • the number of issued cards is generally only 1/3 of the total number of cards, and may even be
  • the operation of querying data and modifying data in the database, and the card management process are processed in the same way, which is a waste of resources, and can completely optimize the recharge process and improve its efficiency. .
  • the embodiment of the present invention proposes to change the original set of database of the VC system and the single node structure of one hardware into two kinds of node structures - "management node” and "recharge node".
  • the management node is responsible for the card management process; the recharge node is only responsible for the technical solution of the recharge process.
  • (1)(3)(5)(6) is a normal process, and all card data needs to go through these processes.
  • the optimization of these processes plays an important role in improving the efficiency of the whole VC system; and (2)(4) It is an abnormal process, and there are only a few cards that have these processes, which has little effect on the efficiency of the entire VC system.
  • the (1) (2) (3) (4) (6) type process can be implemented on the management node, and (4) (5) The class is implemented on the recharge node. (4) Both nodes need to process the data of the issuing card, so both nodes must have (as shown in Figure 4). Because the (2)(4) process has little impact on the system, it can be seen that the degree of coupling between the two nodes is low, which can basically be said to be an independent node.
  • the card management operation on the management node has almost no impact on the recharge process of the recharge node. Therefore, even if there is a problem with the management node, such as an operating system failure or a database downtime, the user recharge process on the recharge node will not be affected.
  • the most resource-intensive operation of the management node is to create a card operation. Under this new architecture, there is no impact on user recharge. Therefore, the management node and the recharge node can achieve high CAPS respectively.
  • the recharge node is completely serving the recharge process, some optimizations can be made for the characteristics of the recharge process.
  • the optimization method is mainly embodied in the following aspects:
  • the user recharge process greatly improves the query speed and update speed, and improves the user recharge experience.
  • the technical solution provided by the embodiment of the present invention is to change a node structure of the original technical solution into two or more node structures.
  • the user recharge process and the card management process are separated and handed over to different software/hardware nodes for processing.
  • the process responsible for processing the user recharge process may be referred to as a “recharge node”, and the process responsible for processing the card management process may be referred to as a “management node”.
  • the management node and the recharge node can be flexibly configured, and can be a 1:1 structure, a 1:n structure, or an n:n structure (as shown in FIG. 5 and FIG. 6); the card data of the recharge node is derived from management.
  • the recharge data of the management node is derived from the recharge node; between the two types of nodes, the distribution card data of the management node can be synchronized to the recharge node by synchronous operation, and the recharge data of the recharge node is synchronized back to the management node;
  • data synchronization it can be done in many forms, such as shell programs, C programs, and so on.
  • Data synchronization can be done in real time in a single piece of data, or it can be done in batches at low traffic peaks.
  • the recharge data is temporarily saved on the recharge node and needs to be transferred to the management node as soon as possible. Once the management node obtains these recharge data, the recharge node can delete the recharge data and reduce the database load.
  • the method of data synchronization can be various, such as Shell program, C program, etc.; according to the needs of the business, the data synchronization time can also be diverse, there is real-time data synchronization, there is a low peak period in the late-night traffic data synchronization.
  • the VC system can be set up on multiple servers, and different servers complete different operations in the VC system to improve system performance. If multiple recharge nodes are set up, the traffic volume of a single recharge node is reduced, and the load capacity of the system is increased.
  • the embodiment of the present invention is based on the above two points, and divides the VC into two kinds of nodes:
  • Recharge node which only processes the user recharge process.
  • the database of the recharge node only the user rechargeable card and the newly recharged card of the user on the same day reduce the data amount of the recharge card; at the same time, in order to further reduce the amount of single-table data, the table field is as small as possible, and only needs to be included. Recharge related fields to reduce disk reads and writes for query operations.
  • Management node which handles other card management processes except the recharge process.
  • the management node database contains all the recharge card data and all attributes.
  • the card table can also be changed to multiple card tables, and the table rules should be the same as the recharge node.
  • the card data table is divided into two types: one is a card table on the management node, and the field is all attributes. Fields, including management attribute fields and recharge attribute fields. Management attribute fields are: batch number, blockade flag, deblock time, creation date, release date, distributor, etc.
  • the recharge section has a card number, password, status, face value, expiration date, etc.
  • There is also a card table on the recharge node which only needs to recharge the attribute field, including card number, password, status, face value, expiration date, calling number, recharged number, Recharge the serial number and so on.
  • sub-table method In order to reduce the amount of data in a single table, you can split the original card table into multiple small tables according to the card number or password.
  • the card table of the recharge node and the card table of the management node can be divided into tables according to the same rules.
  • the method is as follows: according to the last digit of the card number, it is divided into 10 tables, according to the last two digits of the card number, divided into 100 tables; according to the last digit of the password, it is divided into 10 tables, according to the last two digits of the password, divided into 100 tables;
  • the difference between the requirements and the different methods of the table is used.
  • the rules of the table are not limited to the mantissa characters, and the intermediate characters are also used.
  • the processing of business processes (1), create a recharge card, only on the service node, insert card data in the card table of the service node. (2), unissued card modification card information (including blocking card, unlock card, extended validity period, modified face value, delete card, etc.), update card data operation on the management node. (3) To issue a recharge card, you need to perform a card issuance operation at the service node to modify the card status. According to different requirements, the issuing card data can be directly synchronized to the recharging node in real time; or through the timing task, the recharging node can be synchronized at the bottom of the traffic.
  • the card modification card information (including the block card, unlock card, extended validity period, modified face value, delete card, etc.), need to operate at the same time in the management node, recharge node.
  • user recharge only occurs on the recharge node.
  • the recharge data to the synchronization of the management node, c program, shell program, etc. can be used to generate the file from the recharge data of the day, transfer to the management node, update the data of the management node, generate a recharge record.
  • delete the used card only occurs in the management node.
  • the recharge data of the two is not necessarily synchronized in real time (usually, the recharge data of the management node is one day later than the recharge node), so the query card information also needs to be divided into two types. One is to query the card information of the management node, and the other is to query the card information of the recharge node (as shown in FIG. 7).
  • the above technical solutions adopted by the embodiments of the present invention can achieve the following technical effects: (1) The recharge performance that the refill node can provide is improved.
  • the recharge node and the management node are independent of each other, and there is no competition resource, which can fully improve the recharge CAPS.
  • the system using the original technical solution can provide the recharge CAPS is about 100 or so; and the recharge node with node and 100 tables, the recharge node can provide up to 300 recharge CAPS, and the management node can also achieve the card creation operation of about 800 CAPS, and the system performance is greatly improved; 2) Separation of management nodes and recharge nodes reduces the impact of management operations on recharge.
  • the operation on the management node in addition to the card issuance process, the modification process of the issuance card, and the rest of the card management process (including the process of creating a card, the process of modifying the unused card, the process of deleting the used card, etc.) will not affect the recharge node. . Even if the management node has a VC system hangs and the operating system restarts, it only affects the card management process, and has no effect on the user's recharge, improving the user's recharge experience.
  • FIG. 8 is a flowchart of a method for implementing recharging according to an embodiment of the present invention. As shown in FIG. 8, the method includes the following steps:
  • Step S802 receiving, by the first type of node, a first request for managing the recharge card, and synchronizing the issuance card data to the second type of node;
  • Step S804 receiving, by the second type node, a second request for processing the recharge card refill, and synchronizing the refill information to the first type of node.
  • the first type of node manages the management process of the recharge card
  • the second type of node manages the recharge process of the recharge card, that is, the management process and the recharge process are completed by different nodes, and the related technology is solved due to card management.
  • the process and card recharge process are completed in a set of databases, resulting in lower access times per second for recharge operations and competing resources for card management and card refilling.
  • different nodes are implemented. Card management process and card refill process.
  • the embodiment of the present invention achieves the following technical effects: in the related art, since the card management process and the card refilling process are completed in a set of databases, the number of accesses per second of the refill operation is low and Card management and card refilling compete with each other for resources. In the recharge system, different card nodes complete the card management process and card recharge process.
  • a software is provided that is configured to perform the technical solutions described in the above embodiments and preferred embodiments.
  • a storage medium is further provided, wherein the software includes the above-mentioned software, including but not limited to: an optical disk, a floppy disk, a hard disk, an erasable memory, and the like.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the method and system for implementing recharge according to the embodiments of the present invention have the following beneficial effects: the recharging operation caused by the card management process and the card refilling process being completed in a database is solved in the related art.
  • the problem of low access times per second and card management and card replenishment competing for resources realizes that in the recharge system, the card management process and the card recharge process are completed by different nodes.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Control Of Vending Devices And Auxiliary Devices For Vending Devices (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

一种充值实现方法及系统，其中，所述系统包括：第一类节点，设置为对充值卡进行管理，并将发行卡数据同步到第二类节点；所述第二类节点，设置为对充值卡充值进行处理，并将充值数据同步至所述第一类节点。采用上述技术方案，解决了相关技术中，由于卡管理流程和卡充值流程均在一套数据库内完成而导致的充值操作的每秒接入次数较低的问题，进而实现了在充值系统中，由不同的节点来完成卡管理流程和卡充值流程。

Description

充值实现方法及系统 技术领域
本发明涉及通信领域，具体而言，涉及一种充值实现方法及系统。
背景技术
充值卡是运营商的一种产品，为用户使用运营商的付费服务提供充值。由于充值卡的购买和使用很方便，因而被广泛采用。充值中心系统(Voucher Center，以下简称VC)是一套负责管理充值卡数据的软件系统。在某些国家和地区，由于充值卡的面值较小，流通性高，充值中心系统的需要管理的充值卡数量往往达到千万级乃至亿级。
VC需要对整个充值卡生命周期进行管理，最终让运营商的用户实现充值服务。图1为相关技术中VC系统以卡为中心的结构图，如图1所示，充值卡的生命周期主要包括：充值卡创建、充值卡发行、充值卡修改、未用卡删除、充值卡充值和已用卡删除。VC为了管理这些卡数据，需要采用大型数据库软件，如Oracle、Sybase等。
图2为相关技术中VC系统以流程为中心的流程图，如图2所示，充值卡创建，是指在VC的数据库里创建新的充值卡数据。此时的卡的状态称为“未发行”，此状态的充值卡是不能充值的。实物操作是，造出一批充值卡的卡号和密码。
充值卡发行，是指将充值卡的状态由“未发行”变更为“发行”。此状态的卡，可以通过卡号和密码进行卡信息查询、卡充值等操作。实物操作是，将制造好的卡号、密码去印制充值卡片。
充值卡修改，包括封锁卡(封锁后，该卡不允许充值)、解锁卡(解除之前的封锁状态，该卡再次允许充值)、延长有效期、修改卡面值、删除卡等操作。根据卡状态的不同，可以分为两类，一类是未发行卡的修改，一类是发行卡的修改。
未用卡删除，是指由于某些原因，运营商需要将创建好的未用卡(包括未发行的卡、发行卡)从数据库中删除。
充值卡充值，是指用户通过充值卡的卡号、密码将充值卡内金额充值到自己账户上。充值后的充值卡状态变为“已用”，该卡无法进行再次充值了。
已用卡删除，是指已经充过值的卡，在数据库里保存一段时间后，将该卡数据彻底从数据库中删除掉，减少卡数据量，提高数据库性能。
其中，运营商管理人员参与的流程是：充值卡创建，充值卡发行、充值卡修改、未用卡删除、已用卡删除等，可以统称为卡管理流程。运营商的用户参与的流程，只有“充值卡充值”一个，可以称为卡充值流程。
VC系统需要管理大量的数据，因此采用大型数据库软件来管理卡数据。在数据库中通常是用未用卡表、已用卡表两套表进行数据存储和管理。
未用卡表保存的是可以充值的卡数据，用户将通过卡号、密码来使用这个表里的数据进行充值。已用卡表保存的是充过值的卡数据,一般一个月的已用卡放在一个已用卡表里，称为“已用卡月表”。充过值的卡数据，其卡状态由“未用”变成“已用”，同时将其从未用卡表转移到已用卡月表，以减少未用卡的数据量，降低查询负担。
充值卡属性信息，通常有两类属性信息，一类是管理用的属性信息(如批次号、创建时间、操作人员等)，一类是充值用到的属性信息(卡号、密码、金额等)。运营商的用户只会用到充值属性信息，而运营商的管理人员是需要用到所有的属性信息。
节点，在计算机行业中，通常指一台独立的硬件设备；在本文中指的是部署一套能够完成某个功能的软件系统的一台服务器。
而相关技术方案是，VC系统在软件采用一套数据库，充值卡的卡管理流程、卡充值流程的逻辑实现，均在这一套数据库内完成；在硬件上采用一台服务器，数据库、VC系统都部署在这台服务器上，其存在以下缺点：
(1)系统可以容纳的充值的每秒接入次数(CAPS)较低。
随着VC系统中充值卡数量的增加，系统的性能是下降的，卡充值流程响应会变慢，系统可以容纳的充值的每秒接入次数(CAPS)会降低。对于用户方面的感受是，充值等待时间变长，出现超时现象，甚者无法进行充值，影响了用户充值体验。运营商方面，为了能够容纳更多的充值CAPS，就需要采用性能更好的硬件设备来保障VC系统的运行，花费更多的资金。
(2)卡管理流程操作和卡充值流程操作，竞争数据库资源，互相有影响。
卡管理流程是管理人员参与的流程，实现对卡数据进行相关的管理，包括“充值卡创建”，“充值卡发行”、“充值卡修改”、“已用卡删除”。而卡充值流程，是用户进行 充值操作流程，和管理人员无关。卡管理流程和卡充值流程，是在一套数据库内实现，两者共同竞争有限的数据库资源，彼此之间会有影响。如管理人员进行管理操作——创建一个批次10万张卡，此时数据库要进行创卡操作，数据库资源消耗较大；同时有用户在进行充值，此时的充值CAPS就会受到影响，响应变慢，并发性降低。
针对相关技术中，由于卡管理流程和卡充值流程均在一套数据库内完成而导致的充值操作的每秒接入次数较低的问题，尚未提出有效的解决方案。
发明内容
本发明实施例提供了一种充值实现方法及系统，以至少解决相关技术中，由于卡管理流程和卡充值流程均在一套数据库内完成而导致的充值操作的每秒接入次数较低的问题。
根据本发明的一个实施例，提供了一种充值实现系统，包括：第一类节点，设置为对充值卡进行管理，并将发行卡数据同步到第二类节点；所述第二类节点，设置为对充值卡充值进行处理，并将充值数据同步至所述第一类节点。
所述第二类节点，还设置为在所述第二类节点所对应的数据库中仅保存发行卡数据。
所述第二类节点，还设置为按照预设规则对所述第二类节点所对应的数据库单表进行分表。
所述预设规则包括以下至少之一：按照卡号或者密码的排布规则将单表分表为指定数量。
所述第二类节点，仅设置为在卡数据表中存储与充值流程相关的字段，其中，所述与充值流程相关的字段包括以下至少之一：充值卡卡号、充值卡密码、充值卡面值。
所述第二类节点，还设置为将以下至少之一信息添加至所述卡数据表中的指定字段：拨打所述充值卡的号码、被充值号码、充值流水号。
所述第二类节点，还设置为将卡表状态修改为已用卡，并禁止生成独立充值记录和已用卡记录。
根据本发明的另一个实施例，还提供了一种充值实现方法，包括：通过第一类节点接收对充值卡进行管理的第一请求，并将发行卡数据同步到第二类节点；通过所述 第二类节点接收对充值卡充值进行处理的第二请求，并将充值数据同步至所述第一类节点。
所述方法还包括：通过所述第二类节点按照预设规则对所述第二类节点所对应的数据库单表进行分表。
所述预设规则包括以下至少之一：按照卡号或者密码的排布规则将单表分表为指定数量。
通过本发明实施例，采用两种节点分别完成卡管理流程以及卡充值流程功能的技术手段，解决了相关技术中，由于卡管理流程和卡充值流程均在一套数据库内完成而导致的充值操作的每秒接入次数较低以及卡管理和卡充值相互竞争资源的问题，实现了在充值系统中，由不同的节点来完成卡管理流程和卡充值流程。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1为相关技术中VC系统以卡为中心的结构图；
图2为相关技术中VC系统以流程为中心的流程图；
图3是根据本发明实施例的充值实现系统的结构框图；
图4是根据本发明实施例的VC系统以卡为中心的结构图；
图5为根据本发明实施例的VC系统整体结构图；
图6为根据本发明实施例的VC系统另一个整体结构图；
图7是根据本发明实施例的VC系统以流程为中心的流程图；
图8为根据本发明实施例的充值实现方法的流程图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
本发明的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本发明而了解。本发明的目的和其他优点可通过在所写的说明书、权利要求书、以及附图中所特别指出的结构来实现和获得。
为了使本技术领域的人员更好地理解本发明方案，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分的实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本发明保护的范围。
为了至少解决上述技术问题，在本实施例中提供了一种充值实现系统，图3是根据本发明实施例的充值实现系统的结构框图，如图3所示，包括：
第一类节点30，设置为对充值卡进行管理，并将发行卡数据同步到第二类节点32；
第二类节点32，设置为对充值卡充值进行处理，并将充值数据同步至上述第一类节点。
通过本发明实施例提供的上述充值实现系统，通过第一类节点管理充值卡的管理流程，第二类节点管理管理充值卡的充值流程，即管理流程和充值流程采用不同的节点完成，解决了相关技术中，由于卡管理流程和卡充值流程均在一套数据库内完成而导致的充值操作的每秒接入次数较低以及卡管理和卡充值相互竞争资源的问题，实现了在充值系统中，由不同的节点来完成卡管理流程和卡充值流程。
可选地，对于第二类节点32，由于第二类节点32负责充值卡的充值流程，需要充值过程响应速度快，第二类节点32可以仅设置与充值流程密切相关的方面，主要体现在以下方面：
第二类节点32，设置为在上述第二类节点所对应的数据库中仅保存发行卡数据；第二类节点32，还设置为按照预设规则减少上述第二类节点所对应的数据库中单表的数据量，其中，预设规则包括以下至少之一：按照卡号或者密码的排布规则将单表分表为指定数量；第二类节点，仅设置为在卡数据表中存储与充值流程相关的字段，其中，上述与充值流程相关的字段包括以下至少之一：充值卡卡号、充值卡密码、充值卡面值；第二类节点，还设置为将以下至少之一信息添加至上述卡数据表中的指定字段：拨打上述充值卡的号码、被充值号码、充值流水号；第二类节点，还设置为禁止生成独立充值记录和已用卡记录，并将卡表状态修改为已用卡。
需要说明的是，第一类节点为一个或多个，第二类节点为一个或多个。
具体地，在本发明实施例中，上述充值卡的管理流程包括以下至少之一：创建卡流程、未发行卡的管理流程、卡发行流程、发行卡的管理流程、已用卡的删除流程；上述第二类节点还设置为负责发行卡的管理流程以及卡充值流程。
为了更好的理解上述充值实现系统所体现的技术方案，以下结合一个示例进行说明：
基于上述对相关技术卡充值流程和卡管理流程的概括：流程参与人员不一样，卡充值流程只有用户参与，而卡管理流程只有管理人员参与；流程用到的卡数据属性不一样，卡充值流程用的只是充值相关属性，如卡号、密码、面值，数量较少；而卡管理流程用到是全部的属性，不仅包含充值相关属性，还要包含管理用到的属性，如批次、创建日期、修改日期、操作人等全部属性，数量较多；流程效率要求不一样，卡充值流程要求相应速度尽可能快，速度慢就无法接受；而管理流程对效率要求没有卡充值流程高，速度慢一些也是可以接受的；流程可处理的数据不一样，卡管理流程要处理的是所有的卡数据，包括未发行的卡、发行的卡、已用的卡；而充值流程仅需要处理发行的卡。这两者的数据量差异巨大，通常发行卡的数量一般只占所有卡数量的1/3，甚者可能更低。
因此，对于卡充值流程，到数据库中去做查询数据、修改数据等操作，和卡管理流程按照一样的思路去处理，是一种资源的浪费，完全可以针对充值流程做一些优化，提高其效率。
本发明实施例针对上述技术问题，提出了将VC系统的原来的一套数据库、一台硬件的单节点结构，变成两种节点结构——“管理节点”和“充值节点”。管理节点，负责卡管理流程；充值节点，仅负责充值流程的技术方案。
由于对于VC系统的所有流程，按照卡的状态分，有以下几类：
(1)创建卡流程；(2)未发行卡的管理流程，包括修改面值、封锁、解锁、延长有效期、删除等；(3)卡发行流程；(4)发行卡的管理流程，也包括修改面值、封锁、解锁、延长有效期、删除等；(5)卡充值流程；(6)已用卡的删除流程。
其中的(1)(3)(5)(6)是正常流程，所有的卡数据都需要经过这些流程，对这些流程的优化对整个VC系统的效率提升有着重要作用；而(2)(4)是异常流程，只有很少的卡会有这些流程，对整个VC系统效率提升作用不大。
基于本发明那个实施例提供的上述技术方案，可选地，可以将将(1)(2)(3)(4)(6)类流程放在管理节点上实现，而(4)(5)类放在充值节点上实现。(4)是两种节点都需要对发行卡的数据进行处理，因此两种节点都要有(如图4所示)。因为(2)(4)流程对系统影响很小，因此可以看到两种节点之间的耦合度较低，基本上可以说是独立的节点。
管理节点上的卡管理操作，对于充值节点的充值流程是几乎没有影响，因此即使管理节点出现问题，如操作系统故障、数据库宕机等，都不会影响充值节点上的用户充值流程。管理节点最消耗资源的操作是创建卡操作，在这个新的架构下，对用户充值是没有任何影响。因此管理节点、充值节点分别可以实现很高的CAPS，同时，由于充值节点是完全为充值流程服务的，可以针对充值流程的特点做一些优化，优化方法主要体现在以下几个方面：
1、减少充值节点上的卡数量，充值节点上的数据库里只保留发行的卡。未发行的卡、已用的卡，转移到管理节点上；
2、进一步减少单表的数据量，可以分表，将单张卡表根据需要拆分为多张表，如根据卡号、密码以某种规则分成10张卡表，100张卡表等；
3、减少充值节点上的卡数据表的字段数，只保留充值相关的字段，如卡号、密码、面值等；
4、减少充值流程的读写操作，不生成独立充值记录、已用卡记录，只修改充值节点卡表的状态，表示已用卡；同时在卡数据表的字段中增加3个字段，在更新状态的同时记录拨打号码、被充值号码、充值流水号，减少数据库读写操作，加快数据库的处理速度。
而采用上述技术方案，用户充值流程大大提高了查询速度、更新速度，提高了用户充值体验。
综上所述，本发明实施例提供的技术方案就是将原来技术方案的一个节点结构，变成两个或多个节点结构。将用户充值流程和卡管理流程分离，交给不同的软件/硬件节点处理——负责处理用户充值流程的可以称为“充值节点”，负责处理卡管理流程的可以称为“管理节点”。管理节点和充值节点可灵活配置，可以是1:1结构，也可以是1：n结构，还可以是n：n结构(如图5、图6所示)；充值节点的卡数据来源于管理节点，而管理节点的充值数据来源于充值节点；两类节点之间，可通过同步操作，将管理节点的发行卡数据同步到充值节点，将充值节点的充值数据同步回管理节点；而 对于数据同步的实现，可以采用多种形式完成，如shell程序、C程序等。数据同步可以以单条数据形式实时完成，也可以以批量数据在话务低峰时定时完成。
此外，由于系统分为两种节点共同完成VC系统功能，两种节点间的数据要一致，因此就涉及到两种节点之间的数据同步问题。具体来说，有两个数据同步：
一、发行卡数据的同步。管理节点上进行卡发行流程后，数据库里的卡状态变为“发行”。这些新的发行卡需要同步到充值节点上，用户才可以充值。
二、充值数据的同步。充值节点上的发行卡，被用户充值以后，充值数据暂时在充值节点上保存，需要尽快转移到管理节点上去。一旦管理节点获取到这些充值数据，充值节点就可以把这些充值数据删除掉，降低数据库负担。
数据同步的方法可以是多种多样的，如Shell程序、C程序等都可以；可以根据业务的需求，数据同步时效也可以是多样的，有实时数据同步，有在深夜话务低峰期定时数据同步。
在硬件系统上，可以将VC系统架设在多台服务器上，不同的服务器完成VC系统中不同的操作，提高系统性能。如架设多个充值节点，降低单个充值节点的话务量，提高系统的承载量。
为了能够提高VC系统的充值性能，有两种方法：(1)减少VC的卡数据量，(2)减少单张卡的信息，降低磁盘读写操作。本发明实施例就是基于以上两点，将VC分为两个种节点：
(1)充值节点，仅处理用户充值流程。充值节点的数据库中，只有用户可充值的卡和当天用户新充值的卡，减少了充值卡的数据量；同时为了进一步减低单表数据量，同时表的字段尽可能的少，只需要包含与充值相关字段，降低查询操作的磁盘读写。
(2)管理节点，处理除充值流程外的其他卡管理流程。管理节点数据库中，含有全部的充值卡数据和全部属性。为提高管理节点的性能，也可以将卡表改为多张卡表，分表规则要和充值节点相同。
采用这样的技术方案，在充值节点上，由于仅含有发行的卡和当天充值的卡，不包含其他状态的卡，并且由于分表，单张表的数据量降低，同时单张卡的属性字段减少，因此提高了用户充值流程响应速度，提高了用户充值的体验；而在管理节点上，由于不含有用户充值流程，即使速度慢一些也是可以接受的，所以可以做一些占用资源较大的操作，或其他一些如停机、停数据库等操作，而不用影响到用户充值流程。
由于划分为管理节点和充值节点，两种节点之间需要有数据同步操作。主要涉及到卡发行流程、发行卡的修改流程及充值数据从充值节点同步到管理节点的操作。对于卡发行流程、发行卡的修改流程，为提高系统响应及逻辑需要，采用实时处理方式，即VC系统同时对管理节点、充值节点进行操作，实现所见即所得。对于充值数据的同步，采用的是异步处理方式，在深夜话务低峰时候，通过shell程序实现。
本发明实施例对上述技术方案的进一步改进在于，1、对于卡属性字段的分类：根据流程要求的不同，卡数据表分为两种：一种是管理节点上的卡表，字段是全部属性字段，包括管理属性字段和充值属性字段。管理属性字段有：批次号、封锁标志、解封锁时间、创建日期、发行日期、分销商等。充值段有卡号、密码、状态、面值、有效期等；还有一种是充值节点上的卡表，只需要充值属性的字段，有卡号、密码、状态、面值、有效期、呼叫号码、被充值号码、充值流水号等。
2、分表分方法：为降低单表的数据量，可以根据卡号、或密码的进行分表，把原来的一张卡表拆分为多张小表。充值节点的卡表和管理节点的卡表，可以按照相同的规则进行分表。方法有：根据卡号最后一位分为10张表，根据卡号最后两位分为100张表；根据密码最后一位分为10张表，根据密码最后两位分为100张表；可根据具体需求的不同，而采用不同的分表方法；需要说明的是，分表规则不限于尾数字符，也可以用中间字符，本发明实施例对此不作限定。
3、业务流程的处理：(1)、创建充值卡，仅在服务节点上进行，在服务节点的卡表里插入卡数据。(2)、未发行卡修改卡信息(包含封锁卡、解锁卡、延长有效期、修改面值、删除卡等)，在管理节点上做更新卡数据操作。(3)、发行充值卡，需要在服务节点进行卡发行操作，修改卡状态。根据需求不同，可以直接实时将发行卡数据同步到充值节点；也可以通过定时任务，在话务底峰期同步到充值节点。(4)、发行卡修改卡信息(包含封锁卡、解锁卡、延长有效期、修改面值、删除卡等)，需要在管理节点、充值节点同时操作。(5)、用户充值，仅在充值节点上发生。(6)、充值数据到管理节点的同步，可采用c程序、shell程序等，从充值节点获取的当天的充值数据生成文件，传输到管理节点上，更新管理节点的数据，生成充值记录。(7)、删除已用卡，仅在管理节点发生。(8)、由于分为管理节点和充值节点，两者的充值数据不一定是实时同步的(通常，管理节点的充值数据比充值节点晚一天)，因此查询卡信息也需要分为两种，一种是查询管理节点的卡信息，一种是查询充值节点的卡信息(如图7所示)。
本发明实施例采用的上述技术方案，可以起到以下技术效果：(1)充值节点能够提供的充值性能提高。充值节点、管理节点互相独立，没有竞争资源，能够充分提高充值CAPS。如一台服务，采用原有技术方案的系统，能够提供的充值CAPS大约为 100左右；而采用分节点、且分100张表的充值节点，充值节点能够提供的充值CAPS可以达到300左右，同时管理节点还可以实现800左右的CAPS的创卡操作，系统性能大大提高；(2)管理节点、充值节点分离，降低了管理操作对充值的影响。管理节点上的操作，除了卡发行流程、发行卡的修改流程，其余的卡管理流程(包括创建卡流程、未用卡的修改流程、已用卡的删除流程等)均不会影响到充值节点。甚至管理节点发生VC系统挂掉，操作系统重启的操作，也仅影响卡管理流程，对于用户的充值一点也没有影响，提高用户充值体验。
在本发明实施例中，还提供了一种充值实现方法，图8为根据本发明实施例的充值实现方法的流程图，如图8所示，包括以下步骤：
步骤S802，通过第一类节点接收对充值卡进行管理的第一请求，并将发行卡数据同步到第二类节点；
步骤S804，通过上述第二类节点接收对充值卡充值进行处理的第二请求，并将充值信息同步至上述第一类节点。
通过上述各个步骤，通过第一类节点管理充值卡的管理流程，第二类节点管理管理充值卡的充值流程，即管理流程和充值流程采用不同的节点完成，解决了相关技术中，由于卡管理流程和卡充值流程均在一套数据库内完成而导致的充值操作的每秒接入次数较低以及卡管理和卡充值相互竞争资源的问题，实现了在充值系统中，有不同的节点来完成卡管理流程和卡充值流程。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本发明并不受所描述的动作顺序的限制，因为依据本发明，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本发明所必需的。
综上所述，本发明实施例达到了以下技术效果：解决了相关技术中，由于卡管理流程和卡充值流程均在一套数据库内完成而导致的充值操作的每秒接入次数较低以及卡管理和卡充值相互竞争资源的问题，实现了在充值系统中，由不同的节点来完成卡管理流程和卡充值流程。
在另外一个实施例中，还提供了一种软件，该软件设置为执行上述实施例及优选实施方式中描述的技术方案。
在另外一个实施例中，还提供了一种存储介质，该存储介质中存储有上述软件，该存储介质包括但不限于：光盘、软盘、硬盘、可擦写存储器等。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的对象在适当情况下可以互换，以便这里描述的本发明的实施例能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，本发明实施例提供的一种充值实现方法及系统，具有以下有益效果：解决了相关技术中，由于卡管理流程和卡充值流程均在一套数据库内完成而导致的充值操作的每秒接入次数较低以及卡管理和卡充值相互竞争资源的问题，实现了在充值系统中，由不同的节点来完成卡管理流程和卡充值流程。

Claims (10)

  1. 一种充值实现系统，包括：
    第一类节点，设置为对充值卡进行管理，并将发行卡数据同步到第二类节点；
    所述第二类节点，设置为对充值卡充值进行处理，并将充值数据同步至所述第一类节点。
  2. 根据权利要求1所述的系统，其中，所述第二类节点，还设置为在所述第二类节点所对应的数据库中仅保存发行卡数据。
  3. 根据权利要求1所述的系统，其中，所述第二类节点，还设置为按照预设规则对所述第二类节点所对应的数据库单表进行分表。
  4. 根据权利要求3所述的系统，其中，所述预设规则包括以下至少之一：按照卡号或者密码的排布规则将单表分表为指定数量。
  5. 根据权利要求1所述的系统，其中，所述第二类节点，仅设置为在卡数据表中存储与充值流程相关的字段，其中，所述与充值流程相关的字段包括以下至少之一：充值卡卡号、充值卡密码、充值卡面值。
  6. 根据权利要求5所述的系统，其中，所述第二类节点，还设置为将以下至少之一信息添加至所述卡数据表中的指定字段：拨打所述充值卡的号码、被充值号码、充值流水号。
  7. 根据权利要求5所述的系统，其中，所述第二类节点，还设置为将卡表状态修改为已用卡，并禁止生成独立充值记录和已用卡记录。
  8. 一种充值实现方法，包括：
    通过第一类节点接收对充值卡进行管理的第一请求，并将发行卡数据同步到第二类节点；
    通过所述第二类节点接收对充值卡充值进行处理的第二请求，并将充值数据同步至所述第一类节点。
  9. 根据权利要求8所述的方法，其中，所述方法还包括：
    通过所述第二类节点按照预设规则对所述第二类节点所对应的数据库单表进行分表。
  10. 根据权利要求9所述的方法，其中，所述预设规则包括以下至少之一：按照卡号或者密码的排布规则将单表分表为指定数量。
PCT/CN2015/085628 2014-12-26 2015-07-30 充值实现方法及系统 WO2016101621A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410836444.9A CN105787721A (zh) 2014-12-26 2014-12-26 充值实现方法及系统
CN201410836444.9 2014-12-26

Publications (1)

Publication Number Publication Date
WO2016101621A1 true WO2016101621A1 (zh) 2016-06-30

Family

ID=56149163

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/085628 WO2016101621A1 (zh) 2014-12-26 2015-07-30 充值实现方法及系统

Country Status (2)

Country Link
CN (1) CN105787721A (zh)
WO (1) WO2016101621A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019218976A1 (zh) * 2018-05-14 2019-11-21 网联清算有限公司 数据处理方法、装置和计算机可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102693587A (zh) * 2012-05-29 2012-09-26 辽宁省电力有限公司沈阳供电公司 电力客户充值卡缴费业务管理系统及方法
CN103095946A (zh) * 2011-10-28 2013-05-08 中国移动通信集团河北有限公司 一种充值卡充值方法、系统及装置
CN103177004A (zh) * 2011-12-21 2013-06-26 中国移动通信集团河北有限公司 保证充值卡数据一致的方法和系统
CN104038651A (zh) * 2013-03-07 2014-09-10 中兴通讯股份有限公司 一种充值卡管理及充值系统及方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002278839A (ja) * 2001-03-15 2002-09-27 Sony Corp データアクセス管理システム、メモリ搭載デバイス、およびデータアクセス管理方法、並びにプログラム記憶媒体
CN102467770B (zh) * 2010-11-08 2014-03-26 中国移动通信集团安徽有限公司 一种利用充值卡充值的方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103095946A (zh) * 2011-10-28 2013-05-08 中国移动通信集团河北有限公司 一种充值卡充值方法、系统及装置
CN103177004A (zh) * 2011-12-21 2013-06-26 中国移动通信集团河北有限公司 保证充值卡数据一致的方法和系统
CN102693587A (zh) * 2012-05-29 2012-09-26 辽宁省电力有限公司沈阳供电公司 电力客户充值卡缴费业务管理系统及方法
CN104038651A (zh) * 2013-03-07 2014-09-10 中兴通讯股份有限公司 一种充值卡管理及充值系统及方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019218976A1 (zh) * 2018-05-14 2019-11-21 网联清算有限公司 数据处理方法、装置和计算机可读存储介质
US11934371B2 (en) 2018-05-14 2024-03-19 Netsunion Clearing Corporation Data processing method and apparatus, and computer-readable storage medium

Also Published As

Publication number Publication date
CN105787721A (zh) 2016-07-20

Similar Documents

Publication Publication Date Title
US12346303B2 (en) Transaction processing method and apparatus, computer device, and storage medium
US20210203723A1 (en) Data Storage Method and Apparatus
CN103885986B (zh) 主备数据库同步的方法和装置
CN103577454B (zh) 一种文件合并方法和装置
TW202004604A (zh) 基於區塊鏈的交易處理方法及裝置、電子設備
CN109271450A (zh) 数据库同步方法、装置、服务器和存储介质
CN101799797A (zh) 分布式存储系统中用户磁盘配额的动态分配方法
CN104317957B (zh) 一种报表处理的开放平台、系统及报表处理方法
CN106933836B (zh) 一种基于分表的数据存储方法和系统
CN105740248B (zh) 一种数据同步方法、装置及系统
CN112162846A (zh) 事务处理方法、设备及计算机可读存储介质
CN108446315A (zh) 大数据迁移方法、装置、设备及存储介质
CN110083306A (zh) 一种分布式对象存储系统及存储方法
WO2016101621A1 (zh) 充值实现方法及系统
CN111815438A (zh) 一种数据处理方法及装置
Grybniak et al. Waterfall: A scalable distributed ledger technology
CN112669160B (zh) 数据处理方法、装置、电子设备及存储介质
CN109150593A (zh) 云数据系统中资源的管理方法和装置
CN118093647B (zh) 一种支持多副本一致性读的分布式数据库查询系统、方法、设备及介质
CN110019092A (zh) 数据存储的方法、控制器和系统
CN117608829A (zh) 一种基于Akka与kafka的大数据量并行薪酬计算方法
CN106339432A (zh) 一种按查询内容进行负载均衡的系统及其方法
CN105224651A (zh) 一种基于读写分离的信息系统内外网数据库优化方法
CN114996210A (zh) 数据处理方法、装置、计算机设备和存储介质
Maiyya et al. Samya: A geo-distributed data system for high contention aggregate data

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15871695

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15871695

Country of ref document: EP

Kind code of ref document: A1