CN102217339A - Call callback billing method and service control equipment - Google Patents
Call callback billing method and service control equipment Download PDFInfo
- Publication number
- CN102217339A CN102217339A CN2011800004276A CN201180000427A CN102217339A CN 102217339 A CN102217339 A CN 102217339A CN 2011800004276 A CN2011800004276 A CN 2011800004276A CN 201180000427 A CN201180000427 A CN 201180000427A CN 102217339 A CN102217339 A CN 102217339A
- Authority
- CN
- China
- Prior art keywords
- call
- duration
- time
- bridge joint
- reception
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/43—Billing software details
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/41—Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/70—Administration or customization aspects; Counter-checking correct charges
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/70—Administration or customization aspects; Counter-checking correct charges
- H04M15/73—Validating charges
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
- H04M15/82—Criteria or parameters used for performing billing operations
- H04M15/8228—Session based
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42195—Arrangements for calling back a calling subscriber
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42382—Text-based messaging services in telephone networks such as PSTN/ISDN, e.g. User-to-User Signalling or Short Message Service for fixed networks
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Telephonic Communication Services (AREA)
Abstract
The embodiments of the present invention provide a call callback billing method and a service control equipment. Wherein, the call callback billing method includes: receiving a bridging success notification or a callee connection failure notification from a switching equipment, and recording the reception time of the bridging success notification or the called successive failure notification; receiving an initial billing request from the switching equipment, adjusting the session duration carried in the initial billing request according to the reception time of the bridging success notification or the called successive failure notification, and sending a billing notification containing the adjusted session duration to a billing equipment in order to enable the billing equipment to bill according to the adjusted session duration. The embodiments of the present invention can reduce the billing errors for the caller terminal in the Unstructured Supplementary Service Data CallBack (UCB) service effectively.
Description
Technical field
The present invention relates to the communication charge technology, relate in particular to a kind of calling callback charging method and business control device.
Background technology
UCB is (based on USSD (unstructured supplementary service data, Unstructured SupplementaryService Data) calling call-back service, USSD CallBack) realization principle is the HLR (attaching position register of calling terminal, Home Location Register) the response calling terminal is initiated the UCB call request, corresponding SCP (the Service Control Point of notice calling terminal home network, service control point) sets up MT (Mobile Terminated respectively towards calling terminal and terminal called, mobile terminating) calls out, again two sections MT are called out bridge joint, to realize the conversation between calling terminal and the terminal called.
In the specific implementation process of UCB business, often there is certain error in the charging of calling terminal, reason is, in the MT call setup that the charging of calling terminal is often started from calling terminal is finished, but this moment, both sides' conversation may not begin as yet.For example, if at first setting up the MT of calling terminal calls out, and the MT calling that after the MT of calling terminal call setup is finished, just begins to set up terminal called, then in the process of setting up terminal called MT calling, begun calling terminal charge (i.e. charging to calling terminal promptly begins after the MT of calling terminal call setup is finished), therefore do not begin as yet but calling terminal is produced the problem of chargeing although will cause occurring conversation, thereby make charging to calling terminal have error to a certain degree.
Summary of the invention
In view of this, in fact be necessary to provide a kind of calling callback charging method and business control device, there be the to a certain degree problem of error in the charging of calling terminal to solve existing UCB business.
According to an aspect of the present invention, provide a kind of calling callback charging method, comprising:
Reception is successfully notified or the called connection failure notification from the bridge joint of switching equipment, writes down that described bridge joint is successfully notified or the time of reception of called connection failure notification;
Reception is from the initial charging request of described switching equipment, successfully notify or the time of reception of called connection failure notification is calibrated the duration of call of carrying in the described initial charging request based on described bridge joint, send the advice of charge of the duration of call after including calibration to counting equipment, so that the duration of call of described counting equipment after according to described calibration chargeed.
According to a further aspect in the invention, provide a kind of business control device, comprising:
Transceiver module;
Logging modle is used for receiving by described transceiver module and successfully notifies or the called connection failure notification from the bridge joint of switching equipment, writes down that described bridge joint is successfully notified or the time of reception of called connection failure notification;
Calibration module, be used for by the initial charging request of described transceiver module reception from described switching equipment, successfully notify or the time of reception of called connection failure notification is calibrated the duration of call of carrying in the described initial charging request based on described bridge joint, send the advice of charge of the duration of call after including calibration by described transceiver module to counting equipment, so that the duration of call of described counting equipment after according to described calibration chargeed.
The embodiment of the invention is successfully notified based on bridge joint or the time of reception of called connection failure notification is calibrated the duration of call of carrying in the initial charging request, so that based on the duration of call after the calibration calling terminal is chargeed.Hence one can see that, and the charging of calling terminal is started from receiving that bridge joint is successfully notified or the moment of called connection failure notification, but not in the MT call setup of calling terminal finishes, and therefore can effectively reduce in the UCB business charging error to calling terminal.
Description of drawings
Fig. 1 is the exemplary flow chart according to the calling callback charging method of one embodiment of the present invention;
Fig. 2 is the exemplary signaling diagram according to the calling callback charging method of one embodiment of the present invention;
Fig. 3 is the exemplary signaling diagram according to the calling callback charging method of another preferred embodiment of the present invention;
Fig. 4 is the example logic structural representation according to the business control device of one embodiment of the present invention.
Embodiment
Fig. 1 is the exemplary flow chart according to the calling callback charging method 100 of one embodiment of the present invention.
As shown in Figure 1, step 102 receives and successfully to notify or the called connection failure notification from the bridge joint of switching equipment, writes down that described bridge joint is successfully notified or the time of reception of called connection failure notification;
By the technical problem that exists among the prior art of describing in the background technology as can be known, the charging error to calling terminal does not begin but calling terminal has been chargeed to cause because of conversation as yet.In the specific implementation process, the conversation that begins between the calling and called terminal really begins from calling terminal is chargeed, article one ACR message that the metering data that produces in this time interval is sent by switching equipment often (Apply Charging Report, the request report of chargeing) message is carried.Therefore, in the specific implementation process, only need the duration of call of carrying in this article one ACR message calibrated and get final product, this article one ACR message is above-mentioned initial charging request.
In the specific implementation process, also carry the conversation time started in the initial request of chargeing, describedly successfully notify or the time of reception of called connection failure notification is calibrated specifically the duration of call in the described initial charging request and comprised based on described bridge joint:
According to the described conversation time started with described bridge joint is successfully notified or the time of reception of called connection failure notification calculates connecting time, wherein,
Connecting time=bridge joint is successfully notified or time of reception-conversation time started of called connection failure notification;
Calculate the duration of call after the described calibration according to described connecting time and the described duration of call, wherein,
The duration of call=duration of call after the calibration-connecting time.
In the specific implementation process, described bridge joint is successfully notified and can be bridge joint success (PORTS_BRIDGED) message.
In the specific implementation process, described called connection failure notification can be for discharging (Release, Rel) message.
In the specific implementation process, described advice of charge is can CCR (credit control request, Credit-Control-Request) message.
The embodiment of the invention is successfully notified based on bridge joint or the time of reception of called connection failure notification is calibrated the duration of call of carrying in the initial charging request, so that based on the duration of call after the calibration calling terminal is chargeed.Hence one can see that, and the charging of calling terminal is started from receiving that bridge joint is successfully notified or the moment of called connection failure notification, but not in the MT call setup of calling terminal finishes, and therefore can effectively reduce in the UCB business charging error to calling terminal.
Fig. 2 is the exemplary signaling diagram according to the calling callback charging method 200 of one embodiment of the present invention.
As shown in Figure 2, step 202, after calling terminal makes a call the callback operation, the switching equipment of the current place of calling terminal network is caller location MSC (Mobile Switching Center, mobile switching centre)/VLR (Visitor Location Register, VLR Visitor Location Register) be the caller ownership place HLR callback request that makes a call to calling terminal ownership HLR (Home Location Register, attaching position register).
In the specific implementation process, above-mentioned calling callback request can realize by USSD Req message.
In the specific implementation process, caller ownership place HLR can ask caller ownership place SCP to control calling out call-back course by above-mentioned USSD Req forwards being given caller ownership place SCP, and promptly above-mentioned calling callback control request can realize by USSD Req message.
Specifically, caller ownership place MSC/SSP is the described switching equipment of Fig. 1.
In the specific implementation process, the above-mentioned caller notice that continues can be passed through ICA (call attempt, Initiate CallAttempt) message and realizes.
In the specific implementation process, the above-mentioned caller request that continues can be passed through IAM (initial address message, InitialAddress Message) and realize.
Step 210, caller location MSC/VLR is after the successful connection calling terminal, to caller ownership place MSC/SSP notice caller successful connection.
In the specific implementation process, caller ownership place MSC/SSP receives that the time of the notice of caller successful connection is the conversation time started of carrying in the above-mentioned initial charging request.In addition, caller location MSC/VLR can pass through ACM (Address Complete Message, Address Complete Message) to caller ownership place MSC/SSP notice caller successful connection.
In the specific implementation process, caller ownership place MSC/SSP can pass through ERB (BCSM (Basic Call State Model BCSM, Basic Call State Model) event report, Event Report BCSM) message to caller ownership place SCP notice caller successful connection.
Step 214, caller ownership place SCP sends the called connection notice to caller ownership place MSC/SSP.
In the specific implementation process, above-mentioned called connection notice can realize by ICA message.
In the specific implementation process, the above-mentioned called request that continues can realize by IAM.
Step 218, called location MSC/VLR is after the successful connection terminal called, and MSC/SSP notifies called successful connection to the caller ownership place.
In the specific implementation process, called location MSC/VLR can notify called successful connection to caller ownership place MSC/SSP by ACM.
In the specific implementation process, caller ownership place MSC/SSP can notify called successful connection to caller ownership place SCP by ERB message.
Step 222, the conversation of caller ownership place SCP notice caller ownership place MSC/SSP bridge joint calling and called.
In the specific implementation process, caller ownership place SCP can pass through the conversation of BRIDGEPORTS (bridge joint) message informing caller ownership place MSC/SSP bridge joint calling and called.
Step 224, caller ownership place MSC/SSP are after successful bridge joint calling and called conversation, and SCP reports bridge joint successfully to notify to the caller ownership place.
In the specific implementation process, above-mentioned bridge joint is successfully notified and can be realized by bridge joint success (PORTS_BRIDGED) message.
Receive successfully notify from the bridge joint of caller ownership place MSC/SSP after, the time of reception that caller ownership place SCP record bridge joint is successfully notified.
Step 226, caller ownership place MSC/SSP reports article one ACR to caller ownership place SCP, and wherein, this article one ACR is the described initial charging request of Fig. 1.
Step 226, (OnlineCharging Report OCS) reports CCR to caller ownership place SCP to Online Charging System according to article one ACR.
Specifically, caller ownership place SCP calibrates the duration of call of carrying among article one ACR according to the time of reception that bridge joint is successfully notified, send the CCR of the duration of call after including calibration to OCS, so that OCS charges according to the duration of call after calibrating, wherein OCS is the described counting equipment of Fig. 1.Further, carry the conversation time started among above-mentioned article one ACR, this conversation time started is the time that caller ownership place MSC/SSP receives the notice of caller successful connection in the step 210.The time of reception of successfully notifying according to bridge joint is calibrated specifically the duration of call of carrying among article one ACR and is comprised:
The time of reception of successfully notifying according to converse time started and bridge joint calculates connecting time, wherein,
The time of reception that connecting time=bridge joint is successfully notified-conversation time started;
Calculate the duration of call after the described calibration according to connecting time and the described duration of call, wherein,
The duration of call=duration of call after the calibration-connecting time.
The time of reception that the embodiment of the invention is successfully notified based on bridge joint is calibrated the duration of call of carrying in the initial charging request, so that based on the duration of call after the calibration calling terminal is chargeed.Hence one can see that, and the charging of calling terminal is started from moment of receiving that bridge joint is successfully notified, but not calling terminal continues in the success, therefore can effectively reduce in the UCB business charging error to calling terminal.
Fig. 3 is the exemplary signaling diagram according to the calling callback charging method 300 of another preferred embodiment of the present invention.
As shown in Figure 3, step 302, after calling terminal made a call callback operation, the switching equipment of the current place of calling terminal network is caller location MSC/VLR to calling terminal ownership HLR was the caller ownership place HLR callback request that makes a call.
In the specific implementation process, above-mentioned calling callback request can realize by USSD Req message.
Step 304, the relevant SCP (just caller home network in responsible SCP that UCB business controlled) of caller ownership place HLR in the caller home network is that caller ownership place SCP sends calling callback control request, and SCP controls calling out call-back course with request caller ownership place.
In the specific implementation process, caller ownership place HLR can ask caller ownership place SCP to control calling out call-back course by above-mentioned USSD Req forwards being given caller ownership place SCP, and promptly above-mentioned calling callback control request can realize by USSD Req message.
Step 306, caller ownership place SCP sends the caller notice that continues to caller ownership place MSC/SSP, to notify caller ownership place MSC/SSP the calling terminal that continues.
Specifically, caller ownership place MSC/SSP is the described switching equipment of Fig. 1.
In the specific implementation process, above-mentioned caller continues and notifies and can realize by ICA message.
Step 308, caller ownership place MSC/SSP sends the caller request that continues to caller location MSC/VLR, with the calling terminal that continues.
In the specific implementation process, the above-mentioned caller request that continues can realize by IAM.
Step 310, caller location MSC/VLR is after the successful connection calling terminal, to caller ownership place MSC/SSP notice caller successful connection.
In the specific implementation process, caller ownership place MSC/SSP receives that the time of the notice of caller successful connection is the conversation time started of carrying in the above-mentioned initial charging request.In addition, caller location MSC/VLR can be by ACM to caller ownership place MSC/SSP notice caller successful connection.
Step 312, caller ownership place MSC/SSP is to caller ownership place SCP notice caller successful connection.
In the specific implementation process, caller ownership place MSC/SSP can be by ERB message to caller ownership place SCP notice caller successful connection.
Step 314, caller ownership place SCP sends the called connection notice to caller ownership place MSC/SSP.
In the specific implementation process, above-mentioned called connection notice can realize by ICA message.
Step 316, caller ownership place MSC/SSP sends the called request that continues to called location MSC/VLR.
In the specific implementation process, the above-mentioned called request that continues can realize by IAM.
Step 318, called location MSC/VLR fails to caller ownership place MSC/SSP notice called connection in switching called terminal failure (for example terminal called is busy or terminal called is not answered for a long time) afterwards.
In the specific implementation process, the notice of called terminal succeed failure can by discharge (Release, Rel) message is carried, this Rel message shows the requirement call release.
Step 320, the failure of caller ownership place MSC/SSP notice caller ownership place SCP called connection.
In the specific implementation process, caller ownership place MSC/SSP can be by the failure of ERB message informing caller ownership place SCP called connection.
After receiving the notice of failing from the called connection of caller ownership place MSC/SSP, the time of reception of the notice of caller ownership place SCP record called connection failure.
Step 322, caller ownership place MSC/SSP reports article one ACR to caller ownership place SCP, and wherein, this article one ACR is the described initial charging request of Fig. 1.
Step 324, (OnlineCharging Report OCS) reports CCR to caller ownership place SCP to Online Charging System according to article one ACR.
Specifically, caller ownership place SCP calibrates the duration of call of carrying among article one ACR according to the time of reception of the notice of called connection failure, send the CCR of the duration of call after including calibration to OCS, so that OCS charges according to the duration of call after calibrating, wherein OCS is the described counting equipment of Fig. 1.Further, carry the conversation time started among above-mentioned article one ACR, this conversation time started is the time that caller ownership place MSC/SSP receives the notice of caller successful connection in the step 310.According to the time of reception of the notice of called connection failure the duration of call of carrying among article one ACR is calibrated specifically and to comprise:
Time of reception according to the notice of conversation time started and called connection failure calculates connecting time, wherein,
Time of reception-conversation the time started of the notice of connecting time=called connection failure;
Calculate the duration of call after the described calibration according to connecting time and the described duration of call, wherein,
The duration of call=duration of call after the calibration-connecting time.
The embodiment of the invention is calibrated the duration of call of carrying in the initial charging request based on the time of reception of called connection failure notification, so that based on the duration of call after the calibration calling terminal is chargeed.Hence one can see that, in the moment that the charging of calling terminal is started from receiving the called connection failure notification, but not calling terminal continues in the success, therefore can effectively reduce in the UCB business charging error to calling terminal.
Fig. 4 is the example logic structural representation according to the business control device 400 of one embodiment of the present invention.As shown in Figure 4, business control device 400 comprises transceiver module 402, logging modle 404 and calibration module 406.
In the specific implementation process, also carry the conversation time started in the described initial charging request, described calibration module 406 specifically comprises:
First computing module, be used for according to the described conversation time started and described bridge joint is successfully notified or the time of reception of called connection failure notification calculates connecting time, wherein, connecting time=bridge joint is successfully notified or time of reception-conversation time started of called connection failure notification;
Second computing module is used for calculating the duration of call after the described calibration according to described connecting time and the described duration of call, wherein, and the duration of call=duration of call after the calibration-connecting time.
In the specific implementation process, described bridge joint is successfully notified the message into PORTS_BRIDGED; Described called connection failure notification is a Rel message.
In the specific implementation process, described initial charging request is an ACR message.
In the specific implementation process, described advice of charge is a CCR message.
The embodiment of the invention is successfully notified based on bridge joint or the time of reception of called connection failure notification is calibrated the duration of call of carrying in the initial charging request, so that based on the duration of call after the calibration calling terminal is chargeed.Hence one can see that, and the charging of calling terminal is started from receiving that bridge joint is successfully notified or the moment of called connection failure notification, but not in the MT call setup of calling terminal finishes, and therefore can effectively reduce in the UCB business charging error to calling terminal.
Those of ordinary skills as can be known, all or part of step in the said method can be finished by the relevant hardware of program command, this program can be stored in the computer-readable recording medium, this computer-readable recording medium such as ROM, RAM and CD etc.
In sum, more than be preferred embodiment of the present invention only, be not to be used to limit protection scope of the present invention.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1. call out the callback charging method for one kind, it is characterized in that, comprising:
Reception is successfully notified or the called connection failure notification from the bridge joint of switching equipment, writes down that described bridge joint is successfully notified or the time of reception of called connection failure notification;
Reception is from the initial charging request of described switching equipment, successfully notify or the time of reception of called connection failure notification is calibrated the duration of call of carrying in the described initial charging request based on described bridge joint, send the advice of charge of the duration of call after including calibration to counting equipment, so that the duration of call of described counting equipment after according to described calibration chargeed.
2. calling callback charging method as claimed in claim 1, it is characterized in that, also carry the conversation time started in the described initial charging request, describedly successfully notify or the time of reception of called connection failure notification is calibrated specifically the duration of call in the described initial charging request and comprised based on described bridge joint:
According to the described conversation time started with described bridge joint is successfully notified or the time of reception of called connection failure notification calculates connecting time, wherein,
Connecting time=bridge joint is successfully notified or time of reception-conversation time started of called connection failure notification;
Calculate the duration of call after the described calibration according to described connecting time and the described duration of call, wherein,
The duration of call=duration of call after the calibration-connecting time.
3. calling callback charging method as claimed in claim 1 or 2 is characterized in that, described bridge joint is successfully notified the message into bridge joint success PORTS_BRIDGED; Described called connection failure notification is for discharging Rel message.
4. calling callback charging method as claimed in claim 3 is characterized in that, described initial charging request is the request report ACR message of chargeing.
5. calling callback charging method as claimed in claim 4 is characterized in that, described advice of charge is a credit control request CCR message.
6. a business control device is characterized in that, comprising:
Transceiver module;
Logging modle is used for receiving by described transceiver module and successfully notifies or the called connection failure notification from the bridge joint of switching equipment, writes down that described bridge joint is successfully notified or the time of reception of called connection failure notification;
Calibration module, be used for by the initial charging request of described transceiver module reception from described switching equipment, successfully notify or the time of reception of called connection failure notification is calibrated the duration of call of carrying in the described initial charging request based on described bridge joint, send the advice of charge of the duration of call after including calibration by described transceiver module to counting equipment, so that the duration of call of described counting equipment after according to described calibration chargeed.
7. business control device as claimed in claim 6 is characterized in that, also carries the conversation time started in the described initial charging request, and described calibration module specifically comprises:
First computing module, be used for according to the described conversation time started and described bridge joint is successfully notified or the time of reception of called connection failure notification calculates connecting time, wherein, connecting time=bridge joint is successfully notified or time of reception-conversation time started of called connection failure notification;
Second computing module is used for calculating the duration of call after the described calibration according to described connecting time and the described duration of call, wherein, and the duration of call=duration of call after the calibration-connecting time.
8. as claim 6 or 7 described business control devices, it is characterized in that described bridge joint is successfully notified the message into bridge joint success PORTS_BRIDGED; Described called connection failure notification is for discharging Rel message.
9. business control device as claimed in claim 8 is characterized in that, described initial charging request is the request report ACR message of chargeing.
10. business control device as claimed in claim 9 is characterized in that, described advice of charge is a credit control request CCR message.
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2011/073471 WO2011113397A2 (en) | 2011-04-28 | 2011-04-28 | Call callback billing method and service control equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102217339A true CN102217339A (en) | 2011-10-12 |
Family
ID=44649661
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2011800004276A Pending CN102217339A (en) | 2011-04-28 | 2011-04-28 | Call callback billing method and service control equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102217339A (en) |
| WO (1) | WO2011113397A2 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014000607A1 (en) * | 2012-06-25 | 2014-01-03 | 中兴通讯股份有限公司 | Method for implementing intelligent network service, intelligent network system and virtual service switching point |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040063432A1 (en) * | 2002-10-01 | 2004-04-01 | Dumitru Borsan | Sender-address-based telecommunications operator callback system and method |
| CN1553720A (en) * | 2003-05-26 | 2004-12-08 | 华为技术有限公司 | Method for realizing delivery report business |
| CN101005532A (en) * | 2007-01-16 | 2007-07-25 | 华为技术有限公司 | Informing method, device and system for system time revision |
| CN101102368A (en) * | 2007-09-06 | 2008-01-09 | 北京移数通电讯有限公司 | Back call Web800 system and its call method |
| CN101179638A (en) * | 2007-12-18 | 2008-05-14 | 中兴通讯股份有限公司 | Method of determining call duration of callback service |
| CN101562529A (en) * | 2008-04-14 | 2009-10-21 | 华为技术有限公司 | Method and device for charging treatment |
| US20100255863A1 (en) * | 2007-12-27 | 2010-10-07 | Huawei Technologies Co., Ltd. | Method and system of charging for short message value-added service, data center for short message service |
-
2011
- 2011-04-28 CN CN2011800004276A patent/CN102217339A/en active Pending
- 2011-04-28 WO PCT/CN2011/073471 patent/WO2011113397A2/en active Application Filing
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040063432A1 (en) * | 2002-10-01 | 2004-04-01 | Dumitru Borsan | Sender-address-based telecommunications operator callback system and method |
| CN1553720A (en) * | 2003-05-26 | 2004-12-08 | 华为技术有限公司 | Method for realizing delivery report business |
| CN101005532A (en) * | 2007-01-16 | 2007-07-25 | 华为技术有限公司 | Informing method, device and system for system time revision |
| CN101102368A (en) * | 2007-09-06 | 2008-01-09 | 北京移数通电讯有限公司 | Back call Web800 system and its call method |
| CN101179638A (en) * | 2007-12-18 | 2008-05-14 | 中兴通讯股份有限公司 | Method of determining call duration of callback service |
| US20100255863A1 (en) * | 2007-12-27 | 2010-10-07 | Huawei Technologies Co., Ltd. | Method and system of charging for short message value-added service, data center for short message service |
| CN101562529A (en) * | 2008-04-14 | 2009-10-21 | 华为技术有限公司 | Method and device for charging treatment |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2014000607A1 (en) * | 2012-06-25 | 2014-01-03 | 中兴通讯股份有限公司 | Method for implementing intelligent network service, intelligent network system and virtual service switching point |
| CN103517233A (en) * | 2012-06-25 | 2014-01-15 | 中兴通讯股份有限公司 | Method for realizing intelligent network service, intelligent network system, and virtual service switch point |
| CN103517233B (en) * | 2012-06-25 | 2019-01-04 | 中兴通讯股份有限公司 | Realize that method, intelligent net system and the virtual service of intelligent network business exchange point |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2011113397A2 (en) | 2011-09-22 |
| WO2011113397A3 (en) | 2012-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2009138002A1 (en) | Method, system and apparatus for dropping back to voice call from video call | |
| JP2005531166A (en) | Billing method and system for calls forwarded to prepaid subscriber voice mail | |
| CN102215470A (en) | Pay per call processing method and system of communication equipment | |
| US8494499B2 (en) | System and method for achieving call back service | |
| WO2008089675A1 (en) | A method, system, switch device and service control point for implementing call forward | |
| EP2219359A1 (en) | Seamless switching between pre-paid and post-paid charging | |
| CN101742457A (en) | Underpayment prompting method, system and device for users | |
| CN101026877A (en) | Method, systemand device for realizing calling business | |
| CN101754144B (en) | Crosstalk reminding method, system and device | |
| CN102217339A (en) | Call callback billing method and service control equipment | |
| CN100563164C (en) | Method to charging communication flow | |
| CN103702302A (en) | Strong call interpolation method and device | |
| CN106982422A (en) | The method and device of 2G/3G location area informations is obtained under circuit domain dropping | |
| CN102137360B (en) | Network charge adjusting method and device | |
| WO2009052756A1 (en) | The method, device and system for simulating calls | |
| CN102137378B (en) | Call charging method, service control equipment and call control system | |
| CN102238508B (en) | Online charging method, device and system | |
| WO2009136407A2 (en) | Method and system for giving incomplete calls in a telecommunication network | |
| CN101027917A (en) | Intellight network mode personized ring back tone calling protection method and device | |
| CN102118876B (en) | Method or device for carrying out secondary interconnection on non-intelligent user | |
| CN103781042A (en) | Method for carrying out service charging on prepaid called user in roaming state | |
| CN102932768B (en) | Processing method in a kind of call-connection process and device | |
| WO2023238051A1 (en) | System and method for connecting a first subscriber to a second subscriber via a mobile network | |
| CN101500205A (en) | Multimedia service fee counting method and system | |
| CN102025962B (en) | Method and device for triggering charging of falling voice call of video call |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20111012 |