Network device and method for updating data of the network device
Granted 4 Jun 2013 · 2 office actions
Assignee: Foxconn Technology Group
Law firm: Law firm · Log in to unlock
Attorney: Attorney · Log in to unlock
Inventors: Yen-Chen Lu, Chih-Yuan Huang · Examiner: Uyen Le · AU 2157 · TC 2100
Life of the application
10 dated eventsAbstract
A network device and method for updating parameters of the network device provides an object adapting interface. The object adapting interface generates a service access interface and a configuration adapting interface. A management agent of the network device sends a requirement command. If the requirement command is a write command, the configuration adapting interface updates configuration parameters of the management agent stored in a configuration database of the network device. If the requirement command is a read command, the service access interface reads configuration parameters stored in the management agent.
Description
4 parts›BACKGROUND
1. Technical Field
Embodiments of the present disclosure relate to methods for data management of network devices, and more particularly, to a network device and a method for updating data of the network device.
2. Description of Related Art
A network device may include a management agent and at least a service agent. A configuration database (CDB) is required for storing configuration parameters of the service agent. If the configuration parameters need to be accessed, two methods are provided at present. The first method is for the management agent to call application interfaces of the service agent to access the configuration parameters. The management agent has to control communication with the service agent and the CDB. The second method is that each service agent should maintain its own configuration database. If the configuration parameters are modified, and the management agent or the service agent has not been updated in time, errors may occur to the network device.
›BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram of one embodiment of a network device.
FIG. 2 is a block diagram of one embodiment of the object adapting interface in FIG. 1 .
FIG. 3 is a flowchart of one embodiment of a method for updating data of the network device.
FIG. 4 is a flowchart of one embodiment of detailed description of block S 33 of FIG. 3 .
›DETAILED DESCRIPTION · 1 of 2
The disclosure is illustrated by way of examples and not by way of limitation in the fingers of the accompanying drawings in which like references indicate similar elements. It should be noted that references to “an” or “one” embodiment in this disclosure are not necessarily to the same embodiment, and such references mean at least one.
In general, the word “module,” as used hereinafter, refers to logic embodied in hardware or firmware, or to a collection of software instructions, written in a programming language, such as, for example, Java, C, or assembly. One or more software instructions in the modules may be embedded in firmware. It will be appreciated that modules may comprised connected logic units, such as gates and flip-flops, and may comprise programmable units, such as programmable gate arrays or processors. The modules described herein may be implemented as either software and/or hardware modules and may be stored in any type of computer-readable medium or other computer storage device.
FIG. 1 is a block diagram of one embodiment of a network device 1 . In one embodiment, the network device 1 includes a management agent (MA) 10 , a service agent (SA) 11 , an object adapting interface 12 , a configuration database (CDB) 13 , a processor 14 , and a storage system 15 . A MA 10 is a software agent that runs on the network device 1 and provides an interface to manage the network device 1 . The interface is provided for setting parameters of the network device 1 . In one embodiment, the parameters may be firewall parameters. The MA 10 may be, for example, a MS DOS command prompt for inputting commands. The SA 12 is a software agent that runs on the network device 1 and receives parameters set on the MA 10 . The SA 12 may be a firewall of the network device 1 .
The object adapting interface 12 is an interface provided for the MA 10 to communicate with the SA 11 and the CBD 13 . The CBD 13 stores a configuration file of the SA 11 . The configuration file stores configuration parameters of the SA 11 set by a user. The configuration parameters are persistent data. In some embodiments, the configuration parameters may include a name, a data type, user authority of the SA 11 . If the user has set the configuration parameters on the MA 10 , the SA 11 generates a service access interface 120 and a configuration adapting interface 121 in the object adapting interface 12 . The service access interface 120 and the configuration adapting interface 121 are software programs. The service access interface 120 accesses the SA 11 and reads data from the SA 11 or writes data to the SA 11 . The configuration adapting interface 121 updates configuration parameters of SA 11 in the CBD 13 .
The SA 11 also stores the configuration parameters of the SA 11 . The configuration parameters stored in the SA 11 are non-persistent data.
The object adapting interface 12 includes a number of function modules (illustrated in FIG. 2 ). The function modules may comprise computerized code in the form of one or more programs that are stored in the storage device 15 . The computerized code includes instructions that are executed by the processor 14 , to provide one or more aforementioned operations of the object adapting interface 12 .
As shown in FIG. 2 , the object adapting interface 12 may include a receiving module 122 , a calling module 123 , a detection module 124 , and a control module 125 .
The receiving module 122 receives a requirement command from the MA 10 . The requirement command may be a read command or a write command including data to be written. In some embodiments, the requirement command may be to read configuration parameters of the SA 11 or to update the configuration parameters.
The calling module 123 calls the service access interface 120 and the configuration adapting interface 121 .
The detection module 124 detects if the requirement command is a read command or a write command.
If the requirement command is a write command, the control module 125 controls the configuration adapting interface 121 to update the configuration parameters stored in the CBD 13 using the data included in the write command. In some embodiments, the configuration adapting interface 121 locks the CBD 13 and detects if the data included in the write command is persistent data. If the data is persistent data, the configuration adapting interface 121 updates the configuration parameters stored in the CBD 13 using the data. Then, the configuration adapting interface 121 unlocks the CBD 13 . If the data included in the write command is non-persistent data, the configuration adapting interface 121 unlocks the CBD 13 . In some embodiments, if the CBD 13 is locked, the user or some applications cannot access the CBD 13 . If the locked CBD 13 is unlocked, the user and applications can access the CBD 13 .
The control module 125 controls the service access interface 120 to access the configuration parameters stored in the SA 11 and executes the configuration parameters stored in the SA 11 . In some embodiments, if the requirement command is the write command, the control module 125 controls the service access interface 121 to update the configuration parameters stored in the SA 11 . If the requirement command is the read command, the control module 125 controls the service access interface 121 to read the configuration parameters stored in the SA 11 .
FIG. 3 is a flowchart of one embodiment of a method for updating data of the network device 1 . Depending on the embodiment, additional blocks may be added, others removed, and the ordering of the blocks may be changed.
In block S 30 , the receiving module 122 receives a requirement command from the MA 10 . The requirement command may be a read command or a write command including data to be written.
In block S 31 , the calling module 123 calls the configuration adapting interface 121 .
In block S 32 , the detection module 124 detects if the requirement command is the read command or the write command. If the requirement command is the write command, block S 33 is implemented. If the requirement command is the read command, block S 34 is implemented.
›DETAILED DESCRIPTION · 2 of 2
In block S 33 , the control module 125 controls the configuration adapting interface 121 to update the configuration parameters stored in the CBD 13 using the data included in the write command.
In block S 34 , the calling module 123 calls the service access interface 120 . The control module 125 controls the service access interface 120 to access the configuration parameters stored in the SA 11 and executes the configuration parameters stored in the SA 11 .
FIG. 4 is a flowchart of one embodiment of detailed description of block S 33 of FIG. 3 . Depending on the embodiment, additional blocks may be added, others removed, and the ordering of the blocks may be changed.
In block S 330 , the configuration adapting interface 121 locks the CBD 13 . If the CBD 13 is locked, the configuration parameters stored in the CBD 13 cannot be accessed by the user.
In block S 331 , the configuration adapting interface 121 detects if the data included in the write command is persistent data. If the data is persistent data, block S 332 is implemented. If the data is non-persistent data, block S 333 is implemented.
In block S 332 , the configuration parameters of the SA 11 stored in the CBD 13 are updated using the data included in the write command.
In block S 333 , the locked CBD 13 is unlocked.
Although certain inventive embodiments of the present disclosure have been specifically described, the present disclosure is not to be construed as being limited thereto. Various changes or modifications may be made to the present disclosure without departing from the scope and spirit of the present disclosure.
Claims as granted
9 claimsLog in to read the claims of this application.
Log in to unlockClassifications
3 codes- G06F17/00
- G06F7/00
Claim changes
SoonSee which claims were amended, added or cancelled during examination, with every added and removed word marked.
The published claims of this application are not paired with the granted ones in what we hold.
File wrapper
See the full prosecution history — every USPTO and applicant action on this file, in order.
Log in to unlockDocuments
Log in to open the documents of this file: the application as filed, every office action and response, the notice of allowance.
Log in to unlockChain of title
See the full assignment history — every owner this patent has passed through, with recordation dates and reel/frame numbers.
Log in to unlock