The question is ostensibly about terminal limits, and in fact two things:How to prevent account sharingandHow to combine the rules and actual management of the billing.。
Because in many real scenes, Internet fees are collected, often not only to see if the set is good or not, but also whether the account number is contained. One person buys a package and several people in the dorms use it together; one tenant opens an account number with all his cell phones, computers, tablets, TV boxes; even someone lends the account number for long periods of time.Network billing systemThere are no limits on the number of terminals, and users are more free to view the Internet on the face of it. The following results usually follow:Network experience is bad.，Actual gains were spread。
So, it's in the network billing system.Terminal limitNever was it a small, non-existent function, but the key point in the long-term sustainability of many projects.
Let's get to the bottom of this:
Whether an account can be used by multiple users at the same time depends not on how the client thinks but on how the system rules are set.
So, technically, it's not that many people can use it at the same time.Network billing systemPromise not to allow. If the system is setOne account can only bind one device., which is naturally not shared by many at the same time; if setOne account allows two or three devices to be online simultaneously., the user can use multiple end-uses within a limited range. The real problem is not“Can you do that?”But...Should I put it like this? What's the best level of security?。
Many projects are easy to judge here from the outset.
Some managers feel that the terminal numbers are a little more relaxed, and user experiences are better and users are less likely to complain. The idea cannot be entirely wrong, but it is often harder to manage the rest of the world if the scene itself is sensitive to sharing, with the end count loosed.
So,Network billing system limits terminalsThe first level doesn't mean that“Limitations and limitations”Instead, it is intended to maintain the network resources, user experience and fee rules within a manageable range.
The basics are...Account number one terminal.。
The simplest and most direct rule. An account allows only one device, whether mobile or computer or tablet, to be connected to one of them, and the other is denied access to it or the original device is pushed offline. The benefits of this model are clear:The easiest to prevent sharing and the most easy to control abuseThis is always the case, especially in student dormitories, short-term rental networks and temporary access networks.
But account number one is not entirely fine. Because there's more than one device for many users now. One cell phone, one computer, and it's normal. Some users buy a package with their phones, they want to log on the computer and find that the original equipment has been turned over.Account number one terminal, though well managed, may be severe for some of the scenes.. If the project itself is more user-oriented than limited sharing, this rule may not be the most appropriate.
So many mature.Network billing systemNot just.“One.”This option is supported.One account two terminals.Or...Account number multiend classification control。
For example, basic package allows one device, higher level package allows two devices, or computers and mobile phones are classified as each, with a total of only two units.Control SharingandCare for normal usage habitsA balance is found between the use of a user's mobile phone and computer that can be connected to the Internet, and the experience is not so bad; for management, the number of terminals is still framed without spreading indefinitely.
And that's why many projects are not satisfied with the fact that they have been able to do so.“Just limit the number of terminals.”The question will continue to be more detailed:
How do we identify the terminal numbers? How do I bind them? What do I do with the equipment?
These are the issues that are really easy to find in terminal limit.
First, identification.
A real one.Network billing system, usually the end is judged by the identity of the device, most often by binding it through terminal features. For managers, there is no need to remember too much technical detail, just know that the system must be identifiable.“Is this the same device?”If you don't even do this, the terminal limit becomes thin. Users change access, re-card and reconnect, and the system recognizes it as a new device, and management is going to be messy behind them.
- Say it again.
Many clients ask, "Does the terminal be automatically tied or is it hand-handled by a manager?Automatically bindIt's almost necessary. Because of the number of users, it is not possible to get a personal register from a manager for every mobile phone and computer change.Network billing system, the user should be supported to automatically bind the terminal after first login and at the same time the back desk can see which equipment is now tied, which equipment has recently been online, and whether the number of terminals is exceeded. This would make day-to-day management much lighter.
Then the most common source of complaints:What about the change of equipment?。
For example, when the user logs in on an old phone and now changes a new one; or when it logs on a computer, he wants to switch to a tablet. If the system rules are too dead and no untie mechanism, the user will find it particularly difficult. But if the strapped is too loose, it's tantamount to letting the sharing go. So the best practice here is not to let go of the dead, not to let go, but to let it.Network billing systemSupports a more rational end management approach.
For example, it can be set:
User allows to untie old devices, with a limitation of frequency;
Or...When the number of terminals is exceeded, the first online device will automatically be removed from the new device login；
Alternatively, managers will be provided with manual terminal-laden capability from backstage, and exceptional account numbers will be processed in exceptional circumstances.
The advantage of doing so is that normal users will not be completely stuck with the change of equipment, and malicious sharing will not be too easy to drill.
In another case, clients are particularly concerned about:
Can you have a few people on a single account instead of using it at the same time?
The problem is real. Because in many projects, users are not necessarily“Share it with each other”Today, this guy uses it. Tomorrow he logs in again. On the surface, there's no multiple terminals online, but they are essentially a shared account.Network billing systemIf the system allows unlimited number of account changes, the sharing problem is not manageable even if it limits the number online.Concurrent online terminalsAnd the limits are appropriate.Terminal Switch Frequency. For example, frequent terminal replacements are required to trigger verification in a short time or to untie old equipment before new equipment can be tied.
From an operational point of view,Terminal limitIt's not just a game of sharing. It can actually be used for it.Set of meals。
In many projects, the profit margin for basic packages is limited and if all users are implicitly allowed to hang devices indefinitely, there is little difference behind them.Network billing systemSupports linking the terminal numbers to the package levels, and things are different. For example:
Basic package1 equipment
Standard package: 2 sets of equipment
High-grade package.: 3 or more units
The terminal limit is then not just a control tool, but also part of the fee rule. For users, they buy access at whatever level they want to spend; for managers, they control sharing and upgrade the set of design spaces. Many long-run projects that run relatively smoothly are slowly moving forward.
Of course, the terminal limit cannot be applied in a single way.
Different scenarios, different strategies.
Like, in...Student dormitoryThe situation, account sharing problems are usually more obvious and the terminal numbers should be stricter.
Yes.Rented flatThe scene, where many users do have a dual-use need for mobile phones and computers, is often more reasonable in two.
Yes.Business officesIn the scenario, the focus is not usually on fees but on privileges and identity management. The end-number limit, while important, is more to avoid unusual sharing.
Yes.Hotels and temporary accommodationIn the scene, endpoints are often judged in conjunction with the number of rooms and the type of occupants and cannot be fully applied to the logic of accommodation.
So, really good.Network billing systemNot just a rule, but one that can be used to define end-number strategies according to different SSIDs, different groups, different packages. So that when the system is online, not all people are going to walk in the same rules and the more confusing it becomes.
And let's say that we have a user experience.
A lot of people heard it.“Limit Terminals”And you're worried that it won't affect us too much. The problem is not about limitless, but rather about the fact that we have to be able to use them.The rules are clear and the process is not going well.If users can know from the outset that their packages allow a few devices, how to handle them beyond the point of view, and how to operate after changing the equipment, and there are clear indications on the page, then complaints will not usually be too many. Most feared is that there are limits on backstages, no instructions at the front desk, and users think that the network is wrong, but that the end limit is just exceeded. Such systems are not rules, but tips and interactions are not done well.
So a mature set.Network billing systemIn addition to the endpoints available at backstage, these should be accompanied by:
Terminal timeout with clear hint
Users can see their own binding devices.
There's a clear entrance or a clear way to handle it when you need to untie.
The administrator's back desk can quickly access the account's terminal binding records.
These functions appear to be small, but when they are actually online, they will significantly reduce the pressure on the transport.
The blogger says:How to limit the number of terminals in network billing systemsThe core is not technically impossible, but how the rules are best set.
Of course, an account can be designed to be used by multiple people.But that often means sharing is more difficult to control, benefits are more easily lost and network experiences are more vulnerable to being drawn down.
Conversely, if the restriction is too restrictive, it may affect normal user experience.
So the most reasonable thing to do is not to go extreme, but to getNetwork billing systemCapacity is available in all of these areas:
It limits the number of simultaneous online terminals.
It manages terminal binding and tangled.
Controls the frequency of terminal switching
It combines the terminal numbers with the package levels.
It's a different set of rules.
So the terminal limit is no longer just one.“Cutters.”And it's really going to be a very practical part of the network.
You're going to have to take the key word down. The next one is best written:Why do web-based billing systems work with authentication systems? Many projects only charge fees, and the rest are more complicated.。