CN100396018C - Device and method of interpreting or constructing message - Google Patents
Device and method of interpreting or constructing message Download PDFInfo
- Publication number
- CN100396018C CN100396018C CNB031284191A CN03128419A CN100396018C CN 100396018 C CN100396018 C CN 100396018C CN B031284191 A CNB031284191 A CN B031284191A CN 03128419 A CN03128419 A CN 03128419A CN 100396018 C CN100396018 C CN 100396018C
- Authority
- CN
- China
- Prior art keywords
- message
- interpretation
- node
- message structure
- tree
- 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
Images
Landscapes
- Document Processing Apparatus (AREA)
- Devices For Executing Special Programs (AREA)
- Computer And Data Communications (AREA)
Abstract
The present invention states the message interpretation or a construction method. The construction method comprises the following procedures that a. message description texts described by message description language are compiled so as to form message structure description files; b. the message structure description files are read so as to generate a message structure tree; c. messages are orderly interpreted or constructed according to message description information in the message structure tree; d. results formed by interpreting or constructing the messages are outputted. The present invention is used as an integral body so as to directly carry out interaction with users; one message interpretation or one construction device of the present invention is fabricated into a universal interface for integrating test environment; the present invention can consider that the descriptive capability of a message flow path is added so as to support regression test, and thus, testers can rapidly generate a test flow path and a test set and have the comprehensive and visual realization for test results. The method is applied to various test tools of protocol test cards, etc. in our company.
Description
Technical field
The present invention relates to communication technical field, be specifically related to the device and method of a kind of message interpretation or structure.
Background technology
In the system based on message mechanism, as stored-program control exchange, GSM equipment, the message communication process between the monitoring process is one of important means of software test.Need construct some message artificially on the one hand; analyzed by sending posttectonic message and intercept its response to process and module simulation; thereby independent module or process are tested; on the other hand; transmission and response by message between the trace daemon; analyze each territory of message, can distinguish whether each process is working properly or effective, and then a series of modules are carried out test on the function.
In above-mentioned message interpretation or structure, prior art has following two kinds of methods, and first kind is to adopt the form of hard code to realize, promptly to concrete message structure coding; Second kind is to adopt database or message file technology, at first message is decomposed into common segment and non-common segment, common segment such as message elements are with the form of database or message file, and non-common segment is with programming or formulate the form of describing grammatical tagging, realizes by information bank again.
Obviously, there are many shortcomings in above-mentioned prior art, and first method too relies on the structure of concrete message, if revise message structure, will influence the system that all use this program, thereby need update routine, compiles again; Second method lacks the description of the relation between each territory in the message structure, need set up the data message storehouse, be unfavorable for the explanation of message, and test result and tester's level has much relations, is difficult to guarantee the consistency of testing.
Summary of the invention
At above shortcoming, the present invention proposes a kind of message interpretation or constructing apparatus and method, it is set by message structure, message is made an explanation successively or construct according to the message semantic definition information in this message structure tree, can carry out message interpretation and structure effectively, reduce the coding work amount, the flexibility height has good portability and expandability.
For achieving the above object, solution of the present invention is: a kind of message interpretation or building method, and this method comprises following steps:
A, message is become the message semantic definition text with the message semantic definition language description, be compiled into the message structure description document by compilation tool again;
B, read this message structure description document, generate the message structure tree;
C, message made an explanation successively or construct, comprising according to the message semantic definition information in this message structure tree:
C1, according to the message field in this message structure tree, read message or user input successively, the result of calculation expression;
C2, judge whether this message field is desirable,, get back to step c1 so and read next message field, otherwise continue if inadvisable;
C3, judge whether this message field is fundamental type, if, so this message field is made an explanation or construct after export and get back to step c1 and read next message field, otherwise continue;
C4, judge whether current level is dark excessively, if export and get back to step c1 after so this message field being made an explanation and read next message field, otherwise the following one deck that moves to this message structure tree is laid equal stress on and newly begun step c1;
D, with message interpretation or posttectonic result output.
Wherein, compilation tool is meant Lex and the Yacc that adopts under the Unix among the described step a, the syntax rule of correspondence is compiled obtain.
Message structure tree among the described step b includes the descriptor to each message structure of forming message:
(1) message structure tree essential information: agreement number/agreement ID number, structure number, node number, the skew of protocol description inlet, the skew of agreement expression formula inlet, the skew of protocol information inlet;
(2) concordance list;
(3) ode table: child node number, attribute;
(4) expression formula;
(5) node information: skew, length, node identification, node sign, node classification, node type, node characteristic, display properties, expression formula.
The invention also proposes a kind of message interpretation or constructing apparatus, this device comprises:
Collector is used for the message semantic definition text language is compiled into the message structure description document;
Acquisition module is used to read this message structure description document;
Message bearing-age tree module is used to generate the message structure tree;
Message interpretation and constructing module are used for message interpretation and structure;
The message semantic definition text language is compiled into the message structure description document by described collector, described acquisition module has obtained message structure after reading this message structure description document, generate the message structure tree through described message bearing-age tree module, after described message interpretation and constructing module make an explanation successively to message according to the message semantic definition information in this message structure tree or construct, with message interpretation or posttectonic result output.
Wherein, described collector is independently.
The present invention is by formulating the message semantic definition text language, after compilation tool generates the message structure description document, carry out the structure and the explanation of general message according to this document, the user only need just can realize the structure and the explanation of concrete message data by grammer describing message structure; Simultaneously, this message constructing or interpreting means can also be handled sensu lato message data structure, only need to change the input and output of message data, just can realize generation and explanation to various message data stream (as the procotol bag), thereby be analyzed.The present invention makes as a whole direct and user interactions, the General Purpose Interface that wherein a kind of message interpretation or constructing apparatus can be made into the integration testing environment, can consider to increase descriptive power to message flow, support regression test, thereby make the tester can generate testing process and test set apace, and test result had comprehensively get information about.
Describe the present invention in detail below in conjunction with the drawings and specific embodiments.
Description of drawings
Fig. 1 is the system architecture schematic diagram of message interpretation of the present invention or constructing apparatus;
Fig. 2 is the flow chart of message interpretation of the present invention or building method;
Fig. 3 is the flow chart of message interpretation of the present invention or building method step c;
Fig. 4 is the processing sequence figure of described message interpretation of the embodiment of the invention or building method;
Specific implementation
The embodiment of the invention is that example illustrates message interpretation of the present invention or constructing apparatus and method by the message in GSM 04.08 message set.
As shown in table 1 below is in the 277th page of TABLE9.68 of GSM 04.08 message set 4.9.0 version, has write down the structure of part message:
Table 1
| IEI (ID number) | Information element (information unit) | Type/Reference (type/quote) | Presence (existence) | Format (form) | Length (length) |
| Call?control?protocol discriminator | Protocol discriminator | M (necessary) | V | 1/2 | |
| Transaction?identifier | Transaction identifier | M | V | 1/2 | |
| Release?message?type | Message?type | M | V | 1 | |
| ″08″ | Cause | Cause | O (optional) | TLV | 4-32 |
| ″08″ | Second?cause | Cause | O | TLV | 4-32 |
| ″1C″ | Facility | Facilty | O | TLV | 2-？ |
| ″7E″ | User-user | User-user | O | TLV | 3-35 |
As shown in table 2 below is in the 456th page of TABLE10.77 of GSM 04.08 message set 4.9.0 version, has write down the structure of part message:
Table 2
The embodiment of the invention is at similar above message structure, illustrate how to utilize message structure to construct message or explanation message.
Described a kind of message interpretation of present embodiment or constructing apparatus, as shown in Figure 1, it comprises:
Collector is used for the message semantic definition text language is compiled into the message structure description document; Can adopt lexical analyzer (Lex) and syntax analyzer (Yacc) Core Generator under the Unix,, obtain collector compiling of input with rule such as the corresponding message semantic definition grammer of message semantic definition text language.
Acquisition module is used to read this message structure description document; It is made as a generic module cMessageStru.
Message bearing-age tree module is used to generate the message structure tree; It is made as a generic module cMsgStruBuf.
Message interpretation and constructing module are used for message interpretation and structure; It is made as a generic module cMessageParse.
More than four generic modules form the kernel of described a kind of message interpretation of present embodiment or constructing apparatus.
The message semantic definition text language is compiled into the message structure description document by described collector, described acquisition module has obtained message structure after reading this message structure description document, generate the message structure tree through described message bearing-age tree module, after described message interpretation and constructing module make an explanation successively to message according to the message semantic definition information in this message structure tree or construct, with message interpretation or posttectonic result output.
As shown in Figure 2, describe the detailed step of described a kind of message interpretation of the embodiment of the invention or building method below in detail:
The first, the message semantic definition text language is compiled into the message structure description document by compilation tool.
As above table 1,2 is depicted as the described part message structure of present embodiment, below is the part of corresponding message semantic definition text language, and bold Italic wherein partly is the keyword of message semantic definition language.
......
enum?TI_Flag_Type
{
TI_Origination＝0 ″TI?flag?is?Origination″，
TI_Destination＝1 ″TI?flag?is?Destination″
}；
enum?Protocol_Discriminator
{
PD_CC＝0×03 ″Call?control?management″，
PD_MM ＝0×05 ″Mobility?management?message″，
PD_RR＝0×06 ″Radio?resource?management?message″，
PD_SS ＝0×0B ″Supplement?Service?management?message″
}；
......
struct?IE_MESSAGE0408_CC_TYPE ″CC?Message?Type″
{
BITS[1]″Always?is?0″；
BITS[1]″MM?and?CM：The?send?sequence?number，All?Other：0″；
BITS?Message_Type[6]″Message?Type：″enum(Msg_0408_CC_Type)；
}；
struct?IE_TRANSACTION_IDENTIFIER ″Transaction?identifer?And?Protocol
Discriminator″
{
BITS[1]enum(TI_Flag_Type)；
BITS[3]″TI?Value?MM?and?RR：0″；
BITS?PD[4]″PD：″enum(Protocol_Discriminator)；
}；
struct?IE_CAUSE ″Cause″
{
BYTE IEI?enum(IE_0408_Name)＝Cause_0408；
BYTE″Length″len；
BITS?Flag[1]″0/1ext(1bits)″enum(EXTERN_FLAG)；
BITS[2]″Coding?Standard：″enum(CC_CAUSE_CODING)；
BITS[1]″Spare(1bits)″；
BITS[4]″location：″enum(CC_CAUSE_LOCATION)；
BITS[1]″Extern?Flag(1bits)：″enum(EXTERN_FLAG)when(Flag＝＝0)；
BITS[7]″recommendation：″enum(CC_)when(Flag＝＝0)；
，，“BITS[1]，，Extern?Flag2(1bit)：“enum(EXTERN_FLAG)；
BITS[7]″Cause?value″；
OCTECT[]″diagnostic(s)if?any″；
}；
struct?IE_FACILITY″Facilty″；
{
......
}；
struct?IE_USER_USER
{
......
}；
//This?is?the?main?struct?of?GSM?04.08
struct?MSG_0408″L3?information?Contents″
{
IE_TRANSACTION_IDENTIFIER?ProtocolDiscriminator；
switch(ProtocolDiscriminator.PD)
{
case?PD_RR：
......
case?PD_MM：
......
case?PD_CC：
struct″CC?and?SS?message″
{
IE_MESSAGE0408_CC_TYPE msg_cc_type；
switch(msg_cc_type.Message_Type)
{
case?RELEASE：
struct″Release″
{
IE_CAUSE option；
IE_CAUSE option；
IE_FACILITY option；
IE_USER_USER option；
}；/*end?struct″Release″*/
......
}；
}；/*end?struct″CC?and?SS?message″*/
case?PD_SS：
......
}；/*end?switch(protocol_discriminator.PD)*/
}；/*end?struct?MSG_0408*/
Above-mentioned message semantic definition text language is compiled into the message structure description document by described compilation tool, and this message structure description document is with the form storage of file, and it contains and the corresponding internal data structure of message structure, by forming with the lower part:
(1) message structure tree essential information: agreement number/agreement ID number, structure number, node number, the skew of protocol description inlet, the skew of agreement expression formula inlet, the skew of protocol information inlet
(2) concordance list
(3) ode table: child node number, attribute
(4) expression formula
(5) node information: skew, length, node identification, node sign, node classification, node type, node characteristic, display properties, expression formula.
As described below is partial content in this message structure description document:
File header
struct?SMdlFileHeader
{
_ US uID; // protocol stack 0xCEBF, agreement 0xCECF
_ UC aVer[40]; // version information
_ UC aInfo[22]; // descriptive information
union?UHeadData
{
struct
{
_ US uPrtCnt; // agreement number
_ US uCmpCnt; // structure number
_ US uNodCnt; // node number
_ US uMethod; // keep
_ UL 1NodEnt; The skew of // protocol description inlet
_ UL 1ExpEnt; The skew of // agreement expression formula inlet
_ UL 1InfEnt; The skew of // protocol information inlet
}stk；
struct
{
_ US uPrtId; // agreement ID number
_ US uCmpCnt; // structure number
_ US uNodCnt; // node number
_ US uMethod; // keep
_ UL 1NodEnt; The skew of // protocol description inlet
_ UL lExpEnt; The skew of // agreement expression formula inlet
_ UL 1InfEnt; The skew of // protocol information inlet
}prt；
}u；
_UC?aReserved[32-sizeof(UHeadData)]；
}；
// ode table
SNodeData?*pNodes；
//CNodeData
// node data is used for coupling
struct?SNodeData
{
CNID?subnid；
union
{
struct //valid?when?node?is?field?or?compound?type
{
_US uSubCnt；
NODEATTR?uAttr；
_UL 1ExprOff；
}nod；
struct //valid?when?enumerator
{
long?1Low；
long?1High；
}val；
}；
_UL?1InfoOff；
}；
// expression formula
const?char*pExprs；
// node information
const?char*pInfo；
char*pInfoOff；
The second, read this message structure description document, generate the message structure tree.
Behind the internal data structure in the message structure description document in the described acquisition module read step one, form message structure tree as follows by described message bearing-age tree module:
class?CMsgRead
{
public：
//Constructors
CMsgRead()；
CMsgRead(const?CMsgRead&right)；
CMsgRead(const?char*fname)；
//Destructor
～CMsgRead()；
//Assignment?Operation
const?CMsgRead&operator＝(const?CMsgRead&right)；
//Equality?Operations
int?operator＝＝(const?CMsgRead&right)const；
int?operator！＝(const?CMsgRead&right)const；
//Other?Operations
//GetNodeData: the structured data that obtains node.
// parameter:＜node ID, node data pointer 〉
// return: state
int?GetNodeData(NID?nid，CNodeData&ndata)；
//GetNodeInfo: obtain the node descriptor.
// parameter:＜node ID, descriptor pointer 〉
// return: state
int?GetNodeInfo(NID?nid，CNodeInfo&ninfo)；
//GetProtEntry: obtain the agreement inlet.
// parameter:＜agreement ID, inlet ID 〉
// return: agreement Ingress node ID
NID?GetProtEntry(NID?nid，NID?entry＝NID_ENTRYSTRUCT)；
//GetEnumerator: obtain to enumerate information 1
// parameter:＜enumeration structure ID, numerical value 〉
// return: success: the child node NID of enumerated value correspondence; Failure: 0L
inline?NID?GetEnumerator(NID?nid，long?value)；
//GetEnumerator: obtain to enumerate information 2
// parameter:＜enumeration structure ID, descriptor pointer, numerical value 〉
// return: success: TRUE; Failure: FALSE
inline?int?GetEnumerator(NID?nid，long?value，CNodeInfo&ninfo)；
//GetProtList: obtain protocol list
// parameter: protocol list pointer
// return: the tabulation number
int?GetProtList(CProtList&nList)；
//GetMsgList: obtain messaging list
// parameter:＜agreement nid, messaging list pointer 〉
// return: the tabulation number
int?GetMsgList(NID?nid，CMsgList&nlist)；
//GetParaList: tabulation gets parms
// parameter:＜agreement nid, parameter list pointer 〉
// return: the tabulation number
int?GetParaList(NID?nid，CNodeInfoList&nlist)；
//GetSummaryList: obtain summary info
// parameter:＜agreement nid, descriptor pointer 〉
// return: success: child node information list number; Failure :-1
int?GetSummList(NID?nid，C?SummList&nlist)；
//GetNodeDataList: obtain the tabulation of minor structure node data
// parameter:＜node ID+mask, list pointer 〉
// return: success: child node data list number; Failure :-1
int?GetNodeDataList(NID?nid，CNodeDataList&nlist)；
//GetNodeInfoList: obtain the tabulation of minor structure nodal information
// parameter:＜node ID+mask, list pointer 〉
// return: success: child node information list number; Failure :-1
int?GetNodeInfoList(NID?nid，CNodeInfoList&nlist)；
//Attributes
//FileName
const?char*get_FileName()const；
void?set_FileName(const?char*value)；
//valid
int?IsValid(){return?isValid；}
protected：
//Mdl?file?handler
char*FileName；
ifstream?fin；
int?isValid；
//indexed?table?for?search?NID
SIndexTableItem*pIndex；
_US?uTabSize；
//node?table
SNodeData *pNodes；
//expressions
const?char*pExprs；
//information
const?char*pInfo；
char*pInfoOff；
//other?attributes
_US?uPrtCnt；//protocol?count
_US?uCmpCnt；//compound?structure?sum?in?file(allprotocols)
_US?uNodCnt；//node?sum?in?file(all?protocols)
_US?uMethod；
_UL?1NodEnt；
_UL?1ExpEnt；
_UL?1InfEnt；
//count
inline?int?CmpCnt(NID?prt)；//compound?count?in?a?protocol
inline?int?NodCntP(NID?prt)；//node?count?in?a?protocol
inline?int?NodCntC(NID?cmp)；//node?count?in?a?compound
//other?functions
inline?int?GetMatchKey(NID?nid)；
long?LocateNid(NID?nid)；
inline?void?ReadData(SNodeData?&data)；
inline?void?ReadData(long?1Idx，SNodeData?&?data)；
SNodeData*ReadEnum(long?1Idx，long?value)；
inline?void?ReadExpr(L_SIZEBUFFER**buf)；
inline?long?ReadExpr(long?loff，L_SIZEBUFFER**buf)；
inline?void?ReadInfo(char*buf，int?bsize)；
inline?long?ReadInfo(long?loff，char*buf，int?bsize)；
}；
Three, according to the message semantic definition information in this message structure tree message is made an explanation successively or construct.
Described message interpretation and constructing module carry out the explanation or the structure of message.
As shown in Figure 3, it specifically may further comprise the steps:
1, according to the message field in this message structure tree, reads message or user input successively, the result of calculation expression;
Specifically, as shown in Figure 4, the message field in the message structure tree is read at first described message interpretation and constructing module layering from bottom to up successively, comprises the content and the expression formula of each message field, read message or user input simultaneously, again the result of calculation expression.
2, judge whether this message field is desirable,, get back to step 1 so and read next message field, otherwise continue if inadvisable;
3, judge whether this message field is fundamental type, if, so this message field is made an explanation or construct after export and get back to step 1 and read next message field, otherwise continue;
4, judge whether current level is dark excessively, if export and get back to step 1 after so this message field being made an explanation and read next message field, otherwise the following one deck that moves to this message structure tree is laid equal stress on and newly begun step 1.
Four, with message interpretation or posttectonic result output.
When described message interpretation and constructing module are exported message interpretation or posttectonic result by user interface.
Interface, message interpretation or posttectonic output interface as a result, the message interpretation interface of user's input among the top embodiment, can be integrated on the total interface, and described read module, message bearing-age tree module, message interpretation and constructing module provide an empty class, as with the interface in the external world, interface portion is by inheriting this void class, thereby obtain control, and revise, increase that input and output reach and the purpose of user interactions these three module operations.
Claims (5)
1. message interpretation or building method is characterized in that this method comprises following steps:
A, message is become the message semantic definition text with the message semantic definition language description, be compiled into the message structure description document by compilation tool again;
B, read this message structure description document, generate the message structure tree;
C, message made an explanation successively or construct, comprising according to the message semantic definition information in this message structure tree:
C1, according to the message field in this message structure tree, read message or user input successively, the result of calculation expression;
C2, judge whether this message field is desirable,, get back to step c1 so and read next message field, otherwise continue if inadvisable;
C3, judge whether this message field is fundamental type, if, so this message field is made an explanation or construct after export and get back to step c1 and read next message field, otherwise continue;
C4, judge whether current level is dark excessively, if export and get back to step c1 after so this message field being made an explanation and read next message field, otherwise the following one deck that moves to this message structure tree is laid equal stress on and newly begun step c1;
D, with message interpretation or posttectonic result output.
2. a kind of message interpretation as claimed in claim 1 or building method is characterized in that, compilation tool is meant Lex and the Yacc that adopts under the Unix among the described step a, the syntax rule of correspondence are compiled obtain.
3. a kind of message interpretation as claimed in claim 1 or building method is characterized in that, the message structure tree among the described step b includes the descriptor to each message structure of forming message:
(1) message structure tree essential information: agreement number/agreement ID number, structure number, node number, the skew of protocol description inlet, the skew of agreement expression formula inlet, the skew of protocol information inlet;
(2) concordance list;
(3) ode table: child node number, attribute;
(4) expression formula;
(5) node information: skew, length, node identification, node sign, node classification, node type, node characteristic, display properties, expression formula.
4. message interpretation or constructing apparatus is characterized in that this device comprises:
Collector is used for the message semantic definition text language is compiled into the message structure description document;
Acquisition module is used to read this message structure description document;
Message bearing-age tree module is used to generate the message structure tree;
Message interpretation and constructing module are used for message interpretation and structure;
The message semantic definition text language is compiled into the message structure description document by described collector, described acquisition module has obtained message structure after reading this message structure description document, generate the message structure tree through described message bearing-age tree module, after described message interpretation and constructing module make an explanation successively to message according to the message semantic definition information in this message structure tree or construct, with message interpretation or posttectonic result output.
5. a kind of message interpretation as claimed in claim 4 or constructing apparatus is characterized in that described collector is independently.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB031284191A CN100396018C (en) | 2003-04-23 | 2003-04-23 | Device and method of interpreting or constructing message |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB031284191A CN100396018C (en) | 2003-04-23 | 2003-04-23 | Device and method of interpreting or constructing message |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1540924A CN1540924A (en) | 2004-10-27 |
| CN100396018C true CN100396018C (en) | 2008-06-18 |
Family
ID=34322154
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB031284191A Expired - Fee Related CN100396018C (en) | 2003-04-23 | 2003-04-23 | Device and method of interpreting or constructing message |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100396018C (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1967574A (en) * | 2005-11-17 | 2007-05-23 | 深圳市东进通讯技术股份有限公司 | Method and system to realize generating of integrated communications platform process |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1228175A (en) * | 1996-08-20 | 1999-09-08 | 艾利森电话股份有限公司 | Method and system for testing computer system software |
| US6282576B1 (en) * | 1998-09-21 | 2001-08-28 | Unisys Corporation | Method of transferring heterogeneous data with meaningful interrelationships between incompatible computers |
-
2003
- 2003-04-23 CN CNB031284191A patent/CN100396018C/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1228175A (en) * | 1996-08-20 | 1999-09-08 | 艾利森电话股份有限公司 | Method and system for testing computer system software |
| US6282576B1 (en) * | 1998-09-21 | 2001-08-28 | Unisys Corporation | Method of transferring heterogeneous data with meaningful interrelationships between incompatible computers |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1540924A (en) | 2004-10-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103092761B (en) | Method and device of recognizing and checking modifying code blocks based on difference information file | |
| Cordy et al. | Beyond boolean product-line model checking: dealing with feature attributes and multi-features | |
| CN102789413B (en) | A kind of debug system of concurrent program and method | |
| CN109508352B (en) | Report data output method, device, equipment and storage medium | |
| CN100533398C (en) | Debug information collection method and debug information collection system | |
| CN101996132A (en) | Method and device for automatically testing common object request broker architecture (CORBA) interfaces | |
| CN110912782B (en) | Data acquisition method, device and storage medium | |
| JP2003091432A (en) | Software evaluation system and software evaluation tool | |
| CN114741070A (en) | Code generation method and device, electronic equipment and storage medium | |
| Di Lucca et al. | Recovering use case models from object-oriented code: a thread-based approach | |
| CN110309065B (en) | Concurrent execution method, device and equipment of test tasks and storage medium | |
| CN111399828A (en) | Model-driven logic device modeling method and terminal | |
| CN111209326A (en) | Data query method and device, electronic equipment and storage medium | |
| CN107153615A (en) | The method and system of software test, service terminal | |
| CN114579972A (en) | Vulnerability identification method and system for embedded development program | |
| JP2010140407A (en) | Source code inspection device | |
| CN100396018C (en) | Device and method of interpreting or constructing message | |
| Tsai et al. | Scenario-based test case generation for state-based embedded systems | |
| CN1932774A (en) | Embedded system software fast testing system and method based on multi-serial port resource | |
| CN1115628C (en) | Software simulation test method | |
| CN106874191B (en) | Intelligent database execution method and system | |
| CN114780106A (en) | Interface function self-development system | |
| CN108628606B (en) | Method and system for generating WEB network management application program of embedded equipment | |
| CN114020769A (en) | Data blood margin analysis method and device and storage medium | |
| CN100514994C (en) | Communication host computer testing system and method thereof |
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 | ||
| C41 | Transfer of patent application or patent right or utility model | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20160422 Address after: American California Patentee after: Snaptrack, Inc. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: Huawei Technologies Co., Ltd. |
|
| 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: 20080618 Termination date: 20190423 |