On the surface, it's like asking a simple functional question, actually asking if you can really run behind the whole system. Because it's easy for clients to charge.Can the fee rule fit the scene?That's the point.
Some projects are suitable for daily fees, some for monthly charges, some for account charges and others for more interest.A number of devices can be used in an account... if one setNetwork billing systemIt's a basic fee, and the front period may be easy to use. When you try to fix the meal, change the rules, divide the crowd, the system gets more and more awkward.Network billing systemI can't just look.“Can we do it?”- It's up to him.Is the fee model flexible enough?The rules are not sufficiently detailed.
First, the most common is...Timely billing。
This is common in many dormitories, apartments, and temporary access networks. For example, for hours, one day, three days, seven days, users choose according to their own user cycle. The benefits of time-counting are flexible for operators, suitable for short-cycle use and for projects with more demand for the temporary network.
But...Timely billingNot a simple one.“Hours package.”Just fine. It's really practical.Network billing systemThe rules are not too detailed. For example, the set starts immediately or the user starts calculating when it first gets online; the package ends with a direct disconnect or with a warning first; whether the clocks continue after the halfway line is broken; whether multiple short-time packages can be overtaken by purchases; and whether the state of the maximum rate of renewal is synchronized in time. These details are poorly processed and the users can easily feel that the system is being used to determine whether they have been able to make a quick start.“Instability”In many cases, it is not the network that is poor but the costing logic that is too thick.
The second one is very common.Cost per day。
This approach is more appropriate for the network, such as apartments, dormitories, hotel management sites, short-term rental properties, some of which are used for a few days, days, and daily fees more flexible than monthly. For managers, it is also easier to match daily fees with occupancy cycles, rent periods, follow-up updates and recommendations for dinner packages.
Many clients thoughtCost per daySo, it's easy to say that the rest of the story is quite similar. For example, today's opening day is a day or tomorrow is the same time; buying three-day packages, either on natural days or 24 hours; allowing early renewal when the package expires; and then recalculating from the time of purchase. These seem like small problems, which actually have a direct impact on users' experience. In particular, with more than one user count, rules are not clear and can be easily appealed.Network billing systemAnd when we do daily, it is not just about building a set of meals, but also about handling these rules together.
If we go down, we'll have a lot of projects.Monthly。
This model is most common in school dormitories, campus wireless networks, apartment broadband, campus accommodation networks, and long-term rental settings. Since monthly fees are consistent with most user habits, operators can also manage more easily through the cycle.
MonthlyNot just the point.“A month's worth.”But look at this.Network billing systemCan you do the cycle before it's over? Can you warn automatically, if you can wait for a user to renew the fee, if there is an alarm page before the network breaks, if you can see quickly what accounts are fast due, which ones are already late and which account numbers are high. You find that it is not really one month's meal that you have to pay monthly, but let us go.Retention process smooth, fast-paced and user-friendly complaintsAnd that part of the power is doing well, and it's a lot less stress management later.
Besides the time-based fee, there's a client who has a special interest in it.Charges by terminal。
The real demand behind this model is not necessarily for fees alone, and it is often managed. In such environments as dormitories, shared networks, rental networks, etc., clients often ask:How many devices can an account have been connected to the Internet at once?One, one cell phone and computer, and some make different sets of meals into a different terminal. For example, the basic package can be used only with one device, and the higher set can be used with two or three devices online at the same time, which is actually the wayTerminal limitandFee-based packageCombining up.
This pattern is...Network billing systemIt's very practical. Because many real business problems are not the user's willingness to pay, but the account sharing is too serious. One buys a set of meals, several people use it together, and the rest of the network experiences are bad and benefits are being spread out.Terminal number ruleA fine-tune would put a burden on sharing and abuse without affecting normal users. For example, it would be very practical to limit the number of devices that are online at the same time as an account, to allow users to untie old equipment themselves, to change their mobile phones, to kick off old equipment directly or to ban new equipment from entering, which is beyond the end count.
There are other projects that go on not just by time or terminal fees, but also by doing it.Group fee mode。
For example, a month package allows one device by default; if you want to bring another one, buy a higher package. And for example, it's also a monthly package, and the general user gives basic bandwidth, an advanced package provides higher bandwidth, or provides longer online duration.Timely billingandLimit by TerminalPut it together, so that users can buy it in time and be limited by the number of devices. This is not a single charge, but this one.Network billing systemCan you support the multidimensional combination?
Real mature.Network billing systemThe cost model will not be particularly fatal. Because demand on the ground is not always constant. Today, customers may just charge a monthly fee and then they may want to add a skyscraper; now they may only require an account number and a double-end package; they start to want to make base charges and run up and then they want to do preferential meals, holiday packages, and experience packages.
And, you know, a lot of clients are easy to ignore.The fee model and the reminder mechanism are to be matched。
Whether it's on time, by day or by month, the most distasteful thing for users is not the charge itself.Suddenly the net was off.It's still working yesterday. It's suddenly gone. The page doesn't remind you that the first reaction is usually not a user.“I'm gonna have to make it up.”And I think the network is broken. So, okay.Network billing systemNot only can a package be built, but it also allows fast-termizing reminders, expired windows, renewals to the entrance and automatic restoration of these links. The charge is just part of what you see at the front desk, and the real decision is whether the whole set of connections will be smooth or not.
The blogger says that the government is not going to be able to do anything about it.Network billing systemThe clearer the fee-back model supported, the easier it is to structure later on.
Like short-time user scenes, you can focus on pushing.Cost per day; long-term user-friendly scenes that focus on theMonthly; multi-equipment, sharing of problems visible, can be used to createLimit by TerminalThe network charges are not just death rules, but can be adjusted to the situation on the ground. This is important for a truly operational project.
The blogger says:What fee-based models are supported by the web billing systemOn the surface, it is about functionality, and actually about how to fine-tune network operations behind this system.Timely billingThe problem of short-term use is solved by the government.Cost per dayThe site is designed to provide a temporary and residential setting.MonthlyA suitable for long-term stable operations,Fees or restrictions by terminal numberIt is better to control sharing and raising the benefits. If these models are flexible enough to combine, the back-office rules are sufficiently detailed.Network billing systemIt'll go a lot easier.
Many projects are not easy to do at a later stage, not because they're too small for the fee model, but because they really die when they're down. The holsters don't have the flexibility, terminal rules are unclear, renewals are bad, synchronization is slow, end users are not working, management is troublesome.Network billing systemNot how many charges are written in the functional table, but whether they really match your scene and run steady over time.
Keep going down after your keyword. The next one is the best:How do we limit the number of terminals in a network billing system? Can an account be used by multiple people at the same time?。