The campus network Authentication & Billing system, which is to connect three operators, appears to be a few lines in the PPT that actually run for at least two months of prepreparation cycles. If the project plan gives the docking only two weeks, then it's basically possible to say that it's true.——Either you're rushing on, or you're compromisein', or you're missing a lot of the actual required networking work in the scheme.And it's not a shock, but an experience of projects stepping on.
The most time-consuming link for operators is not technology realization, but ratherCommunication coordination and process approvalThe school wants to use the connection of the Brass, which requires approval from at least three levels of the Connect City company Ministry of Political Affairs, Network Department, and Provincial Corporate Cyber Transport Centre. Each level has a one-to-two-week process cycle, which is more than a month away. This is just an approval, not a technical interface time. If the school is to be connected to three operators at the same time, this process will have to go separately with the three others.——There is no uniform time line between the three, and it is likely that the move has been cleared and the telecommunications side is just starting to follow.
The same technical interface is not simple. Operator BRAS has to configure a new RADIS client and dial-up pool, which are high risk changes in the operator's network-based protocol.——It must be implemented in the morning window, before it is approved for change, will have an impact assessment of operations and will prepare a rollback program. A BRAS configuration window may last only two nights a month, or two weeks if the first change fails. So this is just a technical connection.I'm optimistic that we'll have to set aside three or four rounds of window time.And, with the time between rounds and windows, the actual cycle can easily be extended to four to six weeks.
The most easy pit to step on during the docking isSyntax alignment of RADIUS properties fields. The standard RADIUS protocol defines dozens of attribute fields, but each operator has its own agreement in actual use——What attributes are required to fill out, which properties are optional, and what is the coding format for attribute values and range of values. For example, NAS-Port-Type, a feature that some operators require to fill in 15 (Ethernet), or require that they be filled according to the actual type of access. For example, Calling-Station-Id (custody identification), defined as the standard MAC address format (AAA-BB-CC-DD-EE-FF), but some operators receive BRAS in a case-by-case nonseparation (AABBCCDDEFF)."Sometimes certification works and sometimes fails."The weird question.——Because a format mismatch is triggered only on the end of a particular manufacturer, model.
The second technical difficulty isManage and synchronize dial-up poolUnder the proxy mode, the operating chambers allocate to schools a number of dialling accounts (e.g. 10,000 home-based wide accounts), and the school dialing gateways take an empty account from the pool when the user is certified. But there are a series of boundary situations: what if the account in the pool is run out? What if an account is shut down on the operator because it is owed or abnormally?"Zombie account number."What do we do? These questions require dialing the gateway with a sound accounting pool management logic.——These include account health tests (dial-based testing of the number in the pool on a regular basis), automatic recovery (automatic release of account numbers when dialing is time-consuming or abnormally disconnected) and capacity alerts (automatic notification to administrator for expansion if the remaining account number in the pool is below threshold).
The third technical question is...Delays in accessing resources at schools by cross-operatorsThe Internet traffic of students in the proxy mode is exported by operators, but the school resources (library database, teaching system, selection system) are accessed via the campus network. This involves one."Flow Diversion"Problems——Authentication & Billing requires that the target IPs be correctly differentiated when sending user privileges. If the diversion strategy is wrong, students visit and return through operators' exports in a large circle, delays can surge from dozens of milliseconds to hundreds of milliseconds. For such highly sensitive applications as the system for lessons selection, this delay difference is enough to trigger."The school robbery failed."(c) Complaints.
There is also a point where many projects were overlooked in the previous period:Operator-side business support capacity. The first complaint is usually not a operator, but a school information centre. But the Information Centre has no power over the operator’s side of the problem.——They can't see the operator BRAS logs, nor have they been given permission to modify the operator's configuration. This requires that the interface process be clear with the operator and respond to SLA. If this collaboration mechanism is not established, the clearing house becomes online."Crackers."——Students complain about the school, the school calls to operators, the operator returns slowly and students continue to abuse the school.
So back to the title: Why would a docking program need to be prepared two months in advance?At least one month spent on communication coordination and process clearance, with the remaining month divided into multiple rounds of technical interfaces to complete actual docking tests. This is not about the efficiency of one party, but about the rhythm inherent in multi-organization collaboration projects. If project time is really short, then it's about to go online with another operator and then to go through the other operators.——However, this strategy must be clear at the start of the project, and it cannot be discovered that there is insufficient time until the implementation phase and then temporarily shatting.