CN101317439B - Method, system and bureau switchboard for implementing telephone bill association - Google Patents

Method, system and bureau switchboard for implementing telephone bill association Download PDF

Info

Publication number
CN101317439B
CN101317439B CN2007800003563A CN200780000356A CN101317439B CN 101317439 B CN101317439 B CN 101317439B CN 2007800003563 A CN2007800003563 A CN 2007800003563A CN 200780000356 A CN200780000356 A CN 200780000356A CN 101317439 B CN101317439 B CN 101317439B
Authority
CN
China
Prior art keywords
call
session identifier
ticket
generated
scp
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
CN2007800003563A
Other languages
Chinese (zh)
Other versions
CN101317439A (en
Inventor
程从陆
徐静华
方芳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority claimed from CN200610137235A external-priority patent/CN1946120B/en
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN2007800003563A priority Critical patent/CN101317439B/en
Publication of CN101317439A publication Critical patent/CN101317439A/en
Application granted granted Critical
Publication of CN101317439B publication Critical patent/CN101317439B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Meter Arrangements (AREA)
  • Telephonic Communication Services (AREA)

Abstract

A method for correlating call tickets, which mainly includes steps of generating corresponding conversion logo during the calling procedure, letting the communication equipment needing to create corresponding call ticket identify the call ticket to be created with the created conversion logo, so as to implement correlation between the call tickets created by every communication equipment. Accordingly a system and a switch for correlating call tickets are provided. With the method and system, it is possible to implement the correlation between all the call tickets during a calling procedure, including correlation between the normal call tickets, and correlation between the normal call tickets and intelligent call tickets.; Telecom operators may collect call tickets created by every switches according to the call ID of current call, and charges for the call, so as to improve the charging precision and charging efficiency during the charging procedure.

Description

Method, system and local exchange for realizing call ticket association
Technical Field
The invention relates to a communication charging technology, in particular to a method, a system and an office switch for realizing call ticket association.
Background
At present, telecom operators charge users mainly according to call bills generated by the users in the call process. During the user's call, there are usually office switches at multiple office points to charge the call and generate a ticket. After the user finishes the conversation, the office exchanger sends the generated call bill to the network charging center, and the network charging center analyzes and processes the call bill uniformly to generate the charging information of the user. And the operator charges the user according to the charging information.
The existing telecommunication network is often operated by a plurality of operators together, and a sending office, a landing office and a tandem office which pass through in the communication process are not always the equipment of one operator. In the process of communication, each office point where the call passes charges the communication process according to the configuration of the office point, so that call bills of the user in the communication process are scattered and distributed in each originating office, each landing office and each tandem office; meanwhile, because the charging mode and the bill format set by the office switch of each office point are different, the bill forms generated by each office point are different, and the bill generated by each office point in a conversation process cannot be simply identified.
In addition, due to the continuous progress of modern communication technology, other additional services, such as intelligent services, are often accompanied during the call of the user. Therefore, the situation that the intelligent ticket generated by the device for processing the intelligent service and the ordinary ticket generated by the local office switch cannot correspond to each other can be caused.
In summary, in the process of a call, the ordinary call tickets generated by each office end and the call tickets generated by each device for processing additional services cannot be accurately corresponded, so that a telecommunication operator needs to take a turn to obtain various call tickets corresponding to each call. Meanwhile, because the searching process is complex and tedious, the charges and amounts counted by each telecom operator often come in and go out, so that all call tickets generated in one-time call process cannot be correctly and effectively searched, disputes are generated among operators or between the operators and users, and the telecom operators need to invest a large amount of manpower and material resources to check the call tickets generated by different local points one by one, so that the charging accuracy is low and the charging efficiency is low.
Disclosure of Invention
In view of this, the embodiments of the present invention provide a method for implementing call ticket association, and the method can improve charging accuracy and charging efficiency of call charges.
The technical scheme of the embodiment of the invention is realized as follows:
a method for realizing call ticket association comprises the following steps:
in the calling process, generating a session identifier corresponding to the call;
the communication equipment which needs to generate the call corresponding ticket uses the generated conversation mark to mark the ticket which needs to be generated;
when the call includes an intelligent service, the method further comprises:
when triggering the intelligent service, the session identification is sent to a service control point SCP through a service switching point SSP, and when the SSP and SCP need to generate the intelligent call ticket, the session identification is used to generate the intelligent call ticket.
The embodiment of the invention also provides a system for realizing the call ticket association, and the system can improve the charging accuracy and the charging efficiency of the call ticket.
In order to achieve the above purpose, the technical solution of the embodiment of the present invention is realized as follows:
a system for realizing call ticket association comprises a first local exchange and at least one second local exchange;
the first local exchange generates a corresponding session identifier for the current call in the calling process and sends the session identifier;
the second office switch receives the session identification; when the call ticket corresponding to the call needs to be generated, the generated session identifier is used for identifying the call ticket needing to be generated;
the system further comprises a service switching point SSP and a service control point SCP;
the first local exchange or the second local exchange further sends the session identifier to an SCP (service control point) through an SSP (secure session initiation protocol) when the current calling process contains the intelligent service;
and when the SSP and the SCP generate the intelligent call bill as required, the session identification received from the local switch is used for identifying the intelligent call bill generated by the SSP and the SCP.
In addition, the embodiment of the invention also provides an office switch for realizing the call ticket association, and the office switch can improve the charging accuracy and the charging efficiency of the telephone charge.
In order to achieve the above purpose, the technical solution of the embodiment of the present invention is realized as follows:
an office switch for realizing call ticket association comprises a transmission unit and a processing unit;
the session identifier generating unit generates a session identifier for the current call when needed and sends the generated session identifier;
the transfer unit receives the session identifier sent by the session identifier generation unit, and further sends the session identifier to an SCP (service control point) through an SSP (secure session initiation protocol) when the transfer unit determines that the current call process contains the intelligent service;
and when the processing unit needs to generate a call ticket corresponding to the current call, the processing unit acquires the session identifier from the transmission unit and uses the acquired session identifier to identify the call ticket required to be generated.
Meanwhile, the embodiment of the invention provides a system for realizing the call bill relationship, and the system can improve the charging accuracy and the charging efficiency of the call charges.
In order to achieve the above purpose, the technical solution of the embodiment of the present invention is realized as follows:
a system for realizing call ticket association comprises an office switch, a service switching point SSP and a service control point SCP;
when the office switch receives a call containing intelligent service in the calling process, the SSP triggers the SCP to process the intelligent service contained in the call; when a common call ticket needs to be generated, identifying the generated common call ticket by using the received session identification;
the SCP processes the intelligent service contained in the current call and generates a session identifier corresponding to the call; and send the session identification to the local exchange through the SSP;
and the SCP and the SSP connected with the SCP respectively use a session identifier to identify the intelligent call ticket generated by the SCP when the SCP and the SSP need to generate the intelligent call ticket.
According to the technical scheme provided by the embodiment of the invention, in the calling process, the session identification corresponding to the call is generated; and the communication equipment needing to generate the call corresponding ticket marks the call ticket needing to be generated by using the generated session mark. The technical scheme of the invention realizes the relevance between the call tickets generated by each communication device mainly by using the generated session identifier and the call ticket to be generated, wherein the relevance comprises the relevance between the common call tickets and the intelligent call tickets. Therefore, the charging accuracy and the charging efficiency of the telephone charge are improved.
Brief description of the drawings
FIG. 1 is a flow chart of a method of an embodiment of the present invention;
FIG. 2 is a block diagram of a system according to an embodiment of the invention;
FIG. 3 is a block diagram of a local exchange in accordance with an embodiment of the present invention;
FIG. 4 is a flow chart of a second method of the present invention;
fig. 5 is a block diagram of a second system according to an embodiment of the present invention.
Modes for carrying out the invention
In order to realize the purpose of the embodiment of the invention, a session identifier corresponding to a call is generated mainly in the calling process; and identifying the call ticket to be generated by the communication equipment needing to generate the call ticket by using the generated session identifier, thereby realizing the relevance between the call tickets generated by each communication equipment. The method comprises the correlation between common call tickets and the correlation between the common call tickets and the intelligent call tickets.
In the present invention, two aspects are mainly described, the first aspect is: all the devices needing to generate Call bills use the Call ID to identify the Call bills generated by the devices, so that the Call bills generated by all the devices are associated in one Call process. The devices referred to herein include office switches that provide general services, and devices that handle intelligent services. The second aspect is: when the intelligent service exists in the conversation process, the office switch triggers the intelligent service, and the purpose of associating the common call ticket generated by the office switch and the intelligent call ticket generated by the intelligent service processing equipment is achieved.
In intelligent services, a Service Switching Point (SSP) is the connection point of the call network to the intelligent network, which provides access to the set of intelligent network functions. When receiving a request for an intelligent service triggered by an exchange for an office, the SSP communicates with a Service Control Point (SCP) and allows service logic in the SCP to perform call processing in response to the SCP request. The SCP can start different service logics according to the call events reported by the SSP, and sends call control instructions to the corresponding SSP according to the service logics to indicate the SSP to perform the next action, thereby realizing various intelligent calls. The SCP and the SSP communicate with each other according to the standard interface protocol (INAP) of the intelligent network.
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in detail below with reference to the accompanying drawings and examples.
Example one
In this embodiment, it is assumed that the call initiated by the user does not include an intelligent service, but only includes a normal service. The flow of the method of the embodiment is shown in figure 1, which specifically comprises the following steps:
step 101: when the local exchange receives the Call initiated by the local user, a Call ID is generated for the current Call initiated by the current user, and the Call ID is filled in the Call message body sent to the next hop local exchange. The call message body may be of ISUP or SIP-T type, etc., depending on the actual situation. And, the Call message body to which the Call ID is added is sent to the next hop office switch.
Wherein, the Call ID can be defined in accordance with the Network Call reference field (Network Call reference) information element structure defined by the ITU-T q.763 protocol standard, and added to the Call message body.
When the originating office needs to generate a Call ticket, the generated Call ID is recorded.
Step 102: the tandem office processes the call of the user this time after receiving the call message body sent by the sending end office; and after the processing is finished, the Call ID is carried in the Call message body sent to the next hop tandem office, and the Call message body carrying the Call ID is sent to the next hop tandem office. And when the Call bill needs to be generated, recording the Call ID.
Step 103: the Call ID is carried in the Call message body sent to the next hop tandem office, and the Call message body carrying the Call ID is sent to the next hop tandem office until the Call reaches the landing office. And when each tandem office and each landing office need to generate Call bills, recording the Call ID.
Step 104: after the Call is finished, each office switch needing to generate the Call ticket carries the Call ID recorded by the office switch with the Call ticket generated by the office switch.
Therefore, from the beginning to the end of the Call, all the office points needing to generate Call tickets write a uniform Call ID into the Call tickets generated by the office points, so that the consistency of the Call tickets of all the office points in the Call is realized, and when each office point transmits the Call tickets generated by the office point to the network charging center, the network charging center can search the Call tickets generated by each office point according to the Call ID corresponding to the Call.
For some special charging strategies, the originating office does not need to generate a Call ticket, so in this embodiment, the Call ID is generated by the first tandem office that needs to generate a Call ticket for the Call, regardless of the originating office generating the Call ID.
When the office exchanger needing to generate the Call list receives the Call initiated by the office user or the incoming Call through the relay, judging whether the Call message body carries the Call ID, under the condition that the Call message body does not carry the Call ID, generating the Call ID by the current office exchanger, and carrying the generated Call ID in the Call message body sent to the next hop office exchanger.
The office switch that generates the Call ID may also be: the call message body received by the exchange does not contain an office switch carrying a session identifier. The purpose of this treatment is: under the condition that the Call ID is lost due to equipment failure, the Call ID can be generated continuously by adopting the way of generating the Call ID, and the Call ticket generated is identified by the Call ID, so that the association of the Call ticket is realized.
In the above description of the present embodiment, a case where a call initiated by a user only includes a normal service, but not an intelligent service, is described. The office exchanger processes the ticket generated by common service to be common ticket.
When the Call initiated by the user also comprises the intelligent service, when the office switch triggers the SCP to provide the intelligent service for the user, the Call ID corresponding to the Call is sent to the SCP through the SSP, the SCP and the SSP write the Call ID into the intelligent Call bill corresponding to the intelligent service under the condition that the intelligent Call bill needs to be generated according to the configuration of the SCP and the SSP, and the office switch also writes the Call ID into the common Call bill generated by the office switch. Therefore, the association of the call tickets of all local points and the association between the common call tickets and the intelligent call tickets can be realized in the calling process.
When the office exchanger needs to trigger the intelligent service according to the received Call message body, but does not need to generate a common Call bill, and the received Call message body does not carry the Call ID, the office exchanger generates the Call ID and sends the SCP through the SSP. When SSP and SCP need to generate intelligent ticket, using Call ID to identify the generated intelligent ticket, when the exchanger for subsequent office needs to generate common ticket, using the Call ID to identify the generated common ticket.
In addition, the invention also provides a system for realizing the call ticket association, which comprises a first local exchange and at least one second local exchange. The first local exchange generates a corresponding session identifier for the current call in the calling process and sends the session identifier. The second office switch receives the session identifier; and when the call corresponding ticket needs to be generated, the generated session identifier is used for identifying the ticket needing to be generated. And the first local exchange further uses the session identifier when generating the call corresponding ticket, and identifies the ticket needing to be generated.
In addition, in some particular cases, the system further includes at least one third office switch. The third local exchange transmits the session identification between the first local exchange and the second local exchange, between the first local exchange and the third local exchange, between two second local exchanges, between other two third local exchanges, or between the second local exchange and other third local exchanges.
In addition, a service switching point SSP and a service control point SCP are further included. And the first local exchange, the second local exchange or the third local exchange further sends the session identifier to the SCP through the SSP when the intelligent service is determined to be contained in the current call process. SSP and SCP identify the intelligent call ticket generated by itself by the conversation mark received from the exchanger.
Referring to fig. 2, fig. 2 provides only one networking structure of the system for the present embodiment. Including a first office switch 21, a third office switch 22, second office switches 23 and 24, an SSP25, and an SCP 26. In this figure, the first local exchange 21 generates a session identifier corresponding to the current call for the originating office of the current call, and transmits the session identifier to the third local exchange 22. When the third exchange determines that the current call contains the intelligent service, the received session identifier is sent to the SCP through the SSP, and the session identifier is also sent to the second exchange 23. The second local exchange 23 is the local exchange which needs to generate the ticket for the current call, so that the session identifier sent by the first local exchange 21 through the third local exchange 22 is recorded; when the call ticket corresponding to the current call is generated, the call ticket is identified by the session identification; the received session identification is sent to the second office switch 24. The second office switch 24 is the floor office of the current call and is also the office switch that needs to generate the call ticket, so the received session identifier is recorded, and the call ticket is identified by the session identifier when the call ticket corresponding to the current call is generated. In addition, SSP25 and SCP26 identify the intelligent ticket generated by themselves by the session identification received from the exchange for bureau according to whether the intelligent ticket is generated by itself. The system structure shown in fig. 2 is only one specific implementation form, and the technical solution of the embodiment of the present invention is not limited thereto.
The first local exchange and the second local exchange, the first local exchange and the third local exchange, the second local exchange and the third local exchange, and the first local exchange, the second local exchange and the third local exchange described in this embodiment may all be the same local exchange, that is, one local exchange may be used as both the first local exchange and the second local exchange.
Referring to fig. 3, fig. 3 is a block diagram of an office switch for implementing ticket association according to an embodiment of the present invention, and the office switch includes a transfer unit 31 and a processing unit 32. Wherein the transferring unit 31 receives the session identification generated for the current call. When the call ticket corresponding to the current call needs to be generated, the processing unit 32 obtains the session identifier from the transmission unit 31, and uses the obtained session identifier to identify the call ticket that needs to be generated.
In addition, the office switch further includes a session identification generation unit 33. The session identification generation unit 33 generates a session identification for the current call when necessary, and transmits the generated session identification. Correspondingly, the transferring unit 31 receives the session identifier sent by the session identifier generating unit 33; or receiving the session identification sent by the switch for the last hop office.
When the current office switch is not the terminating device of the current call, the transferring unit 31 may further send the received session identifier to the next-hop office switch of the call.
In this embodiment of the present invention, the transferring unit 31 may send the session identifier by carrying the session identifier in the call message body corresponding to the current call. Furthermore, when the received call message body does not find the call message body corresponding to the current call, the transferring unit 31 instructs the session identifier generating unit 33 to generate the session identifier corresponding to the current call. Accordingly, the session identifier generating unit 33 generates the session identifier corresponding to the current call according to the instruction of the transferring unit 31. In addition, the transfer unit 31 sends the session identifier to the SCP through the SSP when determining that the current call process includes the intelligent service according to the received call message body.
Example two
FIG. 4 is a flowchart illustrating the method of the present embodiment. In this embodiment, it is assumed that both SSP and SCP need to generate an intelligent ticket.
Step 401: when the exchange receives the call from the user or the incoming call through relay, the exchange triggers SCP to provide intelligent service to the user through SSP.
Step 402: SCP provides intelligent service for user, at the same time, distributes a unique identification Call ID for this intelligent service, and issues the Call ID to local exchange and SSP through SSP.
Here, the Call ID issuing manner of the SCP may be: the SCP adds a private field in the INAP message, records the currently allocated Call ID in the added private field, sends the INAP message carrying the Call ID to the SSP, and then the SSP sends the Call ID to the local exchange.
Step 403: when the intelligent service in the Call is finished, when an SCP needs to generate an intelligent Call bill, writing the generated Call ID into the intelligent Call bill generated by the SCP; when the SSP needs to generate the intelligent ticket, the Call ID issued by the SCP is written into the intelligent ticket generated by the SSP. When the Call is finished, the office exchanger writes the Call ID issued by the SCP into the self-generated common Call bill.
Fig. 5 is a structural diagram of a ticket association system implemented in this embodiment, where the system includes an office switch 50, an SSP51, and an SCP 52.
When receiving a call containing intelligent service in the call process, the office switch 50 triggers an SCP52 through an SSP51 to process the intelligent service contained in the call; when the ordinary call bill needs to be generated, the received session identifier is used for identifying the generated ordinary call bill. SCP52 processes the intelligent service contained in the current call to generate the conversation mark corresponding to the call; and sends the session identification to the office switch 50 through SSP 51. The SCP52 may further include a session identifier generating unit, which is used to generate a session identifier corresponding to the call when the current intelligent service is processed; and sends the session identification to the operation of the office switch 50 through SSP 51. And when the SCP52 and the SSP51 connected with the SCP52 need to generate the intelligent ticket, the intelligent ticket generated by the SCP is identified by using the session identifier.
In addition, SCP52 sends an INAP message carrying the session identifier to the office switch 50 via SSP 51.
Of course, SSP51 may also be located within the office switch 50 and the process is the same as SSP51 being located in the office switch 50.
When the Call of the user needs the office switch to trigger a plurality of intelligent services to the SCP, because each intelligent service can generate Call bills in the SCP and the SSP corresponding to the intelligent service, the SCP generates a Call ID and sends the Call ID to the office switch through the SSP only when processing the first intelligent service of the current Call, and the SSP and the SCP write the Call ID into a plurality of intelligent Call bills generated by the Call; and similarly, the office switch also writes the Call ID obtained from the SCP into the common Call bill of the office switch for the Call.
Whether the Call ticket is generated by the SSP and the SCP is determined by the telecommunication operator according to the requirement of the whole network, so that the operation of writing the Call ID into the Call ticket is not needed when the Call ticket is not required to be generated due to the configuration of the SSP or the SCP.
In the embodiment, the relevance of the common Call bill generated by the switch of each office point and the intelligent Call bill of the triggered intelligent service in the calling process is realized by writing the Call ID generated by the SCP into the common Call bill generated by the office switch, the intelligent Call bill generated by the SCP and/or the intelligent Call bill generated by the SSP. In the charging process, a calling process with intelligent service, a common Call ticket generated on a local point and an intelligent Call ticket of the intelligent service triggered by the local point can be easily found only according to the Call ID.
The technical scheme provided by the embodiment of the invention mainly generates the session identification corresponding to the call in the calling process; and identifying the call ticket to be generated by the communication equipment needing to generate the call ticket by using the generated session identifier, thereby realizing the relevance between the call tickets generated by each communication equipment. Therefore, the telecom operator can collect Call tickets generated by all local switches according to the Call ID of the Call to charge the Call, and the charging accuracy and the charging efficiency in the charging process are improved.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.

Claims (17)

1. A method for realizing call ticket association is characterized by comprising the following steps:
in the calling process, generating a session identifier corresponding to the call;
the communication equipment which needs to generate the call corresponding ticket uses the generated conversation mark to mark the ticket which needs to be generated;
when the call includes an intelligent service, the method further comprises:
when triggering the intelligent service, the session identification is sent to a service control point SCP through a service switching point SSP, and when the SSP and SCP need to generate the intelligent call ticket, the session identification is used to generate the intelligent call ticket.
2. The method of claim 1, wherein the device generating the session identifier corresponding to the call comprises:
an originating office switch that originates the call; or,
the received call message body does not carry the session identification, and the office switch which generates the call ticket corresponding to the call needs to be generated.
3. The method according to claim 1 or 2,
the method further comprises the following steps: carrying the generated session identifier in a call message body corresponding to the call;
the communication device that needs to generate the call ticket corresponding to the call uses the generated session identifier to identify the call ticket that needs to be generated, and the identification comprises: and during the call, the office switch which needs to generate the call ticket corresponding to the call identifies the call ticket which needs to be generated by receiving the call message body of the call and using the session identifier carried in the call message body.
4. The method of claim 1,
the method further comprises the following steps: when an office switch receives a call containing an intelligent service, the office switch triggers an SCP connected with the office switch through an SSP;
in the process of calling, the generating of the session identifier corresponding to the call includes: the SCP generates a session identifier corresponding to the call in the calling process;
after generating the session identifier corresponding to the call, the SCP further sends the session identifier to the office switch through the SSP;
the communication device that needs to generate the call ticket corresponding to the call uses the generated session identifier to identify the call ticket that needs to be generated, and the identification comprises: when the SCP and the SSP need to generate an intelligent ticket, the session identification is used for identifying the intelligent ticket generated by the SCP and the SSP; and when the office switch needs to generate the common call bill, the office switch marks the generated common call bill by using the received session mark.
5. The method of claim 4,
the method further comprises the following steps: adding a private field in an INAP message of a standard interface protocol, and carrying the session identifier in the added private field in the INAP message;
the SCP sends the session identifier to the office switch through the SSP: the SCP sends INAP information carrying the session identification through SSP, and the session identification is sent to the local exchange.
6. The method according to claim 4 or 5,
when the SCP is triggered to process a plurality of intelligent services, the generating a session identifier corresponding to the call includes: the SCP generates a session identifier aiming at the processed first intelligent service;
the SCP and the SSP use the session identification when needing to generate an intelligent ticket, and the identification of the intelligent ticket generated by the SCP and the SSP comprises the following steps: and identifying the intelligent call ticket generated by the intelligent call ticket per se aiming at each intelligent service by using the session identification generated aiming at the first intelligent service.
7. A system for realizing call ticket association is characterized in that the system comprises a first local exchange and at least one second local exchange;
the first local exchange generates a corresponding session identifier for the current call in the calling process and sends the session identifier;
the second office switch receives the session identification; when the call ticket corresponding to the call needs to be generated, the generated session identifier is used for identifying the call ticket needing to be generated;
the system further comprises a service switching point SSP and a service control point SCP;
the first local exchange or the second local exchange further sends the session identifier to an SCP (service control point) through an SSP (secure session initiation protocol) when the current calling process contains the intelligent service;
and when the SSP and the SCP generate the intelligent call bill as required, the session identification received from the local switch is used for identifying the intelligent call bill generated by the SSP and the SCP.
8. The system of claim 7, further comprising at least one third office switch;
and the third office switch transfers the session identification between the first office switch and the second office switch, or between the first office switch and the third office switch, or between two second office switches, or between other two third office switches, or between the second office switch and other third office switches.
9. The system of claim 7,
and the first local exchange further uses the session identifier to identify the ticket to be generated when generating the ticket corresponding to the call.
10. The system of claim 8,
and the third office switch further sends the session identifier to the SCP through the SSP when the intelligent service is determined to be contained in the current calling process.
11. An office switch for realizing the association of call tickets is characterized by comprising a transmission unit, a processing unit and a session identifier generating unit;
the session identifier generating unit generates a session identifier for the current call when needed and sends the generated session identifier;
the transfer unit receives the session identifier sent by the session identifier generation unit, and further sends the session identifier to an SCP (service control point) through an SSP (secure session initiation protocol) when the transfer unit determines that the current call process contains the intelligent service;
and when the processing unit needs to generate a call ticket corresponding to the current call, the processing unit acquires the session identifier from the transmission unit and uses the acquired session identifier to identify the call ticket required to be generated.
12. The office switch of claim 11,
and the transfer unit receives the session identifier sent by the switch for the last hop office.
13. The office switch according to claim 11 or 12,
the transfer unit further sends the received session identifier to the next hop office switch of the call.
14. The office switch of claim 13,
and the transmission unit transmits the session identifier by carrying the session identifier in a call message body corresponding to the current call.
15. The office switch of claim 14,
when the received call message body does not find the call message body corresponding to the current call, the transfer unit indicates the session identifier generation unit to generate the session identifier corresponding to the current call;
and the session identifier generating unit generates a session identifier corresponding to the current call according to the instruction of the transmission unit.
16. A system for realizing call ticket association is characterized in that the system comprises an office switch, a service switching point SSP and a service control point SCP;
when the office switch receives a call containing intelligent service, the SSP triggers the SCP; when a common call ticket needs to be generated, identifying the generated common call ticket by using the received session identification;
the SCP generates a session identifier corresponding to the call; and send the session identification to the local exchange through the SSP;
and when the SCP and the SSP need to generate the intelligent call ticket, the session identification is used for identifying the intelligent call ticket generated by the SCP and the SSP.
17. The system of claim 16,
and the SCP sends INAP information carrying the session identifier through the SSP and sends the session identifier to the local exchange.
CN2007800003563A 2006-10-20 2007-09-06 Method, system and bureau switchboard for implementing telephone bill association Expired - Fee Related CN101317439B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN2007800003563A CN101317439B (en) 2006-10-20 2007-09-06 Method, system and bureau switchboard for implementing telephone bill association

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN200610137235A CN1946120B (en) 2006-10-20 2006-10-20 Method and system for realizing telephone list association
CN200610137235.0 2006-10-20
CN2007800003563A CN101317439B (en) 2006-10-20 2007-09-06 Method, system and bureau switchboard for implementing telephone bill association
PCT/CN2007/070645 WO2008046330A1 (en) 2006-10-20 2007-09-06 Method, system and switch for correlating call tickets

Publications (2)

Publication Number Publication Date
CN101317439A CN101317439A (en) 2008-12-03
CN101317439B true CN101317439B (en) 2010-08-25

Family

ID=42631537

Family Applications (1)

Application Number Title Priority Date Filing Date
CN2007800003563A Expired - Fee Related CN101317439B (en) 2006-10-20 2007-09-06 Method, system and bureau switchboard for implementing telephone bill association

Country Status (1)

Country Link
CN (1) CN101317439B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116261110B (en) * 2022-12-06 2024-04-12 中国联合网络通信集团有限公司 SDR data determining method, device and storage medium

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1444824A (en) * 2000-05-24 2003-09-24 诺基亚有限公司 Common charging identifier for communication networks
CN1588860A (en) * 2004-08-11 2005-03-02 中国移动通信集团有限公司 Marking and carrying method for subnetwork information in internet

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1444824A (en) * 2000-05-24 2003-09-24 诺基亚有限公司 Common charging identifier for communication networks
CN1588860A (en) * 2004-08-11 2005-03-02 中国移动通信集团有限公司 Marking and carrying method for subnetwork information in internet

Also Published As

Publication number Publication date
CN101317439A (en) 2008-12-03

Similar Documents

Publication Publication Date Title
US6760426B2 (en) Method and system for handling operator calls in a communication network
CN102037702A (en) Composite services provision within a tlecommunications network
CN1946120B (en) Method and system for realizing telephone list association
CN101141359B (en) United service access system and access method
US8009809B2 (en) Method and system for call proceeding in an intelligent network system
CN1123197C (en) Method for controlling a credit customer call
AU2003232386A1 (en) System and method for determining tariffs for real-time calls involving ported directory numbers
CN101729930B (en) Method for realizing multi-intelligent service fusion via intelligent network gateway
CN101083781B (en) Service processing method for intelligent network system
CN107078916A (en) Part CDR processing is reduced in off-line accounting system
CN101317439B (en) Method, system and bureau switchboard for implementing telephone bill association
CN103188756A (en) Cross-domain service routing method, device, system and relevant equipment
CN100558174C (en) A kind of call connection method
CN101335788B (en) System and method for detecting and limiting line resource occupation by calling back
CN101076062B (en) Color bell system and method for calling service in color-bell system
CN1863261B (en) Intelligent external designing charge system and method
CN101188871A (en) Method for realizing voice online charging of CDMA network user
CN101448235B (en) Method and system for achieving charging in interactive voice response service
CN106488441B (en) One-card double-number platform, client, system and connection, call and communication method
CN100508463C (en) Method, system and apparatus for realizing intelligent service
CN100484256C (en) Voice transmission method and system
CN101594357A (en) The triggering method of nested service and device
CN105025454B (en) A kind of charging method, system and network side equipment
CN100589592C (en) Method and system of implementing intelligent network call monitoring
CN102510562B (en) Method for nesting services of code division multiple access (CDMA) user on service control point (SCP), SCP and wireless intelligent network

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
C17 Cessation of patent right
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20100825

Termination date: 20120906