CN101826018B - Interactive development system and method for interface of network element management system - Google Patents
Interactive development system and method for interface of network element management system Download PDFInfo
- Publication number
- CN101826018B CN101826018B CN201010184119.0A CN201010184119A CN101826018B CN 101826018 B CN101826018 B CN 101826018B CN 201010184119 A CN201010184119 A CN 201010184119A CN 101826018 B CN101826018 B CN 101826018B
- Authority
- CN
- China
- Prior art keywords
- data
- request
- module
- layer
- interface
- 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.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 42
- 238000011161 development Methods 0.000 title claims abstract description 41
- 230000002452 interceptive effect Effects 0.000 title claims abstract description 10
- 238000012545 processing Methods 0.000 claims abstract description 151
- 230000002688 persistence Effects 0.000 claims abstract description 48
- 230000006870 function Effects 0.000 claims description 35
- 238000005538 encapsulation Methods 0.000 claims description 22
- 230000006978 adaptation Effects 0.000 claims description 21
- 238000006243 chemical reaction Methods 0.000 claims description 15
- 238000009826 distribution Methods 0.000 claims description 12
- 239000000203 mixture Substances 0.000 claims description 10
- 238000010276 construction Methods 0.000 claims description 8
- 238000013459 approach Methods 0.000 claims description 4
- 238000005516 engineering process Methods 0.000 abstract description 7
- 230000003993 interaction Effects 0.000 abstract description 6
- 238000012856 packing Methods 0.000 abstract 2
- 230000008569 process Effects 0.000 description 22
- 238000010586 diagram Methods 0.000 description 12
- 230000009471 action Effects 0.000 description 5
- 238000004364 calculation method Methods 0.000 description 5
- 238000013461 design Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 230000008901 benefit Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 239000000306 component Substances 0.000 description 3
- 230000004044 response Effects 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000003860 storage Methods 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 241001269238 Data Species 0.000 description 1
- 230000000712 assembly Effects 0.000 description 1
- 238000000429 assembly Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001149 cognitive effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 239000012141 concentrate Substances 0.000 description 1
- 239000008358 core component Substances 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000005520 cutting process Methods 0.000 description 1
- 230000004069 differentiation Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 208000037805 labour Diseases 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000037361 pathway Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 230000026683 transduction Effects 0.000 description 1
- 238000010361 transduction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses an interactive development system and a method for an interface of a element management system (EMS) so as to improve development efficiency of EMS. The system comprises: a presentation Layer used for acquiring a data object according to a request type and a request object in a user request, packing the request type and the data object into a processing request, then sending the request to a logic layer, and finally finishing interaction with the user according to a result of the processing request sent by the logic layer; the logic layer used for differentiating data trend, locally finishing data operation and/or sending a data operation order to a persistence layer according to the request type, and packing the first business data acquired locally and/or the second business data acquired by processing the data operation result fed back by the persistence layer into the result of the processing request; and the persistence layer used for finishing data operation according to the data operation order and acquiring data operation result. Compared with the prior art, the invention realizes the interactive development technology for component-based EMS interfaces and improves EMS development efficiency and code reusability.
Description
Technical field
The present invention relates to a kind of development system and method, relate in particular to a kind of Element management system (EMS) interface alternation development system and method.
Background technology
Along with the development of network technology and the continuous expansion of network size, user is to the demand of network also in continuous increase, and network management has become a vital technology in network Development, is that network is reliable, the guarantee of safety and high-speed cruising.
At present, network equipment provider both domestic and external reaches up to a hundred, and the device category of manufacture is very abundant, and unit type is varied, has met multiple application demand, is applicable to various environment.Huge in the face of quantity, how miscellaneous network equipment, design an extendible interface alternation System Framework flexibly, is the hot issue of current research with the comprehensive visual network management that realizes plurality of devices.
Model-view-controller (Model View Controller, MVC) forcibly make input, processing and the output of application program be separated from each other, make MVC application program be divided into three core components: model, view and controller, they process oneself task separately.
View (View) be user can see and can carry out with it mutual interface, how the user data that don't work changes, view is a kind of mode of exporting data and allowing user to operate.
Model (Model) represents the processing logic of business data and business.In three parts of MVC, model has maximum Processing tasks.Model and data independence, this also just means that a model can provide data for multiple views, the model code of once writing can be reused by multiple views, has improved the reusability of code.
Controller (Controller) is mainly used in receiving user's input and calls model and demand that view removes completing user.Controller does not do any logical process, does not export anything yet, and it just receives user's request, and which model of choice for use goes to process user's request, and determines result after treatment to use which view shows to user.
Fig. 1 is MVC transaction module schematic diagram in prior art.As shown in Figure 1, what first controller reception user proposed by view wants to carry out mutual user's request (User Action), and selects to ask corresponding model to process (Update1) with this user; Then model is responded and is processed user's request by service logic, and returns to result (Notify) to controller; Last controller selects according to result the view that (Update2) is corresponding, and by view, result data is showed to user.
Telecommunication management network (TMN) provides a set of total solution for the realization of telecommunication network management target.TMN model definition four management layers, be respectively Network Element Layer, network layer, O&M layer and operation layer, each management layer has corresponding management system.
Element management system (EMS, Ye Cheng producer webmaster or professional webmaster), configuration, resource and failure message on concern equipment.EMS is the system of one or more telecommunication network elements (NE) of management particular type, and the bottom that is in TMN model is Network Element Layer, has realized the management to the network equipment, is the basis of network management, is determining the service quality of Network.
The direct equipment oriented of EMS, and the Simple Network Management Protocols (SNMP) that adopt between equipment more, also have adopt serial ports even the mode such as privately owned management agreement of socket (SOCKET) manage.Mainly lay particular emphasis on the following aspects:
(1) configuration management of network element.
(2) collection of network element resources information.
(3) collection of network element failure information.
(4) collection of network element performance data.
Because client/server (C/S) pattern has the advantages such as data processing speed is fast, efficiency is high, and cyberrelationship is simple, and network bandwidth expense is little, thereby at exploitation architectural frameworks that adopt traditional C/S model when EMS, as shown in Figure 2 more.
As with the Element management system of equipment direct interaction, need to carry out comprehensive webmaster to equipment, this will distinguish the equipment of variety classes and model, carry out the design and development of difference in functionality point, thereby need to carry out different showing interfaces and data interaction for distinct device in the process of exploitation EMS.But because the network equipment in the communications field is of a great variety, model One's name is legion, makes developer's operation irregularity complexity and the workload of EMS huge, simultaneously again with a large amount of repeated labors.
Inventor studies by analysis, thinks that the MVC design framework of increasing income at present can not meet the functional development of EMS well, and reason is:
(1) Development Framework based on increasing income needs developer to have relatively wide the scope of one's knowledge, and these knowledge are too complicated, and developer is difficult to comprehensive grasp;
(2) upgrading of MVC design framework is too frequent, needs developer to spend a large amount of time and efforts and carrys out unceasing study understanding;
(3) application and development of enterprise-level needs a unified development platform, and to improve development efficiency and the quality of EMS, this has significantly improved cost of development.
In view of the problem of above existence, be necessary to provide a kind of EMS development system and method efficiently.
Summary of the invention
Technical matters to be solved by this invention, is to provide a kind of interface of network element management system interactive development system and method, to improve the development efficiency of EMS.
In order to solve the problems of the technologies described above, the invention provides a kind of interface of network element management system interactive development system, comprise presentation layer, logical layer and data persistence layer, wherein:
Described presentation layer, for receiving the user's request that comprises request type and request object, from interface display information configuration file, obtain data object according to described request type and request object, described request type and data object are packaged into the request of processing and send to described logical layer, and the processing request results sending according to described logical layer completes mutual with user;
Described logical layer, for described processing request is resolved, distinguishes data trend according to the details of described request type and data object, completes data manipulation and/or send data operation commands to described data persistence layer according to described request type in this locality; Be encapsulated in described processing request results and send to described presentation layer complete the second business datum that the first business datum that data manipulation obtains and/or the data manipulation result of processing described data persistence layer feedback obtain in this locality;
Described data persistence layer, for completing data manipulation according to described data operation commands and database and/or equipment, obtains described data manipulation result feedback to described logical layer.
Preferably, described presentation layer comprises interface assembly module, encapsulation/parsing module and processing module, wherein:
Described interface assembly module, be used for receiving described user's request, described user's request is sent to described encapsulation/parsing module, and described the first business datum and/or the second business datum that send for receiving described encapsulation/parsing module, described the first business datum and/or the second business datum are showed to user;
Encapsulation/parsing module, for obtain the interface display information configuration file of related network elements from NE type configuration file according to described request type and request object, from interface display information configuration file, obtain described data object, described request type and data object are encapsulated in described request object, described request object is sent to described processing module; The request object result also sending for receiving described processing module, from described request object result, parse described the first business datum and/or the second business datum, described the first business datum and/or the second business datum are sent to described interface assembly module;
Processing module, for described request object encapsulation is become to described processing request, described processing request is sent to described logical layer, and the described processing request results sending for receiving described logical layer, described processing request results is resolved to described request object result, described request object result is sent to described encapsulation/parsing module.
Preferably, described presentation layer further comprises:
Adaptation module, the special data sending for receiving described interface assembly, is converted to readable data by described special data and feeds back to described interface assembly module;
Wherein, described interface assembly module is further used for judging whether described the first business datum and/or the second business datum include special data, described special data to be sent to described adaptation module, and receive described readable data, by all the other content displayings except described special data in described readable data and described the first business datum and/or the second business datum to user.
Preferably, described logical layer comprises control command module, logic processing module and data processing module, wherein:
Described control command module, for receiving described processing request, resolves described processing request, obtains described request type and data object and sends to described logic processing module; Also send to described presentation layer for the described processing request results that described logic processing module is sent;
Described logic processing module, for distinguish data trend according to the details of described data object, when described data object is internal memory, send to described data processing module according to this request type structure local operation request, when described data object is database and/or equipment, send to described data processing module according to this request type construction data operation requests; Also send to described control command module for the processing request results that described data processing module is sent;
Described data processing module, for completing data manipulation according to described local operation request at described internal memory, obtains the first business datum, for described data operation request being processed into described data operation commands and sending to described data persistence layer; Also for the data manipulation result treatment of described data persistence layer feedback is become to described the second business datum, this first business datum and/or the second business datum are encapsulated in described processing request results and send to described logic processing module.
Preferably, described logical layer further comprises basic tool module and resource distribution module, wherein:
Described basic tool module, for completing public basic operational functions;
Described resource distribution module, for the internationalization processing of showing interface, the reading of picture file in equipment interface, database connects reading of information needed and reading of various resource distribution files.
Preferably, described data persistence layer comprises database interface module and device interface module, wherein:
Described database interface module, is connected with database, for completing data manipulation according to described data operation commands at described database, obtains data manipulation result feedback to described logical layer;
Described device interface module, is connected with equipment, for completing data manipulation according to described data operation commands on described equipment, obtains data manipulation result feedback to described logical layer.
In order to solve the problems of the technologies described above, the present invention also provides a kind of interface of network element management system mutual development approach, is applied to interface of network element management system interactive development system, and described system comprises presentation layer, logical layer and data persistence layer, and the method comprises:
Described presentation layer receives the user's request that comprises request type and request object, obtains data object according to described request type and request object from interface display information configuration file;
Described presentation layer is packaged into by described request type and data object the request of processing and sends to described logical layer;
Described logical layer is resolved described processing request, distinguishes data trend according to the details of described data object, completes data manipulation and/or send data operation commands to described data persistence layer according to described request type in this locality;
Described data persistence layer completes data manipulation according to described data operation commands and database and/or equipment, obtains described data manipulation result feedback to described logical layer;
Described logical layer by complete in this locality data manipulation obtain the first business datum and/or processing said data operating result obtain the second business datum be encapsulated in a processing request results, this processing request results is sent to described presentation layer;
Described presentation layer completes mutual with user according to described processing request results.
Preferably, described presentation layer obtains the step of data object from interface display information configuration file according to described user's request, comprising:
Described presentation layer obtains described interface display information configuration file according to described request type and request object from NE type configuration file, from described interface display information configuration file, obtains described data object.
Preferably, described NE type configuration file is write and is formed according to the configuration information of each network element, corresponding Profile Path and the interface internationalization file path of related names, Element management system version, network element that comprises network element;
Described interface display information configuration file is write and is formed according to the configuration feature point of each network element, the interface display information of all functions that comprise network element.
Preferably, described logical layer is resolved described processing request, distinguishes the step of data trend according to the details of resolving the described data object obtaining, and comprising:
Described logical layer is resolved described processing request, obtain described request type and data object, and from Element management system (EMS) Data Source configuration file, obtain the details of this data object according to data object, distinguish data trend according to the details of described data object, when described data object is internal memory, according to this request type structure local operation request, complete data manipulation in this locality; When described data object is database and/or equipment, send to described data persistence layer according to this request type construction data operational order.
Preferably, described EMS Data Source configuration file forms according to the data item message composition of each network element, comprises the conversion class of the type of described data object and the logical name of each data item, physics name, span, business datum and physical data.
Compared with prior art, the present invention is take MVC pattern as basis, make full use of that the visual development mode of C/S model and data processing speed are fast, efficiency high, realize assembly type EMS interface alternation development technique, the development efficiency of EMS and the reusability of code are improved, reduce developer's workload, improved dirigibility, stability and the robustness of EMS.
Other features and advantages of the present invention will be set forth in the following description, and, partly from instructions, become apparent, or understand by implementing the present invention.Object of the present invention and other advantages can be realized and be obtained by specifically noted structure in instructions, claims and accompanying drawing.
Accompanying drawing explanation
Accompanying drawing is used to provide a further understanding of the present invention, and forms a part for instructions, for explaining the present invention, is not construed as limiting the invention together with embodiments of the present invention.In the accompanying drawings:
Fig. 1 is MVC transaction module schematic diagram in prior art;
Fig. 2 is the architectural framework schematic diagram of C/S model in prior art;
Fig. 3 a is the composition schematic diagram of development system embodiment of the present invention;
Fig. 3 b is the composition schematic diagram of presentation layer in Fig. 3 a illustrated embodiment;
Fig. 3 c is the composition schematic diagram of logical layer in Fig. 3 a illustrated embodiment;
Fig. 3 d is the composition schematic diagram of data persistence layer in Fig. 3 a illustrated embodiment;
Fig. 3 e is Table interface schematic diagram in interface configuration file example of the present invention;
Fig. 3 f is List interface schematic diagram in interface configuration file example of the present invention;
Fig. 4 is the schematic flow sheet of development approach embodiment of the present invention.
Embodiment
Describe embodiments of the present invention in detail below with reference to drawings and Examples, to the present invention, how application technology means solve technical matters whereby, and the implementation procedure of reaching technique effect can fully understand and implement according to this.
It should be noted that, if do not conflicted, each feature in the embodiment of the present invention and embodiment can mutually combine, all within protection scope of the present invention.In addition, can in the computer system such as one group of computer executable instructions, carry out in the step shown in the process flow diagram of accompanying drawing, and, although there is shown logical order in flow process, but in some cases, can carry out shown or described step with the order being different from herein.
Fig. 3 a is the composition schematic diagram of development system embodiment of the present invention.As shown in Figure 3 a, this system embodiment mainly comprises presentation layer 310, logical layer 320 and data persistence layer 330, writing in data procedures:
Presentation layer 310, be connected with this logical layer 320, be used for receiving user's request, in this user's request, request type and request object are comprised, and from NE type configuration file, obtain the interface display information configuration file of related network elements according to request type and request object, from interface display information configuration file, obtain data object, request type and data object are packaged into the request of processing and send to logical layer 320, and the processing request results that sends of receive logic layer 320, and from this processing request results, parse the first business datum and/or the second business datum, this first business datum and/or the second business datum are showed to user, complete the data interaction with user, wherein this request type represents that this user's request is read data request or write data requests, if write data requests also comprises the data of wanting to write that user submits in request type, request object is such as being database or the outside equipment of local internal memory, outside, data interaction comprises to user and shows the data that read and/or receive the data that user will write,
Logical layer 320, be connected with this presentation layer 310 and data persistence layer 330, for receiving the processing request that this presentation layer 310 sends, this processing request is resolved and is obtained the request type and the data object that in this user's request, comprise, and from EMS Data Source configuration file, obtain the details of this data object according to data object, distinguish data trend according to the details of this data object, when this data object is internal memory, complete data manipulation (being divided into read data operation or data writing operation) according to this request type at local internal memory, (when read data operation, this first business datum is read data to obtain the first business datum, when data writing operation, this first business datum is the feedback data after write operation completes), when this data object is database or equipment, send to data persistence layer 330 according to request type generated data operational order, receive the data manipulation result that data persistence layer 330 feeds back, process this data manipulation result and obtain the second business datum, this first business datum and/or the second business datum are encapsulated in a processing request results, this processing request results is sent to presentation layer 310, wherein this request object is accompanied with the object information such as management information bank (mib) node name on table name or the equipment in memory address, database, the details of this data object comprise conversion class of logical name, physics name, span, business datum and the physical data of each data in the type of this data object and data object etc., in this data operation commands, comprise action type (this action type comprises read data operation or data writing operation),
Wherein, said network element type configuration file comprises the configuration file of all kinds of network elements related in EMS performance history, to write according to the configuration information such as model, function of each network element, corresponding Profile Path and the interface internationalization file path etc. of related names, EMS version, network element that comprises network element.In EMS performance history, different network elements has different configuration files, the difference with a series of network element due to function, model, and NE type configuration file may also can be different.
Above-mentioned interface display information configuration file is write and is formed according to the configuration feature point of each network element, the interface display information of all functions that comprised this network element.Developer can be according to the interface display information of the difference in functionality flexible configuration of different network elements (as read-write properties, the data adapter unit etc. of the pattern of interface display, a certain function point) and Data Source information.
Above-mentioned EMS Data Source configuration file forms according to the data item message composition of each network element, comprises the conversion class of the type of described data object and the logical name of each data item, physics name, span, business datum and physical data etc.; Developer can be according to concrete applying flexible be the appropriate logical name of each definition of data item, span and conversion class.
Also for whether including special data in the further request type that judges this user's request, (such as in the operation of writing data, the packet of wanting to write that user submits to contains special data to above-mentioned presentation layer 310; The data of wanting to write that user submits to are included in request type), if included, further the special data in request type is converted to the business datum that can directly operate and/or the business datum that can directly operate in internal memory, and then process the encapsulation of request in database or equipment.
Above-mentioned logical layer 320 is distinguished the data trend of this service data information, refer to logical layer 320 and judge that presentation layer 310 need to obtain the data of which kind of type, such as in reading data course, if need to obtain internal memory resident data, directly send reading command from internal memory, reading out data from internal memory, if need to obtain database data (physical data in database) and/or device data (physical data on equipment), send reading command to data persistence layer 330; Data persistence layer 330 obtains database data from database according to reading command, obtain device data from equipment, and database data and/or device data are fed back to logical layer 320.Logical layer 320, obtaining after the data (one or more in internal memory resident data, database data and device data) that read, is processed into processing request results by read data and sends to presentation layer 310.
Above-mentioned internal memory resident data is mainly divided into two large classes, one class situation is to be placed on the data in internal memory in order to increase data response speed, can be intermediate data, also can be before obtain and in current database data and/or the device data being temporarily stored in internal memory, conventionally according to demand, database data and/or device data are resided in to internal memory for the difference of function, so just do not need reading database and/or equipment continually; Another kind of situation is some complementary intermediate logic data and/or some constant data, and these data are used for identification data type, and type of data manipulation etc., simultaneously also for carrying out some logic judgement or processing.
Above-mentioned device data, is the physical data (comprising the special data on some equipment) on equipment, the data type that wherein this physical data for example defines in snmp protocol, wherein such as ip, mac address, timestamp etc. of this special data.
Above-mentioned database data, device data and internal memory resident data, some is identical data.Data on some equipment need write into Databasce or terminate-and-stay-resident according to demand; A data part in database is carried out appliance-originated, is configuration data or resource data on equipment, and a part is the required data of webmastering software; Some data of database also need terminate-and-stay-resident sometimes.Such as in a concrete application, functions of the equipments need to read some parameter, these parameters are generally by obtaining alternately with equipment, sometimes parameter is changeless constant, that just can directly obtain from internal memory, or from database or equipment, take out direct terminate-and-stay-resident, conveniently often use.When need to increase the data in equipment, when modification or deletion action, just first carry out alternately data manipulation with equipment, after success, revise corresponding internal memory resident data or database data, some operation does not need database data and device data to unify immediately, when needs carry out when synchronous, just the data in equipment are carried out to data with the corresponding data in database and synchronize, reach the unitarity of data, be generally as the criterion with device data.
As shown in Figure 3 b, presentation layer 310 mainly comprises interface assembly module 311, encapsulation/parsing module 312, processing module 313 and adaptation module 314, wherein:
Interface assembly module 311, be used for receiving user's request, this user's request is sent to encapsulation/parsing module 312, and receive encapsulation/parsing module 312 this first business datum and/or the second business datum that send, be further used for judging in this first business datum and/or the second business datum and whether comprise special data, comprise this special data is sent to adaptation module 314, receive the readable data that adaptation module 314 is fed back, by all the other content displayings except this special data in this readable data and this first business datum and/or the second business datum to user (prerequisite that sends to adaptation module 314 to call in other words adaptation module 314 this special data is to have configured the adaptation module 314 that the conversion of this special data need to be called in interface display information configuration file),
Encapsulation/parsing module 312, be connected with interface assembly module 311, the user's request sending for reception interface assembly module 311, and from NE type configuration file, obtain the interface display information configuration file of related network elements according to request type and request object, from interface display information configuration file, obtain data object, request type and data object are encapsulated in request object, this request object is sent to processing module 313; The request object result also sending for receiving processing module 313, and from request object result, parse this first business datum and/or the second business datum, this first business datum and/or the second business datum are sent to interface assembly module 311;
Processing module 313, is connected with encapsulation/parsing module 312, and the request object sending for receiving encapsulation/parsing module 312 is packaged into by the request type of request object and data object the request of processing, and this processing request is sent to logical layer 320; The processing request results also sending for receive logic layer 320, and this processing request results is resolved to request object result, this request object result is sent to encapsulation/parsing module 312;
Above-mentioned interface assembly module 311 comprises equipment interface module and function interface module, wherein equipment interface module is for determining the equipment interface assembly such as duty of board and port on equipment profile and equipment, by assisting of adaptation module 314, can on display device, there be how many slots, have how many boards and port etc.; Dissimilar board and the profile of port are generally not identical; Wherein the duty of board and port can be distinguished with pilot lamp; The wherein function interface assembly with configuration feature of function interface module for determining that equipment is supported, by assisting of adaptation module 314, can and/or receive the data that user will write to user's display data; Configuration feature is wherein mainly the configuration of functions of the equipments value, such as whether port enables, the arranging etc. of port bandwidth, and some demonstrating data information or and user carry out mutual interface (as button, text box, choice box etc.); Wherein this equipment refers to user and in network management system, selects certain equipment of managing, network management system can be added many moneys equipment, every a unit type has corresponding interface display information configuration file, just the function that equipment can be supported when user selects to manage certain equipment shows according to the form of tree, click different functions and can show different interface (being represented by different function interface assemblies), which function interface assembly different function points uses go to represent and is configured in interface display information configuration file.
Above-mentioned adaptation module 314 is mainly used in showing interface, business datum is recombinated or is changed according to different function application, to facilitate interface to carry out data interaction according to the mode of function point.Here said business datum can be understood as intermediate data, i.e. data in logical layer.
The basic composition of general networking equipment comprises: cabinet, board, slot, port and pilot lamp etc., so be divided into chassis component, board assembly, slot component, port assembly and indicating lamp component etc. in equipment interface module, basic configuration data (such as position and directional data, the acquiescence of image data, port show data etc.) in each assembly writes in xml configuration file, easy-to-look-up; Take Java object-oriented method as example, each assembly can abstractly be each java class in realization, for example: board (CardObject.java), port (PortObject.java), pilot lamp (LampObject.java) etc.;
The kind of above-mentioned function interface assembly is diversified, generally comprises chart assembly, list/table row assembly, shows tree assembly, selects assembly and the display module for some special datas (IP address, Mac address and time stamp data etc.); Special data is wherein when being IP address, suppose that the IP address on equipment is: 192,-88,20,-54 (this be IP address a kind of need conversion type, that have is exactly IP address (192.168.20.202) intuitively, does not need conversion), the readable IP address after conversion is: 192.168.20.202; Special data when being Mac address, supposes that the Mac address (being scale-of-two on equipment, here in order conveniently to be write as decimal representation) on equipment is: (17,-35,62 ,-60,-59,107), conversion after readable Mac address be: 11:dd:3e:c4:c5:6b; When special data is timestamp, suppose that the time stamp data on equipment is :-68,24,-77,50,7,-95,-10 ,-40 (by the number of seconds that plays 17: 10: 13.639 on the 1st January in 2000 0: 0: 0 on the 1st January in 1900 of 64 binary representations), the readable time after conversion is: Sat Jan 0117:10:13.639 UTC 2000.The existence of above-mentioned adaptation module 314, makes user's various data that arrangement for reading reports intuitively.When the data that report due to equipment are a lot of, do not have readable, not necessarily can direct reading data for daily life, above-mentioned adaptation module 314 be for these are not had readable data be converted to can direct cognitive data so that user reads.
As shown in Figure 3 c, logical layer 320 mainly comprises control command module 321, logic processing module 322, data processing module 323, basic tool module 324 and resource distribution module 325, in reading data course:
Control command module 321, is connected with presentation layer 310, the processing request sending for receiving presentation layer 310, and resolve processing request, obtain request type and data object wherein, request type and data object are sent to logic processing module 322; Also send to presentation layer 310 for the processing request results that logic processing module 322 is sent;
Logic processing module 322, with control command module 321, data processing module 323, basic tool module 324 is connected with resource distribution module 325, be mainly used in receiving request type and the data object that control command module 321 sends, and from EMS Data Source configuration file, obtain the details of this data object according to data object, distinguish data trend according to the details of data object, if this data object is internal memory, send to data processing module 323 according to this request type structure local operation request, if this data object is database and/or equipment, send to data processing module 323 according to request type construction data operation requests, also send to control command module 321 for the processing request results that data processing module 323 is sent,
Data processing module 323, be connected with data persistence layer 330 and logic processing module 322, for the local operation request sending according to logic processing module 322, in internal memory, complete data manipulation, obtain the first business datum, the data operation request that logic processing module 323 is sent is processed into data operation commands, and this data operation commands is sent to data persistence layer 330, in data writing operation process, in this data operation commands, include the physical data that need to send to database or equipment; The data manipulation result of also feeding back for receiving data persistence layer 330, includes physical data and special data in this data manipulation result, and data manipulation result treatment is become to the second business datum; Also, for this first business datum and/or the second business datum are encapsulated in to processing request results, this processing request results is sent to logic processing module 322; The data type of definition in for example Simple Network Management Protocol of physical data wherein (SNMP), wherein such as ip, mac address, timestamp etc. of this special data.
Such as the read operation to database or equipment, 323 of data processing modules issue data acquisition order to data persistence layer 330 and go to obtain data in database or equipment; If write operation sends data write order to data persistence layer 330, in this data write order, include data value (for example write device of write operation, data value comprises the OID value (unique identification of mib node) of mib node in equipment and wants the data value of write device, OID and value are one to one), and will write into Databasce or equipment in the physical data that is converted in database or equipment of data value send to data persistence layer 330;
Basic tool module 324, is connected with logic processing module 322, has been mainly used in some public basic operational functions, the parsing of for example host-host protocol and encapsulation, the serializing of various objects, data base read-write operation, the reading and the operation such as the read-write of system journal of the configuration files such as xml;
Resource distribution module 325, be connected with logic processing module 322, be mainly used in the internationalization processing of interface display, in equipment interface, picture file reads, database connects reading with the resource distributions such as (comprising data processing module 323 configuration files, equipment mib data configuration file and interface display configuration file etc.) of reading of various resource distribution files of information needed and operates, and generally coordinates other modules to use.
The main process (take read and write data storehouse or equipment as example, not comprising the part of distinguishing data trend) that system embodiment of the present invention reads and writes data below:
(1) read data (looking into operation):
When clicking function point in EMS management system, user (for example to check the base attribute of equipment, as the attribute such as software version, manufacturer) time, presentation layer 310 receives user's request, call the data object that corresponding interface display assembly obtains request, and data object is encapsulated in request object and asks to send to logical layer 320 by processing.
Logical layer 320 is processed request by control command module parses after receiving the request of processing, and send the result of parsing to logic processing module, logic processing module gets and request is converted to physical data (may be the logic table name that physics table name is corresponding in request, logical name need to be converted to physics name) after request and sends data persistence layer 330 to.
After data persistence layer 330 receives request command, generated data obtains order (the SNMP order of data base manipulation statement or operating equipment) operating database or equipment, and send data manipulation result (physical data getting) to logical layer 320, logical layer 320 by the physical data receiving be converted to business datum (for special data can calling data processing module change) and by business data transmission to presentation layer, presentation layer 310 shows user by showing interface assembly and the business datum (calling adaptation module 314 need to be converted to the discernible readable data of user time changes) receiving.
(2) write data (operation such as increasing, delete, change):
When user opens function point in EMS management system, add, for example, when modification or deletion action (adding or delete the size etc. of the control flow of transduction pathway, certain port of modification equipment for device port), presentation layer 310 is by adding, revise or delete interface reception user's write operation requests order, request command (is comprised to the data value of write operation, these data values can be the data after changing by adaptation module, belong to business datum) send to logical layer 320.Control command module in logical layer 320 receives and analysis request order, send the order after resolving to logic processing module, the business datum that logic processing module will issue equipment or database is converted to physical data (for special data calling data processing module), and physical data is included in the order that sends data persistence layer 330 to, transfers to data persistence layer 330.
For write operation, while being generally write device or database success, upgrade internal storage data simultaneously, in internal memory, mostly deposit the device data or the database data that often read, facilitate data to read, improve response speed; Having sub-fraction is the internal memory resident data for logical process, just can directly change internal storage data in the time that write operation relates to these data.
Realize the differentiation to business datum in logic processing module 322, business datum required presentation layer 310 is divided into internal memory resident data, database data and device data, simultaneously to database data and device data, and need the special data calling data processing module 323 of special processing to carry out data conversion treatment; Such data are divided with regard to clear and definite logical process object, have improved data processing and response speed.
Above-mentioned mib has comprised all management information on the network equipment, is not the database of a physics, but the notional set of management information.Each function on the network equipment can be regarded a mib in management information bank as, and mib node is certain function point in a function.For example a function need to arrange 5 attributes, and each attribute is exactly a mib node, and whole function is just made up of 5 mib nodes, and whole function is exactly a mib, and the information on the network equipment is just abstracted into the mib storehouse of a lot of mib compositions.
When interface display, control command module is by the corresponding interface assembly of resource distribution module 325 initialization in xml configuration file and logical layer 320, and obtain corresponding readable data by the adaptation module 314 in presentation layer 310, readable data is showed to user.
The logical process that logic processing module 322 is wherein carried out, comprise the logical process that some are special, for example, such as when certain switch enable (opening), which data item could show or which function just available, in the time that switch forbids (cutting out), which data do not show or which function unavailable; It is subordinated to logic processing module, calls etc. in the time having specific logical to process.
Above-mentioned internationalization refers to that interface shows different interface languages according to the operating system of different language, for example, after NE Explorer being installed in the windows of Chinese version operating system, will show Chinese interface, after NE Explorer being installed in the windows of English edition operating system, will show English interface, this is to show for the user of the use different language to different nationalities provides different Language Interface.
As shown in Figure 3 d, data persistence layer 330 mainly comprises database interface module 331 and device interface module 332, in reading data course:
Based on modular EMS interface alternation development system embodiment, take full advantage of the design philosophy of the low coupling of high cohesion in MVC framework, between modules, be all loosely-coupled, in exploitation and maintenance, can need to select suitable module to unify encapsulation according to EMS exploitation, simplify development process, reduce exploitation complexity, improve development efficiency.
System embodiment of the present invention is writing in data procedures, data be wherein divided into read and write database data, equipment issues data and internal memory resident data; Internal memory resident data is processed by logic processing module 322, reads and writes database data and equipment and issues data and processed by database interface module 331 and device interface module 332 respectively.
System embodiment of the present invention is processed interface display to separate in the mode of module with logic business, the mode of simultaneously interface module being selected with configuration is added the exhibition method of configuration interface module (can) simultaneously, and Data Source, adaptation module 314 and interface assembly loader etc. to selected interface module configuration interactive.
System embodiment of the present invention is processed logic business to separate in the mode of module with data processing, simultaneously for data processing module 323 (selecting the data processing module 323 of acquiescence in situation about not configuring) and the specific logical of logic business function point configuration process special data are processed adapter.
Interface configuration file example below:
<Dialog?Name＝″VLAN_CONVERTOR″Class＝″javax.swing.JDialog″Height＝″365″Width＝″645″SaveBtn＝″true″>
<Panel?Border＝″none″Name＝″rcQinQVlanMapPortTable″Toolbar＝″show″Buttonbar＝″show″AddBtn＝″show″DeleteBtn＝″show″ModifyBtn＝″hide″MaxColuWidth＝″200″Class＝″com.raisecom.ems.templet.client.panel.SnmpTablePanel″TableName＝″rcQinQVlanMapPortTable″/>
</Dialog>
EMS Data Source information instances (MIB configuration information):
<MibTable?Name＝″rcQinQVlanMapPortTable″Type＝″Table″ModifyRefresh＝″true″>
<MibNode?Logic＝″rcPortIndex″Physics＝″rcPortIndex″Max＝″26″Min＝″1″OrderType＝″Integer″Access＝″noaccess″/>
<MibNode?Logic＝″rcQinQVlanMapIndex″Physics＝″rcQinQVlanMapIndex″OrderType＝″Integer″Access＝″noaccess″IndexCollecter＝″com.raisecom.ems.ros4.client.collecter.QinQVlanMapIndexCollecter″/>
<MibNode?Logic＝″rcQinQVlanMapCeVlanList″Physics＝″rcQinQVlanMapCeVlanList″>
<MibNodeAdapter?Class＝″com.raisecom.ems.ros4.server.adapter.VlansetAdapter″/>
<ValueAdapter?Class＝″com.raisecom.ems.templet.client.adapter.VlansetValueAdapter″/>
</MibNode>
<MibNode?Logic＝″rcQinQVlanMapPeVlanList″Physics＝″rcQinQVlanMapPeVlanList″>
<MibNodeAdapter?Class＝″com.raisecom.ems.ros4.server.adapter.VlansetAdapter″/>
<ValueAdapter?Class＝″com.raisecom.ems.templet.client.adapter.VlansetValueAdapter″/>
</MibNode>
</MibTable>
Above-mentioned configuration file is mainly described with extend markup language (XML) file.
Content in label <Dialog> and </Dialog> is the descriptor of an interface dialog box, for example: Name (title that dialog box shows), Class (loading classes), Height (height of dialog box), Width (dialog box wide), SaveBtn (in dialog box, whether save button shows, TRUE is for showing, false is for hiding).
What in label <Panel>, describe is the displaying contents in dialog box, for example: Border (Show Styles of table), Name (display Name of table), (whether tool bar shows Toolbar, show is for showing, hide is for hiding), (whether button bar shows Buttonbar, show is for showing, hide is for hiding), AddBtn/DeleteBtn/ModifyBtn (increases, whether show) if deleting and revising button, MaxColuWidth (the maximum display width being listed as in table), Class (loading classes), TableName (table data are source data object title).
Which row is the details that in label <MibTable> and </MibTable> are Data Source table (comprise, the maximal value of column mean and minimum value, the configuration information of adapter and special data conversion etc.), for example: (table name claims Name, identical with the TableName in label Panel), Type (generally has two kinds: Table and List, Table represents, List represents a line item, interface is respectively as shown in Fig. 3 e and Fig. 3 f, " NTP system variable " shown in Fig. 3 f is aforesaid List, " long-range ntp server table " and " clock filtering table " are aforesaid Table), ModifyRefresh (refresh data whether when data modification in table, true is for refreshing, false is not for refreshing).
Row in each <MibNode> label representative table, for example: Logic (logical name), Physics (physics name), Max/Min (maximum/minimum value), OrderType (sort type), whether Access (allows access, noaccess: do not allow; ROnly: read-only; RWrite: read-write), IndexCollecter (index loading classes).
The conversion class (in the data processing module of logical layer) of the physical data that what the Class in label <MibNodeAdapter> represented is uses in logical layer and business datum mutual election conversion.
Interface assembly module that what the Class in label <ValueAdapter> represented is is used for business datum to be converted into the adapter class (being arranged in the adaptation module of presentation layer) of readable data.
Above-mentioned is that a profile instance of interface configuration file and EMS Data Source configuration file (is the part of this profile instance, be not whole), brief description in configuration file each field identification meaning and how to be configured, wherein the value of field can be carried out flexible configuration according to demand.Can utilize configuration file to configure relevant display mode according to different applicable cases, comprise the configuration of adapter etc.
Fig. 4 is the schematic flow sheet of development approach embodiment of the present invention, and this embodiment is in order to illustrate the process of reading out data in performance history of the present invention.In conjunction with system embodiment shown in Fig. 3 a, the embodiment of the method shown in Fig. 4 mainly comprises the steps:
Step S410, presentation layer receives user's request, and user's request comprises request type and request object, and from interface display information configuration file, obtains data object according to request type and request object in user's request;
Step S420, presentation layer is packaged into by request type and data object the request of processing and sends to logical layer;
Step S430, logical layer is resolved processing request, distinguishes data trend according to the details of resolving the data object obtaining, and completes data manipulation and/or sends data operation commands to data persistence layer according to resolving the request type obtaining in this locality;
Step S440, data persistence layer completes data manipulation according to data operation commands and database and/or equipment, obtains data manipulation result feedback to logical layer;
Step S450, logical layer by complete in this locality data manipulation obtain the first business datum and/or deal with data operating result obtain the second business datum be encapsulated in a processing request results, this processing request results is sent to presentation layer;
Step S460, presentation layer completes mutual with user according to processing request results.
Above-mentioned presentation layer obtains the step of data object from interface display information configuration file according to user's request, comprising:
Presentation layer obtains interface display information configuration file according to request type and request object in user's request from NE type configuration file, from interface display information configuration file, obtains data object.
Above-mentioned NE type configuration file is write and is formed according to the configuration information of each network element.
Above-mentioned logical layer is resolved processing request, distinguishes the step of data trend according to the details of resolving the data object obtaining, and comprising:
Logical layer is resolved processing request, obtain request type and data object, and from EMS Data Source configuration file, obtain the details of this data object according to data object, distinguish data trend according to the details of data object, when data object is internal memory, according to this request type structure local operation request, complete data manipulation in this locality; When data object is database and/or equipment, send to data persistence layer according to this request type construction data operational order.
Technical solution of the present invention is according to the present situation of current network device management, for the actual conditions of EMS exploitation, modular EMS interface alternation development system and the method based on the MVC that propose with modular development scheme, the exploitation of EMS interface alternation is separated with modular mode, solve the development problem of the EMS of the network equipment that kind and model are various, reduce complexity and the workload of exploitation, improved dirigibility, stability and the robustness of reusability, development efficiency and the EMS system of program.Like this, be more conducive to the commercialization of EMS, be more conducive to sharing out the work and helping one another of development teams.
It should be noted that, can in the computer system such as one group of computer executable instructions, carry out in the step shown in the process flow diagram of accompanying drawing, and, although there is shown logical order in flow process, but in some cases, can carry out shown or described step with the order being different from herein.In addition, those skilled in the art should be understood that, above-mentioned of the present invention each module or each step can realize with general calculation element, they can concentrate on single calculation element, or be distributed on the network that multiple calculation elements form, alternatively, they can be realized with the executable program code of calculation element, thereby, they can be stored in memory storage and be carried out by calculation element, or they are made into respectively to each integrated circuit modules, or the multiple modules in them or step are made into single integrated circuit module to be realized.Like this, the present invention is not restricted to any specific hardware and software combination.
Although the disclosed embodiment of the present invention as above, the embodiment that described content just adopts for the ease of understanding the present invention, not in order to limit the present invention.Technician in any the technical field of the invention; do not departing under the prerequisite of the disclosed spirit and scope of the present invention; can do any modification and variation what implement in form and in details; but scope of patent protection of the present invention, still must be as the criterion with the scope that appending claims was defined.
Claims (8)
1. an interface of network element management system interactive development system, comprises presentation layer, logical layer and data persistence layer, it is characterized in that:
Described presentation layer, for receiving the user's request that comprises request type and request object, from interface display information configuration file, obtain data object according to described request type and request object, described request type and data object are packaged into the request of processing and send to described logical layer, and the processing request results sending according to described logical layer completes mutual with user;
Described logical layer, for described processing request is resolved, distinguish data trend according to the details of described request type and data object, when described data object is internal memory, according to this request type structure local operation request, complete data manipulation in this locality, when described data object is database and/or equipment, send to described data persistence layer according to this request type construction data operational order; Be encapsulated in described processing request results and send to described presentation layer complete the second business datum that the first business datum that data manipulation obtains and/or the data manipulation result of processing described data persistence layer feedback obtain in this locality;
Described data persistence layer, for completing data manipulation according to described data operation commands and database and/or equipment, obtains described data manipulation result feedback to described logical layer;
Described presentation layer comprises interface assembly module, encapsulation/parsing module and processing module, wherein:
Described interface assembly module, be used for receiving described user's request, described user's request is sent to described encapsulation/parsing module, and described the first business datum and/or the second business datum that send for receiving described encapsulation/parsing module, described the first business datum and/or the second business datum are showed to user;
Encapsulation/parsing module, for obtain the interface display information configuration file of related network elements from NE type configuration file according to described request type and request object, from interface display information configuration file, obtain described data object, described request type and data object are encapsulated in described request object, described request object is sent to described processing module; Wherein, described NE type configuration file is write and is formed according to the configuration information of each network element, corresponding Profile Path and the interface internationalization file path of related names, Element management system version, network element that comprises network element; Described interface display information configuration file is write and is formed according to the configuration feature point of each network element, the interface display information of all functions that comprise network element; The request object result also sending for receiving described processing module, from described request object result, parse described the first business datum and/or the second business datum, described the first business datum and/or the second business datum are sent to described interface assembly module;
Processing module, for described request object encapsulation is become to described processing request, described processing request is sent to described logical layer, and the described processing request results sending for receiving described logical layer, described processing request results is resolved to described request object result, described request object result is sent to described encapsulation/parsing module.
2. system according to claim 1, is characterized in that, described presentation layer further comprises:
Adaptation module, the special data sending for receiving described interface assembly, is converted to readable data by described special data and feeds back to described interface assembly module;
Wherein, described interface assembly module is further used for judging whether described the first business datum and/or the second business datum include special data, described special data to be sent to described adaptation module, and receive described readable data, by all the other content displayings except described special data in described readable data and described the first business datum and/or the second business datum to user.
3. system according to claim 1, is characterized in that, described logical layer comprises control command module, logic processing module and data processing module, wherein:
Described control command module, for receiving described processing request, resolves described processing request, obtains described request type and data object and sends to described logic processing module; Also send to described presentation layer for the described processing request results that described logic processing module is sent;
Described logic processing module, for distinguish data trend according to the details of described data object, when described data object is internal memory, send to described data processing module according to this request type structure local operation request, when described data object is database and/or equipment, send to described data processing module according to this request type construction data operation requests; Also send to described control command module for the processing request results that described data processing module is sent;
Described data processing module, for completing data manipulation according to described local operation request at described internal memory, obtains the first business datum, for described data operation request being processed into described data operation commands and sending to described data persistence layer; Also for the data manipulation result treatment of described data persistence layer feedback is become to described the second business datum, this first business datum and/or the second business datum are encapsulated in described processing request results and send to described logic processing module.
4. system according to claim 3, is characterized in that, described logical layer further comprises basic tool module and resource distribution module, wherein:
Described basic tool module, for completing public basic operational functions;
Described resource distribution module, for the internationalization processing of showing interface, the reading of picture file in equipment interface, database connects reading of information needed and reading of various resource distribution files.
5. system according to claim 1, is characterized in that, described data persistence layer comprises database interface module and device interface module, wherein:
Described database interface module, is connected with database, for completing data manipulation according to described data operation commands at described database, obtains data manipulation result feedback to described logical layer;
Described device interface module, is connected with equipment, for completing data manipulation according to described data operation commands on described equipment, obtains data manipulation result feedback to described logical layer.
6. the mutual development approach of interface of network element management system, is applied to interface of network element management system interactive development system, and described system comprises presentation layer, logical layer and data persistence layer, it is characterized in that, the method comprises:
Described presentation layer receives the user's request that comprises request type and request object, obtains data object according to described request type and request object from interface display information configuration file;
Described presentation layer is packaged into by described request type and data object the request of processing and sends to described logical layer;
Described logical layer is resolved described processing request, distinguish data trend according to the details of described data object, when described data object is internal memory, according to this request type structure local operation request, complete data manipulation in this locality, when described data object is database and/or equipment, send to described data persistence layer according to this request type construction data operational order;
Described data persistence layer completes data manipulation according to described data operation commands and database and/or equipment, obtains described data manipulation result feedback to described logical layer;
Described logical layer by complete in this locality data manipulation obtain the first business datum and/or processing said data operating result obtain the second business datum be encapsulated in a processing request results, this processing request results is sent to described presentation layer;
Described presentation layer completes mutual with user according to described processing request results;
Described presentation layer obtains the step of data object from interface display information configuration file according to described user's request, comprising:
Described presentation layer obtains described interface display information configuration file according to described request type and request object from NE type configuration file, from described interface display information configuration file, obtains described data object;
Described NE type configuration file is write and is formed according to the configuration information of each network element, corresponding Profile Path and the interface internationalization file path of related names, Element management system version, network element that comprises network element;
Described interface display information configuration file is write and is formed according to the configuration feature point of each network element, the interface display information of all functions that comprise network element.
7. method according to claim 6, is characterized in that, described logical layer is resolved described processing request, distinguishes the step of data trend according to the details of resolving the described data object obtaining, and comprising:
Described logical layer is resolved described processing request, obtain described request type and data object, and from Element management system EMS Data Source configuration file, obtain the details of this data object according to data object, distinguish data trend according to the details of described data object, when described data object is internal memory, according to this request type structure local operation request, complete data manipulation in this locality; When described data object is database and/or equipment, send to described data persistence layer according to this request type construction data operational order.
8. method according to claim 7, is characterized in that:
Described EMS Data Source configuration file forms according to the data item message composition of each network element, comprises the conversion class of the type of described data object and the logical name of each data item, physics name, span, business datum and physical data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010184119.0A CN101826018B (en) | 2010-05-20 | 2010-05-20 | Interactive development system and method for interface of network element management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010184119.0A CN101826018B (en) | 2010-05-20 | 2010-05-20 | Interactive development system and method for interface of network element management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101826018A CN101826018A (en) | 2010-09-08 |
| CN101826018B true CN101826018B (en) | 2014-05-14 |
Family
ID=42689950
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010184119.0A Expired - Fee Related CN101826018B (en) | 2010-05-20 | 2010-05-20 | Interactive development system and method for interface of network element management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101826018B (en) |
Families Citing this family (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104281441B (en) * | 2013-07-09 | 2018-11-23 | 腾讯科技（深圳）有限公司 | Data extraction method and device based on MVC |
| CN103488534A (en) * | 2013-09-23 | 2014-01-01 | 浪潮集团山东通用软件有限公司 | Method for enabling business logic layer to feed back control information to presentation layer |
| WO2015100655A1 (en) * | 2013-12-31 | 2015-07-09 | 北京新媒传信科技有限公司 | Interactive communication software implementation method and implementation platform |
| CN105745620B (en) * | 2013-12-31 | 2019-04-30 | 北京新媒传信科技有限公司 | The implementation method and realization platform of software architecture |
| CN104765596A (en) * | 2014-01-08 | 2015-07-08 | 腾讯科技（深圳）有限公司 | Request handling method and device |
| CN106055590A (en) * | 2016-05-23 | 2016-10-26 | 环球大数据科技有限公司 | Power grid data processing method and system based on big data and graph database |
| CN106919638A (en) * | 2016-07-14 | 2017-07-04 | 阿里巴巴集团控股有限公司 | Data persistence processing method, apparatus and system |
| CN106484899B (en) * | 2016-10-21 | 2022-02-22 | 用友网络科技股份有限公司 | Column information dynamic loading display method based on scene |
| CN108287854B (en) * | 2017-01-10 | 2021-06-22 | 网宿科技股份有限公司 | Method and system for data persistence in stream calculation |
| CN107528974A (en) * | 2017-08-22 | 2017-12-29 | 世纪禾光科技发展（北京）有限公司 | request processing method, device, computing device and storage medium |
| CN111198899B (en) * | 2018-11-19 | 2022-12-13 | 中移(苏州)软件技术有限公司 | Development system and method for entity rendering in application program |
| CN109769156B (en) * | 2019-03-28 | 2022-04-12 | 瑞斯康达科技发展股份有限公司 | Visual implementation method and device of GPON business model |
| CN109992263B (en) | 2019-04-05 | 2022-09-13 | 腾讯科技（深圳）有限公司 | Method and device for executing visual programming |
| CN114217899B (en) * | 2021-12-15 | 2023-10-17 | 深圳平安智慧医健科技有限公司 | Data persistence method, device, electronic equipment and storage medium |
| CN115203176B (en) * | 2022-09-15 | 2023-03-07 | 太平金融科技服务(上海)有限公司深圳分公司 | Database operation method, device, equipment, storage medium and program product |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1728700A (en) * | 2004-07-26 | 2006-02-01 | 中兴通讯股份有限公司 | Web telecommunication network management system based on 'struts' architecture, and method |
| EP1819094A1 (en) * | 2005-11-28 | 2007-08-15 | Huawei Technologies Co., Ltd. | Script language based network device configuration management system and method |
| CN101383718A (en) * | 2007-09-05 | 2009-03-11 | 中兴通讯股份有限公司 | Method and device for network management system to share a part of pause rule |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH11298475A (en) * | 1998-04-08 | 1999-10-29 | Oki Electric Ind Co Ltd | System data maintenance processing method in network management system and storage medium recording its program |
| JP3790173B2 (en) * | 2002-03-01 | 2006-06-28 | 日本電信電話株式会社 | Network management method and network management system used therefor |
-
2010
- 2010-05-20 CN CN201010184119.0A patent/CN101826018B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1728700A (en) * | 2004-07-26 | 2006-02-01 | 中兴通讯股份有限公司 | Web telecommunication network management system based on 'struts' architecture, and method |
| EP1819094A1 (en) * | 2005-11-28 | 2007-08-15 | Huawei Technologies Co., Ltd. | Script language based network device configuration management system and method |
| CN101383718A (en) * | 2007-09-05 | 2009-03-11 | 中兴通讯股份有限公司 | Method and device for network management system to share a part of pause rule |
Non-Patent Citations (4)
| Title |
|---|
| JP特开2003-258796A 2003.09.12 |
| JP特开平11-298475A 1999.10.29 |
| 周丹 等.基于Web的网管系统的设计与实现.《广东通信技术》.2008,37-41. |
| 基于Web的网管系统的设计与实现;周丹 等;《广东通信技术》;20081231;37-41 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101826018A (en) | 2010-09-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101826018B (en) | Interactive development system and method for interface of network element management system | |
| CN106445484B (en) | The method and system of data tracking are realized by Software Development Kit | |
| US7120896B2 (en) | Integrated business process modeling environment and models created thereby | |
| CN106528129A (en) | Web application interface generation system and method | |
| CN101847100B (en) | Method for expanding software application and device | |
| CN100580622C (en) | Telecommunication region modeling tool based on unified modeling language and modeling method | |
| CN102034152B (en) | The method for integrating of heterogeneous software system data and system based on SOA framework | |
| CN113508403A (en) | System and method for interoperable communication of automation system components with multiple information sources | |
| CN103645908B (en) | Full life circle development achievement system of intemetware | |
| CN103701633B (en) | Setup and maintenance system of visual cluster application for distributed search SolrCloud | |
| CN111176645A (en) | Power grid big data application-oriented data integration management system and implementation method thereof | |
| CN110324169A (en) | A kind of method and apparatus of interface management | |
| EP2661014A1 (en) | Polling sub-system and polling method for communication network system and communication apparatus | |
| JP2005512346A (en) | Network element management system | |
| CN101304331B (en) | Platform for uniting north direction interfaces and starting method thereof | |
| CN111641521B (en) | Method for deploying big data clusters on cloud based on Ambari | |
| CN113742033A (en) | Kubernetes cluster federal system and implementation method thereof | |
| Farwick et al. | Towards living landscape models: Automated integration of infrastructure cloud in enterprise architecture management | |
| CN117851163A (en) | Service inspection tool based on self-grinding openstack platform | |
| CN113505054B (en) | Network data static test system and test method for unmanned aerial vehicle control station | |
| CN102929619A (en) | Process automation software development system across hardware platform | |
| Kulscár et al. | Bringing Clouds down to Earth: Modeling Arrowhead Deployments via Eclipse Vorto. | |
| CN102652307B (en) | The method supported for the plug and play of computer architecture and system | |
| CN102129468B (en) | Method for displaying customizable cluster state | |
| Lin et al. | A flexible graphical user interface for performance modeling |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20140514 |