CN101256650A - Method and system for extracting enterprise data based on service entity - Google Patents
Method and system for extracting enterprise data based on service entity Download PDFInfo
- Publication number
- CN101256650A CN101256650A CNA2008101024027A CN200810102402A CN101256650A CN 101256650 A CN101256650 A CN 101256650A CN A2008101024027 A CNA2008101024027 A CN A2008101024027A CN 200810102402 A CN200810102402 A CN 200810102402A CN 101256650 A CN101256650 A CN 101256650A
- Authority
- CN
- China
- Prior art keywords
- business entity
- entity
- data
- configuration file
- business
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method and a system for extracting enterprise data on the basis of service entities, belonging to the field of information processing; the method of the invention comprises the steps of: carrying out unified definition to data sources via the establishment of project configuration files and constructing a service entity set according to the configuration files, so that each service entity mapped to the database is managed in an unified manner and each service entity uses the unified method to access distributed databases. The system of the invention comprises an entity management layer, a service entity layer and a data access layer, the invention provides flexible data extraction solving proposal for the distributed databases of the enterprise, thus diminishing the time of software developers to learn the various databases and reducing the cost for transplantation from a database to another database, accordingly, the invention is beneficial to the steady and continuous running of the final system.
Description
Technical field
The present invention relates to a kind of business data extracting method and system, relate in particular to a kind of business data extracting method and system, belong to field of information processing based on Business Entity.
Background technology
Along with developing rapidly and the widespread use of data base management system (DBMS) of database technology, the data of people's accumulation are more and more.In IT application in enterprises was used, each layer computer systems such as supply chain management, enterprise operation management, production management, control in real time also all existed numerous data.How from magnanimity information, to retrieve information of interest fast, become the problem that people press for solution.Psychological study shows that 83% from vision in the external information that the mankind obtain.Information visualization can transfer a large amount of abstracted informations to visual form, promptly conveniently scans global information, can find focus information fast again, makes people be unlikely to get lost in the encirclement of information.Information visualization provides the instrument of a quick retrieving information for people.The information visualization process be from data to visual form again to adjustable mapping process of people's sensory perceptual system, and data extract is important link in the information visualization process.
Same data mining technology also is the useful technology that retrieves information of interest from magnanimity information fast.Because it can be analyzed the mass data of extensive existence, these data-switching are become Useful Information and knowledge.The workload of data pre-service link often accounts for 70% more than of data mining amount of work, and data extract is wherein important data pre-treatment step.
Data extract need go to extract related data usually from the Service Database of each application system.Yet in the IT application in enterprises development is a progressive process.When just beginning appliance computer, people are usually from word processing, report printing.And then, develop or introduce application system one by one to realize that certain specific application, satisfied local demand are purpose.The application system of these sporadic developments or introduction, generally can not unify to consider data standard or information sharing problem, the data organization form is difficult to avoid occurring diversified phenomenon, what have is stored in the mini-relational data base (as Access, FoxPro), what have is stored in the large-scale relational database in (as Oracle, Sql Server), and also some is present in (as PI, InfoPlus, Agilor) in the real-time data base.The visit of these heterogeneous databases and integration problem become the difficult problem that the technician faces, and often require a great deal of time and manpower when being transplanted to another kind of database for a kind of interface of database development.
Therefore, how numerous distributed data bases are unified visit and data extract, become the important technological problems that present urgent need solves.
Summary of the invention
In view of this, the object of the present invention is to provide a kind of method and system that distributed data base is carried out data extract, with the problem that is difficult in solution information visualization data extract link, data mining pre-service or enterprise application system exploitation and the integrating process heterogeneous database is conducted interviews, improve development efficiency, improve the extensibility and the availability of system.
For achieving the above object, the present invention adopts following method to realize:
The present invention at first provides distributed data source to carry out the method and system of unified Definition.This method is based on the define method (reference: World Wide Web Consortium of XSD, XML Schema, 2001, http://www.w3.org/XML/Schema.), extensibility is good, position, user name, password that the while user only need unify data source define, and no longer need the connection string of database is write, and also transplant easily and dispose simultaneously.System also supports the multiple storage mode and the cipher mode of defined file, reduced the risk that key message relates to dew.
The present invention is mapped Business Entity in the table of data source and view and application system or the method, adopts the definition of XSD to carry out standardization equally, and uses extend markup language expansion (XML) file to be configured and to store.The present invention is directed to Business Entity in aforesaid system business entity and the method and defined the interface of standard, realize adding, deletion, revise, according to standard methods such as major key inquiries.As extendfile, the XML file can define the method for Business Entity, and these methods correspond on the SQL statement of corresponding definition; Also can define simultaneously the storing process of Business Entity.The XML file finished of definition can be used as the statement file to database description application programming interface (API), and provides and for example need the SQL method of showing to API and the tabulation of storing process.
Simultaneously, the present invention defines by the leading character of name that the parametrization inquiry of disparate databases type is spoken, guaranteed that database is carried out the pairing SQL statement of standard operation (as interpolation, deletion, modification etc.) had both met the standard of ANSI SQL92, also met the requirement that different pieces of information is derived from body.
The method according to this invention, the definition of Business Entity have been improved the reusability of assembly by organization of unity and management, have also made things convenient for application system that Business Entity is called simultaneously.Simultaneously, the present invention also can catch the data structure of database, when the data type of field changes, need not again program to be compiled once more, only need reload configuration file and get final product, improve the availability of system, also accelerate the progress of iterative development.
Technical scheme of the present invention is:
A kind of business data extracting method based on Business Entity the steps include:
1) set up the data source configuration file, the data source in according to configuration file enterprise being used is carried out unified Definition;
2) set up entity management device configuration file, set the entity file that need use when extracting business data;
3) set up the Business Entity configuration file, set the attribute and the method for each Business Entity;
4) make up Business Entity according to above-mentioned configuration file, obtain the Business Entity collection;
5) unify Business Entity to database accessing method;
6) Business Entity conducts interviews to database according to the corresponding access method of request call, extracts corresponding business data.
Described entity management device configuration file comprises entity management device ID, the position of entity configuration file, explanation, remarks; Described Business Entity configuration file comprises Business Entity ID, corresponding data source ID, corresponding table name or view name, self-defining method, the storing process that need call, explanation, remarks; Described data source configuration file comprises whether data source ID, data source type, data adapter unit supplier, database location, user name, password, important information are encrypted.
The construction method of described Business Entity collection is:
1) Project Manager is created the Business Entity manager according to entity management device configuration file; Described entity management device configuration file is the XML form, and described entity management device comprises the ID of Business Entity collection, the position of Business Entity collection configuration file;
2) the Business Entity manager generates Business Entity according to the Business Entity configuration file of this Business Entity; Described configuration file is the XML form, and the data structure of described Business Entity comprises: the storing process and the parameter of the data type that the method for the title of Business Entity, the position of Business Entity, Business Entity and method need be used, Business Entity definition
3) Business Entity is joined the Business Entity collection;
4) judge that whether the Business Entity generation is finished, if finish then the ends with system initialization, otherwise forwards step 1) to.
Described Business Entity manager disposes the parameter of this Business Entity according to the data source configuration file of this Business Entity, and described data source configuration file is the XML form.
Provide unified Business Entity to database accessing method by single view entity and single table entity in the described method.
The access method that described single view entity provides comprises universal method and customizing method, described universal method includes but not limited to one or more of following method: obtain database connect be used to carry out affairs, begin db transaction, obtain dial framework structure information, whole viewdata of inquiry, according to given parameter query viewdata, described customizing method is for carrying out self-defining method, promptly user configured SQL statement or the pairing storing process of Business Entity according to the business rule that extracts.
The access method that described single table entity provides includes but not limited to one or more of following method: obtain database connect be used to carry out affairs, begin db transaction, obtain dial framework structure information, whole viewdata of inquiry, according to given parameter query viewdata, whole table upgrade, insert data, deleted data, modification data, according to the major key of database table inquire about certain bar data whether exist, according to the major key data query of database table.
The manner of execution of described access method is:
1) the Business Entity manager extracts the pairing Business Entity of method that is called;
2) Business Entity is concentrated the SQL statement of extracting the method that is called from this Business Entity method;
3) the pragmatic body method of working is concentrated the parameter type that extracts the method that is called;
4) generate parameter and assignment, carry out invoked way access database.
The manner of execution of described storing process is:
1) the Business Entity manager extracts the pairing Business Entity of storing process that is called;
2) Business Entity is concentrated the title of extracting the storing process that is called the correspondence database from this Business Entity method;
3) the pragmatic body method of working is concentrated the parameter type that extracts the method that is called;
4) generate parameter and assignment, carry out invoked storing process accessing database.
A kind of business data extraction system based on Business Entity comprises entity management layer, service entity layer, data access layer;
Described entity management layer is used for realizing effective Organization And Management to Business Entity according to the configuration information of configuration file that described configuration file comprises data source configuration file, entity management device configuration file, Business Entity configuration file;
Described service entity layer is used for Business Entity is corresponded to the table or the view of affiliated data source, provides unified access method by method or the storing process that defines for upper system;
Described data access layer is used to encapsulate the method to the Database Systems visit, and database is conducted interviews.
Good effect of the present invention
From technique scheme as can be seen, the present invention has following beneficial effect:
1, system architecture is simply clear: adopt the architecture design of layering, help team develops;
2, study and use are simple: use OO design, easier study and use;
3, development efficiency height: encapsulated a series of universal method, the developer need not to be concerned about the database access details, has improved development efficiency greatly;
4, iterative development is more quick: when carrying out iterative development, can reflect the data updated library structure automatically, improve the agility of iterative development;
5, extensibility is good: can carry out secondary development on this basis, realize self-defining function;
6, database is transplanted conveniently: service logic and bottom data visit are separated, help the transplanting of database, the groundwork when carrying out the database transplanting is the change respective profiles;
7, availability height: adopt data source and the configurable mode of engineering, can change the practical operation that data are visited, need not the assembly of this layer is compiled once more by revising configuration.
Be appreciated that the general introduction of front and the description both of follow-up embodiment only are exemplary and illustrative, do not limit this claimed invention.When considering detailed description of the present invention below the reading in conjunction with the accompanying drawings, it is obvious that others of the present invention, advantage and novel feature can become.
Description of drawings
Fig. 1 is the structural representation of distributed data base data extraction system provided by the invention;
Fig. 2 is the realization flow figure of distributed data base data extraction method provided by the invention;
The method flow diagram that Fig. 3 constructs the Business Entity collection of management during for system start-up provided by the invention;
Fig. 4 is the method flow diagram of Business Entity provided by the invention institute define method when carrying out;
Method flow diagram when Fig. 5 carries out for storing process that Business Entity provided by the invention defines;
Fig. 6 is for can use various aspects of the present invention to generate the client-server system of data middle layer according to the present invention.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, below in conjunction with specific embodiment, and with reference to accompanying drawing, the present invention is described in more detail.
At first referring to Fig. 1, Fig. 1 is the structural representation of distributed data base data extraction system provided by the invention.This structural representation illustrates the multilayer client-server architecture 140 that is deployed with the distributed data extraction system according to the present invention in middle layer 110.The structure of three layers of physical layering is provided, i.e. client layer, middle layer and database layer, wherein client layer 100 comprises teller work station, PDA and the miscellaneous equipment that can use the web browser.For the solution towards service, this layer comprises computing machine and the equipment that uses service.Generally, arrange in 100 in such multilayer, the client applications process represents to operate in the application program on the computer platform, wherein computer platform can be the same computer platform of database server, and perhaps it can be the remote computation machine platform that is connected to server by the communication media such as certain type of communication network etc.
The disposing application program software-component generally can be responsible in middle layer 110, and in the situation of weblication, also can be deployed on the Web server.Such middle layer 110 can comprise professional outward appearance layer 120, Business Logic 130, entity management layer 150, service entity layer 160, data access layer 170.
Professional outward appearance layer 120 is just given one of caller calling interface very clearly usually, and it is responsible for the various relations simplifications of complicated service logical layer, the rule that Business Logic 130 comprises business object itself and is applied to them.This also is the position at main business object place.They call Business Entity or system object.The business rule of system will be encoded in these objects, although the partial service rule may be in fact encoded in the storing process of database and trigger.
Distributed data base 180 can be by the one or more entities with the correlation inquiry ability on the execution list.Can use one group of processing language (for example, Structured Query Language (SQL)) to visit the group of entities of storing in the table, wherein this language is appointed as the source of data with one or more table, and only exports those row (if any) that satisfy specified criteria.
Based on the structural representation of distributed data base data extraction system shown in Figure 1, Fig. 2 shows the realization flow figure of distributed data base data extraction method, and this method may further comprise the steps:
Step 210: at first set up entity management device configuration file (with reference to appendix A), this document mainly comprises information such as the position, explanation, remarks of entity management device ID, entity configuration file; Set up Business Entity configuration file (with reference to appendix B), this document mainly comprises Business Entity ID, corresponding data source ID, corresponding table name or view name, carries out information such as self-defining method (promptly needing the SQL statement carried out, if the parametrization SQL statement has then also comprised the definition of parameter), the storing process (if the storing process of band parameter has then also comprised the definition of parameter) that need call, explanation, remarks according to the business rule that extracts; Set up data source configuration file (with reference to appendix C), this document comprises mainly whether data source ID, data source type, data adapter unit supplier, database location, user name, password, important information information such as encrypt.When system start-up, as shown in Figure 3, Project Manager 305 can be constructed Business Entity under the assistance of entity management device configuration file 320, Business Entity configuration file 340 and data source configuration file 342 and be obtained the Business Entity collection.These XML configuration files can be analyzed with relevant to be determined Project Manager 305 how this generates class.
Step 220: the method for Business Logic invocation step 210 Business Entity of constructing, need indicate the title of method when calling and the information of operated data is composed to relevant parameters according to the requirement of calling of method, these information will be organized as Hash table in system, be that parameter is called with this Hash table then, can realize the method that distributed data base is unified to visit.
Step 230: the entity management layer is distributed to request to specified Business Entity after receiving the call request of Business Logic.
Step 240: Business Entity calls corresponding data access method according to the call request of receiving, database is unified visit.
Described in the above-mentioned steps 210 system being carried out initialization comprises: Project Manager will specify the Business Entity constructing definitions of storing in the XML file to become the Business Entity object, and will construct good Business Entity and be organized into the Business Entity collection.
The method of described in the above-mentioned steps 220 distributed data base being unified to visit is as follows, mainly provide unified access method among the present invention by single view entity and single table entity, wherein the single view entity can correspond to certain view of indication relational database according to relevant configuration in the entity configuration file, and the unified access method that provides comprises universal method and customizing method two parts.Universal method is that system realizes automatically; And customizing method needs the user to dispose relevant SQL statement or disposes pairing storing process.Universal method comprises:
(1) obtaining database connects to be used to carry out affairs;
(2) beginning db transaction;
(3) obtain the framework information of table;
(4) whole viewdata of inquiry;
(5) according to given parameter query viewdata.
Single table entity then can correspond to certain table of indication relational database, and it also provides following universal method except having inherited the method that the single view entity provides:
(1) whole table upgrades;
(2) insert data;
(3) deleted data;
(4) revise data;
(5) whether exist according to major key parameter query bar data;
(6) according to the major key data query of database table.
Above-mentioned steps 240 comprises: after Business Entity is received request, to select corresponding relation data source according to data source property, and according to the request the method name obtain corresponding SQL statement or storing process name, simultaneously with parametrization query SQL statement or the band parameter storing process in parameter carry out carrying out after the assignment.
The method of during system start-up that the invention described above provides the Business Entity collection of management being constructed can also be with reference to figure 3, the method flow diagram that Fig. 3 constructs the Business Entity collection of management during for system start-up provided by the invention, and this method may further comprise the steps:
Step 305: during system start-up, will carry out initial work, system will create Project Manager automatically.
Step 315: under the assistance of entity management device configuration file 320, create the entity management device.Entity management device configuration file can be the XML form, and Project Manager 305 can determine how this generates the entity management device according to entity management device configuration file.These entity management devices can comprise the ID of Business Entity collection, the position of Business Entity collection configuration file etc.
Step 325: judge that according to the standard of manager configuration file whether the entity management device that generates generates successful, then continues step 335 to generating successful entity management device; Unsuccessful then go to step 355.
Step 335: under the assistance of Business Entity configuration file 340, create Business Entity.The Business Entity configuration file can be the XML form, and entity management device 315 can determine how this generates Business Entity according to the Business Entity configuration file.The storing process of the parameter of needs, definition and parameter (providing pairing storing process name of Business Entity and parameter during definition) etc. when the attribute of these Business Entities and element can comprise the method for the ID of title, the data source of Business Entity, corresponding table or view name, definition and pairing SQL statement and parametrization SQL query.Simultaneously, the entity management device need generate the necessary attribute of connection string as this Business Entity under the assistance of relation data source profile 342 when creating Business Entity.The relation data source profile also can be the XML form, can be analyzed with relevant and determine entity management device 315 how this generates the concatenation character string attribute of Business Entity.These connection strings can comprise database location, user name, password etc.
Step 345: judge according to the standard of data source configuration file whether the connection string that generates generates success, if generate successfully then continue step 350; Unsuccessful then go to step 355.
Step 350: the Business Entity that generates is joined the Business Entity collection, and waiting system calls.
Step 355: the mistake during to generation writes Debugging message, and goes to the next entity management device 315 of generation.
Step 365: judged to the configuration file bottom according to whether whether the Business Entity collection generates and finished, finished then ends with system initialization, generated next entity management device 315 otherwise go to.
Can be when the method that defines in the Business Entity that the invention described above provides is carried out with reference to figure 4, method flow diagram when Fig. 4 carries out for the method that defines in the Business Entity provided by the invention, this method may further comprise the steps: system call instance method 405 at first will provide Business Entity 410 by the entity management device; Next step is at 415 places, and Business Entity extracts corresponding SQL statement to this Business Entity method collection 420; Next asking successfully 425 places to be judged, failure then goes to method call and finishes 460, successful then arrive next step requesting method right parameter type 430; Step 430 needs to extract type of correspondence parameter in the pragmatic body method collection 420 of working equally; Next at 435 places whether request is judged effectively that the invalid method call that then goes to finishes 460, effective then when generating parametrization SQL query to next step need parameter and assignment, manner of execution, accessing database 440; Step 440 need conduct interviews to database 445; Whether next step is at 450 places, successfully judge carrying out, and is successful then go to 460 prescribing methods and call end, unsuccessful then to 455 places, mistake is write Debugging message.
Can be when the storing process that defines in the Business Entity that the invention described above provides is carried out with reference to figure 5, the method flow diagram when Fig. 5 carries out for the storing process that defines in the Business Entity provided by the invention, this method and Fig. 4 are similar, can be with reference to the description of Fig. 4.
The exemplary patterns that can be used as the part of configuration file 320 presents at the end of this document, as the appendix A part; The exemplary patterns that can be used as the part of configuration file 340 presents at the end of this document, as appendix B part; The exemplary patterns that can be used as the part of configuration file 342 presents at the end of this document, as the appendix C part.As previously mentioned, such exemplary patterns can be for example to use the schema construction of XML pattern language to define and describe the form of the extend markup language (XML) of a class XML document.These schema constructions can be used to retrain and prove meaning, purposes and relation as data type used in the XML document, element and content thereof, attribute and value thereof, entity, content and symbolic representation.Like this, generally speaking, any computer system that can visit the XML pattern can be according to XML mode treatment XML document.And any computer system that generally can visit the XML pattern can write or revise XML document and use for other computer system that also can visit the XML pattern.Pattern can be used for defining any basically data type that is used for definition data structure, comprises the combination of logic, scale-of-two, scale-of-eight, the decimal system, sexadecimal, integer, floating-point, character, character string, user-defined data type and these data types.The XML attribute can be defined the data type of representing by mode-definition.
Can use various aspects of the present invention to generate the client-server system of data middle layer according to the present invention can also be with reference to figure 6, can be the various terminals that browser is housed based on the client 610 of Web, comprises computing machine, smart machine etc.; System 600 can comprise one or more Web servers 620, also can comprise one or more application servers 630, client 610, Web server 620 and application server 630 can be communicated by letter between two or more computer processes by the form according to data packets for transmission of the present invention.As shown, system 600 comprises the communication construction 650 that can promote between client 610, Web server 620 and the application server 630.Client 610 can be visited and be upgraded database on the server computer 640 that is positioned at the runtime server process.
Although the present invention illustrates and describes with reference to the aspect shown in some; institute is understood that; the above only is specific embodiments of the invention; be not limited to the present invention; within the spirit and principles in the present invention all; any modification of being made, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Appendix A
<？xml?version＝″1.0″encoding＝″utf-8″？>
<xs:schema xmlns＝″http://tempuri.org/ProjectInfo.xsd″
xmlns:mstns＝″http://tempuri.org/ProjectInfo.xsd″
xmlns:xs＝″＝http://www.w3.org/2001/XMLSchema″
targetNamespace＝″http://tempuri.org/ProjectInfo.xsd″
elementFormDefault＝″qualified″id＝″ProjectInfo″>
<xs:element?name＝″ProjectInfo″>
<xs:complexType>
<xs:sequence>
<xs:element?name＝″ID″type＝″xs:ID″/>
<xs:element?name＝″EntitiesInfo″type＝″EntitiesInfo″
maxOccurs＝″unbounded″/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType?name＝″EntitiesInfo″>
<xs:sequence>
<xs:element?name＝″ID″type＝″xs:ID″/>
<xs:group?ref＝″ProjectLocation″/>
<xs:element?name＝″Specification″type＝″xs:string″/>
<xs:element?name＝″Memo″type＝″xs:string″/>
</xs:sequence>
</xs:complexType>
<xs:simpleType?name＝″AbstractLocation″>
<xs:restriction?base＝″xs:string″>
<xs:enumeration?value＝″System″/>
<xs:enumeration?value＝″Local″/>
</xs:restriction>
</xs:simpleType>
<xs:group?name＝″ProjectLocation″>
<xs:choice>
<xs:element?name＝″AbstractWay″type＝″AbstractLocation″/>
<xs:element?name＝″ConcreteWay″type＝″xs:string″/>
</xs:choice>
</xs:group>
</xs:schema>
Appendix B
<？xml?version＝″1.0″encoding＝″utf-8″？>
<xs:schema xmlns＝″http://tempuri.org/EntityInfo.xsd″
xmlns:mstns＝″http://tempuri.org/EntityInfo.xsd″
xmlns:xs＝″http://www.w3.org/2001/XMLSchema″
targetNamespace＝″http://tempuri.org/EntityInfo.xsd″
elementFormDefault＝″qualified″id＝″EntityInfo″>
<xs:simpleType?name＝″SingleEnityKeyType″>
<xs:restriction?base＝″xs:string″>
<xs:enumeration?value＝″WithKey″/>
<xs:enumeration?value＝″NoKey″/>
</xs:restriction>
</xs:simpleType>
<xs:complexType?name＝″Key″>
<xs:sequence>
<xs:element?name＝″ID″type＝″xs:ID″/>
<xs:element?name＝″EntityID″type＝″xs:string″/>
<xs:element?name＝″Field″type＝″xs:string″/>
<xs:element?name＝″Specification″type＝″xs:string″/>
</xs:sequence>
<xs:attribute?name＝″Name″type＝″xs:string″/>
</xs:complexType>
<xs:complexType?name＝″KeyRef″>
<xs:sequence>
<xs:element?name＝″ID″type＝″xs:ID″/>
<xs:element?name＝″EntityID″type＝″xs:string″/>
<xs:element?name＝″Field″type＝″xs:string″/>
<xs:element?name＝″Specification″type＝″xs:string″/>
<xs:element?name＝″Refer″type＝″xs:string″/>
</xs:sequence>
<xs:attribute?name＝″Name″type＝″xs:string″/>
</xs:complexType>
<xs:complexType?name＝″ReferSingleEntity″>
<xs:sequence>
<xs:element?name＝″ID″type＝″xs:ID″/>
<xs:element?name＝″Specification″type＝″xs:string″/>
</xs:sequence>
</xs:complexType>
<xs:complexType?name＝″DefinedSql″>
<xs:sequence>
<xs:element?name＝″ID″type＝″xs:ID″/>
<xs:element?name＝″SqlString″type＝″xs:string″/>
<xs:element?name＝″Para″type＝″Para″minOccurs＝″0″
maxOccurs＝″unbounded″/>
<xs:element?name＝″Specification″type＝″xs:string″/>
</xs:sequence>
</xs:complexType>
<xs:complexType?name＝″DefinedSp″>
<xs:sequence>
<xs:element?name＝″ID″type＝″xs:ID″/>
<xs:element?name＝″Para″type＝″Para″minOccurs＝″0″
maxOccurs＝″unbounded″/>
<xs:element?name＝″Specification″type＝″xs:string″/>
</xs:sequence>
</xs:complexType>
<xs:simpleType?name＝″SingleEnityWorkWay″>
<xs:restriction?base＝xs:string″>
<xs:enumeration?value＝″Normal″/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType?name＝″EnitySetWorkWay″>
<xs:restriction?base＝″xs:string″>
<xs:enumeration?value＝″Normal″/>
</xs:restriction>
</xs:simpleType>
<xs:complexType?name＝″SingleEntityInfo″>
<xs:sequence>
<xs:element?name＝″ID″type＝″xs:ID″/>
<xs:element?name＝″Type″type＝″SingleEnityKeyType″/>
<xs:element?name＝″CreateSql″type＝″xs:string″/>
<xs:group?ref＝″SchemaLocation″/>
<xs:element?name＝″WorkWay″type＝″SingleEnityWorkWay″/>
<xs:element?name＝″Specification″type＝″xs:string″/>
<xs:element?name＝″Memo″type＝″xs:string″/>
<xs:element?name＝″SqlDefined″type＝″DefinedSql″
minOccurs＝″0″maxOccurs＝″unbounded″/>
<xs:element?name＝″SpDefined″type＝″DefinedSp″minOccurs＝″0″
maxOccurs＝″unbounded″/>
</xs:sequence>
<xs:attribute?name＝″TableName″type＝″xs:string″/>
<xs:attribute?name＝″DataSource″type＝″xs:string″use＝″optional″/>
</xs:complexType>
<xs:complexType?name＝″EntitySetInfo″>
<xs:sequence>
<xs:element?name＝″ID″type＝″xs:ID″/>
<xs:element?name＝″Entity″type＝″ReferSingleEntity″
maxOccurs＝″unbounded″/>
<xs:element?name＝″Key″type＝″Key″minOccurs＝″0″
maxOccurs＝″unbounded″/>
<xs:element?name＝″KeyRef″type＝″KeyRef″minOccurs＝″0″
maxOccurs＝″unbounded″/>
<xs:element?name＝″WorkWay″type＝″EnitySetWorkWay″/>
<xs:element?name＝″Specification″type＝″xs:string″/>
<xs:element?name＝″Memo″type＝″xs:string″/>
</xs:sequence>
<xs:attribute?name＝″Name″type＝″xs:string″/>
</xs:complexType>
<xs:element?name＝″Entities″>
<xs:complexType>
<xs:sequence>
<xs:element?name＝″SingleEntityInfo″type＝″SingleEntityInfo″
minOccurs＝″0″maxOccurs＝″unbounded″/>
<xs:element?name＝″EntitySetInfo″type＝″EntitySetInfo″
minOccurs＝″0″maxOccurs＝″unbounded″/>
</xs:sequence>
<xs:attribute?name＝″DataSource″type＝″xs:string″/>
</xs:complexType>
</xs:element>
<xs:group?name＝″SchemaLocation″>
<xs:choice>
<xs:element name＝″AbstractSchemaLocation″
type＝″AbstractLocation″/>
<xs:element?name＝″ConcreteSchemaLocation″type＝″xs:string″/>
</xs:choice>
</xs:group>
<xs:simpleType?name＝″AbstractLocation″>
<xs:restriction?base＝″xs:string″>
<xs:enumeration?value＝″System″/>
<xs:enumeration?value＝″Local″/>
<xs:enumeration?value＝″DataBase″/>
</xs:restriction>
</xs:simpleType>
<xs:complexType?name＝″Para″>
<xs:sequence>
<xs:element?name＝″ID″type＝″xs:ID″/>
<xs:element?name＝″Type″type＝″xs:string″minOccurs＝″0″/>
<xs:element?name＝″Direction″type＝″ParaDirection″
minOccurs＝″0″/>
</xs:sequence>
</xs:complexType>
<xs:simpleType?name＝″ParaDirection″>
<xs:restriction?base＝″xs:string″>
<xs:enumeration?value＝″Input″/>
<xs:enumeration?value＝″Output″/>
<xs:enumeration?value＝″InputOutput″/>
<xs:enumeration?value＝″ReturnValue″/>
</xs:restriction>
</xs:simpleType>
</xs:schema>
Appendix C
<？xml?version＝″1.0″encoding＝″utf-8″？>
<xs:schema xmlns＝″http://iel.iscas.ac.cn/Config.xsd″
xmlns:mstns＝″http://iel.iscas.ac.cn/Config.xsd″
xmlns:xs＝″http://www.w3.org/2001/XMLSchema″
targetNamespace＝″http://iel.iscas.ac.cn/Config.xsd″elementFormDefault＝″qualified″
id＝″Config″>
<xs:element?name＝″Connections″>
<xs:complexType>
<xs:sequence>
<xs:element?name＝″DsDefine″type＝″Define″minOccurs＝″0″
maxOccurs＝″unbounded″/>
</xs:sequence>
<xs:attribute?name＝″IsEncrypt″type＝″xs:boolean″use＝″required″/>
</xs:complexType>
</xs:element>
<xs:complexType?name＝″Define″>
<xs:sequence>
<xs:element?name＝″ID″type＝″xs:ID″/>
<xs:element?name＝″Memo″type＝″xs:string″/>
<xs:group?ref＝″Config″/>
</xs:sequence>
<xs:attribute?name＝″EncryptAlgorithm″type＝″AlgorithmType″
use＝″required″/>
<xs:attribute?name＝″DataProvider″type＝″DataProviderType″
use＝″required″/>
<xs:attribute?name＝″DataSource″type＝″DataSourceType″
use＝″required″/>
</xs:complexType>
<xs:simpleType?name＝″AlgorithmType″>
<xs:restriction?base＝″xs:string″>
<xs:enumeration?value＝″SHA1″/>
<xs:enumeration?value＝″DES″/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType?name＝″DataProviderType″>
<xs:restriction?base＝″xs:string″>
<xs:enumeration?value＝″Odbc″/>
<xs:enumeration?value＝″Oledb″/>
<xs:enumeration?value＝″Oracle″/>
<xs:enumeration?value＝″Sql″/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType?name＝″DataSourceType″>
<xs:restriction?base＝″xs:string″>
<xs:enumeration?value＝″Access″/>
<xs:enumeration?value＝″Excel″/>
<xs:enumeration?value＝″DB2″/>
<xs:enumeration?value＝″Informix″/>
<xs:enumeration?value＝″Oracle″/>
<xs:enumeration?value＝″SQL?Server″/>
</xs:restriction>
</xs:simpleType>
<xs:complexType?name＝″OracleStandard″>
<xs:sequence>
<xs:element?name＝″DataSource″type＝″xs:string″/>
<xs:element?name＝″UserId″type＝″xs:string″/>
<xs:element?name＝″Password″type＝″xs:string″/>
</xs:sequence>
</xs:complexType>
<xs:complexType?name＝″SqlStandard″>
<xs:sequence>
<xs:element?name＝″Server″type＝″xs:string″/>
<xs:element?name＝″Database″type＝″xs:string″/>
<xs:element?name＝″UserId″type＝″xs:string″/>
<xs:element?name＝″Password″type＝″xs:string″/>
<xs:element?name＝″AttachDBFilename″type＝″xs:string″/>
</xs:sequence>
</xs:complexType>
<xs:complexType?name＝″OledbAccessStandard″>
<xs:sequence>
<xs:element?name＝″Provider″type＝″ProviderType″/>
<xs:element?name＝″DataSource″type＝″xs:string″/>
<xs:element?name＝″UserId″type＝″xs:string″/>
<xs:element?name＝″Password″type＝″xs:string″/>
</xs:sequence>
</xs:complexType>
<xs:simpleType?name＝″ProviderType″>
<xs:restriction?base＝″xs:string″>
<xs:enumeration?value＝″Microsoft.Jet.OLEDB.4.0″/>
</xs:restriction>
</xs:simpleType>
<xs:complexType?name＝″OdbcAccessStandard″>
<xs:sequence>
<xs:element?name＝″Driver″type＝″DrivererType″/>
<xs:element?name＝″Dbq″type＝″xs:string″/>
<xs:element?name＝″UserId″type＝″xs:string″/>
<xs:element?name＝″Password″type＝″xs:string″/>
</xs:sequence>
</xs:complexType>
<xs:simpleType?name＝″DrivererType″>
<xs:restriction?base＝″xs:string″>
<xs:enumeration?value＝″Microsoft?Access?Driver(*.mdb)″/>
</xs:restriction>
</xs:simpleType>
<xs:group?name＝″Config″>
<xs:choice>
<xs:element?name＝″DsOracleStandard″type＝″OracleStandard″/>
<xs:element?name＝″DsSqlStandard″type＝″SqlStandard″/>
<xs:element?name＝″DsOledbAccessStandard″
type＝″OledbAccessStandard″/>
<xs:element?name＝″DsOdbcAccessStandard″
type＝″OdbcAccessStandard″/>
<xs:element?name＝″DsOdbcExcelStandard″
type＝″OdbcExcelStandard″/>
</xs:choice>
</xs:group>
<xs:complexType?name＝″OdbcExcelStandard″>
<xs:sequence>
<xs:element?name＝″Driver″type＝″DrivererType″/>
<xs:element?name＝″DriverId″type＝″xs:string″/>
<xs:element?name＝″Dbq″type＝″xs:string″/>
<xs:element?name＝″DefaultDir″type＝″xs:string″/>
</xs:sequence>
</xs:complexType>
</xs:schema>
Claims (10)
1. the business data extracting method based on Business Entity the steps include:
1) set up the data source configuration file, the data source in according to configuration file enterprise being used is carried out unified Definition;
2) set up entity management device configuration file, set the entity file that need use when extracting business data;
3) set up the Business Entity configuration file, set the attribute and the method for each Business Entity;
4) make up Business Entity according to above-mentioned configuration file, obtain the Business Entity collection;
5) unify Business Entity to database accessing method;
6) Business Entity conducts interviews to database according to the corresponding access method of request call, extracts corresponding business data.
2. the method for claim 1 is characterized in that described entity management device configuration file comprises entity management device ID, the position of entity configuration file, explanation, remarks; Described Business Entity configuration file comprises Business Entity ID, corresponding data source ID, corresponding table name or view name, self-defining method, the storing process that need call, explanation, remarks; Described data source configuration file comprises whether data source ID, data source type, data adapter unit supplier, database location, user name, password, important information are encrypted.
3. method as claimed in claim 2 is characterized in that the construction method of described Business Entity collection is:
1) Project Manager is created the Business Entity manager according to entity management device configuration file; Described entity management device configuration file is the XML form, and described entity management device comprises the ID of Business Entity collection, the position of Business Entity collection configuration file;
2) the Business Entity manager generates Business Entity according to the Business Entity configuration file of this Business Entity; Described configuration file is the XML form, and the data structure of described Business Entity comprises: the storing process and the parameter of the data type that the method for the title of Business Entity, the position of Business Entity, Business Entity and method need be used, Business Entity definition
3) Business Entity is joined the Business Entity collection;
4) judge that whether the Business Entity generation is finished, if finish then the ends with system initialization, otherwise forwards step 1) to.
4. method as claimed in claim 3 is characterized in that described Business Entity manager disposes the parameter of this Business Entity according to the data source configuration file of this Business Entity, and described data source configuration file is the XML form.
5. the method for claim 1 is characterized in that providing unified Business Entity to database accessing method by single view entity and single table entity.
6. method as claimed in claim 5, it is characterized in that the access method that described single view entity provides comprises universal method and customizing method, described universal method includes but not limited to one or more of following method: obtain database connect be used to carry out affairs, begin db transaction, obtain dial framework structure information, whole viewdata of inquiry, according to given parameter query viewdata, described customizing method is for carrying out self-defining method, promptly user configured SQL statement or the pairing storing process of Business Entity according to the business rule that extracts.
7. method as claimed in claim 5 is characterized in that access method that described single table entity provides includes but not limited to one or more of following method: obtain database connect be used to carry out affairs, begin db transaction, obtain dial framework structure information, whole viewdata of inquiry, according to given parameter query viewdata, whole table upgrade, insert data, deleted data, modification data, according to the major key of database table inquire about certain bar data whether exist, according to the major key data query of database table.
8. as claim 6 or 7 described methods, it is characterized in that the manner of execution of described access method is:
1) the Business Entity manager extracts the pairing Business Entity of method that is called;
2) Business Entity is concentrated the SQL statement of extracting the method that is called from this Business Entity method;
3) the pragmatic body method of working is concentrated the parameter type that extracts the method that is called;
4) generate parameter and assignment, carry out invoked way access database.
9. method as claimed in claim 3 is characterized in that the manner of execution of described storing process is:
1) the Business Entity manager extracts the pairing Business Entity of storing process that is called;
2) Business Entity is concentrated the title of extracting the storing process that is called the correspondence database from this Business Entity method;
3) the pragmatic body method of working is concentrated the parameter type that extracts the method that is called;
4) generate parameter and assignment, carry out invoked storing process accessing database.
10. the business data extraction system based on Business Entity comprises entity management layer, service entity layer, data access layer;
Described entity management layer is used for realizing effective Organization And Management to Business Entity according to the configuration information of configuration file that described configuration file comprises data source configuration file, entity management device configuration file, Business Entity configuration file;
Described service entity layer is used for Business Entity is corresponded to the table or the view of affiliated data source, provides unified access method by method or the storing process that defines for upper system;
Described data access layer is used to encapsulate the method to the Database Systems visit, and database is conducted interviews.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101024027A CN101256650B (en) | 2008-03-21 | 2008-03-21 | Method and system for extracting enterprise data based on service entity |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101024027A CN101256650B (en) | 2008-03-21 | 2008-03-21 | Method and system for extracting enterprise data based on service entity |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101256650A true CN101256650A (en) | 2008-09-03 |
| CN101256650B CN101256650B (en) | 2012-02-15 |
Family
ID=39891454
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008101024027A Expired - Fee Related CN101256650B (en) | 2008-03-21 | 2008-03-21 | Method and system for extracting enterprise data based on service entity |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101256650B (en) |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010145194A1 (en) * | 2009-06-18 | 2010-12-23 | Du Bo | Enterprise application software producer |
| CN102033871A (en) * | 2009-09-25 | 2011-04-27 | 中国移动通信集团浙江有限公司 | Method and system for sharing public resource data by multiple information systems |
| CN102065066A (en) * | 2009-11-17 | 2011-05-18 | 中国移动通信集团广东有限公司 | Access device and access method for data service content of data service portals |
| CN102110111A (en) * | 2009-12-29 | 2011-06-29 | 北京大学 | Method and system for processing database operating command |
| CN102521232A (en) * | 2011-11-09 | 2012-06-27 | Ut斯达康通讯有限公司 | Distributed acquisition and processing system and method of internet metadata |
| CN102902763A (en) * | 2012-09-21 | 2013-01-30 | 东软集团股份有限公司 | Method and device for relating and retrieving information processing data and processing information tasks |
| CN103838574A (en) * | 2014-02-20 | 2014-06-04 | 浪潮集团山东通用软件有限公司 | General method for grouped summarizing of data tables |
| CN103942311A (en) * | 2014-04-21 | 2014-07-23 | 湖南深拓智能设备股份有限公司 | Multiplexing method of monitoring system variables |
| CN104484358A (en) * | 2014-12-02 | 2015-04-01 | 山东中创软件工程股份有限公司 | Process template displaying method and system |
| CN104933664A (en) * | 2015-06-19 | 2015-09-23 | 中国铁道科学研究院电子计算技术研究所 | Passenger ticket data visualization method |
| CN105159920A (en) * | 2015-07-28 | 2015-12-16 | 卡斯柯信号有限公司 | Attribute tag based database access method |
| CN105607906A (en) * | 2015-12-18 | 2016-05-25 | 北京金山安全软件有限公司 | Service implementation method and device and electronic equipment |
| CN105989153A (en) * | 2015-03-02 | 2016-10-05 | 阿里巴巴集团控股有限公司 | Interaction method and device of database |
| WO2016206044A1 (en) * | 2015-06-25 | 2016-12-29 | Microsoft Technology Licensing, Llc | Extracting enterprise project information |
| CN106844323A (en) * | 2017-02-20 | 2017-06-13 | 济南浪潮高新科技投资发展有限公司 | A kind of entity construction method and device |
| CN107239479A (en) * | 2017-03-28 | 2017-10-10 | 阿里巴巴集团控股有限公司 | A kind of method and device of data storage and inquiry based on block chain |
| CN110109987A (en) * | 2018-04-03 | 2019-08-09 | 中建材信息技术股份有限公司 | A kind of agility data warehouse schema and its construction method and application |
| CN111260305A (en) * | 2018-11-30 | 2020-06-09 | 塔塔顾问服务有限公司 | Generating an extensible and customizable location-independent agile delivery model |
| CN112115212A (en) * | 2020-09-29 | 2020-12-22 | 中国工商银行股份有限公司 | Parameter identification method and device and electronic equipment |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103746854A (en) * | 2014-01-27 | 2014-04-23 | 国家电网公司 | Communication mechanism for information management layer and function application layer of communication network system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101075304A (en) * | 2006-05-18 | 2007-11-21 | 河北全通通信有限公司 | Method for constructing decision supporting system of telecommunication industry based on database |
-
2008
- 2008-03-21 CN CN2008101024027A patent/CN101256650B/en not_active Expired - Fee Related
Cited By (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010145194A1 (en) * | 2009-06-18 | 2010-12-23 | Du Bo | Enterprise application software producer |
| CN102033871A (en) * | 2009-09-25 | 2011-04-27 | 中国移动通信集团浙江有限公司 | Method and system for sharing public resource data by multiple information systems |
| CN102065066A (en) * | 2009-11-17 | 2011-05-18 | 中国移动通信集团广东有限公司 | Access device and access method for data service content of data service portals |
| CN102110111A (en) * | 2009-12-29 | 2011-06-29 | 北京大学 | Method and system for processing database operating command |
| CN102521232A (en) * | 2011-11-09 | 2012-06-27 | Ut斯达康通讯有限公司 | Distributed acquisition and processing system and method of internet metadata |
| CN102902763A (en) * | 2012-09-21 | 2013-01-30 | 东软集团股份有限公司 | Method and device for relating and retrieving information processing data and processing information tasks |
| CN103838574A (en) * | 2014-02-20 | 2014-06-04 | 浪潮集团山东通用软件有限公司 | General method for grouped summarizing of data tables |
| CN103942311A (en) * | 2014-04-21 | 2014-07-23 | 湖南深拓智能设备股份有限公司 | Multiplexing method of monitoring system variables |
| CN103942311B (en) * | 2014-04-21 | 2017-04-12 | 湖南深拓智能设备股份有限公司 | Multiplexing method of monitoring system variables |
| CN104484358A (en) * | 2014-12-02 | 2015-04-01 | 山东中创软件工程股份有限公司 | Process template displaying method and system |
| CN105989153A (en) * | 2015-03-02 | 2016-10-05 | 阿里巴巴集团控股有限公司 | Interaction method and device of database |
| CN104933664A (en) * | 2015-06-19 | 2015-09-23 | 中国铁道科学研究院电子计算技术研究所 | Passenger ticket data visualization method |
| WO2016206044A1 (en) * | 2015-06-25 | 2016-12-29 | Microsoft Technology Licensing, Llc | Extracting enterprise project information |
| CN107430607A (en) * | 2015-06-25 | 2017-12-01 | 微软技术许可有限责任公司 | Extract Enterprise Project information |
| CN105159920A (en) * | 2015-07-28 | 2015-12-16 | 卡斯柯信号有限公司 | Attribute tag based database access method |
| CN105607906B (en) * | 2015-12-18 | 2019-03-22 | 苏州奖多多科技有限公司 | A kind of service implementation method, device and electronic equipment |
| CN105607906A (en) * | 2015-12-18 | 2016-05-25 | 北京金山安全软件有限公司 | Service implementation method and device and electronic equipment |
| CN106844323A (en) * | 2017-02-20 | 2017-06-13 | 济南浪潮高新科技投资发展有限公司 | A kind of entity construction method and device |
| US10942921B2 (en) | 2017-03-28 | 2021-03-09 | Advanced New Technologies Co., Ltd. | Blockchain-based data storage and query method and device |
| CN107239479A (en) * | 2017-03-28 | 2017-10-10 | 阿里巴巴集团控股有限公司 | A kind of method and device of data storage and inquiry based on block chain |
| CN107239479B (en) * | 2017-03-28 | 2020-03-13 | 创新先进技术有限公司 | Block chain based data storage and query method and device |
| US11204915B2 (en) | 2017-03-28 | 2021-12-21 | Advanced New Technologies Co., Ltd. | Blockchain-based data storage and query method and device |
| US10713239B2 (en) | 2017-03-28 | 2020-07-14 | Alibaba Group Holding Limited | Blockchain-based data storage and query method and device |
| CN110109987A (en) * | 2018-04-03 | 2019-08-09 | 中建材信息技术股份有限公司 | A kind of agility data warehouse schema and its construction method and application |
| CN111260305A (en) * | 2018-11-30 | 2020-06-09 | 塔塔顾问服务有限公司 | Generating an extensible and customizable location-independent agile delivery model |
| CN112115212A (en) * | 2020-09-29 | 2020-12-22 | 中国工商银行股份有限公司 | Parameter identification method and device and electronic equipment |
| CN112115212B (en) * | 2020-09-29 | 2023-10-03 | 中国工商银行股份有限公司 | Parameter identification method and device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101256650B (en) | 2012-02-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101256650B (en) | Method and system for extracting enterprise data based on service entity | |
| US6810429B1 (en) | Enterprise integration system | |
| US7580946B2 (en) | Smart integration engine and metadata-oriented architecture for automatic EII and business integration | |
| CN100468396C (en) | Mapping architecture for arbitrary data models | |
| CN101690123B (en) | Apparatus, system, and method for a data server-managed web services runtime | |
| CN100580662C (en) | Heterogeneous report form integration and centralized management device and system | |
| US7984417B2 (en) | Meta-model information associated with an enterprise portal | |
| Dowler et al. | Table access protocol version 1.0 | |
| US8234308B2 (en) | Deliver application services through business object views | |
| KR100671506B1 (en) | A mobile middleware and a method for processing business logic using it | |
| US8656056B2 (en) | Web-enabled mainframe | |
| CN103299303A (en) | Extensible RDF databases | |
| WO2006026702A2 (en) | Methods and systems for semantic identification in data systems | |
| US20040181502A1 (en) | Generation of business intelligence entities from a dimensional model | |
| CN109241054A (en) | A kind of multimodal data library system, implementation method and server | |
| CN103914290A (en) | Operating command processing method and device | |
| Ma et al. | A template-based model transformation approach for deriving multi-tenant saas applications | |
| CN111966692A (en) | Data processing method, medium, device and computing equipment for data warehouse | |
| CN101604338A (en) | User-defined information query method of a kind of realization and device | |
| US20060224556A1 (en) | SQL interface for services | |
| Dowler et al. | IVOA Recommendation: Table Access Protocol Version 1.0 | |
| Borkar et al. | XML data services | |
| Kozankiewicz et al. | Integration of heterogeneous resources through updatable views | |
| Auth et al. | A software architecture for XML-based metadata interchange in data warehouse systems | |
| CN116521686B (en) | Dynamic data table processing method, device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20120215 Termination date: 20150321 |
|
| EXPY | Termination of patent right or utility model |