Communicating network information using universal resource locators

• US 6,385,615 B1
• Filed: 05/21/1999
• Issued: 05/07/2002
• Est. Priority Date: 05/21/1999
• Status: Expired due to Term

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Haeri, Arsalan, Soneson, Eric D.
• Primary Examiner(s): Mizrahi, Diane D.
• Application Number:
  US09/316,887
• Time in Patent Office: 1,082 Days
• Field of Search: 707/10, 709/218, 709/224, 709/225, 709/226, 709/227, 709/229, 709/239, 709/250, 709/238
• US Class Current: 1/1
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: Y10S 707/99931 Database or file accessing

Abstract

A method and apparatus are provided for communicating network information among network devices using protocols based on Universal Resource Locators. In one embodiment, an apparatus for retrieving RADIUS or SNMP information in a network, comprises a first URL interface executed by a client; a second URL interface executed by a server having a plurality of stored values; and means distributed among the first URL interface and the second URL interface for creating and storing a URL that includes an identifier of one or more of the stored values, retrieving that value from the server based on the identifier, and transporting the value from the server to the client. In another embodiment, a method comprises creating and storing a URL that includes a request for the value; communicating the URL to the server; extracting the request from the URL; and communicating a responsive URL, which includes the value of the attribute and an identifier of the attribute, from the server to the requesting client.

Claims

1. A method of retrieving a value of a RADIUS accounting attribute that is stored in a RADIUS server of a network, the method comprising:

creating and storing a Uniform Resource Locator (URL) that includes a request for a value of the RADIUS attribute;

wherein creating and storing a URL includes creating and storing the URL in the form;

radius[s];

//<

server-name>

;

port#>

/<

operation>

/<

radius payload>

wherein “

[s]”

identifies an optional parameter indicating that a secure connection is to be established, the value <

server-name>

identifies the RADIUS server, the value <

port#>

identifies a listening port number for a URL-based RADIUS process on the server, the value <

operation>

identifies an operation for the RADIUS server to carry out, and the value <

radius payload>

comprises a dictionary name and one or more attribute-value pairs,

communicating the URL to the RADIUS server;

extracting the request from the URL; and

communicating a responsive URL, which includes the value of the attribute and an identifier of the attribute, from the RADIUS server.

2. A method as recited in claim 1, wherein creating and storing a URL includes creating and storing the URL using a server identifier value that uniquely identifies the RADIUS server.

3. A method as recited in claim 1, wherein creating and storing a URL includes creating and storing the URL using a port identifier value that identifies a listening port of the RADIUS server at which the RADIUS server computer system receives client requests that comprise a URL containing a RADIUS protocol request.

4. A method as recited in claim 1, wherein creating and storing a URL includes creating and storing the URL using an operation value that identifies a RADIUS operation to be carried out by the RADIUS server in response to receiving the URL.

5. A method of processing a value of a RADIUS accounting attribute that is stored in a RADIUS server of a network, the method comprising:

executing a RADIUS agent and an interface software element at the managed device;

creating and storing a Uniform Resource Locator (URL) that comprises a request for the RADIUS accounting attribute at the client computer system, the request including information identifying the attribute and a type of processing to be carried out;

wherein creating and storing a URL includes creating and storing the URL in the form;

radius[s];

//<

server-name>

;

port#>

/<

operation>

/<

radius payload>

wherein “

[s]”

identifies an optional parameter indicating that a secure connection is to be established, the value <

server-name>

identifies the RADIUS server, the value <

port#>

identifies a listening port number for a URL-based RADIUS process on the server, the value <

operation>

identifies an operation for the RADIUS server to carry out, and the value <

radius payload>

comprises a dictionary name and one or more attribute-value pairs,

processing the request based on the type to result in the value of the attribute; and

communicating the value of the attribute to the managed device in a responsive URL.

6. A method as recited in claim 5, wherein creating and storing a URL includes creating and storing the URL using a server identifier value that uniquely identifies the RADIUS server.

7. A method as recited in claim 5, wherein creating and storing a URL includes creating and storing the URL using a port identifier value that identifies a listening port of the RADIUS server at which the RADIUS server computer system receives client requests that comprise a URL containing a RADIUS protocol request.

8. A method as recited in claim 5, wherein creating and storing a URL includes creating and storing the URL using an operation value that identifies a RADIUS operation to be carried out by the RADIUS server in response to receiving the URL.

9. A method as recited in claim 5, wherein creating and storing a URL includes creating and storing the URL in the form:

radius[s];

//<

server-name>

;

<

port#>

/<

operation>

/<

radius payload>

wherein “

[s]”

identifies an optional parameter indicating that a secure connection is to be established, the value <

server-name>

identifies the RADIUS server, the value <

port#>

identifies a listening port number for a URL-based RADIUS process on the server, the value <

operation>

identifies an operation for the RADIUS server to carry out, and the value <

radius payload>

comprises a dictionary name and one or more attribute-value pairs.

10. Apparatus for retrieving RADIUS information in a network, comprising:

a first URL interface executed by a client;

a second URL interface executed by a RADIUS server having a plurality of stored RADIUS accounting attributes; and

means distributed among the first URL interface and the second URL interface for creating and storing a Uniform Resource Locator (URL) that includes an identifier of one or more RADIUS accounting attributes, retrieving a value for that RADIUS accounting attribute from the RADIUS server based on the identifier, and transporting the value from the server to the client, wherein creating and storing a URL includes creating and storing the URL in the form;

radius [s];

//<

server-name>

;

port#>

/<

operation>

/<

radius payload>

wherein “

[s]”

identifies an optional parameter indicating that a secure connection is to be established, the value <

server-name>

identifies the RADIUS server, the value <

port#>

identifies a listening port number for a URL-based RADIUS process on the server, the value <

operation>

identifies an operation for the RADIUS server to carry out, and the value <

radius payload>

comprises a dictionary name and one or more attribute-value pairs.

11. An apparatus as recited in claim 10, wherein the means for creating and storing a URL further includes means for creating and storing the URL using a server identifier value that uniquely identifies the RADIUS server.

12. An apparatus as recited in claim 10, wherein the means for creating and storing a URL includes means for creating and storing the URL using a port identifier value that identifies a listening port of the RADIUS server at which the RADIUS server computer system receives client requests that comprise a URL containing a RADIUS protocol request.

13. An apparatus as recited in claim 10, wherein the means for creating and storing a URL includes means for creating and storing the URL using an operation value that identifies a RADIUS operation to be carried out by the RADIUS server in response to receiving the URL.

14. A computer-readable medium carrying one or more sequences of instructions for retrieving a value of a RADIUS accounting attribute that is stored in a RADIUS server of a network, wherein execution of the one or more sequences of instructions by one or more processors causes the one or more processors to perform the steps of:

creating and storing a Uniform Resource Locator (URL) that includes a request for a value of the RADIUS attribute;

wherein creating and storing a URL includes creating and storing the URL in the form;

radius [s];

//<

server-name>

;

port#>

/<

operation>

/<

radius payload>

wherein “

[s]”

identifies an optional parameter indicating that a secure connection is to be established, the value <

server-name>

identifies the RADIUS server, the value <

port#>

identifies a listening port number for a URL-based RADIUS process on the server, the value <

operation>

identifies an operation for the RADIUS server to carry out, and the value <

radius payload>

comprises a dictionary name and one of more attribute-value pairs,

communicating the URL to the RADIUS server;

extracting the request from the URL; and

communicating a responsive URL, which includes the value of the attribute and an identifier of the attribute, from the RADIUS server.