WO2012083631A1

WO2012083631A1 - Method for managing device parameters of radio frequency identification (rfid) system and rfid system

Info

Publication number: WO2012083631A1
Application number: PCT/CN2011/074176
Authority: WO
Inventors: 陈金茹; 张金海
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-12-21
Filing date: 2011-05-17
Publication date: 2012-06-28
Also published as: CN102063655A

Abstract

A method for managing device parameters of a Radio Frequency Identification (RFID) system and an RFID system are disclosed. The method includes: the type information of devices is acquired by the RFID system; the actual model classes corresponding to the type information of devices are acquired from the prestored corresponding relationship between the types and the actual model classes by the RFID system; the device parameters of devices input by users are stored by the RFID system according to the actual model classes corresponding to the devices; when the device parameters of devices need to be managed, the actual models are generated by the RFID system according to the stored device parameters of devices. The effect of simplifying the process of the RFID system managing the devices is achieved.

Description

Device parameter management method and RFID system for RFID system

The present invention relates to the field of communications, and in particular to a device parameter management method and an RFID system for a radio frequency identification (JD) system. Background technique

In the RFID application system, there are many types of equipment to be maintained, and the models of different manufacturers are very numerous. Moreover, in the actual integration process, the selection of equipment is often later in time. For the same system, different users may also select devices from different manufacturers, and their device parameters are different.

In the past application development, each new type of equipment was introduced, and a series of operations such as designing the model object, writing the database design, modeling the database, and designing the database operation interface, etc., were performed to realize the new equipment. Management of parameters.

In the case where the device type model is relatively fixed, the above method is not problematic. However, as mentioned above, in practical applications, especially in the aspect of intelligent transportation, the model selection of the device is changed frequently. If the steps of the above application development are repeated for each new one, the code development amount is relatively large, At the same time, it involves changes in the presentation layer, business layer and persistence layer, and the development work is cumbersome. Summary of the invention

SUMMARY OF THE INVENTION A primary object of the present invention is to provide a device parameter management scheme for an RFID system to address at least the above problems.

According to an aspect of the present invention, a device parameter management method for an RFID system is provided, including: an RFID system acquiring model information of a device; and an RFID system acquiring model information of the device from a correspondence between a pre-stored model and an actual model class. Corresponding actual model class; the RFID system stores the device parameters of the device input by the user according to the actual model class corresponding to the device; when the device parameter of the device needs to be managed, the RFID system generates the actual device according to the device parameter of the stored device. model.

Preferably, before the RFID system obtains the actual model class corresponding to the model of the device from the correspondence between the pre-stored model and the actual model class, the method further includes: the RFID system receiving the model information of the device input by the user; the RFID system receiving The correspondence between the model information input by the user and the actual model class; the RFID system saves the correspondence in the database.

Preferably, the RFID system receives the correspondence between the model information input by the user and the actual model class, including: the RFID system acquires an unused actual model type; the RFID system numbers the attributes of the unused actual model types and displays them to the user; The system receives instructions from the user, deletes the attributes that are not needed in the attributes of the actual model type that are not used, and maps the remaining attributes to the model information.

Preferably, the RFID system obtains unused actual model types including: the RFID system queries subclasses of all device abstract classes; the RFID system prompts the user to select all of the subclasses of all device abstract classes that have been configured The model class; the RFID system removes subclasses of the already configured model classes from subclasses of all device abstract classes.

Preferably, the RFID system stores the device parameters of the device input by the user according to the actual model class corresponding to the device, including: the device maintenance interface of the actual model class corresponding to the RFID system generation device; and the RFID system stores the device input by the user on the device maintenance interface. Device parameters.

Preferably, the device maintenance interface of the actual model class corresponding to the RFID system generating device comprises: the RFID system uses a reflection mechanism to obtain each attribute type in the actual model class; the RFID system generates an edit control of the actual model class corresponding to the device according to each attribute type; The system calls the device parameter maintenance interface template, and all the controls are laid out to generate a device maintenance interface.

Preferably, the RFID system generates an edit control of the actual model class corresponding to the device according to each attribute type, including: if the attribute type is a numeric type or a string type attribute, the RFID system generates a text edit box; if the attribute type is a Boolean type attribute, The RFID system generates a radio edit box; if the attribute type is a date type attribute, the RFID system generates a date edit box.

Preferably, after the RFID system stores the device parameters of the device according to the actual model class corresponding to the device, the method includes at least one of the following: the RFID system adds parameter information of the new device according to the operation of the user; the RFID system is operated according to the user. Modify the parameter information of the device; the RFID system queries the parameter information of the device according to the operation of the user; the RFID system deletes the parameter information of the device according to the operation of the user.

Preferably, the RFID system adds the parameter information of the new device according to the operation of the user, including: the RFID system prompts the user to select the model of the device; the RFID system displays the device maintenance interface of the actual model type corresponding to the model according to the model; the RFID system receives the user in the device Maintain the device parameter information filled in the interface and store the parameter information in the database.

Preferably, the RFID system queries the parameter information of the device according to the operation of the user, the RFID system determines the device to be queried according to the operation of the user, and the RFID system obtains the parameter information of the device to be queried, and obtains the parameter information of the device to be queried according to the model information of the device to be queried. The actual model class corresponding to the device to be queried; the RFID system converts the parameter information of the device to be queried into the actual model of the device to be queried according to the actual model class corresponding to the device to be queried, and returns the actual model object to the user.

Preferably, the RFID system converts the parameter information of the device to be queried into an actual model of the device to be queried: the RFID system creates an instance of the actual model; the RFID system acquires the attribute of the stored parameter information of the device to be queried; the RFID system is to be The attribute of the parameter information of the queried device is converted into the type of the corresponding attribute in the actual model; the RFID system assigns the converted attribute value to the corresponding attribute of the instance of the actual model;

The RFID system returns an instance of the actual model.

Preferably, the RFID system converts the attribute of the parameter information of the device to be queried into the type of the corresponding attribute in the actual model, including: if the attribute type is a digital type, the RFID system calls the PAS parse method of the digital type to correspond to the attribute of the standard model. Converted to the type of the corresponding attribute in the actual model; if the attribute type is Boolean, the RFID system calls the parse method of the Boolean type to convert the attribute of the corresponding standard model into the type of the corresponding attribute in the actual model; if the attribute type is a date type, RFID system Use the calendar method of Calendar to convert the attributes of the corresponding standard model into the types of corresponding attributes in the actual model.

Preferably, the RFID system assigns the converted attribute value to the corresponding attribute of the instance of the actual model, including: the RFID system acquires the assignment method name of the corresponding attribute; the RFID system obtains the assignment method of the corresponding attribute according to the method name; the RFID system converts the converted value The attribute value is used as a method parameter to perform an assignment method.

Preferably, the number of device parameters of the device does not exceed a predetermined threshold.

Preferably, the type of device parameter of the device is a single type.

According to another aspect of the present invention, an RFID system is provided, including: a first acquisition module configured to acquire model information of a device; and a second acquisition module configured to be in a correspondence relationship between a pre-stored model and an actual model class Obtaining an actual model class corresponding to the model information of the device; the storage module is configured to store, according to the actual model class corresponding to the device, a device parameter of the device input by the user; and generating a module, configured to When the device parameters of the device are managed, an actual model of the device is generated according to the stored device parameters of the device.

Through the present invention, the corresponding relationship between the model of the system storage device and the actual model class is adopted, and the device parameters of the corresponding storage device are used to generate the actual model, and the process of managing the device parameters of the RFID system in the related art is complicated. The problem, in turn, achieves the effect of the process of managing the RFID system management device. DRAWINGS

The drawings are intended to provide a further understanding of the present invention, and are intended to be a part of the present invention, and the description of the present invention is not intended to limit the invention. In the drawing:

1 is a flowchart of a device parameter management method of an RFID system according to an embodiment of the present invention; FIG. 2 is a structural block diagram of a parameter configuration management scheme system according to an embodiment of the present invention;

3 is a schematic diagram of a standard data model in accordance with an embodiment of the present invention;

4 is a flow chart of a new device model according to an embodiment of the present invention;

FIG. 5 is a flowchart of generating a new device parameter maintenance interface according to an embodiment of the present invention; FIG.

6 is a flowchart of device information query according to an embodiment of the present invention;

7 is a flow chart of converting a standard data model into an actual data model according to an embodiment of the present invention; FIG. 8 is a flowchart of a model class attribute type conversion according to an embodiment of the present invention;

Figure 9 is a block diagram showing the structure of an RFID system according to an embodiment of the present invention. detailed description

The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that, in the case of non-conflict, the features in the embodiments and the embodiments in the present application may be combined with each other.

Embodiment 1 An embodiment of the present invention provides a device parameter management method for an RFID system. FIG. 1 is a flowchart of a device parameter management method for an RFID system according to an embodiment of the present invention. As shown in FIG. 1, the method includes: Step S102, The RFID system acquires model information of the device;

Step S104: The RFID system acquires an actual model class corresponding to the model information of the device from a correspondence between the pre-stored model and the actual model class;

Step S106: The RFID system stores the device parameters of the device input by the user according to the actual model class corresponding to the device.

Step S108: When the device parameters of the device need to be managed, the RFID system generates an actual model of the device according to the device parameters of the stored device.

In this embodiment, the correspondence between the model of the RFID system storage device and the actual model class, and the device parameters of the storage device according to the corresponding relationship, thereby generating an actual model when needed, thereby completing the process of managing the device by the RFID system .

Wherein, the number of device parameters does not exceed a predetermined threshold; the type of the device parameter is a single type (for example, a numeric type, a boolean type, or a date type).

In a preferred embodiment of the embodiment of the present invention, the RFID system can receive the model information of the device input by the user before the RFID system obtains the actual model class corresponding to the model of the device from the correspondence between the pre-stored model and the actual model class. And receiving the correspondence between the model information input by the user and the actual model class, and then the RFID system saves the correspondence in the database.

The RFID system receiving the correspondence between the model information input by the user and the actual model class may include: the RFID system acquires an unused actual model type, and numbers the attributes of the unused actual model type, and then displays the information to the user; The system receives instructions from the user, deletes the attributes that are not needed in the attributes of the actual model type that are not used, and maps the remaining attributes to the model information.

Preferably, the RFID system acquiring unused actual model types may include: the RFID system queries subclasses of all device abstract classes, and prompts the user to select all configured model classes in all subclasses of the device abstract class, and then, the RFID system Deletes a subclass of the already configured model class in a subclass of all device abstract classes, and the rest is the actual model type that is not used.

In another preferred embodiment of the embodiment of the present invention, the RFID system stores the device parameters of the device input by the user according to the actual model class corresponding to the device, and may include: an actual model class device maintenance interface corresponding to the RFID system generation device; and then, the RFID system The system stores the device parameters of the device that the user inputs on the device maintenance interface.

The device maintenance interface of the actual model class corresponding to the RFID system generating device may include: the RFID system uses a reflection mechanism to obtain each attribute type in the actual model class; the RFID system generates an edit control of the actual model class corresponding to the device according to each attribute type; The system calls the device parameter maintenance interface template, and all the controls are laid out to generate a device maintenance interface.

Preferably, the RFID system generates an edit control of the actual model class corresponding to the device according to each attribute type, and may include: if the attribute type is a numeric type or a string type attribute, the RFID system generates a text code If the attribute type is a Boolean type attribute, the RFID system generates a radio edit box; if the attribute type is a date type attribute, the RFID system generates a date edit box.

In still another preferred embodiment of the embodiment of the present invention, after the RFID system stores the device parameters of the device according to the actual model class corresponding to the device, the following steps may be performed: The RFID system adds parameters of the new device according to the operation of the user. The RFID system modifies the parameter information of the device according to the operation of the user; the RFID system queries the parameter information of the device according to the operation of the user; the RFID system deletes the parameter information of the device according to the operation of the user.

The RFID system adds the parameter information of the new device according to the operation of the user, and may include: the RFID system prompts the user to select the model of the device; the RFID system displays the device maintenance interface of the actual model type according to the model; the RFID system receives the user in the device. Maintain the device parameter information filled in the interface and store the parameter information in the database.

In a further preferred embodiment of the embodiment of the present invention, the parameter information of the querying device may be: the RFID system determines the device to be queried according to the operation of the user, and the RFID system obtains the parameter information of the device to be queried according to the operation of the user. And obtaining the actual model class corresponding to the device to be queried according to the model information of the device to be queried; the RFID system converts the parameter information of the device to be queried into the actual model of the device to be queried according to the actual model class corresponding to the device to be queried. The actual model object is returned to the user.

The RFID system converts the parameter information of the device to be queried into the actual model of the device to be queried, which may include: the RFID system creates an instance of the actual model, and obtains the attribute of the stored parameter information of the device to be queried; the RFID system will query The attribute of the parameter information of the device is converted into the type of the corresponding attribute in the actual model; the RFID system assigns the converted attribute value to the corresponding attribute of the instance of the actual model; the RFID system returns an instance of the actual model.

Preferably, the RFID system converts the attribute of the parameter information of the device to be queried into the type of the corresponding attribute in the actual model, which may include: if the attribute type is a digital type, the RFID system calls the digital type of the parse method to correspond to the standard The attribute of the model is converted into the type of the corresponding attribute in the actual model; if the attribute type is a Boolean type, the RFID system calls the parse method of the Boolean type to convert the attribute of the corresponding standard model into the type of the corresponding attribute in the actual model; if the attribute type is The date type, the RFID system calls the calendar method to convert the attributes of the corresponding standard model into the types of corresponding attributes in the actual model.

Preferably, the RFID system assigns the converted attribute value to the corresponding attribute of the instance of the actual model, which may include: the RFID system acquires the assignment method name of the corresponding attribute, and obtains the assignment method of the corresponding attribute according to the method name, and then the RFID system converts The attribute value after the execution as the method parameter performs the assignment method.

Embodiment 2

This embodiment proposes a general solution for device parameter management. The system maintains the correspondence between each type of equipment of each type and the equipment model class, and manages the equipment parameters persistently with a unified standard data model. After the user submits the parameter changes in the standard model, the system transforms the actual model into a standard model; when the user requests parameter management, the system converts the unified standard model into the actual device model. Application system The managed device has a new type of device introduced. It only needs to add a single model class of the device, and configure the properties of the device model. The other related codes are not changed, and the management of the new device parameters can be completed.

The number of device parameters needs to be set to the upper limit. The device parameter type can be a cartridge type.

Further, the method described in this embodiment includes the following steps:

(1) The system maintains the correspondence between each type of equipment of each type and the equipment model class;

(2) User management device parameters.

Further, the system maintains the correspondence between each type of manufacturer equipment and the equipment model class of each type, including the following steps:

(1) The model class for the developer to write a new model device;

(2) The developer fills in the new model information, including the corresponding model class name and its parameter attribute information;

(3) The system persists the correspondence (for example, in a database);

(4) The system generates the device maintenance interface of the model.

Further, the user management device parameters include the following steps:

(1) The user adds new device information;

(2) The user modifies the device information;

(3) The user queries the device information;

(4) The user deletes the device information.

Further, the developer fills in the new model information, including the corresponding model class name and its parameter attribute information, including the following steps:

(1) The user fills in the basic information of the model;

(2) The system queries all unused actual device model classes;

(3) The user selects a device model class corresponding to the model;

(4) The system displays all attribute numbers of the selected model class to the interface;

(5) The user deletes the attributes that do not need to be configured;

(6) The user adds a label to each attribute;

(7) The model information is completed.

Further, the system queries all unused actual device model classes including the following steps:

(1) The system queries subclasses of all device abstract classes;

(2) The user queries all the model classes that have been configured;

(3) The system rejects the subclasses of the configured models.

Further, the device maintenance interface that the system generates the model includes the following steps:

(1) The system obtains each attribute type in the model class by using a reflection mechanism;

(2) The system generates a corresponding edit control according to each attribute type;

(3) The system selects the corresponding data verification specification according to each attribute type;

(4) Corresponding to the attribute description of the actual model attribute and the attribute corresponding control;

(5) The system calls the device parameter maintenance interface template;

(6) The system lays out all the controls and generates an editing interface (ie, device maintenance interface). Further, the user adds new device information including the following steps:

(1) The type and model of the device selected by the user;

(2) The system calls up the corresponding maintenance interface according to the model;

(3) The user fills in the device parameter information;

(4) The system persists the parameter information as a standard data model.

Further, the user querying the device information includes the following steps:

(1) The user selects the device to be queried;

(2) The system queries the standard model information of the device;

(3) The system queries the model class corresponding to the device according to the model information;

(4) The system converts the standard model into the actual model of the device;

(5) The system returns the actual model object to the user.

Further, the system generates a corresponding edit control according to each attribute type, including the following steps:

(1) If it is a numeric type or a string type attribute, select a text edit box;

(2) If it is a Boolean type attribute, select the radio edit box;

(3) If it is a date type attribute, select the date edit box.

Further, the system converts the standard model into the actual model of the device, including the following steps:

(1) The system creates an instance of the actual model class;

(2) The system extracts the attributes in the standard model corresponding to each attribute in the actual model class;

(3) The system converts the attributes of the standard model into the types of corresponding attributes of the actual model class;

(4) The system assigns the converted attribute value to the corresponding attribute of the actual model instance;

(5) The system returns an instance of the actual model.

Further, the system converts the attributes of the standard model into the types of the corresponding attributes of the actual model class, as follows:

(1) If the attribute is a numeric type, the parse method of the numeric type is called for conversion; (2) If the attribute is a boolean type, the parse method of the boolean type is called for conversion;

(3) If the attribute is a date type, the method of calling Calendar is used to generate an instance of the date type. Further, the system assigns the converted attribute value to the corresponding attribute of the actual model instance, and the following steps are included:

(1) The system obtains the assignment method name of the attribute;

(2) The system obtains the assignment method of the attribute according to the method name;

(3) Execute the assignment method by using the converted attribute value as a method parameter.

In the integration process in which the device model frequently changes, this embodiment has an obvious effect on reducing the difficulty of secondary development and the uniformity of the whole system, mainly in:

(1) There is no need to change the secondary development presentation layer and business layer. Just add a device model class. (2) The interface with other subsystems does not need to be changed, which reduces the degree of coupling of the code.

Embodiment 3 As shown in FIG. 2, the main function of the embodiment of the present invention is that the system converts the parameter input by the user into a standard data model and saves it into the database; when the parameter needs to be called, the system converts the standard model saved in the database into the actual device model. , returned to the caller.

As shown in FIG. 3, the standard data model of the embodiment of the present invention includes: an abstract device model (301), a device special attribute model (302), a device type model (303), a device model model (305), and a device model corresponding attribute model. ( 304 ).

In Figure 3, 303 is a device type model, which includes attributes such as name and number, which are the basic attributes of the device. The initial value of the model is determined at system initialization. Each device type contains multiple device models ( 305 ), and devices from different manufacturers correspond to different models.

In Figure 3, 305 is a device model model, which contains basic attributes such as name, number, and corresponding model class name, and belongs to a device type (303). The device model model can contain multiple model corresponding attributes ( 304 ).

In Fig. 3, 304 is a model corresponding attribute model, which includes basic attributes such as attribute name, attribute label, attribute number, etc., belonging to a device model (305), which specifies which extended attributes are available for the model.

In Figure 3, the 301 abstract device model, which contains basic attributes such as name, Internet Protocol (IP) address, belongs to a device type, a device model, and corresponds to a device special attribute (302). Among them, 1) abstract device model refers to the parent class of all actual device models, which contains some common attributes of all devices; 2) abstract device model corresponds to a device special attribute model, which is used to store the value of the device's own properties; 3) The device model of the 305 stores the special attributes of the device. The special attribute model is used to store the value of the special attribute of each device.

In FIG. 3, 302 is a device special attribute model, in which all special attributes of the device are stored, and a specified number of attribute domains are included, and the extended attributes of the actual device are saved in a string form to the corresponding domain attribute, and the model has an attribute domain. There is redundancy, corresponding to an abstract device (301).

Suppose the system introduces a Road-Side Unit (RSU) device, which has five special attributes: power, configuration port, data port, download port, and service port. The corresponding model class is RSU Adapter, the class attribute names corresponding to the five device attributes are: rsupower, rsuconfigport, rsudataport, rsudownloadport, rsuotherport. 4 is a flowchart of a device parameter management method of an RFID system according to Embodiment 3 of the present invention. As shown in FIG. 4, in the case of creating a new device model, the system processing of the RSU device includes:

In step 401, the user fills in the basic information of the device model. For example, the example 101 is: name/example model, number /000001, and the type is RSU.

In step 402, the system queries subclasses of all device abstract classes.

In step 403, the system queries all classes of the configured model.

Step 404, the system culls the configured model class.

Step 405: Display the culled class list on the interface.

Step 406, select the model class name corresponding to the model, for example, example 101 selects RsuparaAdapter. In step 407, the system displays all the attribute numbers of the selected model class to the interface. For example, the example 101 displays 1 / rsupower, 2 I rsuconfigport, 3 I rsudataport, 4 I rsudownloadport , 5 I rsuotherport.

In step 408, the user deletes the attribute that does not need to be configured, and the example 101 does not have this item.

Step 409, the user adds a label to each attribute, example 101 is 1 / rsupower I power, 2 I rsuconfigport IS own port, 3 / rsudataport I data port, 4 / rsudownloadport I download port, 5 / rsuotherport I service port .

In step 410, the system persists the selected model information and saves it to a database or file.

Step 411, the system generates a maintenance interface of the new device.

Further, as shown in FIG. 5, the step 411 can be further divided into the following steps:

Step 501: The system obtains each attribute type in the model class by using a reflection mechanism. For example, each of the 101 attribute types is an integer (Integer).

Step 502, generating a corresponding edit control according to each attribute type.

Step 503, if the attribute type is a number or a string, a text box is generated, and the example 101 conforms to the branch.

Step 504 If the attribute type is Boolean, a pulldown is generated.

Step 505 If the attribute type is Date, a date edit box is generated.

Step 506 If the attribute type does not belong to the above type, the prompt is not supported, and the process ends.

Step 507 Select the corresponding data validation rule according to each attribute type.

Step 508 Corresponds to the attribute description of the actual model attribute and the attribute corresponding control.

In step 509, the system lays out all the controls and generates an editing interface.

Users can use the system-generated interface to maintain new device parameters. For example, add a device with the device type RSU, model name/example model, number /000001, the device name is sample device 00001, and the IP address is 192.168.0.1. , Extended attribute power 3000, configuration port 3001, data port 3002, download port 3003, service port 3004. As shown in Figure 6, the process of querying the parameters of a device is as follows:

Step 601, select the device to be queried, for example, select: sample device 00001.

Step 602, call the query interface.

Step 603: The system queries the standard model information of the device.

Step 604, if the device exists, the system converts the standard device model into an actual device model. Step 605: Return device information to the user.

Step 606: If the device does not exist, the device is prompted to be absent.

Further, as shown in FIG. 7, the step 604 can be further divided into the following steps:

Step 701: Obtain a standard device data model.

Step 702: Obtain a device model, and the example corresponding model is a model added in the example of the RSU in this embodiment. Step 703: If the model class corresponding to the model exists, obtain an instance of the actual device model corresponding to the model device, and an example of the class RsuparaAdapter is used in the example.

Step 704, obtaining an extended attribute set corresponding to the type, where is 1 / rsupower / power, 2

I rsuconfigport I S own port, 3 / rsudataport I data port, 4 / rsudownloadport I download port, 5 / rsuotherport I service port.

Step 705, obtaining extended attribute values of the standard data model, in the examples, field 1/3000, field2/3001, field3/3002, field4/3003, field5/3004.

Step 706: Find the corresponding attribute of each extended attribute of the actual device model in the standard model. 1 I rsupower I field 1, 2 I rsuconfigport I field2, 3 I rsudataport field3, 4 I rsudownloadport field4, 15 I rsuotherport I field5.

Step 707, performing type conversion on the standard attribute.

Step 708: Assign the converted attribute value to the corresponding attribute of the actual model.

Step 709: If the model class corresponding to the model does not exist, an error is reported.

Further, as shown in FIG. 8, the step 707 can be further divided into the following steps:

Step 801, determining the actual attribute type.

Step 802, if the attribute type is a number, call the parse method to convert.

Step 803, if the attribute type is a boolean type, call the parse method to convert.

Step 804, if the attribute type is a date type, the method of calling Calendar generates an instance of the date type.

Step 805, if the attribute type is a string, no conversion is performed.

Step 806, returning the converted attribute object.

In the integration process in which the device model frequently changes, the embodiment has obvious effects on reducing the difficulty of secondary development and the uniformity of the entire system. All the external query interfaces, the return type are abstract device classes, and the actual return It is the actual type that is converted. The caller only needs to change the required type to the required type after obtaining the data. Add new equipment, the interface does not need to be changed. In the example, the interface return type is an abstract device model, and the actual return is RsuparaAdatper.

Embodiment 4

Embodiments of the present invention also provide a radio frequency identification (RFID) system for implementing the methods of Embodiments 1 through 3.

FIG. 9 is a structural block diagram of a radio frequency identification (RFID) system according to an embodiment of the present invention. As shown in FIG. 9, the system includes: a first acquisition module 92, configured to acquire model information of the device; and a second acquisition module 94 coupled The first obtaining module 92 is configured to obtain an actual model class corresponding to the model information of the device from a correspondence between the pre-stored model and the actual model class; the storage module 96 is coupled to the second acquiring module 94, and is configured to be configured according to the device. Corresponding actual model class, storing device parameters of the device input by the user; generating module 98, coupled to the storage module 96, configured to generate the actual device according to the device parameter of the stored device when the device parameter of the device needs to be managed model. Preferably, the system further includes: a first receiving module configured to receive model information of the device input by the user; and a second receiving module configured to receive a correspondence between the model information input by the user and the actual model class; the saving module is set to Save the correspondence in the database.

Preferably, the second receiving module comprises: a first obtaining submodule configured to acquire an unused actual model type; a display submodule configured to number the attributes of the unused actual model type and display to the user; The module, set to receive instructions from the user, deletes the unneeded attributes of the attributes of the unused actual model type, and maps the remaining attributes to the model information.

Preferably, the first obtaining submodule comprises: a first query unit, configured to query subclasses of all device abstract classes; a first prompting unit, configured to prompt the user to select all configured models in a subclass of all device abstract classes Class; removes a unit that is set to remove subclasses of the already configured model classes from subclasses of all device abstract classes.

Preferably, the storage module 96 includes: a generating submodule, configured to generate a device maintenance interface of the actual model class corresponding to the device; and a storage submodule configured to store device parameters of the device input by the user on the device maintenance interface.

Preferably, the generating submodule comprises: an obtaining unit, configured to obtain each attribute type in the actual model class by using a reflection mechanism; the first generating unit is configured to generate an editing control of the actual model class corresponding to the device according to each attribute type; The unit is set to call the device parameter maintenance interface template, and all the controls are laid out to generate a device maintenance interface.

Preferably, the first generating unit is configured to generate a text edit box when the attribute type is a numeric type or a string type attribute; when the attribute type is a Boolean type attribute, generate a radio edit box; when the attribute type is a date type attribute , generate a date edit box.

Preferably, the RFID system is configured to add parameter information of the new device according to the operation of the user; the RFID system is configured to modify parameter information of the device according to the operation of the user; and the RFID system is configured to query parameter information of the device according to the operation of the user; The RFID system is configured to delete parameter information of the device according to the operation of the user.

Preferably, the system comprises: a prompting module, configured to prompt the user to select a model of the device; a display module, configured to display a device maintenance interface of the actual model class corresponding to the model according to the model; the first storage module, configured to receive the user in the device maintenance Device parameter information filled in the interface, and the parameter information is stored in the database.

Preferably, the system includes: a determining module, configured to determine a device to be queried according to a user operation; a third obtaining module, configured to obtain parameter information of the device to be queried, and obtain a query according to the model information of the device to be queried The actual model class corresponding to the device; the return module is set to convert the parameter information of the device to be queried into the actual model of the device to be queried according to the actual model class corresponding to the device to be queried, and return the actual model object to the user.

Preferably, the returning module includes: creating a sub-module, which is set to create an instance of the actual model; and a second acquiring sub-module, configured to obtain the attribute of the stored parameter information of the device to be queried; the conversion sub-module, being set as the device to be queried The attribute of the parameter information is converted into the type of the corresponding attribute in the actual model; The submodule is set to assign the converted property value to the corresponding property of the instance of the actual model; return the submodule, set to return an instance of the actual model.

Preferably, the conversion submodule is set to call the numeric type Pas parse method to convert the attribute of the corresponding standard model into the type of the corresponding attribute in the actual model when the attribute type is a numeric type; when the attribute type is a Boolean type, the call is performed. The bossel type parse method converts the attributes of the corresponding standard model into the types of corresponding attributes in the actual model. When the attribute type is date type, the calendar method of calling the calendar is used to convert the attributes of the corresponding standard model into corresponding attributes in the actual model. Types of.

Preferably, the assignment sub-module comprises: a first acquisition unit, configured to obtain an assignment method name of the corresponding attribute; a second acquisition unit, configured to obtain an assignment method of the corresponding attribute according to the method name; the assignment unit is set to be converted The attribute value is used as the method parameter to perform the assignment method.

Preferably, the type of device parameter of the device is a single type.

In summary, in the embodiment of the present invention, the correspondence between the model of the system storage device and the actual model class, according to the device parameters of the corresponding relationship storage device, thereby generating an actual model when needed, thereby achieving a tubular RFID system. The effect of the process of managing the device.

Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein. The steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claims A method for managing device parameters of a radio frequency identification RFID system, including:

The RFID system acquires model information of the device;

Obtaining, by the RFID system, an actual model class corresponding to model information of the device from a correspondence between a pre-stored model and an actual model class;

The RFID system stores device parameters of the device input by the user according to the actual model class corresponding to the device;

When the device parameters of the device need to be managed, the RFID system generates an actual model of the device according to the stored device parameters of the device. The method according to claim 1, wherein before the obtaining, by the RFID system, the actual model class corresponding to the model of the device from the correspondence between the pre-stored model and the actual model class, the method further includes:

The RFID system receives model information of the device input by a user;

Receiving, by the RFID system, the model information input by a user and the corresponding relationship of the actual model class;

The RFID system saves the correspondence in a database. The method according to claim 2, wherein the receiving, by the RFID system, the correspondence between the model information input by the user and the actual model class comprises:

The RFID system acquires an actual model type that is not used;

The RFID system numbers the attributes of the unused actual model types and displays them to the user;

The RFID system receives an instruction from a user, deletes an attribute that is not required in the attribute of the unused actual model type, and associates the remaining attribute with the model information. The method according to claim 3, wherein the actual model type of the RFID system that is not used includes:

The RFID system queries subclasses of all device abstract classes; The RFID system prompts the user to select all of the model classes that have been configured in the subclasses of all device abstract classes;

The RFID system deletes subclasses of the already configured model classes in subclasses of all device abstract classes.

The method according to claim 1, wherein the RFID system stores the device parameters of the device input by the user according to the actual model class corresponding to the device, including:

The RFID system generates a device maintenance interface of an actual model class corresponding to the device; the RFID system stores device parameters of the device input by the user on the device maintenance interface.

The method according to claim 5, wherein the device maintenance interface of the actual model class corresponding to the RFID system generated by the RFID system comprises:

The RFID system uses a reflection mechanism to obtain each attribute type in the actual model class; the RFID system generates an edit control of the actual model class corresponding to the device in each of the attribute types;

The RFID system invokes a device parameter maintenance interface template, and all the controls are laid out to generate the device maintenance interface.

The method according to claim 6, wherein the RFID system generates an edit control of the actual model class corresponding to the device according to the respective attribute types, including:

If the attribute type is a numeric type or a string type attribute, the RFID system generates a text edit box;

If the attribute type is a Boolean type attribute, the RFID system generates a radio edit box; if the attribute type is a date type attribute, the RFID system generates a date edit box.

8. The method according to claim 1, wherein after the RFID system stores the device parameters of the device according to the actual model class corresponding to the device, the method includes at least one of the following:

The RFID system adds parameter information of the new device according to the operation of the user; the RFID system modifies parameter information of the device according to the operation of the user; the RFID system queries parameter information of the device according to the operation of the user ; The RFID system deletes parameter information of the device according to the operation of the user.

The method according to claim 8, wherein the adding, by the RFID system, the parameter information of the new device according to the operation of the user includes:

The RFID system prompts the user to select a model of the device;

The RFID system displays the device maintenance interface of the actual model class corresponding to the model; the RFID system receives the device parameter information filled in by the user on the device maintenance interface, and stores the parameter information in a database.

10. The method according to claim 8, wherein the RFID system queries the parameter information of the device according to the operation of the user, including:

The RFID system determines the device to be queried according to the operation of the user; the RFID system acquires parameter information of the device to be queried, and obtains the query to be queried according to the model information of the device to be queried. The actual model class corresponding to the device; the RFID system converts the parameter information of the device to be queried into the actual model of the device to be queried according to the actual model class corresponding to the device to be queried, and the actual model The object is returned to the user.

The method according to claim 10, wherein the RFID system converts parameter information of the device to be queried into an actual model of the device to be queried, including:

The RFID system creates an instance of the actual model;

The RFID system acquires an attribute of the stored parameter information of the device to be queried; the RFID system converts an attribute of the parameter information of the device to be queried into a type of a corresponding attribute in the actual model;

The RFID system assigns the converted attribute value to a corresponding attribute of an instance of the actual model;

The RFID system returns an instance of the actual model.

The method according to claim 11, wherein the RFID system converts an attribute of parameter information of the device to be queried into a type of a corresponding attribute in the actual model, including: If the attribute type is a numeric type, the RFID system calls a Paspar method of the numeric type to convert the attribute of the corresponding standard model into a corresponding type of the corresponding model in the actual model;

If the attribute type is a Boolean type, the RFID system calls a parse method of a Boolean type to convert the attribute of the corresponding standard model into a type of the corresponding attribute in the actual model;

If the attribute type is a date type, the method of calling the calendar Calendar by the RFID system converts the attributes of the corresponding standard model into the types of corresponding attributes in the actual model.

13. The method according to claim 11, wherein the RFID system assigns the converted attribute value to the corresponding attribute of the instance of the actual model, including:

The RFID system acquires an assignment method name of the corresponding attribute;

The RFID system acquires the assignment method of the corresponding attribute according to the method name; the RFID system executes the assignment method by using the converted attribute value as a method parameter.

The method according to any one of claims 1 to 13, wherein the number of device parameters of the device does not exceed a predetermined threshold.

The method according to any one of claims 1 to 13, wherein the type of the device parameter of the device is a simple type.

16. A radio frequency identification RFID system, including:

a first obtaining module, configured to acquire model information of the device;

a second acquiring module, configured to obtain an actual model class corresponding to the model information of the device from a correspondence between the pre-stored model and the actual model class;

a storage module, configured to store, according to the actual model class corresponding to the device, a device parameter of the device input by a user;

And generating a module, configured to generate an actual model of the device according to the stored device parameter of the device when the device parameter of the device needs to be managed.