CN107450943A - One kind test whether normal method and system of upgraded version detection function - Google Patents
One kind test whether normal method and system of upgraded version detection function Download PDFInfo
- Publication number
- CN107450943A CN107450943A CN201710545788.8A CN201710545788A CN107450943A CN 107450943 A CN107450943 A CN 107450943A CN 201710545788 A CN201710545788 A CN 201710545788A CN 107450943 A CN107450943 A CN 107450943A
- Authority
- CN
- China
- Prior art keywords
- test
- information
- devices
- upgraded version
- upgrade
- 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
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/368—Test management for test version control, e.g. updating test cases to a new software version
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The present invention discloses a kind of test whether normal method and system of upgraded version detection function, including:Obtain the bottom-up information of Devices to test;The bottom-up information includes the upgrade information parameter for being used for determining upgraded version;According to Devices to test bottom-up information and default upgraded version configuration upgrade server;Start the ROMPaq of Devices to test;Based on current version information and the upgraded version being configured in upgrade server, judge whether the upgraded version detection function of Devices to test is normal.The present invention is advantageous to simplify test, improves testing efficiency.
Description
Technical field
The present invention relates to whether network communication technology field, more particularly to a kind of test upgraded version detection function are normal
Method and system.
Background technology
With the aggravation of market competition, market requires shorter and shorter for the R&D cycle of new product, especially software and hardware
Product.
On the one hand, market is diversified for the demand of software, and demand itself is huge, and in the market lacks convenient survey
Method for testing.
On the other hand, for the rigors of R&D cycle, many products need to improve production by software upgrading in the later stage
Product.
Current product typically has the function of automatic updating software release, reliable in order to ensure automatic upgrade function
Property it is necessary to carrying out substantial amounts of test job to the function.
Test for software upgrading is also more and more, it is necessary to test the reliable of upgrade method typically before edition upgrading
Property.
At present for mainly manually carry out version confirmation, by tester configuration upgrade automatically when
Between, then check whether upgrade tip, if can upgrade;If the version error of push, is also not easy to find out the root of problem
Source.
Publication No. CN 106708517A patent discloses a kind of method of testing of radio firmware upgrading, including following
Step:S101, wireless communication module is connected with computer, the software to be upgraded in the wireless communication module is copied into the meter
On calculation machine;S102, radio firmware upgrade server is opened, select upgrading difference bag;S103, by the difference packet replication to the meter
On calculation machine;S104, using the difference bag by the software upgrading to be upgraded to have upgraded software;S105, this has been upgraded into software answered
Make on the computer;S106, with reference to the software to be upgraded and the difference bag upgrading standard software is obtained, judge that this has upgraded
Whether with this to have upgraded software consistent for standard software.This invention mainly passes through the front and rear software of directly contrast upgrading and upgrading institute
With difference bag, come judge radio firmware upgrading whether successful method.The data that present invention needs transmit are larger, not easy enough.
Now, each manufacturer typically can test upgrading in test equipment and pass through before new ROMPaq is issued, in order to
Ensure reliability, it is necessary to substantial amounts of test is done, to adapt to various possible situations.Solve all ask before being pushed to user
Topic, it is ensured that the reliable and stable upgrading of user.But typically adopt manually tested at present, so the workload meeting of test
Very big, the cycle of test also can be long, increases the cost of enterprise.
The content of the invention
Main test upgraded version detection function of the invention, simplifies difficulty of test, improves the efficiency of test, propose a kind of survey
Try the whether normal method and system of upgraded version detection function.
Details are as follows for methods described:
Obtain the bottom-up information of Devices to test;The bottom-up information includes the upgrade information ginseng for being used to determine upgraded version
Number;
According to Devices to test bottom-up information and default upgraded version configuration upgrade server;
Start the ROMPaq of Devices to test;
Based on current version information and the upgraded version that is configured in upgrade server, the upgrade version of Devices to test is judged
Whether this detection function is normal.
Further, after Devices to test bottom-up information is obtained, in addition to step:
Judge the upgrade information parameter in Devices to test bottom-up information is with the corresponding parameter being stored in test system
No matching;If matching, continues executing with step S12, otherwise, terminate test;
Further, the bottom-up information for obtaining Devices to test includes:
Telnet agreements are established with Devices to test to be connected;
Export Devices to test bottom-up information;
Disconnection is connected with the telnet agreements of Devices to test.
Further, it is described to be included according to Devices to test bottom-up information and default upgraded version configuration upgrade server:
SSH agreements are established with upgrade server to be connected;
According to Devices to test bottom-up information and default upgraded version configuration upgrade server;
Disconnection is connected with the SSH agreements of Devices to test.
Further, the upgrade information parameter includes hardware number, production code member and current version information.
The system includes:
Bottom-up information acquiring unit, for obtaining the bottom-up information of Devices to test;The bottom-up information, which includes, to be used to determine
The upgrade information parameter of upgraded version;
Dispensing unit, upgrade server is configured according to Devices to test bottom-up information and default upgraded version;
ROMPaq start unit, for starting the ROMPaq of Devices to test;
First judging unit, based on current version information and the upgraded version being configured in upgrade server, judge to treat
Whether the upgraded version detection function of measurement equipment is normal.
Further, in addition to:
Second judging unit, for judging the upgrade information parameter in Devices to test bottom-up information and being stored in test system
In corresponding parameter whether match;If matching, continues executing with step S12, otherwise, terminate test.
Further, the bottom-up information acquiring unit includes:
Test equipment connects subelement, is connected for establishing telnet agreements with Devices to test;
Bottom identification information exports subelement, for exporting Devices to test bottom identification information;
Test equipment disconnects subelement, is connected for disconnecting with the telnet agreements of Devices to test.
Further, the dispensing unit includes:
Server connects subelement, is connected for establishing SSH agreements with upgrade server;
Subelement is configured, upgrade server is configured according to Devices to test bottom-up information and default upgraded version;
Server disconnects subelement, is connected for disconnecting with the SSH agreements of Devices to test.
Further, the upgrade information parameter includes hardware number, production code member and current version information.
Purport of the present invention simplifies difficulty of test, improves testing efficiency, reduces difficulty of test, shortens test period, reduces product
Cost.
Brief description of the drawings
Fig. 1 is a kind of test whether normal method flow of upgraded version detection function that the embodiment of the present invention one provides
Figure;
Fig. 2 is a kind of test whether normal system architecture frame of upgraded version detection function that inventive embodiments two provide
Figure.
Embodiment
It is the specific embodiment of the present invention and with reference to accompanying drawing below, technical scheme is further described,
But the present invention is not limited to these embodiments.
Devices to test comprising examining system is by Topology connection to Devices to test and upgrade server.
Devices to test can be office equipment or housed device.
It is also understood that specific embodiment described herein is used only for understanding the present invention, it is not used to limit this hair
It is bright.
Embodiment one
Present embodiments provide a kind of test whether normal method of upgraded version detection function, the flow chart of methods described
As shown in Figure 1.With reference to accompanying drawing, details are as follows:
Step S101, obtain the bottom-up information of Devices to test;The bottom-up information includes the liter for being used for determining upgraded version
Level information parameter;
Specifically, the bottom-up information for obtaining Devices to test, comprises the following steps:
Telnet agreements are established with Devices to test to be connected;
Export Devices to test bottom-up information;
Disconnection is connected with the telnet agreements of Devices to test.
Test system is to be connected by telnet agreements with Devices to test, and telnet agreements are one in TCP/IP protocol suite
Member, it is the standard agreement and major way of internet telnet service;Equipment can be obtained by the connection of telnet agreements
Bottom-up information.
Specifically, by calling related program function to export the bottom-up information of Devices to test.
Specifically, described request upgrade information parameter includes hardware number, production code member and current version information;Version
This management system pushes new version to Devices to test according to these parameters, and the version that mistake can be pushed if parameter is wrong is led
Cause upgrading failure.
Further, it is assumed that have the router that a kind of production code member is K2, the router of this model has several different hardwares
Numbering such as A1, A2, A6 etc.;Unique ROMPaq version information can be determined according to two kinds of numberings.
In addition, institute's parameter in need is put into also possible in a text sequence number, single sequence number can
To determine the software version of upgrading.
Specifically, different companies for the classification of product be it is different, the version of upgrading determines that parameter is also to differ
Sample.The possible product line of some companies is relatively simple, and edition management system just can determine that under renewal only according to a parameter
One version;And as the difference of company needs in escalation process the parameter verified it is also differentiated.But these parameters
Difference shall not be beyond the scope of the present invention.
Described parameter is stored in the bottom-up information of Devices to test, and current version information is after upgrading by new version
Information can be caused to cover;Other information is all attribute intrinsic when Devices to test dispatches from the factory, and will not be changed with upgrading, such as production code member and
Hardware number.
Matched if all of parameter, then prove that the request upgrade information that Devices to test is sent is correct, version management
System pushes next version according to correspondingly parameter.If parameter mismatches, correspondingly error message is prompted to tester.
In addition, test equipment and Devices to test be using Topology connection by the way of, but is directed to different equipment, interface difference,
Connected mode is different.
Alternatively, judge that the upgrade information parameter in Devices to test bottom-up information is corresponding in test system with being stored in
Whether parameter matches;If matching, continues executing with step S102, otherwise, terminate test;
Specifically, a upgrade parameter information can be also stored in a test system, for judging what is obtained from Devices to test
Whether bottom-up information parameter is accurate.
If the upgrade parameter in the equipment bottom-up information obtained from Devices to test is to being stored in corresponding in test system join
Numerical value mismatches, and terminates test.
Step S102, upgrade server is configured according to Devices to test bottom-up information and default upgraded version;
Specifically, it is described that upgrade server is configured including following according to Devices to test bottom-up information and default upgraded version
Step:
SSH agreements are established with upgrade server to be connected;
According to Devices to test bottom-up information and default upgraded version configuration upgrade server;
Disconnection is connected with the SSH agreements of Devices to test.
Test system is connected with upgrade server by SSH agreements, and SSH aims at telnet session and other network services
The agreement of security is provided;Upgrade server can easily be configured by the connection of SSH agreements.
Alternatively, Devices to test firmware rule is added in upgrade server;When Devices to test phase upgrade server is sent
During upgrade request, the upgrade information that upgrade server can be sent according to Devices to test identifies Devices to test, and determines whether to rise
Level and the version of upgrading.
Usually, firmware rule includes comparing the current version of the latest edition and Devices to test in server, if
Version in server is higher than the current version of Devices to test, then sends upgrade information and the version of upgrading to Devices to test;
If the version in server is not higher than the current version of Devices to test, corresponding earth signal is fed back to Devices to test, it is to be measured to set
It is standby according to feedack user to be prompted not have redaction scalable.
In addition, after configuration, disconnect the connection with upgrade server.
Step S103, start the ROMPaq of Devices to test;
Specifically, control sends instructions to Devices to test, starts the ROMPaq of Devices to test, ROMPaq is opened
Afterwards, start to send upgrade request to upgrade server, upgrade parameter is included in upgrade request, so that upgrade server judges whether
Upgrading, if upgrading, it is determined that the version of upgrading, and feedback-related information is to Devices to test.
Specifically, by calling the relative program function of Devices to test, the auto-upgrade program of Devices to test is started.
Step S104, based on current version information and the upgraded version being configured in upgrade server, judge to be measured set
Whether standby upgraded version detection function is normal.
If in step s 102, configuring the redaction of Devices to test firmware, upgrade server sends to Devices to test and risen
Level information, upgrade information include the version of upgrading, and the upgrade information that Devices to test feeds back according to upgrade server prompts user
Upgraded.
Specifically, test system obtains the upgrading feedback information for the upgrade server that Devices to test receives, and is incorporated in step
The version in upgrade server is configured in rapid S102, judges whether the ROMPaq function of Devices to test is normal.
Optionally, if the firmware version of the Devices to test configured in step s 102 is higher than the current version of Devices to test
This, then Devices to test receives the information for being upgraded to latest edition and newest firmware version.
Alternatively, if the firmware version of the Devices to test configured in step s 102 is not higher than the current version of Devices to test
This, then Devices to test receives the scalable information of no redaction.
Test system can determine whether out whether the ROMPaq of Devices to test is normal according to above-mentioned rule, and by result with appropriate
Mode feed back to tester.
In addition, test equipment is set with Devices to test, upgrade server by the way of Topology connection, but for different
Standby, interface is different, and connected mode is different.
Above-mentioned step does not have strict execution sequence, and the change of all realizations for being contemplated that and not influenceing function is all
Should be in the protection orientation of the present invention.
Embodiment two
Accordingly, the present invention provides a kind of test whether normal system of upgraded version detection function, the knot of the system
Structure block diagram is as shown in Figure 2.
The system is included with lower part:
Bottom-up information acquiring unit 110, for obtaining the bottom-up information of Devices to test;The bottom-up information, which includes, to be used for really
Determine the upgrade information parameter of upgraded version;
The bottom-up information includes the upgrade information parameter for being used for determining upgraded version;
Alternatively, the upgrade information parameter includes:Hardware number, production code member and current version information.
Further, the upgrade information parameter can be adjusted according to actual conditions, as long as the ginseng of this function can be realized
Number can.
Dispensing unit 120, upgrade server is configured according to Devices to test bottom-up information and default upgraded version;
Specifically, described upgrade server includes edition management system, and edition management system can be according to Devices to test
The upgrade request of transmission determines the version of upgrading.
ROMPaq start unit 130, for starting the ROMPaq of Devices to test;
First judging unit 140, based on current version information and the upgraded version being configured in upgrade server, judge
Whether the upgraded version detection function of Devices to test is normal.
Further, the system also includes:
Second judging unit 150, for judging the upgrade information parameter in Devices to test bottom-up information and being stored in test
Whether the corresponding parameter in system matches;If matching, continues executing with step S12, otherwise, terminate test.
Further, the bottom-up information acquiring unit includes:
Test equipment connects subelement 111, is connected for establishing telnet agreements with Devices to test;
Bottom identification information exports subelement 112, for exporting Devices to test bottom identification information;
Test equipment disconnects subelement 113, is connected for disconnecting with the telnet agreements of Devices to test.
Further, the dispensing unit includes:
Server connects subelement 121, is connected for establishing SSH agreements with upgrade server;
Subelement 122 is configured, upgrade server is configured according to Devices to test bottom-up information and default upgraded version;
Server disconnects subelement 123, is connected for disconnecting with the SSH agreements of Devices to test.
After the completion of configuration subelement 122 configures, server disconnects subelement disconnection and is connected with the SSH of Devices to test.
Further, the upgrade information parameter includes hardware number, production code member and current version information.
A kind of test whether normal system of upgraded version detection function provided in the present embodiment is applied to embodiment one
In method, related content details in embodiment one, just repeats no more here.
It is worth noting that the interface difference of test equipment is very big, the agreement of transmission is also not necessarily identical, but connect
The change of mode and communication mode, all should be in the protection domain of this method and system.
In embodiment provided herein, it should be appreciated that described method and system is all schematical, in reality
Can difference by adjustment in the implementation process of border.
In addition, the specific name of each functional unit or module is also only to facilitate mutually differentiation, is not used to the present invention
Protection domain.
Specific embodiment described herein is only to spirit explanation for example of the invention.Technology belonging to the present invention is led
The technical staff in domain can be made various modifications or supplement to described specific embodiment or be replaced using similar mode
Generation, but without departing from the spiritual of the present invention or surmount scope defined in appended claims.
Claims (10)
1. one kind test whether normal method of upgraded version detection function, it is characterised in that including step:
S11:Obtain the bottom-up information of Devices to test;The bottom-up information includes the upgrade information ginseng for being used to determine upgraded version
Number;
S12:According to Devices to test bottom-up information and default upgraded version configuration upgrade server;
S13:Start the ROMPaq of Devices to test;
S14:Based on current version information and the upgraded version that is configured in upgrade server, the upgrade version of Devices to test is judged
Whether this detection function is normal.
2. the test whether normal method of upgraded version detection function according to claim 1, it is characterised in that obtaining
After Devices to test bottom-up information, in addition to step:
Judge upgrade information parameter in Devices to test bottom-up information and the corresponding parameter that is stored in test system whether
Match somebody with somebody;If matching, continues executing with step S12, otherwise, terminate test.
3. the test whether normal method of upgraded version detection function according to claim 1, it is characterised in that described to obtain
Taking the bottom-up information of Devices to test includes:
Telnet agreements are established with Devices to test to be connected;
Export Devices to test bottom-up information;
Disconnection is connected with the telnet agreements of Devices to test.
4. the test whether normal method of upgraded version detection function according to claim 1, it is characterised in that according to treating
Measurement equipment bottom-up information and default upgraded version configuration upgrade server include:
SSH agreements are established with upgrade server to be connected;
According to Devices to test bottom-up information and default upgraded version configuration upgrade server;
Disconnection is connected with the SSH agreements of Devices to test.
5. the test whether normal method of upgraded version detection function according to claim 1, it is characterised in that the liter
Level information parameter includes hardware number, production code member and current version information.
6. one kind test whether normal system of upgraded version detection function, it is characterised in that including:
Bottom-up information acquiring unit, for obtaining the bottom-up information of Devices to test;The bottom-up information, which includes, to be used to determine upgrading
The upgrade information parameter of version;
Dispensing unit, upgrade server is configured according to Devices to test bottom-up information and default upgraded version;
ROMPaq start unit, for starting the ROMPaq of Devices to test;
First judging unit, based on current version information and the upgraded version being configured in upgrade server, judge to be measured set
Whether standby upgraded version detection function is normal.
7. the test whether normal system of upgraded version detection function according to claim 6, it is characterised in that the system
System also includes:
Second judging unit, for judging the upgrade information parameter in Devices to test bottom-up information and being stored in test system
Whether corresponding parameter matches;If matching, continues executing with step S12, otherwise, terminate test.
8. the test whether normal system of upgraded version detection function according to claim 6, it is characterised in that the bottom
Layer information acquisition unit includes:
Test equipment connects subelement, is connected for establishing telnet agreements with Devices to test;
Bottom identification information exports subelement, for exporting Devices to test bottom identification information;
Test equipment disconnects subelement, is connected for disconnecting with the telnet agreements of Devices to test.
9. the test whether normal system of upgraded version detection function according to claim 6, it is characterised in that described to match somebody with somebody
Putting unit includes:
Server connects subelement, is connected for establishing SSH agreements with upgrade server;
Subelement is configured, upgrade server is configured according to Devices to test bottom-up information and default upgraded version;
Server disconnects subelement, is connected for disconnecting with the SSH agreements of Devices to test.
10. the test whether normal system of upgraded version detection function according to claim 6, it is characterised in that described
Upgrade information parameter includes hardware number, production code member and current version information.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710545788.8A CN107450943A (en) | 2017-07-06 | 2017-07-06 | One kind test whether normal method and system of upgraded version detection function |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710545788.8A CN107450943A (en) | 2017-07-06 | 2017-07-06 | One kind test whether normal method and system of upgraded version detection function |
Publications (1)
Publication Number | Publication Date |
---|---|
CN107450943A true CN107450943A (en) | 2017-12-08 |
Family
ID=60488300
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201710545788.8A Pending CN107450943A (en) | 2017-07-06 | 2017-07-06 | One kind test whether normal method and system of upgraded version detection function |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN107450943A (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107992423A (en) * | 2017-12-14 | 2018-05-04 | 郑州云海信息技术有限公司 | A kind of test method and device of the firmware promotion and demotion of dual control storage system |
CN109347695A (en) * | 2018-09-18 | 2019-02-15 | 上海移远通信技术股份有限公司 | A kind of upgrade testing system and method |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070204262A1 (en) * | 2006-02-17 | 2007-08-30 | International Business Machines Corporation | Facilitating the automated testing of daily builds of software |
CN102255748A (en) * | 2011-06-27 | 2011-11-23 | 中兴通讯股份有限公司 | Automated testing system and method, version server and terminal |
CN103729201A (en) * | 2012-10-11 | 2014-04-16 | 上海手机测试公共服务平台有限公司 | Testing method for wireless firmware upgrade |
CN104469409A (en) * | 2014-11-28 | 2015-03-25 | 四川长虹电器股份有限公司 | Automatic testing method for smart television software differential upgrading |
CN104536876A (en) * | 2014-11-26 | 2015-04-22 | 四川长虹电器股份有限公司 | An Android platform based automatically updating and testing method and system |
CN106850267A (en) * | 2016-12-29 | 2017-06-13 | 杭州迪普科技股份有限公司 | AP version upgrading methods and device |
-
2017
- 2017-07-06 CN CN201710545788.8A patent/CN107450943A/en active Pending
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070204262A1 (en) * | 2006-02-17 | 2007-08-30 | International Business Machines Corporation | Facilitating the automated testing of daily builds of software |
CN102255748A (en) * | 2011-06-27 | 2011-11-23 | 中兴通讯股份有限公司 | Automated testing system and method, version server and terminal |
CN103729201A (en) * | 2012-10-11 | 2014-04-16 | 上海手机测试公共服务平台有限公司 | Testing method for wireless firmware upgrade |
CN104536876A (en) * | 2014-11-26 | 2015-04-22 | 四川长虹电器股份有限公司 | An Android platform based automatically updating and testing method and system |
CN104469409A (en) * | 2014-11-28 | 2015-03-25 | 四川长虹电器股份有限公司 | Automatic testing method for smart television software differential upgrading |
CN106850267A (en) * | 2016-12-29 | 2017-06-13 | 杭州迪普科技股份有限公司 | AP version upgrading methods and device |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107992423A (en) * | 2017-12-14 | 2018-05-04 | 郑州云海信息技术有限公司 | A kind of test method and device of the firmware promotion and demotion of dual control storage system |
CN109347695A (en) * | 2018-09-18 | 2019-02-15 | 上海移远通信技术股份有限公司 | A kind of upgrade testing system and method |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20100136960A1 (en) | Control software for unlocking relocking cellular telephones | |
CN104811979B (en) | Method for testing pressure based on FOTA upgrading and device | |
CN107450943A (en) | One kind test whether normal method and system of upgraded version detection function | |
US20170359844A1 (en) | Switching-on method, base station, base station controller, switching-on system and storage medium | |
CN102006183A (en) | Configuration parameter based Method and configuration equipment for configuring network equipment | |
WO2006058500A1 (en) | A method for acquiring network key performance indicators and the key performance indicators groupware thereof | |
CN108092835A (en) | The detection method and device of electric automobile charging pile | |
CN110781083B (en) | H5 client code setting multi-environment testing method and system | |
CN101782857A (en) | Payment terminal, software upgrading method and system thereof | |
CN110321531A (en) | Laboratory Instruments information management system | |
CN109446075A (en) | Interface testing method and device | |
CN103138946B (en) | A kind of POE power supply management methods and device | |
CN103118172A (en) | Mobile terminal subscriber identity module (SIM) card compatibility testing method and system | |
CN112448757A (en) | Port occupation testing method and system, user terminal, background system and medium | |
WO2018040967A1 (en) | Software module management method and system | |
CN108696475A (en) | A kind of distribution power automation terminal automatic registration method and device with safety certification | |
CN104639663A (en) | Method and system for simultaneously and automatically upgrading software of multiple optical modems | |
WO2007075758A2 (en) | Methods, systems and computer program products for evaluating suitability of a network for packetized communications | |
CN108090764A (en) | Data security control method and device in e-payment | |
CN103491557B (en) | The processing method and processing device of upgrading base station data | |
CN112019405B (en) | Automatic testing method and system | |
CN113327411A (en) | Communication parameter self-adaptive system of metering automation terminal | |
WO2024022539A1 (en) | Client-side energy measurement data exchange protocol remote testing method, system, computer readable storage medium, and computer program product | |
CN104823410A (en) | Parameter configuration system | |
CN109412811B (en) | Method for issuing authentication certificate and acquiring authentication certificate |
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 | ||
TA01 | Transfer of patent application right |
Effective date of registration: 20201104 Address after: 318015 no.2-3167, zone a, Nonggang City, no.2388, Donghuan Avenue, Hongjia street, Jiaojiang District, Taizhou City, Zhejiang Province Applicant after: Taizhou Jiji Intellectual Property Operation Co.,Ltd. Address before: 201616 Shanghai city Songjiang District Sixian Road No. 3666 Applicant before: Phicomm (Shanghai) Co.,Ltd. |
|
TA01 | Transfer of patent application right |