The fee-breaker is the most sensitive strategy in the operation of the campus wireless wifi system. It's too hard to break the net.——The balance is immediately closed and the students complain; it's too soft.——The cost gap can be maintained for some time, and the loss of billing revenue and fairness are questioned. How to design a fee breakup strategy that would ensure both that the bill is serious and that does not make user experience unacceptable?
The problem with the hard wire is more than a complaint.
The balance is zero and the network is broken. Logically cleanest.——The billing system immediately sends out a strategy to make Authentication Gateway force the user to go down. But this hard-line is working on two issues. One is that it has bad experience. Students are watching online course videos, submitting their jobs, doing online tests and suddenly the network is off.——The complaints about this type of scene are particularly intense because the time for disconnection is not right. Second, students cannot charge after a break.——If you break the net, you can't get a full page, you can't get it back. Students can only use their classmates to fill it or run to the information centre counter for cash."Arrears→Fill→Restore"The chain is much longer.
The core of the problem is not that it's hard-line."Makes the network softer."But..."Make it more fast."The U.S. WiFi system should be supported"Fill is restored"——The billing system, when notified of the payment return, immediately sends a strategy to restore access to the user without waiting for manual processing by the carrier or scheduled batch processing by the system. The chargeback is held within 10 seconds between the payment call back and the release of the strategy. If the delay exceeds one minute, the student waits for a minute before accessing the Internet or complains.
Soft breakout: buffer period after payment
Soft breakout is done by giving a buffer period after the user's balance reaches zero.——For example, the Internet continues to be available 24 hours or 3 days, during which time a default charge is posted on the authentication page to guide users to charge. The net breaks are only real after the buffer period has ended. The benefits of this approach are that users experience better: they don't lose the net because they forget the charge and have enough time to process their contributions. The disadvantage is that traffic consumption in the buffer period cannot be charged.——The length of the buffer period is determined by the school’s actual situation. If the line of recharge is easy (self-help on-line, stable payment channels) the buffer period can be shorter (12-24 hours). If there are barriers to the line of charging (e.g. some schools only support the cash charge below the line), the buffer period takes longer (3-5 days) and gives students enough time to pay their contributions.
There is also a variant of the soft break-in network: not completely off during buffer periods, but only at a speed that allows students to view web pages, receive mail but cannot see videos and download large files."Slow-speed buffer."Strategy"Completely off the grid."There are many fewer complaints, while traffic consumption is minimal during low-speed buffers, which hardly put any pressure on export bandwidth. Low-speed buffers do not provide free access to the Internet.——It's a cost (the system is still operational), but it's a much better experience for students than a complete disconnection."We're going to have to slow down."Function, it is recommended that the speed of down instead of direct offline be preferred.
Design logic for late alarms
The alerts are notices sent by the campus wireless wifi system when user balances are running out or have been depleted. The reminders can be made in several ways: authenticating window alarms, text alerts, mail alarms. The reminder should contain current balances, expected time available (based on current flow consumption rates), and a punctuation portal link.——The alarm is not until the balance is zero, if the balance is below a threshold. The early warning is intended to allow users to process the charge before the balance is exhausted and avoids off-grid or down-speeding.
The alarm frequency is not too high. One reminder per day is enough, and no user will emit any outstanding charges for each authentication.——The frequency of reminders is considered harassment by the students, but they are ignored.——Text messages are expensive and students have less tolerance for harassment.
Compliance considerations for fee-splitting
The Uwifi Wire on campus system has another easy to ignore compliance dimension: the physical name certification compliance requirement requires that a user of the campus web logs be kept continuously. If the user is out of charge, the user will not produce an Internet log.——It's not a problem in itself, but the question is..."The status of the client in the network system"Completeness. Some billing systems remove the user ' s online status record after a fee break, leaving the user with an empty network for some time——From the perspective of web-based auditing,"There's a log but no Internet access."It's different. Space states mean..."This man disappeared from the campus network.", which may be challenged by the audit as missing data. The correct course is to keep a log of the user’s account number status after the fee has been cut off (labelled as"Timeout on arrears") Do not clear or archive until user charge is restored or account number is cancelled.
The special scene's offline strategy.
There are several special scenarios that need to be specifically addressed in the late fee breakup strategy. First, there is a breakout protection during the examination: online test hours (end of the exam week) and no student should be underpaid break or downtime.——Even if the balance is insufficient, it should be maintained and the arrears processed after the examination. This protection strategy needs to be pre-positioned so that they cannot be handled manually. Second, the easing of the early start of the new school (two weeks before the beginning): the freshman may not have been familiar with the charging process at the time of entry, but the amount of the arrears should be more light than usual.——The three are strategic adjustments during the long vacation period (cold summer break): most students leave school, there are fewer online users and the payment of arrears can be more stringent.——The buffer period is shortened and the frequency of reminders increased, as leave does not require consideration of large-scale pressure to file complaints.
Automation of network breakbacks
The recovery process should be automated as much as possible after the fee is off."Time balance check + autorecover"——If the user has not returned to the system for some reason, and the strategy is not sent out in time (delays on the return of calls, failure of the strategy), the billing system should automatically scan all those who owe it during the next scheduled inspection cycle (e.g. every five minutes) to find that the balance has been restored but the strategy has not been released, and automatically send a recovery strategy. A full reliance on manual treatment of the recovery option is not feasible in a large-scale scenario——A 5,000-person school may be filled with dozens of unpaid households every day, and it is not possible for the personnel to recover manually from each.
Early warning of loss of unpaid households
Users with long-outstanding fees (over 7 days unfilled) may have abandoned the campus network——The loss of such users has a direct impact on the operating income of the campus wireless WiFi system.——List"The debt is over seven days, but the account's still active."The user lists, which may just be missing the full value, can be pulled back by a text message alert."The debt is over 30 days and the account's inactive.", the user can be marked as"Silence User"The probability of recovery for such users is low and the focus should be on access to new users and retention of active users.
The late fee breakup strategy isn't."One cut off the net."So simple, it takes into account the availability of a collection channel, protection needs at specific times, compliance audit requirements, and early warning of user loss. Combining these factors is a strategy that ensures both the seriousness of the billing and the absence of push-off.