Individual Equipment Approach¶
The main advantage of an individual customer equipment approach is that it allows the provider to create several components (even of different types) for one item of a customer equipment, and provide one service for all components simultaneously.
Scheme 12: Individual equipment approach
In general, the implementation is done in the following steps:
-
creating customer premises equipment, so that automatically (according to a specification) one component of CPE is created by default;
-
adding addresses for components of CPE;
-
adding bindings to the components of equipment, equipment itself, and network services.
Typically, the components of CPE get bindings like:
-
Connection management to the network service (firewall, shaper) in order to control the access parameters;
-
Network connection to a component of provider equipment (for example, to a switch port) for CPE identification by port and managing the access via the provider equipment.
Possible cases within implementation also include:
-
a customer, owning several items of CPE;
-
one CPE with several components;
-
a possible binding of a CPE component either to the provider equipment only, or to the network service only, or even no binding at all (if no management of CPE is required).
Example of Individual Equipment Approach¶
See the example below. The provider uses Ethernet and IPoE for the Internet access services. CPE authentication is done at the access control switch by combination: the provider equipment port, and the CPE IP and MAC addresses.
Scheme 13: Organizing IPoE access to the Internet
The customer owns CPE of а Workstation type with only one component of a Port type. In the system, the component has the IP and MAC addresses. It also gets the binding of the type Network connection to the access control switch port for authentication purposes, as well as the binding of the Access management type to the program firewall for the inbound and outbound bandwidth limitation.
For such product catalog entries as D-Link DES-3526 and Program firewall, events are customized using the abovementioned types of binding.

