CN110413264A - A kind of software application framework and its configuration unit - Google Patents

A kind of software application framework and its configuration unit Download PDF

Info

Publication number
CN110413264A
CN110413264A CN201910693704.4A CN201910693704A CN110413264A CN 110413264 A CN110413264 A CN 110413264A CN 201910693704 A CN201910693704 A CN 201910693704A CN 110413264 A CN110413264 A CN 110413264A
Authority
CN
China
Prior art keywords
layer
interface
module
application
software application
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.)
Pending
Application number
CN201910693704.4A
Other languages
Chinese (zh)
Inventor
刘欢
吴鹏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nanjing Chenhuang Software Technology Co Ltd
Original Assignee
Nanjing Chenhuang Software Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Nanjing Chenhuang Software Technology Co Ltd filed Critical Nanjing Chenhuang Software Technology Co Ltd
Priority to CN201910693704.4A priority Critical patent/CN110413264A/en
Publication of CN110413264A publication Critical patent/CN110413264A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/20Software design
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/30Creation or generation of source code
    • G06F8/36Software reuse
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/76Adapting program code to run in a different environment; Porting

Abstract

The present invention provides a kind of software application framework and its configuration unit, software application framework includes hardware driving layer, functional module layer, application-interface layer, Business Logic and application layer, cross-layer calling is unable between each layer, Business Logic is provided with each application module for delineation of activities, functional module layer corresponds to the application module on Business Logic and is provided with functional module for calling, the common interface of exploitation is provided on application module and basic module, application layer is the overall operation frame of program, tissue calls service logic, functional module layer is used for encapsulate different functional modules, application-interface layer, public api interface is provided and is called for application interface for upper layer, hardware driving layer is made of each drive module, unified interface is provided upwards.The invention enables software application framework clear logics, and code maintenance is convenient, greatly reduce the time of designer.

Description

A kind of software application framework and its configuration unit
Technical field
The present invention relates to computer software architecture systems technology fields, and in particular to a kind of software application framework and its configuration Unit.
Background technique
Software developer and software engineer designed using software architecture, discussed, documenting and reuses software systems, soft Element is abstracted when part framework is to software systems operation, and it is abstract that software systems may have plurality of layers, or by multi-play Services process It is formed, every layer of abstract or each operation flow has the software architecture of oneself.
Accomplish application code logic it is clear, and avoid it is duplicate make wheel, good application architecture is not how can it be carried on if.Such as Good framework, transplanting not will be a very painful thing to fruit.If good framework, multiplexing are not the biggest problem, It cannot be multiplexed original code to a greater extent.If not good framework, once driving changes, institute's some places will change, Time-consuming and laborious and error-prone.If not good framework, the code of hardware driving layer is interspersed in application layer, looking to be Complete confusion, logic is unclear, and code maintenance gets up can be highly difficult.
Software development is a dynamic process, and software architecture is often modified and redefined to designer and developer, it is therefore an objective to For the requirement that some column datas of Dynamic Matching software operation change, therefore a kind of software application framework is such as in the process of development If fruit scalability and reusability can increase, the design time of designer will be substantially reduced, increase its design efficiency.
Summary of the invention
(1) the technical issues of solving
In view of the deficiencies of the prior art, it the present invention provides a kind of software application framework and its configuration unit, overcomes existing Have the deficiency of technology, using the calling and change of the module on basis, realize the Auto-matching of software architecture and multilayer it is abstract between Recombination.
(2) technical solution
In order to achieve the above object, the present invention is achieved by the following technical programs:
A kind of software application framework and its configuration unit, software application framework include hardware driving layer, functional module layer, answer With interface layer, Business Logic and application layer, cross-layer calling is unable between each layer, the Business Logic is provided with for business The each application module divided, the functional module layer correspond to the application module on Business Logic and are provided with function for calling Module, the common interface of exploitation is provided on the application module and basic module, and the application layer is the overall of program Operation frame, tissue call service logic, and the functional module layer is used for encapsulate different functional modules, the application interface Layer provides public api interface and calls for application interface for upper layer, and the hardware driving layer is made of each drive module, to It is upper that unified interface is provided.
Preferably, the application layer can realize several tasks with embedded OS.
Preferably, each module provides unified interface, subsequent to increase, and cannot change original interface.
Preferably, mutually indepedent between same layer module, it is independent of each other, cannot mutually call, connecing for its lower layer can only be called Mouthful.
Preferably, the application layer is the overall procedure and frame of program, and Business Logic is called to realize function.
Preferably, the functional module independent compilation.
Preferably, the hardware driving layer can be divided into multilayer, wherein at least include interface layer, drive layer and mechanical floor, The interface layer provides unified interface, the driving layer interface unified to interface layer exposure for user, these interfaces are used for It completes actual connection disconnection and data transmit-receive, the mechanical floor provides unified interface to driving layer, these interfaces pass through visit Physical hardware is asked to realize the communication with module.
Preferably, it is accessed mutually between the interface layer, driving layer and mechanical floor by the interface of standard, interface layer External interface, driving layer is to the interface of interface layer, and mechanical floor is on the interface of driving layer offer.
Preferably, functional module can be divided into submodule.
Preferably, application module can continue to be layered.
(3) beneficial effect
The embodiment of the invention provides a kind of software application framework and its configuration units.Have it is following the utility model has the advantages that using The modularized design of the methods and basic function called layer by layer, so that software application framework clear logic, code maintenance side Just, the time of designer is greatly reduced.
Detailed description of the invention
In order to more clearly explain the embodiment of the invention or the technical proposal in the existing technology, to embodiment or will show below There is attached drawing needed in technical description to be briefly described, it should be apparent that, the accompanying drawings in the following description is only this Some embodiments of invention for those of ordinary skill in the art without creative efforts, can be with It obtains other drawings based on these drawings.
Fig. 1 is the system schematic of heretofore described software application framework and its configuration unit.
Specific embodiment
In order to make the object, technical scheme and advantages of the embodiment of the invention clearer, below in conjunction with the embodiment of the present invention In attached drawing, technical scheme in the embodiment of the invention is clearly and completely described, it is clear that described embodiment is A part of the embodiment of the present invention, instead of all the embodiments.Based on the embodiments of the present invention, those of ordinary skill in the art Every other embodiment obtained without creative efforts, shall fall within the protection scope of the present invention.
As shown in fig.1, the present invention provides a kind of software application framework and its configuration unit, software application framework includes hard Part drives layer, functional module layer, application-interface layer, Business Logic and application layer, and cross-layer calling is unable between each layer, and business is patrolled It collects layer and is provided with each application module for delineation of activities, functional module layer corresponds to the setting of the application module on Business Logic There is the functional module for calling, the common interface of exploitation is provided on application module and basic module, application layer is program Overall operation frame, tissue call service logic, and functional module layer is used for encapsulate different functional modules, application interface Layer provides public api interface and calls for application interface for upper layer, and hardware driving layer is made of each drive module, mentions upwards For unified interface.
Preferably, application layer can realize several tasks with embedded OS.
Preferably, each module provides unified interface, subsequent to increase, and cannot change original interface.
Preferably, mutually indepedent between same layer module, it is independent of each other, cannot mutually call, connecing for its lower layer can only be called Mouthful.
Preferably, application layer is the overall procedure and frame of program, and Business Logic is called to realize function.
Preferably, functional module independent compilation.
Preferably, hardware driving layer can be divided into multilayer, wherein at least include interface layer, driving layer and mechanical floor, interface Layer provides unified interface for user, and the driving layer interface unified to interface layer exposure, these interfaces are for completing actual company Disconnection and data transmit-receive are connect, mechanical floor provides unified interface to driving layer, these interfaces are realized by access physical hardware With the communication of module.
Preferably, it is accessed mutually between interface layer, driving layer and mechanical floor by the interface of standard, interface layer is external Interface, driving layer is to the interface of interface layer, and mechanical floor is on the interface of driving layer offer.
Preferably, functional module can be divided into submodule.
Preferably, application module can continue to be layered.
Specific embodiment is such as:
Embodiment one: being driving layer and application layer API API points, rather than all programs all call driving layer API.It is (whole It all calls driving layer API to will lead to driving calling in application in a application to be seen everywhere, can not transplant and be multiplexed to greatest extent)
An application is first carried out functional module division, and overall structure is layered, then designs functional independence Modules (such as algoritic module, file library module communicate library module), the open common interface on module.
Driving layer provides common interface to call for upper layer.Each functional module can (such as algoritic module be pure with independent compilation ANSI C, can be in any platform reuse), or driving layer interface (file library module has invoked driving read-write Flash) is called, always For it, speech and in short, encapsulating out the reusable functional module of each functional independence.
Totally divide hardware driving layer -- > functional module layer -- > application-interface layer -- > Business Logic -- > application layer
Application layer, is the overall operation frame of program, and tissue calls service logic.Certain embedded operation system can be used System realizes several tasks.Such as timed task, card processing task, menu task, communication task.
Business Logic, such as CPU card processing, the processing of Ministry of Communications's card, Interlink Card is handled, and M1 card processing, communications records upload, Blacklist downloading, admission fee parameter downloading etc..
Application-interface layer provides public api interface and calls for application interface for upper layer.These interfaces can also be by lower layer Functional module, which is opened to, to be come, and application-interface layer is responsible for summarizing.
Functional module layer can encapsulate different functional modules.Such as algorithms library, library, communication pool, Unionpay library, upwards The interface of application-interface layer is provided, calls driving interface downwards.
Hardware driving layer, is made of each drive module, provides unified interface upwards.
If driving varies by, or changes different platform, driving layer only need to be changed, application layer is unaffected.
If functional module varies by, upgrade function functional module is only needed, other modules are unaffected, and application layer is not yet It is impacted.
According to this logical design it is good after, main work is exactly in Business Logic.Application layer is then the total of program Body process and frame, it is main that Business Logic is called to realize different functions.
Our present code structures are substantially come by this thinking.
Hardware driving layer -- > functional module layer -- > application-interface layer -- > Business Logic -- > application layer.
Look at the code of following two style, which you prefer.
Equally it is to save parameter, AlgCRC16, WritePraFlash ((unsigned char*) & have to be splitted into NetPra, NETPRA_ADDR, sizeof (_ NetPra)) two steps
There are also AH_Para_Verify this, in application layer be really it is extra, detection failure is read from Flash again.It closes In parameter, legitimacy is detected once being switched on.
Since being all parameter to be saved, an encapsulation should be just done, as shown above, the different parameters that system is used do a Planning.Application layer calls APP_Open_UseFile or APP_Read_UseFile,
Rather than directly remove read-write Flash.
With NC_FileLib, for file library module, if to be used in other platforms, such as EH0918 handset apparatus, only Need to transplant several hardware layer interfaces.
NC_FileSys library, with hardware, relevant interface is in Hook file,
Again following function is realized:
void HW_FRAM_Init(void)
unsigned int HW_FRAM_Read(unsigned int addr,unsigned int size, unsigned char*buffer)
unsigned int HW_FRAM_Write(unsigned int addr,unsigned int size, unsigned char*buffer)
// erasing FLASH one page (minimum unit of FLASH erasing)
unsigned int HW_Flash_PageErase(unsigned int page)
unsigned int HW_Flash_Read(unsigned int addr,unsigned int size, unsigned char*buffer)
unsigned int HW_Flash_NotEraseWrite(unsigned int addr,unsigned int size,unsigned char*buffer)
// erasing FLASH one page (minimum unit of FLASH erasing)
unsigned int HW_Flash_PageErase(unsigned int page)
Embodiment two:
According to the above modular design method, by taking one intelligence pos application of exploitation as an example:
The functional module that one intelligence pos is related to has:
Read-write card function saves and reads consumer record, searches and save blacklist, interface display, menu is shown, under communication It carries parameter and uploads record etc..
The following are in portability function module to computer, self-made simulation Pos tool:
Realize that (bankcard consumption, record storage, on record are completed in only realization functionally to a simulation pos on computers It passes, blacklist, the functions such as admission fee downloading.Interface is Dos window.It is exactly a function if subsequent also work it out interface with QT Complete simulation POS machine, but obtain and the C++ for falling into disuse many years is picked up again.It can continue to improve and do a host computer mould Quasi- pos changes compiler and operates on true POS after host computer artificial debugging and cross compile).
The functional module used has file storage module, card processing module, algoritic module, Unionpay's library module.I am these Module is transplanted on computer.
About the realization of card processing module, due to not having card read head for ID on computer, then with external card reader.Card reader serial ports It connects on computer.A read-write card service is done on computer, and the read-write card interface of TCP interface is provided.
Library is transplanted, is the flash of operation in embedded program, the interface used in library is read on computers The form of written document is replaced.
Algorithms library is transplanted, algorithms library is all that c writes, and is directly recompilated with gcc in windows platform.
Realize effect:
Simulation POS is communicated with Unionpay:
POSP simulator is a tool for simulating Unionpay backstage.Run bus, exe registers, downloading IC card parameter with Public key is simultaneously saved to computer,
Simulate Interlink Card consumption:
Card reader is connected on computer by serial ports, and read-write card is run on computer and services tcpserver.exe, read-write is provided Block APDU instruction interface.Utilize the small tool remote reader done before.
Sometimes for test card consumption, it cannot recompilate into every time, at this time can use LUA foot This.Select the 11st.LUA script is write into the instruction for needing test card, is then executed,
The functional module of encapsulation, i.e., various libraries are as follows:
Liblua.a executes lua script and uses
Libblkfile.a blacklist is searched and storage
Libmaycalc.a algorithms library, such as SHA, DES algorithm
Libmycard.a Ka Ku provides the APDU of operation sheet
Libmyfile.a library provides file storage and reads
Libmycom.a communication pool provides socket communication
Libmyup.a Unionpay library, Interlink Card handle logical AND Unionpay background communication business
Each functional module, and submodule can be further subdivided into.
It illustrates by communication pool:
Embedded device requires to support a variety of different communication modules.For example hardware device has A701, A801, B502 Deng communication module has GL868, MG323, MC8630, N710, ZIGBEE etc., these equipment support all or part of communicate respectively Module.
Driving is roughly divided into three layers:
1, interface layer: providing unified interface for user, such as: Connect, TxData, RxData, Disconnect Deng.
2, drive layer: the interface unified to interface layer exposure, these interfaces are for completing actual connection disconnection and data Transmitting-receiving etc., such as: DevConnect, DevTxData, RxData, Disconnect etc..This layer meeting and the communication module supported Correlation will not directly access any hardware capability, all be realized by the mechanical floor of bottom including serial communication, GPIO control.
3, mechanical floor: unified interface is provided to driving layer, these interfaces are realized by access physical hardware and module Communication, such as: XXXPowerOn, SerialSend, SerialReceive etc., and define which module is the equipment support.
It is accessed mutually between three layers by the interface of standard.
1, interface layer external interface (API that user's operation communication module uses):
uint32_t Com_Dev_Start(void);
// equipment re-powers, and establishes connection with network
uint32_t Com_Dev_Restart(void);
// equipment suspension power-off
uint32_t Com_Dev_Stop(void);
// connection remote server
uint32_t Com_Dev_Connect(uint8_t*ip,uint16_t port,uint32_t timeout, uint32_t channel);
// disconnect
uint32_t Com_Dev_Disconnect(uint32_t channel);
// send data
uint32_t Com_Dev_TxData(uint8_t*buf,uint32_t len,uint32_t timeout, uint32_t channel);
// receive data
uint32_t Com_Dev_RxData(uint8_t*buf,uint32_t*rxlen,uint32_t len, uint32_t timeout,uint32_t channel);
// obtain signal quality
uint32_t Com_Dev_GetSQ(uint8_t*csq);
2, interface (to interface layer shield the difference of each communication module) of the driving layer to interface layer:
struct ComDevFunc{uint32_t(*start)(ComDevDesc*dev);uint32_t(*restart) (ComDevDesc*dev);uint32_t(*stop)(ComDevDesc*dev);uint32_t(*connect) (ComDevDesc*dev,uint8_t*ip,uint16_t port,uint32_t timeout,uint32_t channel); uint32_t(*disconnect)(ComDevDesc*dev,uint32_tchannel);uint32_t(*txData) (ComDevDesc*dev,uint8_t*buf,uint32_t len,uint32_t timeout,uint32_t channel); uint32_t(*rxData)(ComDevDesc*dev,uint8_t*buf,uint32_t*rxlen,uint32_t len, uint32_t timeout,uint32_t channel);uint32_t(*getVer)(ComDevDesc*dev,uint8_t* buf,uint32_t versize);uint32_t(*getCSQ)(ComDevDesc*dev,uint8_t*csq);};
3, the interface (the relevant content of platforms such as shielding serial port, GPIO pin) that mechanical floor provides driving layer: int Com_PortOpen(uint32_t baud);
int Com_PortClose(void);
int Com_PortSend(uint8_t*buf,int len);
int Com_PortRecv(uint8_t*buf,int len,int timeout);
int Com_PortGetLen(void);
int Com_PortFlush(void);
// particular hardware correlation function, is realized in Model_XXXXX.h
// only need to realize the module that platform is supported
void COM_GL868Power(int state);
void COM_MC8332Power(int state);
void COM_MG323Power(int state);
void COM_EMV3081Power(int state);
void COM_CC2530Power(int state);
void COM_N710Power(int state);
Bibliographic structure
The method for supporting new module:
For example A701 equipment will increase newly and support SUPER123 module:
1, increase a file Dev_6G_SUPER123.c in Devices catalogue and realize in ComDevFunc structure Each function of definition
2, increase power supply control function COM_SUPER123Power in device file Model_A701.c.
3, driving function is added in device file Model_A701.c into gComFuncs array.
The method for being adapted to new equipment:
1, a file Model_XXXX.c is newly increased in Models catalogue
2, serial communication function (Com_PortXXXX series, with reference to the definition in Model.h) is realized
3, the power-on and power-off function COM_XXXXPower (int state) for the communication module supported is realized;
4, gComFuncs array is realized, wherein quoting the driving function of all support modules.
Reference to part system function:
For part system correlation function, such as delay, the printing of Debugging message etc., default is all provided and is realized, and will Default, which is realized, is claimed as minorant.Can be carried out when user needs to carry out customized in this way it is customized, if you do not need to Can directly ignore not will cause compile error.
Such function has following three:
void Com_Hook_Printf(char*fmt,...);
void Com_Hook_PrintHex(uint8_t*buf,int len);
// delay function is redefined, the scheduling characteristic of operating system can be made full use of if using operating system, Avoid waste caused by waiting indefinitely
void Com_Hook_DelayMs(uint32_t ms);
The function of generally being used in driving:
Common function is driven for partially writing communication module, a series of auxiliary function is provided in module, avoids The duplication of labour
It should be noted that, in this document, relational terms such as first and second and the like are used merely to a reality Body or operation are distinguished with another entity or operation, are deposited without necessarily requiring or implying between these entities or operation In any actual relationship or order or sequence.Moreover, the terms "include", "comprise" or its any other variant are intended to Non-exclusive inclusion, so that the process, method, article or equipment including a series of elements is not only wanted including those Element, but also including other elements that are not explicitly listed, or further include for this process, method, article or equipment Intrinsic element.In the absence of more restrictions, the element limited by sentence "including a ...", it is not excluded that There is also other identical elements in process, method, article or equipment including the element.
The above embodiments are merely illustrative of the technical solutions of the present invention, rather than its limitations;Although with reference to the foregoing embodiments Invention is explained in detail, those skilled in the art should understand that: it still can be to aforementioned each implementation Technical solution documented by example is modified or equivalent replacement of some of the technical features;And these modification or Replacement, the spirit and scope for technical solution of various embodiments of the present invention that it does not separate the essence of the corresponding technical solution.

Claims (10)

1. a kind of software application framework and its configuration unit, it is characterised in that: software application framework includes hardware driving layer, function Module layer, application-interface layer, Business Logic and application layer are unable to cross-layer calling, the Business Logic setting between each layer There is each application module for delineation of activities, the functional module layer corresponds to the application module on Business Logic and is provided with confession The functional module of calling, the common interface of exploitation is provided on the application module and basic module, and the application layer is journey The overall operation frame of sequence, tissue call service logic, and the functional module layer is used for encapsulate different functional modules, institute Application-interface layer is stated, public api interface is provided and is called for application interface for upper layer, the hardware driving layer is by each driving mould Block composition, provides unified interface upwards.
2. software application framework as described in claim 1 and its configuration unit, it is characterised in that: the application layer can be with embedding Enter formula operating system and realizes several tasks.
3. software application framework as described in claim 1 and its configuration unit, it is characterised in that: each module offer uniformly connects Mouthful, it is subsequent to increase, original interface cannot be changed.
4. software application framework as described in claim 1 and its configuration unit, it is characterised in that: between same layer module mutually solely It is vertical, it is independent of each other, cannot mutually call, the interface of its lower layer can only be called.
5. software application framework as described in claim 1 and its configuration unit, it is characterised in that: the application layer is program Overall procedure and frame call Business Logic to realize function.
6. software application framework as described in claim 1 and its configuration unit, it is characterised in that: the functional module is independently compiled It translates.
7. software application framework as described in claim 1 and its configuration unit, it is characterised in that: the hardware driving layer can be with It is divided into multilayer, wherein at least includes that interface layer, driving layer and mechanical floor, the interface layer provide unified interface, institute for user The driving layer interface unified to interface layer exposure is stated, these interfaces are described for completing actual connection disconnection and data transmit-receive Mechanical floor provides unified interface to driving layer, these interfaces realize the communication with module by access physical hardware.
8. software application framework as claimed in claim 7 and its configuration unit, it is characterised in that: the interface layer, driving layer It is accessed mutually between mechanical floor by the interface of standard, interface layer external interface, drives layer to the interface of interface layer, if On the interface that standby layer provides driving layer.
9. software application framework as described in claim 1 and its configuration unit, it is characterised in that: functional module can be divided into son Module.
10. software application framework as described in claim 1 and its configuration unit, it is characterised in that: application module can continue Layering.
CN201910693704.4A 2019-07-30 2019-07-30 A kind of software application framework and its configuration unit Pending CN110413264A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910693704.4A CN110413264A (en) 2019-07-30 2019-07-30 A kind of software application framework and its configuration unit

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910693704.4A CN110413264A (en) 2019-07-30 2019-07-30 A kind of software application framework and its configuration unit

Publications (1)

Publication Number Publication Date
CN110413264A true CN110413264A (en) 2019-11-05

Family

ID=68364131

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910693704.4A Pending CN110413264A (en) 2019-07-30 2019-07-30 A kind of software application framework and its configuration unit

Country Status (1)

Country Link
CN (1) CN110413264A (en)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111273941A (en) * 2020-01-17 2020-06-12 北京实干兴邦科技有限公司 Marine control system
CN111309291A (en) * 2020-01-19 2020-06-19 北京航空航天大学 Modularized embedded software architecture, customization method and customization system thereof
CN111596897A (en) * 2020-05-07 2020-08-28 北京百度网讯科技有限公司 Code multiplexing processing method and device and electronic equipment
CN111930353A (en) * 2020-08-12 2020-11-13 Oppo(重庆)智能科技有限公司 Sensor driving architecture implementation method, device, architecture, terminal equipment and medium
CN113220336A (en) * 2020-01-21 2021-08-06 腾讯科技(深圳)有限公司 Code processing method, device, medium and electronic equipment
CN113434118A (en) * 2021-05-31 2021-09-24 深圳市国电科技通信有限公司 Layered architecture system of concentrator based on Java platform
CN113542315A (en) * 2020-04-13 2021-10-22 Oppo广东移动通信有限公司 Communication framework, service event processing method and device

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107491858A (en) * 2017-07-05 2017-12-19 北京科东电力控制系统有限责任公司 A kind of electric power transaction platform based on micro services application architecture
CN107948008A (en) * 2017-10-23 2018-04-20 珠海许继芝电网自动化有限公司 A kind of modeling method for low-voltage network monitoring system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107491858A (en) * 2017-07-05 2017-12-19 北京科东电力控制系统有限责任公司 A kind of electric power transaction platform based on micro services application architecture
CN107948008A (en) * 2017-10-23 2018-04-20 珠海许继芝电网自动化有限公司 A kind of modeling method for low-voltage network monitoring system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
周华: "支持电网安全运行的网荷互动技术研究", 《中国优秀硕士学位论文全文数据库 工程科技Ⅱ辑》 *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111273941A (en) * 2020-01-17 2020-06-12 北京实干兴邦科技有限公司 Marine control system
CN111309291A (en) * 2020-01-19 2020-06-19 北京航空航天大学 Modularized embedded software architecture, customization method and customization system thereof
CN111309291B (en) * 2020-01-19 2021-09-24 北京航空航天大学 Modularized embedded software architecture, customization method and customization system thereof
CN113220336A (en) * 2020-01-21 2021-08-06 腾讯科技(深圳)有限公司 Code processing method, device, medium and electronic equipment
CN113542315A (en) * 2020-04-13 2021-10-22 Oppo广东移动通信有限公司 Communication framework, service event processing method and device
CN113542315B (en) * 2020-04-13 2024-04-05 Oppo广东移动通信有限公司 Communication framework, business event processing method and device
CN111596897A (en) * 2020-05-07 2020-08-28 北京百度网讯科技有限公司 Code multiplexing processing method and device and electronic equipment
CN111930353A (en) * 2020-08-12 2020-11-13 Oppo(重庆)智能科技有限公司 Sensor driving architecture implementation method, device, architecture, terminal equipment and medium
CN111930353B (en) * 2020-08-12 2023-12-15 Oppo(重庆)智能科技有限公司 Sensor driving architecture implementation method, device, architecture, terminal equipment and medium
CN113434118A (en) * 2021-05-31 2021-09-24 深圳市国电科技通信有限公司 Layered architecture system of concentrator based on Java platform
CN113434118B (en) * 2021-05-31 2024-01-12 深圳市国电科技通信有限公司 Java platform-based hierarchical architecture system of concentrator

Similar Documents

Publication Publication Date Title
CN110413264A (en) A kind of software application framework and its configuration unit
CN106940428B (en) Chip verification method, device and system
CN102033743B (en) System and method for expanding model driving development capability by applying plug-in
Lessmann et al. Comparative study of wireless network simulators
CN105144118B (en) Using test and analysis
CN106997297A (en) A kind of software development management platform and method based on DevOps
CN103136101A (en) Software automated testing unified operation platform
CN103067502A (en) Hardware system for cloud development and testing
CN104750603A (en) Multi-core DSP (Digital Signal Processor) software emulator and physical layer software testing method thereof
CN104486255A (en) Service resource dispatching method and device
CN101739289B (en) Method and device for setting display mode in Linux virtual machine
CN107153529A (en) A kind of embedded software development method, device and platform
CN104714804A (en) Track traffic automatic fare collection system reader-writer middleware
CN109933521A (en) Automated testing method, device, computer equipment and storage medium based on BDD
CN102646056A (en) Function expansion method and device for grid GIS (geographic information system) platform based applications
CN101261600A (en) Software test apparatus and test software design method
CN109992555A (en) A kind of management board shared for multipath server
CN110275716A (en) Deployed with devices method and device, equipment operation method and electronic equipment
Lesage et al. A hierarchical component model for large parallel interactive applications
CN104850449A (en) Method and apparatus for implementing system architecture
CN109117159A (en) A kind of automatic identification refreshes the method and device of firmware
CN109947466A (en) A kind of reverse method and device thereof for obtaining UE4 global object table
CN115951970A (en) Heterogeneous multi-simulation software integrated development environment
Saulnier et al. Simulation model reusability
CN101159601A (en) System, device and method for updating network element

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication

Application publication date: 20191105

RJ01 Rejection of invention patent application after publication