A service implementation method and device based on private attributes of third-party equipment

Abstract

The invention discloses a service implementation method and device based on a private attribute of third-party equipment. The method comprises the following steps of: configuring a corresponding relation of an IP (internet protocol) address of the third-party equipment and an equipment manufacturer to which the equipment belongs on an authentication server, configuring the analysis rule of the private attribute of the equipment manufacturer and configuring a releasing strategy of the private attribute of the third-party equipment; when the authentication server receives an access request message of the third-party equipment, determining the equipment manufacturer to which the equipment belongs according to the IP address of the third-party equipment, analyzing the private attribute information carried in the message according to the analysis rule of the private attribute of the equipment manufacturer and carrying out corresponding processing according to the analyzed private attribute information; and when the authentication server returns an access response message to the third-party equipment, determining the private attribute value needing to be released according to the releasing strategy of the private attribute of the third-party equipment and sending the carried access response message to the third-party equipment. According to the service implementation method and device provided by the invention, the self-adaptive processing for the private attribute of the third-party equipment can be realized on the basis of a configuration mode.

Description

technical field [0001] The present invention relates to the field of communication technology, in particular to a method and device for realizing a service based on private attributes of third-party equipment. Background technique [0002] RADIUS (Remote Authentication Dial In User Service, Remote Authentication Dial In User Service) is a protocol that carries authentication, authorization, accounting and configuration information between network access devices and authentication servers. In order to support scalability, the RADIUS protocol defines a Vendor-Specific (vendor-specific) attribute (attribute number 26), which allows vendors to support their extended attributes. These attributes are not for general purposes, and it must not (MUST not) affect Operation of RADIUS protocol. If the RADIUS server cannot parse the vendor private information sent by the client, the RADIUS server must (MUST) ignore this attribute (but can point it out), if the client does not receive th...

AI Technical Summary

Problems solved by technology

[0006] Since the Vendor-Specific attributes of third-party manufacturers are generally not disclosed to the public, and the access devices are uncertain, and the Vendor-Specific attribute protocols of third-party manufacturers may change, it is obviously very inflexible to fix them in the program

In addition, the above solution can only deliver a specific value to the access device and cannot adapt to the user's final networking environment

It can be seen that the existing technology cannot fundamentally support the Vendor-Specific attributes of third-party vendors

Images