Abstract: A network management system includes a plurality of server units. A first management server included in a first server unit transmits a disconnection setting request for disconnecting an abnormal flow to each of a communication node connected to a self-region covered by the first management server, and one or more second server units covering one or more primary adjacent regions adjacent to the self-region. Disconnection setting is executed in response to the disconnection setting request. Each of a plurality of regions includes two or more areas each of which is covered by corresponding one of two or more base stations connected to an identical communication node.

Abstract: A network management system includes a plurality of server units. A first management server included in a first server unit transmits a disconnection setting request for disconnecting an abnormal flow to each of a communication node connected to a self-region covered by the first management server, and one or more second server units covering one or more primary adjacent regions adjacent to the self-region. Disconnection setting is executed in response to the disconnection setting request. Each of a plurality of regions includes two or more areas each of which is covered by corresponding one of two or more base stations connected to an identical communication node.

Abstract: In a general connection service using the PPPoE protocol, since user determination cannot be performed before a PPP authentication phase, even when a connection request is received from an invalid user, an access server and an authentication server operate under loaded conditions. Accordingly, an invalid user list is held in the access server, and user information is added to a PADI packet. In this arrangement, an invalid user can be determined at early stages and the packet can be deleted, thereby the load can be reduced. Further, regarding the invalid user, pseudo-connection completion is made and an occurrence of retry is prevented, thereby the load can be reduced.

Abstract: A listening-or-viewing charge is differentiated with bit rates depending on distributed programs. A broadband access server for holding user channels by PPP and replicating and transferring multicast packets have a counter for counting the number of distributed multicast packets and the number of distributed bytes at each multicast group address. The counter values (byte counts and packet counts) when a user joins a multicast group and when the user leaves the multicast group and a multicast session ID containing a PPP user ID and a multicast group address are sent to a multicast accounting radius server. The multicast accounting server provides an accounting on a basis of the byte counts, the packet counts, or a bit rate.

Abstract: A packet transfer apparatus has a controller for controlling transmission of a PADO packet on the basis of the information that is previously set in the packet transfer apparatus in order that the PADO packet can be transmitted back to the terminals or a PADI can be discarded when the PADI packet sent from the terminals to the packet transfer apparatus does not have any Service-Name specified. In addition, another controller is used. This controller is provided so that, when a Service-Name that indicates the type of an offered communication service is specified in the PADI packet, it can judge whether the Service-Name is previously registered in a memory and decide to transmit the PADO packet to the terminal if the Service-Name is previously registered, but to discard the PADI packet if the Service-Name is not registered.

Abstract: A listening-or-viewing charge is differentiated with bit rates depending on distributed programs. A broadband access server for holding user channels by PPP and replicating and transferring multicast packets have a counter for counting the number of distributed multicast packets and the number of distributed bytes at each multicast group address. The counter values (byte counts and packet counts) when a user joins a multicast group and when the user leaves the multicast group and a multicast session ID containing a PPP user ID and a multicast group address are sent to a multicast accounting radius server. The multicast accounting server provides an accounting on a basis of the byte counts, the packet counts, or a bit rate.

Abstract: A listening-or-viewing charge is differentiated with bit rates depending on distributed programs. A broadband access server for holding user channels by PPP and replicating and transferring multicast packets have a counter for counting the number of distributed multicast packets and the number of distributed bytes at each multicast group address. The counter values (byte counts and packet counts) when a user joins a multicast group and when the user leaves the multicast group and a multicast session ID containing a PPP user ID and a multicast group address are sent to a multicast accounting radius server. The multicast accounting server provides an accounting on a basis of the byte counts, the packet counts, or a bit rate.

Abstract: A packet transfer apparatus has a controller for controlling transmission of a PADO packet on the basis of the information that is previously set in the packet transfer apparatus in order that the PADO packet can be transmitted back to the terminals or a PADI can be discarded when the PADI packet sent from the terminals to the packet transfer apparatus does not have any Service-Name specified. In addition, another controller is used. This controller is provided so that, when a Service-Name that indicates the type of an offered communication service is specified in the PADI packet, it can judge whether the Service-Name is previously registered in a memory and decide to transmit the PADO packet to the terminal if the Service-Name is previously registered, but to discard the PADI packet if the Service-Name is not registered.

Abstract: A listening-or-viewing charge is differentiated with bit rates depending on distributed programs. A broadband access server for holding user channels by PPP and replicating and transferring multicast packets have a counter for counting the number of distributed multicast packets and the number of distributed bytes at each multicast group address. The counter values (byte counts and packet counts) when a user joins a multicast group and when the user leaves the multicast group and a multicast session ID containing a PPP user ID and a multicast group address are sent to a multicast accounting radius server. The multicast accounting server provides an accounting on a basis of the byte counts, the packet counts, or a bit rate.