CN110932943B - Test system supporting WIN, INAP and SIP communication protocols - Google Patents
Test system supporting WIN, INAP and SIP communication protocols Download PDFInfo
- Publication number
- CN110932943B CN110932943B CN201911362462.7A CN201911362462A CN110932943B CN 110932943 B CN110932943 B CN 110932943B CN 201911362462 A CN201911362462 A CN 201911362462A CN 110932943 B CN110932943 B CN 110932943B
- Authority
- CN
- China
- Prior art keywords
- protocol
- call
- sip
- inap
- win
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/50—Testing arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/18—Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
Abstract
The invention discloses a test system supporting WIN, INAP and SIP communication protocols, which comprises: a call control service module for readingtxtThe script file initiates, establishes and releases a plurality of calls, dynamically adjusts the call rate and simulates a large number of calls to the tested system; the protocol interface service module is used for processing the receiving and sending of each protocol message and supporting the initiation, establishment and release of a call, and comprisesSIPA protocol module,WINA protocol module,INAP/CAPAnd a protocol module. By means of the system, support is achievedWIN、INAP、SIPA plurality of communication protocol test systems; the testing process of the calling class is simplified; the testing efficiency is improved; to be undiagnosedWIN、INAP、SIPUsers of communication protocols are also readily and quickly able to master and use.
Description
Technical Field
The invention relates to the technical field of intelligent communication, in particular to a test system supporting WIN, INAP and SIP communication protocols.
Background
With the development of communication technology, the number of communication protocols increases, and the content becomes more and more complex, and commonly used communication protocols such as WIN (Wireless Intelligent Network Protocol), INAP (Intelligent Network Application Protocol), SIP (Session initiation Protocol), and the like. Most of the existing protocol test tools only support a specific single communication protocol and a specific scene, and the test tools supporting a plurality of communication protocol classes are few, and a plurality of protocol test tools are usually required to be adopted for testing various communication systems adopting a plurality of communication protocols. However, different testers have different design ideas and implementation modes, and a user needs to learn various testing tools, so that the learning cost is high, and the use efficiency is low. When the test tool is used for influencing the test result, a large amount of manpower is required for checking. In addition, the updating of the test tool often cannot keep up with the updating speed of the communication protocol, so that the test cannot be performed.
Disclosure of Invention
Aiming at the technical problems in the related art, the invention provides a test system supporting WIN, INAP and SIP communication protocols, which can overcome the defects in the prior art.
In order to achieve the technical purpose, the technical scheme of the invention is realized as follows:
a test system supporting WIN, INAP and SIP communication protocols comprises a call control service module, wherein,
the call control service module is used for reading the script file of txt, initiating, establishing and releasing a plurality of calls, dynamically adjusting the call rate and simulating a large number of calls to a tested system, and comprises a call service module and a protocol interface service module;
the protocol interface service module is used for processing the receiving and sending of each protocol message and supporting the initiation, establishment and release of a call, and comprises an SIP protocol module, a WIN protocol module and an INAP/CAP protocol module.
Further, the call service module is used for executing the test script and outputting the result.
Further, the SIP protocol module is configured to set a UDP port used for receiving and sending SIP protocol messages by configuring a config.as.gen when the call control service module simulates an SIP protocol call, where the config.as.gen is a basic configuration file.
Further, the WIN protocol module is configured to set a port, to which the call control service module is connected, to the tcap _ ansi process by configuring config.server.gen when the call control service module simulates an MSC to initiate a WIN protocol call, where config.server.gen is a service configuration file, and tcap _ ansi is a service configuration file.
Further, the INAP/CAP protocol module is configured to set a port, to which the call control service module is connected to the tcap process, by configuring config.server.gen when the call control service module simulates SSP to initiate an INAP/CAP protocol call.
Furthermore, a SIPTW gateway is added between the call control service module and the SCP service component according to the requirement to distribute the call.
Further, the tcap _ ansi process on the call control service module side is connected with the tcap _ ansi process on the SCP service component side through an sccp interface.
Further, the tcap process on the call control service module side is connected with the tcap process on the SCP service component side through the sccp interface.
Furthermore, in the test script of the WIN protocol, a calling party and a called party in each process comprise a calling session; in the test script of the SIP protocol, a calling party and a called party in each process comprise an outgoing call session and an incoming call session; in the test script of the INAP/CAP protocol, each flow comprises a call session.
The invention has the beneficial effects that: by the system, a plurality of communication protocol test systems of WIN, INAP and SIP are supported; the testing process of the calling class is simplified; the user can complete the test only by compiling a simple and understandable call flow script without paying attention to the bottom layer signaling message so as to improve the test efficiency; and users who do not understand WIN, INAP and SIP communication protocols are easy to grasp and use quickly.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a schematic block diagram of a test system supporting WIN, INAP and SIP communication protocols according to an embodiment of the present invention;
FIG. 2 is a block diagram of a call control service of a test system supporting WIN, INAP and SIP communication protocols according to an embodiment of the present invention;
fig. 3 is a SIP protocol session logic diagram for call control service support of a test system supporting WIN, INAP, SIP communication protocols according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of the present invention.
As shown in fig. 1, a test system supporting WIN, INAP, SIP communication protocol according to an embodiment of the present invention includes a call control service module, wherein,
the call control service module is used for reading the script file of txt, initiating, establishing and releasing a plurality of calls, dynamically adjusting the call rate and simulating a large number of calls to a tested system, and comprises a call service module and a protocol interface service module;
the protocol interface service module is used for processing the receiving and sending of each protocol message and supporting the initiation, establishment and release of a call, and comprises an SIP protocol module, a WIN protocol module and an INAP/CAP protocol module.
In an embodiment of the present invention, the call service module is configured to execute the test script and output the result.
In a specific embodiment of the present invention, the SIP protocol module is configured to set a UDP port used for sending and receiving SIP protocol messages by configuring a config.
In a specific embodiment of the present invention, the WIN protocol module is configured to set a port, to which the call control service module is connected to the tcap _ ansi process, by configuring config.server.gen when the call control service module simulates an MSC to initiate a WIN protocol call.
In a specific embodiment of the present invention, the INAP/CAP protocol module is configured to set a port, to which the call control service module is connected to the tcap process, by configuring config.server.gen when the call control service module simulates SSP to initiate an INAP/CAP protocol call.
In one embodiment of the invention, a SIPGW gateway is added between the call control service module and SCP service component as needed to distribute calls.
In a specific embodiment of the present invention, the tcap _ ansi process on the call control service module side is connected to the tcap _ ansi process on the SCP service component side through a sccp interface.
In a specific embodiment of the present invention, the tcap process on the call control service module side is connected to the tcap process on the SCP service component side through a sccp interface.
In a specific embodiment of the present invention, in the test script of the WIN protocol, each flow of the calling party and the called party includes a call session; in the test script of the SIP protocol, a calling party and a called party in each process comprise an outgoing call session and an incoming call session; in the test script of the INAP/CAP protocol, each flow comprises a call session.
For the convenience of understanding the above technical aspects of the present invention, the following detailed description will be given of the above technical aspects of the present invention in terms of specific modes of use.
Script primitive description:
the call control service needs to process service call flows of different protocols, so that the script language describing the call flow needs to have universality and can adapt to call scenes of various protocols.
The call control service divides call processing into two layers of service of script analysis and interface protocol processing. The script analysis service is only responsible for analyzing and executing the call flow script, and calls the interface protocol service of the lower layer through the universal ines interface to receive and send messages.
The call flow script is composed of operations to be executed, and each operation is basically composed as follows:
table 1 script primitive operational elements
| Type of operation | Type of protocol | | Parameter | 1 | |
… |
Each field is divided by a blank space in the operation, the script analysis service only processes the operation type and the protocol type, and the message type and the parameters are synthesized by the script analysis service into an xml message body and sent to the interface protocol service for processing.
The operation types include: send, recv, wait, and checkdb.
(1) The send operation is used for controlling the interface protocol service to send a specified message;
(2) recv operation is used for judging messages received by the interface protocol service;
(3) wait operation is used for controlling the script to wait to be executed;
(4) the checkdb operation is used to check the database tables according to specified conditions.
The state flow of each operation is as shown in fig. 2:
the protocol types include: SIP, WIN and INAP/CAP, calling control service calls corresponding protocol interface service according to protocol type.
The servicekeys of the protocol interface services corresponding to the SIP protocol are 1 and 2, which respectively correspond to SIP _ out.
Servicekeys of protocol interface services corresponding to the WIN protocol are 3 and 4, which correspond to WIN _ out.
The servicekeys of the protocol interface services corresponding to the INAP/CAP protocol are 5 and 6, which respectively correspond to the inac _ out.
Script session description:
(1) different flows of calling and called exist in the call processing flow of most services, and the call control service needs to support the description of a plurality of flows in one script. According to the multi-session requirement, a session identifier is added in the operation type of the execution script, and is used for the script to analyze the interface service on which the service distinguishing operation is executed. The session identification is added in the operation type field, split in ":" and operation type. The multiple instances of the interface service are associated with the unique script analysis service by adding the session identifier in the ines message, and the script analysis service uniformly schedules and runs the whole call flow. And the script analysis service automatically creates and associates the session according to the execution script.
(2) In the test script of the SIP protocol, each flow (calling party, called party, etc.) includes an outgoing call session and an incoming call session.
(3) In the test script of the WIN protocol, each flow (caller, callee, etc.) comprises a call session.
(4) In the test script of INAP/CAP protocol, each flow comprises a call session.
Taking a SIP call as an example, the call controls session association in the service call process, as shown in fig. 3.
And (3) script syntax description:
the script of the call control service is composed of primitives, each of which is composed of an operation type, a protocol type, a message type, and a parameter sequence. Definition of operation type and protocol type. The message type is the name of the message to be sent and received, and the parameter sequence is the parameter item contained in the message. The parameter items in the parameter sequence are divided by spaces, each parameter item comprises a parameter type and a parameter value, and the parameter types and the parameter values are divided by "|". The operation primitive can be written in rows, the unfinished row ends with a character "\", and the last row does not end with a character "\" to indicate that the entire operation ends. The parameter items of the operation primitive support variable representation, starting with the character "$" followed by the parameter name. The variable indicates that the parameter value transmission was obtained from the last received message. The script of callgen supports the annotation function, the annotation line is started with the character "#", and it must be the first character that is "#".
SIP syntax:
(1) SIP messages
Since SIP message construction is relatively complex, the script breaks down the message types of INVITE and 200OK into 3 fields, respectively, with the characters between the fields being split.
Table 2SIP message list:
INVITE message type definition, as shown in table 3:
table 3SIP message INVITE type format:
| message type | SDP* | Number format |
The message type is INVITE;
SDP is the address information of the calling terminal in the INVITE message, and is selected from CALL/SIP/SDP in the CALL.
The number format includes both sip and tel, specifying the manner in which the number is encoded in the INVITE message.
200/6xx/ACK/UPDATE/PRACK message types are defined as follows:
table 4SIP message 200/6xx/ACK/UPDATE/PRACK type format:
| message type | Name of method | SDP* |
The message type is 200;
the method name is that the 200OK message corresponds to that request, e.g., INVITE, BYE, CANCEL, etc.;
SDP is called terminal address information in the 200OK message, selected from callgen. If the SDP is not present in the 200OK message, the entry may not be filled in.
Examples of SIP applications are:
scenario script for calling number 13331113448 of telecom cell phone to call called number 13331113449:
send:0SIP INVITE:SDP0:sip URL|13331113449 TO|13331113449\
FROM|13331113448PAI|13331113448ROUTE|call＝orig
wait 5
recv:1SIPINVITEURL|+8613331113449TO|+8613331113449 FROM|13331113448\
PAI|3448
send:2 SIP INVITE:SDP0:sip URL|+8613331113449 TO|+8613331113449\
FROM|13331113448 PAI|3448 ROUTE|call＝term
wait 5
recv:3SIPINVITEURL|+8613331113449TO|+8613331113449 FROM|13331113448\
PAI|3448
send:3 SIP 180
wait 5
recv:2 SIP 180
send:1 SIP 180
wait 5
recv:0 SIP 180
wait 5
send:3 SIP 200:INVITE:SDP1
wait 5
recv:2 SIP 200
send:1 SIP 200:INVITE:SDP1
wait 5
recv:0 SIP 200
send:0 SIP ACK
wait 5
recv:1 SIP ACK
send:2 SIP ACK
wait 5
recv:3 SIP ACK
wait 10
send:0 SIP BYE
wait 5
recv:1SIP BYE
WIN parameters:
table 5WIN message parameter list:
WIN application example
Scenario for CDMA calling number 18900000000 calling called number 18911111111:
send:0WIN ORREQ trigger|26 called|18911111111 calling|18900000000\
mdn|18911111111esn|00000000msc|111111ms|000000
wait 5
recv:0WIN orreq
send:0WINANLYZDtrigger|26 called|18911111111 calling|18900000000\
mdn|18911111111msc|111111
wait 5
recv:0WIN anlyzd
wait 5
send:0WIN OANSWER
wait 5
send:0WIN ODISCONNECT
wait 5
recv:0WIN odisconnect
INAP/CAP grammar
INAP/CAP messages
TABLE 6INAP/CAP message List
INAP/CAP parameters, as shown in Table 9.
TABLE 7 INAP/CAP message parameter List
Examples of the applications
Scene script of fixed network calling number 01058853201 calling called number 01067544011:
end:0INAP IDP servicekey|200\
called|01067544011calling|01058853201
wait 5
recv:0INAP RRBE
wait 5
recv:0INAP ETC
send:1INAP ARI$scf_id$correlation_id
wait 5
recv:1INAP PA
wait 5
send:1INAP SRR
send:1INAP TC_END
wait 5
recv:0INAP DFC
wait 5
recv:0INAP ReleaseCall
script execution description
The scripts executed by the call control service are stored in the $ HOME/cin/case directory. When the call control service executes the scripts in batch, the script files under the $ HOME/cin/case directory are sorted according to the file names, and then the scripts are executed in sequence.
The execution result of the callgen script is recorded in the $ HOME/cin/callgen.log file, and the callgen.log file is created again each time the script execution is called by a command. When the script execution is abnormal, the call control service records the script file name, the line number and the error reason.
The call control service provides two starting test modes, one is a batch execution mode; the other is a single script execution mode. Before starting the test, firstly using an access to enter a call control service (the input is a scfgen in an access prompt), and the starting test command is as follows: i 0< script _ name >.
(1) And when the script _ name is 0, starting batch execution.
(2) When the script _ name is the script name, single script execution is started.
Instructions for use
Installing and deploying:
(1) decompressing, installing and deploying a package of a testing system callgen.
(2)tar zxvf callgen.tar.gz；
1. If the service supporting the tested system is based on the sip protocol, the system is configured
2. If the tested system is supported by the service based on the inap protocol, cin/etc/config.tcapgen is configured
USER APPDLGID LOGIN ROUTINE SOCKET CLIENT 192.168.2.217 27752
SCCP ROUTINE SOCKET SERVER 27753
LocalAddress 65794 200
TransactionTimer 600
baseDialogueID 100000000
maxTrans 10000
Description of the drawings: the first row configures the ip address 192.168.2.217 and port 27752 of the system under test
3. And if the tested system is supported to be the service based on the win protocol, configuring cin/etc/config
USER APPDLGID LOGIN ROUTINE SOCKET CLIENT 192.168.2.218 65667SCALE 6
SCCP ROUTINE SOCKET SERVER 2777
localAddress[1305ff040c001202]62237300
remoteGT 4252161 13[1292001204]8613741351
transactionTimer 600
baseDialogueID 1000000
groupID 0
maxTrans 100
timeUnit 100
Description of the drawings: the first row configures the ip address 192.168.2.218 and port 65667 of the system under test
4. Initiating call control services
Executing a command: init
Executing a command: access 88999
Executing a command: a scfgen0
The start is successful.
Instructions for use:
1. arranging the test scripts, storing the test scripts as text types, and placing the test scripts under a $ home/cin/case directory;
1) to test services supporting the win protocol, the CDMA calling number 18900000000 calls are numbered
Function scene scripts of code 18911111111, saved as win _ 1.0.1:
send:0WIN ORREQ trigger|26 called|18911111111 calling|18900000000\
mdn|18911111111esn|00000000msc|111111ms|000000
wait 5
recv:0WIN orreq
send:0WINANLYZDtrigger|26called|18911111111
calling|18900000000\
mdn|18911111111msc|111111
wait 5
recv:0WIN anlyzd
wait 5
send:0WIN OANSWER
wait 5
send:0WIN ODISCONNECT
wait 5
recv:0WIN odisconnect
2) to test the service supporting the inap protocol, the fixed network calling number 01058853201 calls the function scenario script of the called number 01067544011, which is stored as inap _ 1.0.2:
send:0INAP IDP servicekey|200\
called|01067544011calling|01058853201
wait 5
recv:0INAP RRBE
wait 5
recv:0INAP ETC
send:1INAP ARI$scf_id$correlation_id
wait 5
recv:1INAP PA
wait 5
send:1INAP SRR
send:1INAP TC_END
wait 5
recv:0INAP DFC
wait 5
recv:0INAP ReleaseCall
3) to test the service supporting the sip protocol, the functional scenario script of the called number 13331113449 called by the calling number 13331113448 of the telecom handset is stored as sip _ 1.0.3:
send:0 SIP INVITE:SDP0:sip URL|13331113449 TO|13331113449\
FROM|13331113448PAI|13331113448ROUTE|call＝orig
wait 5
recv:1SIPINVITEURL|+8613331113449TO|+8613331113449
FROM|13331113448\
PAI|3448
send:2SIP INVITE:SDP0:sip URL|+8613331113449 TO|+8613331113449\
FROM|13331113448PAI|3448ROUTE|call＝term
wait 5
recv:3SIPINVITEURL|+8613331113449TO|+8613331113449FR OM|13331113448\
PAI|3448
send:3 SIP 180
wait 5
recv:2 SIP 180
send:1 SIP 180
wait 5
recv:0 SIP 180
wait 5
send:3 SIP 200:INVITE:SDP1
wait 5
recv:2 SIP 200
send:1 SIP 200:INVITE:SDP1
wait 5
recv:0 SIP 200
send:0 SIP ACK
wait 5
recv:1 SIP ACK
send:2 SIP ACK
wait 5
recv:3 SIP ACK
wait 10
send:0SIP BYE
wait 5
recv:1SIP BYE
send:2SIP BYE
wait 5
recv:3SIP BYE
2. executing scripts
1) Executing a single script command: i 0< script _ name >
2) Executing script commands in batches: i 00
3. Viewing execution script results
The execution result of the call control service script is recorded in a $ HOME/cin/callgen.log file, and the callgen.log file is created again each time the script execution is called by a command.
Log records the future success! Indicating that the authenticated call function passed.
Log will record the script file name, line number and error reason when the script execution is abnormal.
The noun explains:
WIN: wireless Intelligent Network Protocol;
INAP: intelligent Network Application Protocol, Intelligent Network Application Protocol;
CAP: CAMEL Application Part, CAMEL Application protocol;
SIP: session Initial Protocol, Session initiation Protocol;
INVITE: inviting the user to join the call;
and ACK: confirming that the client has received a final response to the INVITE;
OPTIONS: an option to request information about the capabilities of the server;
BYE: terminating the call between the two users on the call;
CANCEL: canceling the call;
REGISTER: registering, providing mapping of address resolution, and enabling the server to know the positions of other users;
UPDATE: updating the information;
PRACK: a provisional response confirmation;
ORREQ, establishing a call;
ANALYZD call addressing;
OANSWER response;
ODISCONNECT terminates the call;
InitialDP: reporting the call;
InitiateCallAttempt: starting a call trial;
connection: connecting a target user;
ReleaseCall: releasing the call;
ApplyChargingReport: and (6) reporting the charging.
In summary, by means of the above technical solution of the present invention, a plurality of communication protocol test systems of WIN, INAP, and SIP are supported by the system; the testing process of the calling class is simplified; the user can complete the test only by compiling a simple and understandable call flow script without paying attention to the bottom layer signaling message so as to improve the test efficiency; and users who do not understand WIN, INAP and SIP communication protocols are easy to grasp and use quickly.
The above description is only exemplary of the present invention and should not be taken as limiting the invention, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (4)
1. A test system supporting WIN, INAP and SIP communication protocols is characterized by comprising: the call control service module is used for reading the script file of txt, initiating, establishing and releasing a plurality of calls, dynamically adjusting the call rate and simulating a large number of calls to a tested system; the call control service starting test mode comprises a batch script execution mode and a single script execution mode;
the call control service module comprises a call service module and a protocol interface service module;
the call service module is used for executing the test script and outputting a result, analyzing and executing the call flow script, and calling the interface protocol service of the lower layer through the universal ines interface to receive and send messages;
the protocol interface service module is used for processing the receiving and sending of each protocol message and supporting the initiation, establishment and release of a call, and comprises an SIP protocol module, a WIN protocol module and an INAP/CAP protocol module;
the SIP protocol module is used for setting a UDP port used for receiving and sending SIP protocol messages by configuring config.as.gen when the call control service module simulates SIP protocol calls;
the WIN protocol module is used for setting a port for connecting the call control service module with the tcap _ ansi process by configuring config.server.gen when the call control service module simulates the MSC to initiate WIN protocol call;
the INAP/CAP protocol module is used for setting a port for connecting the call control service module with the tcap process by configuring config.server.gen when the call control service module simulates SSP to initiate an INAP/CAP protocol call;
in the test script of the WIN protocol, a calling party and a called party in each process comprise a calling session; in the test script of the SIP protocol, a calling party and a called party in each process comprise an outgoing call session and an incoming call session; in the test script of the INAP/CAP protocol, each flow comprises a call session.
2. A test system supporting WIN, INAP, SIP communication protocol in accordance with claim 1 wherein a SIPTW gateway is added between the call control service module and SCP service component to distribute calls as required.
3. A test system supporting WIN, INAP and SIP communication protocols according to claim 1, wherein the tcap _ ansi process at the call control service module side is connected with the tcap _ ansi process at the SCP service component side through a sccp interface.
4. A test system supporting WIN, INAP and SIP communication protocols according to claim 1, wherein the tcap process at the call control service module side is connected with the tcap process at the SCP service component side through a sccp interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911362462.7A CN110932943B (en) | 2019-12-26 | 2019-12-26 | Test system supporting WIN, INAP and SIP communication protocols |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911362462.7A CN110932943B (en) | 2019-12-26 | 2019-12-26 | Test system supporting WIN, INAP and SIP communication protocols |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110932943A CN110932943A (en) | 2020-03-27 |
| CN110932943B true CN110932943B (en) | 2022-09-23 |
Family
ID=69861057
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911362462.7A Active CN110932943B (en) | 2019-12-26 | 2019-12-26 | Test system supporting WIN, INAP and SIP communication protocols |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110932943B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112866063A (en) * | 2021-02-19 | 2021-05-28 | 上海中通吉网络技术有限公司 | SIP protocol pressure measurement tool based on Jmeter |
| CN113259201B (en) * | 2021-06-17 | 2023-10-10 | 中国农业银行股份有限公司 | Link performance test method, device, server and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1968427A (en) * | 2005-11-18 | 2007-05-23 | 中兴通讯股份有限公司 | Method for operating traditional intelligent network service in soft switching network |
| CN101547266A (en) * | 2008-03-29 | 2009-09-30 | 华为技术有限公司 | Method and system for providing intelligent service and gateway |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1758612B (en) * | 2004-10-10 | 2010-06-30 | 北京中创信测科技股份有限公司 | Method for simulating multi-protocol simulation flow by state apparatus |
| CN101222385B (en) * | 2008-01-18 | 2011-03-16 | 重庆重邮东电通信技术有限公司 | Design method and system of protocol simulation system facing service |
| US8375144B2 (en) * | 2010-03-22 | 2013-02-12 | Metaswitch Networks Ltd | System for connecting applications to legacy and next generation networks |
-
2019
- 2019-12-26 CN CN201911362462.7A patent/CN110932943B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1968427A (en) * | 2005-11-18 | 2007-05-23 | 中兴通讯股份有限公司 | Method for operating traditional intelligent network service in soft switching network |
| CN101547266A (en) * | 2008-03-29 | 2009-09-30 | 华为技术有限公司 | Method and system for providing intelligent service and gateway |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110932943A (en) | 2020-03-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7454505B2 (en) | Communication endpoint supporting multiple provider models | |
| JP6348926B2 (en) | Telephone communication application service | |
| US6189031B1 (en) | Method and system for emulating a signaling point for testing a telecommunications network | |
| CN103763446B (en) | Use the IMS network access of existing equipment | |
| CN101156393B (en) | Method for processing registration message according to inceptive filtering regulation in IMS network | |
| US6421424B1 (en) | Client simulator and method of operation for testing PSTN-to-IP network telephone services for individual & group internet clients prior to availability of the services | |
| US8532092B2 (en) | Methods, systems, and computer readable media for providing next generation network (NGN)-based end user services to legacy subscribers in a communications network | |
| CN110932943B (en) | Test system supporting WIN, INAP and SIP communication protocols | |
| KR20040077677A (en) | Call processing in mobile telecommunications networks | |
| CN101478458A (en) | SIP protocol security test method | |
| CN104883704B (en) | A kind of automatic error correction method and device of mobile terminal access point parameters | |
| US8639740B2 (en) | Communication server with a service logic execution environment | |
| US7809368B2 (en) | Architecture for location independent, automated integration testing and quality assurance of next generation IMS services | |
| MX2010005458A (en) | Systems and methods for automatic user-enabled account identifier association. | |
| US7756139B2 (en) | Apparatus and method for converting megaco protocol | |
| WO2002039757A1 (en) | Transmission of service data | |
| US8027435B2 (en) | Method and system for protocol embedded automated test control | |
| CN101184258A (en) | Message intercommunication method, system and message intercommunication entity | |
| CN101232536A (en) | Malicious call identification method | |
| US20060069783A1 (en) | Program, method and device for managing information shared among components, recording medium and communication apparatus | |
| US7974611B2 (en) | Method, apparatus or software for managing a call in a telecommunications network | |
| CN105915665A (en) | Method for managing a user in a telecommunication network, and associated device | |
| CN109151221A (en) | Call prompting method reminds server and computer readable storage medium | |
| CN101789932B (en) | Game service processing method, device and system | |
| US20080267174A1 (en) | Method, Apparatus And Software For Providing Communications Between A Packet Switched Network And A Public Switched Telephone Network |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |