CN102263808A - Session control service method, device and system - Google Patents
Session control service method, device and system Download PDFInfo
- Publication number
- CN102263808A CN102263808A CN2010101947176A CN201010194717A CN102263808A CN 102263808 A CN102263808 A CN 102263808A CN 2010101947176 A CN2010101947176 A CN 2010101947176A CN 201010194717 A CN201010194717 A CN 201010194717A CN 102263808 A CN102263808 A CN 102263808A
- Authority
- CN
- China
- Prior art keywords
- session
- node
- source address
- control service
- received
- 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.)
- Granted
Links
Images
Abstract
The invention discloses a session control service method, a session control service device and a session control service system. A session service node modifies a source address of a maintained transaction state into the last hop of address on the session control service system according to received session initializing information; and the session service node performs subsequent session interaction crossing a load balancing device according to the modified source address. By the session control service method, the session control service device and the session control service system, load of the load balancing device can be reduced and the load balancing device is prevented from becoming a performance neck of the whole session control service system.
Description
Technical field
The present invention relates to the communications field, be specifically related to a kind of session control method of servicing, device and system.
Background technology
SIP (conversation initialized protocol) is the session protocol that comprises repeatedly negotiations process, SCS (session control service system) needs that are used for SIP session control service will all be transmitted to same SS (conversational services) node from all message of the complete S IP session of same UE (subscriber equipment), and this SS node also can be with the sip response message loopback in this complete S IP session to same UE.
At present, have two kinds in order to the main flow way that realizes above-mentioned specification requirement: a kind of main flow way provides the LB (load balancing device) of front-end proxy agent form, this load balancing device is transmitted data according to the information that extracts and is safeguarded and transmit record from sip message, to guarantee that UE sends to same SS node with all interactive information in this session, this session between UE and the SS node can correctly be carried out.
This way need write down the transmit status of sip message, yet when situation such as the machine of delaying occurring when the load balancing device, before the subsequent message of the session of carrying out can't be properly routed to corresponding SS node; Adding subsequent session message all needs through this load balancing device, so very big for the performance impact of system.
Another kind of main flow way is: the load balancing device is specifically designed to the IP exchanges data, according to the packet source IP address sip request message is forwarded to corresponding SS node, will distributes to the SIP business processing device from the SIP data service of external network according to the equilibrium configuration.
Though this way does not need to carry out the Session Initiation Protocol data processing of network application layer, and is high to hardware requirement; And still need to write down the transmit status of sip message, follow-up conversation message also needs by the load balancing device.
As seen, present load balancing device all needs to write down the transmit status of sip message, and belongs to the also necessary process load balancing of the subsequent session message device ability correct route of same session, cause the load balancing device to become the performance bottleneck of whole SCS.This disaster tolerance that obviously is unfavorable for SCS is handled, and can have a strong impact on carrying out smoothly of session process.
Summary of the invention
In view of this, main purpose of the present invention is to provide a kind of session control method of servicing, device and system, to reduce the load of load balancing device, avoids the load balancing device to become the performance bottleneck of whole SCS.
For achieving the above object, technical scheme of the present invention is achieved in that
A kind of session control method of servicing, this method comprises:
The SS node is according to the conversation initialization information received, is the last jumping address of SCS with the source address modification of the transaction status safeguarded; The subsequent session that the SS node is crossed LB according to amended source address is mutual.
Described SCS last one jumps the received and the rport value in via territory in the conversation initialization request message of receiving for the SS node address,
The process of revising described source address comprises:
The SS node reads the received and the rport value in via territory in the conversation initialization request message of receiving, and the source address modification of the transaction status that will safeguard for current sessions is received and the rport value that is read.
Further comprise:
SentHost and sentPort value in the via territory of transmission message institute foundation are composed respectively to described received and rport.
The SS node carries out described subsequent session when mutual, and the process of carrying out session interaction with the session initiator comprises:
The SS node will be crossed the load balancing device from session recipient's the response message that shows acceptance and/or end session and directly send to described session initiator according to the source address of the transaction status of safeguarding for current sessions.
Described LB is the non-SIP entity of application layer.
A kind of session control service unit, this device comprise session control service unit, routing iinformation maintenance unit; Wherein,
Described routing iinformation maintenance unit is used for according to the conversation initialization information received, is the last jumping address of SCS with the source address modification of the transaction status safeguarded;
Described session control service unit, the subsequent session that is used for crossing according to amended source address LB is mutual.
Described SCS last one jumps the received and the rport value in via territory in the conversation initialization request message of receiving for the SS node address;
Described session control service unit is used to receive described received and rport value and sends to described routing iinformation maintenance unit;
Described routing iinformation maintenance unit, the source address modification that is used for the transaction status that will safeguard for current sessions is received and the rport value of receiving.
A kind of session control service system, this system comprises SS node, LB; Described SS node is used for according to the conversation initialization information received, is the last jumping address of SCS with the source address modification of the transaction status safeguarded; And it is mutual to cross the subsequent session of LB according to amended source address.
Described SS node comprises routing iinformation maintenance unit, session control service unit; Wherein,
Described routing iinformation maintenance unit is used for according to the conversation initialization information received, is the last jumping address of SCS with the source address modification of the transaction status safeguarded;
Described session control service unit, the subsequent session that is used for crossing according to amended source address LB is mutual.
Described LB is the non-SIP entity of application layer; Described SCS last one jumps the received and the rport value in via territory in the conversation initialization request message of receiving for the SS node address;
Described session control service unit is used to receive described received and rport value and sends to described routing iinformation maintenance unit;
Described routing iinformation maintenance unit, the source address modification that is used for the transaction status that will safeguard for current sessions is received and the rport value of receiving.
Session control method of servicing of the present invention, device and system can reduce the load of load balancing device, avoid the load balancing device to become the performance bottleneck of whole SCS.
Description of drawings
Fig. 1 is the application scenarios schematic diagram of SCS;
Fig. 2 is the system diagram of the SCS of one embodiment of the invention;
Fig. 3 is the schematic diagram of SCS deployment examples among Fig. 2;
Fig. 4 is the session control service procedure figure of one embodiment of the invention;
Fig. 5 is the session control service procedure figure of another embodiment of the present invention;
Fig. 6 is a session control service procedure sketch of the present invention.
Embodiment
Propose a kind of new load balancing mentality of designing below, mainly utilize the application layer routing rule in the Session Initiation Protocol to realize high performance session control service ability by integration.
In general, can change the load balancing device into the session ways of distribution by simple directed forward mode, the load balancing device that is positioned at the SCS front end is responsible for receiving new conversation request message, and be responsible for transmitting this message and give the SS node that is positioned at the SCS rear end, the SS node is made amendment to the routing iinformation of supporting subsequent session according to the relevant routing rule of Session Initiation Protocol after receiving this message, make the follow-up reciprocal process of this session move on this SS node, and no longer pass through the load balancing device of front end.
The aforesaid operations mode needs the directed working method of transmitting all conversation messages with traditional load balancing device, change the mode of distribution session task into, the carrying out of session almost carried out between SS node and UE entirely, and no longer by the load balancing device, so just obviously reduced the load of load balancing device, and significantly promoted system processing power, therefore can avoid the load balancing device to become the performance bottleneck of whole SCS.If load balancing device collapse in the subsequent session process only needs the start-up system backup so that the load balancing device recovers operate as normal; So neither influence existing session, also can fast and reliable ground starting load balancer, to receive new conversation request message, at utmost reduce call loss.
In actual applications, SCS of the present invention runs under the of future generation high trustable network background of fusion, as: the of future generation high trustable network of the integration of three networks shown in Figure 1.SCS can unify to receive and handle the service request from networks such as telecommunications network, Broadcasting Cable Network, the Internets, set up and safeguard concrete session connection according to the conversational service request that receives, make between the terminal on the identical or different network and can carry out session connection.Particularly, above-mentioned conversational service request can be a conversation request message, and this message is carried with Session Initiation Protocol.By the SIP signaling is carried out analyzing and processing, SCS can provide support for the dynamic assignment of the session control of conversational service, session life cycle management, Session Resources and optimization etc.
As shown in Figure 2, SCS comprises the load balancing device that is positioned at front end and is positioned at the SS node of rear end, is SS node distribution sip message by the load balancing device, and the SS node carries out conversational services according to the sip message that receives again.
Particularly, the load balancing device can be according to the SIP conversation request message that receives from network, judge according to the sip message specific format whether this message is the conversation initialization request message, and the result is then according to polling algorithm this conversation initialization request message to be transmitted to the SS node.So far, the conversation initialization request message has been transmitted to the SS node, and the pairing whole session of this conversation initialization request message will be moved on the SS node, and the subsequent session message of this session will no longer be passed through the load balancing device.
Session control service unit in the SS node can be carried out the dynamic assignment and the optimization of SIP session processing, life cycle management and Session Resources, and can be pressed into this SS node communication address from application layer according to the SIP routing policy of RFC3261 regulation.In existing application, the Session Initiation Protocol stack generally can be safeguarded a transaction status (as the resiprocate protocol stack) for the SIP affairs, and this transaction status comprises the source address and the destination address of packet.The value that source address is preserved is generally one and jumps the address.The source address modification of the transaction status that the routing iinformation maintenance unit in the SS node can be safeguarded the SS node is that SCS last jumps the address, the value that makes amended source address is received the SCS last of this message for the load balancing device and is jumped the address, to reach the effect of shielding load balancing unit address, thereby make follow-up sip response, conversation request message etc. can cross the load balancing device, reach and make session move to the purpose of SS node from the load balancing device.
Described SCS last one jumps the received and the rport value in via territory in the conversation initialization request message that can be received for the session control service unit in the SS node address, and the session control service unit can send to the routing iinformation maintenance unit with this received and rport value, and the source address modification of the transaction status that will be safeguarded for current sessions by the routing iinformation maintenance unit is received and the rport value of receiving.
What need explanation a bit is when the SIP software terminal among the UE sends message according to the RFC3261 relevant regulations, to be to send according to sentHost in the via territory and sentPort; If run into special application scenarios (situation such as passing through) as fire compartment wall or subnet, described message is to send according to received in the via territory and rport value, the value of sentHost and sentPort can be composed respectively to received and rport in this case, can be realized smoothly that to guarantee UE message sends.
When the load balancing device in using system shown in Figure 2 communicates, can be implemented in common double-core PC and go up up to 7000 forwarding rates more than the INVITE of per second.When the SS node produces performance loss because of using the Session Initiation Protocol stack, can be as shown in Figure 3 with the mode compensating loss of energy of multi-link SS node.Owing to be the distributed conversation service system, so the load balancing device can be deployed on the physical node identical with the SS node, also can be deployed on the physical host separately.
When load balancing device and SS node are deployed on the different physical hosts respectively, adopt the network address and transport layer address to communicate between load balancing device and the SS node.When starting a SS node, this SS node can initiatively be registered on the load balancing device.Afterwards, even the load balancing device is restarted because of a variety of causes,, also can make the load balancing device have the communication information of all SS nodes because the heartbeat heartbeat that the SS node is sent is the heartbeat of registration type.Therefore the load balancing device can correctly be distributed to the SS node with session initialization request message, realizes constantly monitoring the ability of all SS nodes.And load balancing device and SS node all can be monitored the data flow in the network, so that handle session signaling at any time, and the delay problem that can not cause the queuing of user's demand signalling to cause.
Referring to Fig. 4, Fig. 4 is the session control service procedure figure of one embodiment of the invention, and this flow process may further comprise the steps:
Step 401:LB receives the conversation request message in the network, according to sip message format analysis packet.
Step 402:LB judges whether the conversation request message of being received is the conversation initialization request message, if enter step 403; Otherwise, return step 401.
Step 403: session initialization request message is sent to the SS node.
Step 404:SS node receives conversation initialization request message and subsequent session message.
Step 405:SS node judges whether the message of receiving is effective request, if enter step 406; Otherwise, enter step 411.
Step 406:SS node judges whether the message of being received is the conversation initialization request message, if enter step 407; Otherwise, enter step 409.
Step 407:SS node is that SCS last jumps the address with the source address modification of the transaction status of maintenance.
The contact address of step 408:SS querying node called subscriber registration, the called location of routing addressing; Return 404.
Step 409:SS node judges whether the message of being received is the subsequent message of the local session of being kept, if enter step 410; Otherwise, enter step 411.
Step 410:SS node carries out the subsequent session Message Processing, returns step 404.
Step 411:SS node error process, log, delivery system takies resource, responds related news; Return step 404.
When the current sessions at UE carried out the session control service, the signalling interactive process of flow process shown in Figure 4 can be represented as shown in Figure 5.Referring to Fig. 5, Fig. 5 is the session control service procedure figure of another embodiment of the present invention.Among Fig. 5, message in the whole session process has only the conversation initialization request message through the load balancing device, follow-up conversation message is by after the processing of SS node, all can cross the load balancing device and directly and the SS node mutual, therefore very little to the load pressure of load balancing device, this has not only improved the distribution capability of load balancing device, also can avoid the load balancing device machine of delaying from another angle as far as possible.
Flow process shown in Figure 5 may further comprise the steps:
Step 501: when UEA wished to call out UE B, UE A sent conversation request message to LB, and this conversation request message is the conversation initialization request message in conversation initial stage.
Step 502: the load balancing device receives the conversation request message of UE A from network, confirms that by analysis this message is the conversation initialization request message, load balancing device and then this message is distributed to available SS node according to polling algorithm.
And the SS node can be according to the conversation initialization request message of being received, the source address modification of the transaction status that will safeguard for current sessions is that SCS last jumps the address, and safeguards amended source address; As: the SS node reads the received and the rport value in via territory in the conversation initialization request message of receiving, and the source address modification of the transaction status that will safeguard for current sessions is received and the rport value that is read, make the SS node in subsequent session, can directly with as UE A directly notify, and cross LB according to amended source address from a jumping on one's body.
Certainly, if the SCS of SS node last jump be not UE A but be connected in UE A and the SS node between other SIP application layer entity, the source address modification of the transaction status that then will safeguard for current sessions of SS node is this SIP application layer entity address so.
Step 503:SS node is pressed into the application layer routing iinformation in the conversation initialization request message of being received after related news such as validation verification are handled.Afterwards, the SS node navigates to concrete called subscriber UE B with current sessions, and this conversation initialization request message is crossed the load balancing device directly sends to UE B.
Step 504:UE B directly returns 180 jingle bells/response messages such as 200 affirmations to the SS node.
Step 505:SS node will be crossed the load balancing device from the response message that showing of UEB accepts session and directly send to UEA according to the source address of the transaction status of safeguarding for current sessions.
Step 506:UE A stipulates to SS node loopback ACK acknowledge message according to RFC3261 after receiving that 180 jingle bells/200 of UE B are confirmed.
Step 507:SS node directly receives the ACK acknowledge message that UEA sent from network, behind the state of preserving this session this ACK acknowledge message is sent to the B by UE.
Step 508: in follow-up communication process, UE A and UE B all have the right to stop current session.Suppose the session that the UEA active termination is current, UE A sends BYE on-hook message to the SS node, and the SS node directly sends to the SS node according to RFC3261 with this BYE on-hook message.
Step 509:SS node sends this BYE on-hook message to UE B according to RFC3261 after receiving the BYE on-hook message of UEA transmission.
After step 510:UE B receives BYE on-hook message, wait response message to the SS node, finish current sessions according to RFC3261 transmission 200 affirmations.
After step 511:SS node was received and confirmed from 200 of UE B, the relevant information of preserving current sessions also finished this session; And according to the source address of the transaction status of safeguarding for this session, will show that 200 affirmations of end session are transmitted to UE A, and make UE A finish current sessions.
As seen from Figure 5, the conversation initialization request message need be through outside the load balancing device, and other subsequent session message all are directly to send to the SS node and need not through the load balancing device; And, as the non-SIP entity of application layer, the distribution policy of load balancing device is the poll distribution, no longer write down and keep any forwarding state, therefore having reduced the conventional load balancer need do directed work of treatment of transmitting to message, has improved the processing speed to forwards of load balancing device.In actual applications, the operating efficiency of load balancing device can improve 5 to 10 times.
Describe as can be known in conjunction with above system and flow process, session control service technology of the present invention can be represented as shown in Figure 6.Referring to Fig. 6, Fig. 6 is a session control service procedure sketch of the present invention, and this flow process may further comprise the steps:
Step 610:SS node is according to the conversation initialization information received, is the last jumping address of SCS with the source address modification of the transaction status safeguarded.
The subsequent session that step 620:SS node is crossed LB according to amended source address is mutual.
In sum as seen, the special session information that the present invention is safeguarded by the modification system, the source address of guaranteeing the transaction status that it is safeguarded is consistent with the last jumping address of SCS, can correctly carry out the application layer route according to RFC3261 when making the Session Initiation Protocol stack send message, the load balancing device is all crossed in the feasible transmission process that belongs to the subsequent session message of same session, farthest alleviate the load pressure of load balancing device, so the load balancing device is difficult for becoming the performance bottleneck of whole service system.
Load balancing device among the present invention only is responsible for the conversation initialization request message of distribution SIP session and the SIP packet is not carried out any modification, not the forwarding state of record request message etc.And, when the load balancing device is delayed machine, because terminals and the direct communication of SS node such as UE, so can not influence current ongoing session; Only need start the standby system of this load balancing device, can continue to handle smoothly follow-up conversation request message by certain backstage connection processing, thus simpler effective on technology realizes.
The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention, all any modifications of being done within the spirit and principles in the present invention, is equal to and replaces and improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1. a session control method of servicing is characterized in that, this method comprises:
Conversational services SS node is according to the conversation initialization information received, is the last jumping address of session control service system SCS with the source address modification of the transaction status safeguarded; The subsequent session that the SS node is crossed load balancing device LB according to amended source address is mutual.
2. method according to claim 1 is characterized in that, described SCS last jumps the received and the rport value in via territory in the conversation initialization request message of receiving for the SS node address,
The process of revising described source address comprises:
The SS node reads the received and the rport value in via territory in the conversation initialization request message of receiving, and the source address modification of the transaction status that will safeguard for current sessions is received and the rport value that is read.
3. method according to claim 1 is characterized in that, further comprises:
SentHost and sentPort value in the via territory of transmission message institute foundation are composed respectively to described received and rport.
4. according to each described method of claim 1 to 3, it is characterized in that the SS node carries out described subsequent session when mutual, the process of carrying out session interaction with the session initiator comprises:
The SS node will be crossed the load balancing device from session recipient's the response message that shows acceptance and/or end session and directly send to described session initiator according to the source address of the transaction status of safeguarding for current sessions.
5. according to each described method of claim 1 to 3, it is characterized in that described LB is the non-SIP entity of application layer.
6. a session control service unit is characterized in that, this device comprises session control service unit, routing iinformation maintenance unit; Wherein,
Described routing iinformation maintenance unit is used for according to the conversation initialization information received, is the last jumping address of SCS with the source address modification of the transaction status safeguarded;
Described session control service unit, the subsequent session that is used for crossing according to amended source address LB is mutual.
7. device according to claim 6 is characterized in that, described SCS last jumps the received and the rport value in via territory in the conversation initialization request message of receiving for the SS node address;
Described session control service unit is used to receive described received and rport value and sends to described routing iinformation maintenance unit;
Described routing iinformation maintenance unit, the source address modification that is used for the transaction status that will safeguard for current sessions is received and the rport value of receiving.
8. a session control service system is characterized in that, this system comprises SS node, LB; Described SS node is used for according to the conversation initialization information received, is the last jumping address of SCS with the source address modification of the transaction status safeguarded; And it is mutual to cross the subsequent session of LB according to amended source address.
9. system according to claim 8 is characterized in that, described SS node comprises routing iinformation maintenance unit, session control service unit; Wherein,
Described routing iinformation maintenance unit is used for according to the conversation initialization information received, is the last jumping address of SCS with the source address modification of the transaction status safeguarded;
Described session control service unit, the subsequent session that is used for crossing according to amended source address LB is mutual.
10. according to Claim 8 or 9 described systems, it is characterized in that described LB is the non-SIP entity of application layer; Described SCS last one jumps the received and the rport value in via territory in the conversation initialization request message of receiving for the SS node address;
Described session control service unit is used to receive described received and rport value and sends to described routing iinformation maintenance unit;
Described routing iinformation maintenance unit, the source address modification that is used for the transaction status that will safeguard for current sessions is received and the rport value of receiving.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010194717.6A CN102263808B (en) | 2010-05-28 | 2010-05-28 | Session control service method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010194717.6A CN102263808B (en) | 2010-05-28 | 2010-05-28 | Session control service method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102263808A true CN102263808A (en) | 2011-11-30 |
| CN102263808B CN102263808B (en) | 2014-04-30 |
Family
ID=45010260
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010194717.6A Expired - Fee Related CN102263808B (en) | 2010-05-28 | 2010-05-28 | Session control service method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102263808B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109145061A (en) * | 2018-07-26 | 2019-01-04 | 阿里巴巴集团控股有限公司 | A kind of method, database and the server of database distribution session object |
| CN110022344A (en) * | 2017-11-01 | 2019-07-16 | 阿里巴巴集团控股有限公司 | Communication means, non-transitory computer-readable storage media, storage access system |
| CN111491007A (en) * | 2020-03-04 | 2020-08-04 | 北京中盾安全技术开发公司 | SIP center signaling control service load balancing method and load balancer thereof |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1666476A (en) * | 2002-07-10 | 2005-09-07 | 思科技术公司 | System and method for communicating in a loadbalancing environment |
| CN101119270A (en) * | 2007-09-14 | 2008-02-06 | 华中科技大学 | Network boundary treatment method |
-
2010
- 2010-05-28 CN CN201010194717.6A patent/CN102263808B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1666476A (en) * | 2002-07-10 | 2005-09-07 | 思科技术公司 | System and method for communicating in a loadbalancing environment |
| CN101119270A (en) * | 2007-09-14 | 2008-02-06 | 华中科技大学 | Network boundary treatment method |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110022344A (en) * | 2017-11-01 | 2019-07-16 | 阿里巴巴集团控股有限公司 | Communication means, non-transitory computer-readable storage media, storage access system |
| CN110022344B (en) * | 2017-11-01 | 2022-05-31 | 阿里巴巴集团控股有限公司 | Communication method, non-transitory computer-readable storage medium, storage access system |
| CN109145061A (en) * | 2018-07-26 | 2019-01-04 | 阿里巴巴集团控股有限公司 | A kind of method, database and the server of database distribution session object |
| CN111491007A (en) * | 2020-03-04 | 2020-08-04 | 北京中盾安全技术开发公司 | SIP center signaling control service load balancing method and load balancer thereof |
| CN111491007B (en) * | 2020-03-04 | 2023-08-18 | 北京中盾安全技术开发公司 | SIP center signaling control service load balancing method and load balancing device thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102263808B (en) | 2014-04-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103339901B (en) | Terminal in content guiding network environment and the communication means of intermediate node and terminal and intermediate node | |
| US8402132B2 (en) | Method, system and device for device capabilities exchange | |
| CN109067578B (en) | Method and device for multicast fast switching | |
| CN104811459A (en) | Processing method, processing device and system for message services and message service system | |
| US10880369B2 (en) | Session persistence method, device, and storage medium | |
| CN102075343A (en) | An out-of-band management realization method, a system for the same and an out-of-band management switch | |
| CN1917512B (en) | Method for establishing direct connected peer-to-peer channel | |
| CN101631127A (en) | File transfer method and clients | |
| CN101252527A (en) | Method for transferring network, network transfer server and inner core managing module | |
| JP2007181079A (en) | Communication route control system | |
| CN102612164B (en) | A kind of restart for network element after discharge the methods, devices and systems of resource | |
| CN101137104B (en) | Method and system for implementing resource release | |
| CN102263808B (en) | Session control service method, device and system | |
| CN105516176A (en) | Call center system, communication connection method and device of call center system | |
| CN103067981B (en) | A kind of content caching by-pass method and system | |
| CN103051484B (en) | Session service processing method, system and Session Border Controll | |
| CN102137088A (en) | Message exchanging method for service delivery platform (SDP) system, SDP system and device | |
| CN103516601B (en) | Route transmission method and apparatus and system | |
| KR100773778B1 (en) | Method for controlling server with multicast transmitting and System thereof | |
| CN102299871B (en) | Communication method and gateway equipment | |
| CN101860544A (en) | Transmitting system and method of session initiation protocol message | |
| CN105577433B (en) | A kind of ACS cluster management method, device and system | |
| CN105991629B (en) | TCP connection method for building up and device | |
| CN103701943B (en) | The control method and device of MAC Address | |
| CN115334139B (en) | Communication connection control method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20140430 Termination date: 20160528 |