WO2006047963A1 - Charging correlating and charging managing method for trunked voice service - Google Patents

Abstract

A charging correlating method for trunked voice service includes the following steps: Controlling PoC server assigns unique PoC charging identifier (PCID) to the integrated trunked session, and transfers the PCID to the SIP network which the terminals participated in the trunked session belong to through the trunked session procedure, and uses the PCID to implement the charging correlating of calling session and called session. A charging managing method for trunked voice service includes the following steps: Controlling PoC server assigns unique PCID to the integrated trunked session using said charging correlating method, and in the call charging table generated by the SIP network that the caller and the called terminal belong to, charges the call charging tables having the same PCID as one call charging table generated by one session.

Description

 Charging association and charging management method for cluster voice service

 The present invention relates to the field of charging management technologies for communication networks, and in particular, to a charging association and charging management method for a trunked voice service. Background of the invention

 With the development of communication technologies, Internet Protocol (IP) networks have the ability to provide voice communication services. Network operators have begun to try to provide users with point-to-multipoint, multi-point to multi-point voice services, such as: Cluster SMS service, cluster image service, and cluster voice service (PoC).

 The PoC service is based on a network subsystem supporting the Session Initiation Protocol (SIP), such as the IMS Internet Protocol Multimedia Subsystem or the MMD, and controls the session flow between the terminals by supporting the SIP/IP signaling flow, and The IP-based cluster service is provided to the terminal by the PoC server to which the terminal belongs.

 The following describes the prior art by taking the Poc service based on IMS as an example.

 The calling terminal establishes a session interaction with the called terminal via the IMS network to which the called terminal belongs through the IMS network to which the calling terminal belongs. The IMS network may include a Call State Control Function Entity (CSCF) and an Application Server (AS) that provides the above-mentioned session service.

In the PoC service, the ASs that provide services to the calling terminal and the called terminal are the PoC server (PoC Server) to which the calling terminal and the called terminal belong, respectively. „ According to different functions in the session, the PoC server can be divided into control. The specific difference between the PoC server and the participating PoC server is that the controlling PoC server establishes a session by calling the called terminal, and the participating members of the session can be added or deleted in the session; The PoC server is responsible for establishing a connection between the terminal and the controlling PoC server, and controlling the terminal according to the subscription data of the terminal. When the cluster communication is performed between the terminals, the IMS charging identifiers (ICIDs) for identifying the sessions are respectively allocated.

 Since the PoC is a B2BUA (Back to Back User Agent) type service, the complete cluster session between the calling terminal and the called terminal established by the PoC server is actually performed by the calling terminal and the Controlling PoC server. The calling session consists of the called session and the called session between the called terminal and the Controlling PoC server. Therefore, the system will assign different ICIDs to the calling session and the called session according to the two different sessions of the calling terminal and the called terminal, hereinafter referred to as the calling ICID and the called ICID.

 The above-mentioned calling ICID is allocated by the P-CSCF in the IMS registered by the calling terminal, and the called ICID is allocated by the Controlling PoC server. In some types of cluster sessions, a single PoC server can be used as the Controlling PoC server. The PoC server to which the calling terminal belongs can be used as the Controlling PoC server. The IMS where the Controlling PoC server is located may be the same as the IMS to which the caller belongs, or may be the same as the IMS to which the called party belongs, or may be different from the IMS to which the master/call belongs.

 See Figure la, Figure la is a schematic diagram of the signaling path in the process of establishing a cluster session; the basic process is: Calling terminal -> P-CSCF -> S-CSCF -> Calling PoC server -> S-CSCF ->> Controlling PoC server where IMS - "Controlling PoC server -" Controlling PoC server is located in IMS - "S-CSCF" (called S-CSCF) - "called PoC server -" S-CSCF (S-CSCF where the called party is located) -> P-CSCF (P-CSCF where the called party is located) - "The called terminal." The signalling path from the called party is completely opposite to this.

In the following, a separate PoC server is used as the Controlling PoC server, and the Controlling PoC server and the calling terminal are in the same IMS as an example to describe a specific ICID allocation method. Referring to FIG. 1b, FIG. 1b is a distribution flowchart of a prior art ICID, and the process includes the following steps:

 Step 101: Terminal A, which is the calling party in the trunking communication, sends a service request to the IMS to which it belongs.

 Step 102: After receiving the service request, the Proxy Call Session Control Function (P-CSCF) in the IMS allocates a calling ICID to the current session of the terminal A.

 Step 103: The P-CSCF adds the calling ICID to the service request, and then sends the service request to the serving call session control function entity (S-CSCF) registered by the terminal A in the IMS.

 Step 104: After receiving the service request, the S-CSCF in the IMS saves the calling ICID included in the service request.

 Step 105: The S-CSCF sends the service request including the calling ICID to the PoC server and the control PoC server to which the terminal A belongs.

 Because the PoC server cannot directly communicate with each other, in this step, the S-CSCF sends the service request to the PoC server to which the terminal A belongs, and receives the service request message returned by the S-CSCF. Request to send control PoC Server.

 Step 106: After receiving the service request, the PoC Server saves the calling ICID included in the service request, and allocates a called ICID to the session of the called terminal B.

 Of course, if there are multiple called terminals, the controlling PoC Server allocates different called ICIDs to the sessions of the plurality of called terminals according to the plurality of called terminal identifiers included in the service request.

 Steps 107-108: After allocating the called ICID, the control PoC Server adds the called ICID to the service request, and sends the service request to the IMS to which the terminal B belongs via the S-CSCF of the IMS to which the terminal A belongs.

Step 109: After receiving the service request including the primary/called ICID, the S-CSCF of the IMS to which the terminal B belongs saves the primary/called ICID. Step 110: The S-CSCF sends a service request including the primary/called ICID to the PoC Servero to which the terminal B belongs.

 Step 111: After receiving the service request, the PoC server to which the terminal B belongs saves the calling ICID and the called ICID included in the service request.

 Step 112: The PoC Server to which the terminal B belongs sends a service request including the master/called ICID to the P-CSCF in the IMS to which the terminal B belongs, via the S-CSCF registered by the terminal B in the IMS to which the terminal B belongs.

 Step 113: The P-CSCF in the IMS to which the terminal B belongs stores the master/called ICID included in the service request, and deletes all ICIDs included in the received service request.

 Step 114: The P-CSCF in the IMS to which the terminal B belongs sends the service request for deleting the ICID to the terminal B.

 Steps 115-121: After receiving the service request, the terminal B belongs to the IMS to which the terminal belongs, the POS to which the terminal B belongs, the IMS to which the terminal B belongs, the IMS to which the terminal A belongs, the PoC server to which the terminal A belongs, and the IMS to which the terminal A belongs. , return a confirmation response to terminal A.

 As shown in FIG. 1 , the IMS of the calling party sends a service request to the controlling PoC server. The IMS can also send a service request to the controlling PoC server. The processing flow is similar and will not be repeated here.

 Of course, the S-CSCF registered by the terminal A and the S-CSCF registered by the terminal B may be the same or different. The PoC server to which the terminal A belongs and the PoC server to which the terminal B belongs may be the same or different. The above 3 8 ? and / or? 0€861 61" When these functional entities are the same, the operation between the corresponding functional entities in Figure 1 is omitted.

Similarly, if the PoC Server to which the calling terminal belongs is used as the Controlling PoC server, the operations between the corresponding functional entities in FIG. 1 are omitted. If the PoC server to which the called terminal belongs is used as the Controlling PoC server, the corresponding processing in FIG. 1 is omitted in the processing flow of sending the service request from the IMS to the controlling PoC Server by the called IMS. The operation between functional entities.

 After the above process, terminal A can establish a session with the terminal B and all other called terminals to perform cluster communication. With the session operation of the calling terminal and each called terminal, the IMS will respectively add the calling terminal ICID and each called terminal ICID in the subsequently generated bill, and transmit the bill to the billing center.

 When the billing center dialog box performs the billing operation, it identifies the ICID contained in the bill, and applies a unified method for bills with the same ICID, while different bills may be applied to bills with different ICIDs. The charging method applied by the billing center to bills with different ICIDs may be the same or different. The specific billing methods are the same depending on the billing logic set in the billing center.

 Since each operation of each terminal generates a bill, it is possible that the bills received by the billing center have multiple ICIDs having the same ICID. In this case, the billing center applies a unified method of billing for these bills with the same ICID. It can be seen that the prior art application ICID associates all operations in a session and applies a uniform method charging for all operations in a session.

 As can be seen from the above, in the prior art, the calling terminal and the called terminal belonging to the same group respectively assign different ICIDs, and insert the ICID into the corresponding bill, and then the billing center applies the specific billing according to different ICIDs. Method billing. If a terminal temporarily withdraws from the session flow of the cluster communication for some reason in the process of cluster communication, and then rejoins the session, the IMS considers that the session rejoined by the terminal is a new session, but The terminal is assigned a new ICID. Thus, for the user, the session that was performed before the exit and the session that was performed after the rejoin became two unrelated, different sessions.

Therefore, in the subsequent charging operation, the ICID allocated before the terminal temporarily exits the cluster communication is added to the corresponding bill, and the terminal rejoins the cluster communication. The assigned ICID will also be added to the corresponding bill. Although the ICIDs in the above CDRs are different, these CDRs are actually generated by the same session process performed by the same terminal. Therefore, under normal circumstances, these CDRs should be uniformly charged for charging.

 However, when the billing center charges the bills, it only charges according to the bill-specific application method with different ICIDs. Therefore, after exiting the cluster session and rejoining the cluster session in the same session process performed by the same terminal The generated bills may be billed by different methods. This charging method is not reasonable, which reduces user satisfaction; and it is easy to generate billing errors such as repeated billing and leakage billing, which adversely affects the security and reliability of billing operations. Summary of the invention

 In view of this, a main object of the present invention is to provide a charging association method for a trunked voice service, so that in a complete cluster session flow of PoC communication, all terminals belonging to the same group have all operations in the group. The generated bills are all associated to bill the associated bills as bills generated by the same session.

 Another object of the present invention is to provide a charging management method for a trunked voice service, so that in a complete cluster session flow of PoC communication, all the terminals belonging to the same group that are associated in the group operate in the group. The generated bills are billed as bills generated by the same session.

 To achieve an aspect of the above object, the present invention provides a method for charging a cluster voice service, the method comprising the following steps:

 A. Controlling the cluster voice service server The Controlling PoC Server allocates a unique cluster voice service charging identifier PCID to the cluster service session when a cluster session starts.

B. The Controlling PoC Server transmits the above PCID to the calling terminal. The SIP network and the SIP network to which the called terminal belongs, by adding the PCID to the bills of the terminals participating in the current cluster service session, realize the billing of each calling session and called session included in the current cluster service session. Association.

 In the step B, the Controlling PoC Server can separately transmit the PICD to the SIP network to which the calling terminal belongs and the SIP network to which the called terminal belongs through a dedicated SIP message.

 In the step B, the Controlling PoC Server can add the PCID to the service request message and the acknowledgment response message, and respectively transmit the message to the SIP network to which the calling terminal belongs and the SIP network to which the called terminal belongs.

 The SIP network may be an IMS network or an MMD network.

 When the SIP network is an IMS network, the step A may include:

 Al, the calling terminal sends a service request to the Controlling PoC Server through the IMS to which the calling terminal belongs;

 A2, Controlling PoC Server assigns a unique PCID to the cluster session;

 The step B includes:

 Bl, the Controlling PoC Server will assign the PCID assigned to the cluster session to the IMS of the calling terminal that is sent to the current session and sent to the current session.

 B2, the IMS to which the calling terminal belongs, the service request containing the PCID, and sent to the PoC server to which the calling terminal belongs and the IMS to which the called terminal of the current cluster session belongs;

 B3. The IMS to which the called terminal belongs shall send the service request of the PCID to the PoC Server to which the called terminal belongs, and delete the PCID in the service request and send it to the called terminal.

B4, in the process that the called terminal returns an acknowledgment response to the calling terminal, the PoC Server to which the calling terminal belongs sends the PCID along with the acknowledgment response to the IMS to which the calling terminal belongs; B5. In the current session of the cluster session, the PCID is added to the CDRs of each terminal participating in the current cluster service session.

 The step A1 may include:

 Al l , the calling terminal sends a service request to the P-CSCF of the IMS to which it belongs;

 A12. The P-CSCF of the IMS to which the calling terminal belongs is assigned the calling ICID to the calling session, and sends the joining request to the S-CSCF signed by the calling user;

 A13. The S-CSCF sends a service request including the calling ICID to the PoC Server and the Controlling PoC Server to which the calling terminal belongs.

 In the step A2, the Controlling PoC Server also allocates the called ICID to the called session, and joins the service request;

 In the step B2, the S-CSCF of the IMS to which the calling terminal belongs sends the service request to the PoC server to which the calling terminal belongs and the IMS to which the called terminal of the current cluster session belongs;

 In the step B3, the S-CSCF of the IMS to which the called terminal belongs sends the service request including the PCID to the PoC server to which the called terminal belongs, and sends the service request to the P-CSCF of the IMS to which the called terminal belongs. The PCID and all ICIDs in the service request are deleted by the P-CSCF and sent to the called terminal.

 When the SIP network is an IMS network, the step A may include:

 Al. The calling terminal sends a service request to the IMS to which the called party belongs by using the IMS to which the calling terminal belongs.

 A2, the IMS to which the called terminal belongs sends a service request to the Controlling PoC Server; a3. The Controlling PoC Server assigns a unique PCID to the cluster session;

 The step B includes:

Bl, Controlling PoC Server will assign the PCID to this cluster session, join Sended to the IMS to which the called terminal belongs to the service request;

 B2. The IMS to which the called terminal belongs shall send the service request including the PCID to the PoC Server to which the called terminal belongs, and delete the PCID in the service request and send it to the called terminal. b3. Return the called terminal to the calling terminal. During the acknowledgment response, the PCID of the called terminal belongs to the IMS to which the calling party belongs, along with the acknowledgment response by the IMS to which the called terminal belongs;

 B4. The IMS to which the calling terminal belongs includes an acknowledgment response of the PCID, and is sent to the PoC Server to which the calling terminal belongs;

 B5. In the current session of the cluster session, the PCID is added to the CDRs of each terminal participating in the current cluster service session.

 The step al may include:

 Al l , the calling terminal sends a service request to the P-CSCF of the IMS to which it belongs; al2, the P-CSCF of the IMS to which the calling terminal belongs is assigned the calling ICID to the calling session, and sends the joining service request to the calling user to sign the contract. S-CSCF;

 Al3, the S-CSCF sends the service request including the calling ICID to the PoC server to which the calling terminal belongs and the IMS to which the called party belongs;

 In the step a2, the S-CSCF of the IMS to which the called party belongs sends a service request including the calling ICID to the Controlling PoC Server;

 In the step a3, the Controlling PoC Server further allocates the called ICID to the called session, and joins the service request;

 In the step b2, the S-CSCF of the IMS to which the called terminal belongs sends the service request to the PoC server to which the called terminal belongs, and sends the service request to the P-CSCF of the IMS to which the called terminal belongs, by the P-CSCF. The PCID and all ICIDs in the service request are deleted and sent to the called terminal;

In the step b4, the S-CSCF of the IMS to which the calling terminal belongs will contain the PCID. The acknowledgment response is sent to the PoC Server to which the calling terminal belongs.

 The Controlling PoC Server may be a separate PoC Server; or a PoC Server to which the calling terminal belongs; or a PoC Serve to which the called terminal belongs.

 If a new terminal joins the cluster session or the terminal that has quit the network rejoins the cluster session during the cluster session, the PCID of the cluster session and other CDRs can be used in the call list generated by the calling session or the called session. The calling session or the called session is associated.

 In order to achieve the above object, the present invention provides a charging management method for a trunked voice service, the method comprising the following steps:

 A. Controlling the cluster voice service server The Controlling PoC Server allocates a unique cluster voice service charging identifier PCID to the cluster service session when a cluster session starts.

 B. The Controlling PoC Server transmits the PCID to the SIP network to which the calling terminal belongs and the SIP network to which the called terminal belongs, and the PCID is added to the CDRs of each terminal participating in the current cluster service session to implement the cluster. The charging association between each calling session and the called session included in the service session;

 C At the end of the cluster service session, the CDRs with the same PCID are billed as the CDRs generated by the same session in the CDRs generated by the SIP network to which the master/called terminal belongs.

 The step C may include:

 Cl, the SIP network to which the calling terminal belongs, and the SIP network to which the called terminal belongs, respectively transmit the bill containing the PCID to the billing center;

 C2. The billing center identifies the PCIDs included in all the bills, and determines the bills with the same PCID as the bills of the same complete cluster session;

 C3. The charging center performs charging for the charging policy of the cluster session.

The step C3 may be: The charging center adopts a unified method to participate in the current cluster meeting. All terminals of the call are charged.

 In the step B, the Controlling PoC Server can separately transmit the PICD to the SIP network to which the calling terminal belongs and the SIP network to which the called terminal belongs through a dedicated SIP message.

 In the step B, the Controlling PoC Server may add the PCID to the service request message and the acknowledgment response message, and respectively transmit the message to the SIP network to which the calling terminal belongs and the SIP network to which the called terminal belongs.

 The SIP network may be an IMS network or an MMD network.

 When the SIP network is an IMS network, the step A may include:

 A1. The calling terminal sends a service request to the Controlling PoC Server through the IMS to which the calling terminal belongs.

 A2, Controlling PoC Server assigns a unique PCID to the cluster session;

 The step B includes:

 Bl, the Controlling PoC Server will assign the PCID assigned to the cluster session to the IMS of the calling terminal that is sent to the current session and sent to the current session.

 B2, the IMS to which the calling terminal belongs, the service request containing the PCID, and sent to the PoC server to which the calling terminal belongs and the IMS to which the called terminal of the current cluster session belongs;

 B3> The IMS to which the called terminal belongs shall send the service request of the PCID to the PoC Server to which the called terminal belongs, and delete the PCID in the service request and send it to the called terminal.

 B4, in the process of returning the acknowledgment response from the called terminal to the calling terminal, the PCC belongs to the IMS to which the calling terminal belongs, by the PoC Server to which the calling terminal belongs;

B5. In the current session of the cluster session, the PCID is added to the CDRs of each terminal participating in the current cluster service session. When the SIP network is an IMS network, the step A may include:

 Al. The calling terminal sends a service request to the IMS to which the called party belongs by using the IMS to which the calling terminal belongs.

 A2, the IMS to which the called terminal belongs sends a service request to the Controlling PoC Server; a3. The Controlling PoC Server assigns a unique PCID to the cluster session;

 The step B includes:

 Bl, Controlling PoC Server will assign the PCID assigned to the cluster session to the service request and send it to the IMS to which the called terminal belongs;

 B2. The IMS to which the called terminal belongs shall send the service request including the PCID to the PoC Server to which the called terminal belongs, and delete the PCID in the service request and send it to the called terminal. b3. Return the called terminal to the calling terminal. During the acknowledgment response, the PCID of the called terminal belongs to the IMS to which the calling party belongs, along with the acknowledgment response by the IMS to which the called terminal belongs;

 B4. The IMS to which the calling terminal belongs includes an acknowledgment response of the PCID, and is sent to the PoC Server to which the calling terminal belongs;

 B5. In the current session of the cluster session, the PCID is added to the CDRs of each terminal participating in the current cluster service session.

 The Controlling PoC Server may be a separate PoC Server; or a PoC Server to which the calling terminal belongs; or a PoC Serve to which the called terminal belongs.

 If a new terminal joins the cluster session or the terminal that has quit the network rejoins the cluster session during the cluster session, the PCID of the cluster session and other CDRs can be used in the call list generated by the calling session or the called session. The calling session or the called session is associated.

The process of rejoining the cluster session by the terminal that is halfway out during the cluster session may include: Dl. The terminal that quits halfway sends a service request to the controlling PoC Serve through the IMS to which the terminal belongs;

 D2, controlling the PoC Serve to determine whether the terminal is a group member of the current cluster session, and if yes, adding the PCID of the cluster session to the acknowledgment response, returning to the IMS to which the terminal belongs, and performing step D3; otherwise, pressing the new cluster Session processing

 D3. The IMS to which the terminal belongs sends the acknowledgment response including the PCID to the PoC Serve to which the terminal belongs, and deletes the PCID in the acknowledgment response and sends it to the terminal. Compared with the prior art, in the charging association method provided by the present invention, the Controlling PoC Server allocates a unique PoC charging identifier (PCID) for a complete cluster session, and transmits the PCID to the participating cluster through the cluster session process. a SIP network to which each terminal of the session belongs, and is saved by the SIP network, and the charging association between the calling session and the called session is implemented by the PCID; so that in a complete session flow of the PoC communication, each belonging to the same group The CDRs generated by all the operations of the terminal in the group are all associated with the PCID, so that the associated CDRs are charged as CDRs generated by the same session.

 In the charging management method provided by the present invention, the Controlling PoC Server uses the above-mentioned charging association method to allocate a unique PCID for a complete cluster session; in the bill generated by the SIP network to which the calling/called terminal belongs, it will have the same The bill of the PCID is billed as a bill generated by the same session. BRIEF DESCRIPTION OF THE DRAWINGS

 Figure la is a schematic diagram of a signaling path in the process of establishing a cluster session;

 Figure lb is a distribution flow chart of the prior art ICID;

 2 is a flowchart of a first preferred embodiment of a charging association method according to the present invention;

 3 is a flowchart of a second preferred embodiment of a charging association method according to the present invention;

4 is a flow chart of an embodiment of a billing management method to which the present invention is applied. Mode for carrying out the invention

 The present invention will be described in detail below with reference to the specific embodiments of the invention.

 In the charging association method provided by the present invention, the Controlling PoC Server allocates a unique PoC charging identifier (PCID) to a complete cluster session, and transmits the PCID to the SIP network to which each terminal participating in the cluster session belongs through the cluster session process. And being saved by the SIP network, and the charging association between the calling session and the called session is implemented by the PCID; so that all operations of the terminals belonging to the same group in the group in a complete session flow of the PoC communication The generated CDRs are all associated with the PCID to charge the associated CDRs as CDRs generated by the same session.

 In the charging management method provided by the present invention, the Controlling PoC Server uses the above-mentioned charging association method to allocate a unique PCID for a complete cluster session; in the bill generated by the SIP network to which the calling/called terminal belongs, it will have the same The bill of the PCID is billed as a bill generated by the same session.

 The following describes the charging association method and the charging management method provided by the present invention in detail.

 There are many types of cluster services, such as: cluster SMS service, cluster image service, PoC, and so on. The method of the present invention is described by taking the IMS-based PoC service as an example. The charging management method based on other services such as the IMS or the MMD, such as the cluster short message service and the cluster image service, and the charging management method of the PoC service. the same.

The key point of the present invention: The PCID may be allocated by a separate control PoC Server, or by a PoC Server to which the calling terminal controlling the PoC Server belongs, or by a PoC Server to which the called terminal controlling the PoC Server belongs. For example, in a temporary group session such as Ad Hooc, the PoC Server to which the calling terminal belongs is used to control the PoC Server, which is responsible for establishing and managing the cluster session, so the PoC Server is used by the PoC Server. Assigning a PCID; in a pre-defined fixed group or chat mode group session, the PoC Server to which the terminal acting as the administrator in the calling terminal or called terminal belongs to control the PoC Server, which is responsible for establishing and managing The cluster session, so the PCID is assigned by the PoC Server.

 In the following, the charging association method provided by the present invention is described in detail by taking the IMS network as the example, the PCID is allocated by the separate control PoC Server, and the Controlling PoC server is in the same IMS as the calling terminal.

 Referring to FIG. 2, FIG. 2 is a flowchart of a first preferred embodiment of a charging association method according to the present invention. The process includes the following steps:

 Step 201: The terminal A, which is the calling party in the cluster communication, sends a service request to the IMS to which it belongs, and hopes to establish a cluster session with the terminal B for cluster communication.

 The service request in this step is usually an invite message, which includes the identifier of the terminal A as the calling party and the identifier of the terminal B as the called party, and the identifier of the cluster where the terminal A is located. The cluster identifiers of the terminals belonging to the same group are the same, and are used to identify that the current master/called terminal belongs to the same group.

 Step 202: As the first functional entity in the IMS that interacts with the terminal A, after receiving the service request, the P-CSCF allocates a calling ICID to the current calling party of the terminal A, and the calling ICID Join the business request.

 Step 203: The P-CSCF sends the service request that has joined the calling ICID to the S-CSCF registered by the terminal A.

 Step 204: After receiving the service request, the S-CSCF saves the calling ICID included in the service request.

 Step 205: The S-CSCF sends the service request including the calling ICID to the PoC server and the control PoC server to which the terminal A belongs.

The PoC Server is a type of an AS, and is used to provide an IMS-based cluster language to a terminal. The voice service, when the terminal is registered in the S-CSCF of the IMS, the IMS selects a PoC server according to the subscription data of the user, and uses the PoC server as the PoC server to which the terminal belongs to provide the IMS-based cluster voice service to the terminal.

 As in the prior art, in this step, the PoC server cannot directly communicate with each other. Therefore, in this step, the S-CSCF sends the service request to the PoC server to which the terminal A belongs, and receives the service request returned by the S-CSCF. , then the S-CSCF sends the service request to control PoC Serve

 Step 206: After receiving the service request, the PoC Server learns that the terminal A wants to establish a session, and then saves the calling ICID included in the service request, and allocates an ICID to the called party. Of course, if there are multiple called terminals, the PoC Server allocates multiple different called ICIDs according to multiple called terminal identifiers included in the service request; meanwhile, a unique PCID is also assigned to the current cluster session.

 Step 207-208: After the PoC Server allocates the PCID and the called ICID, the PCID and the called ICID are added to the IMS to which the service request is sent by the S-CSCF of the IMS to which the terminal A belongs.

 Step 209: The S-CSCF of the IMS to which the terminal B belongs, after receiving the service request, saves the master/called ICID and the PCID.

 Step 210: The S-CSCF sends the service request including the primary/called ICID and the PCID to the PoC server to which the terminal B belongs.

 The PoC server to which the terminal A belongs cannot communicate with the PoC server to which the terminal B belongs. Therefore, the PoC server to which the terminal A belongs adds the service request of the PCID and the called ICID to the terminal A registered in the IMS to which the terminal A belongs. -CSCF.

 Step 211: After receiving the service request, the PoC server to which the terminal B belongs saves the master/called ICID and the PCID included in the service request.

Step 212: The PoC server to which the terminal B belongs is via the terminal B in the IMS to which the terminal B belongs. The registered S-CSCF sends a service request including the master/called ICID and the PCID to the P-CSCF in the IMS to which the terminal B belongs.

 Step 213: The P-CSCF in the IMS to which the terminal B belongs stores the primary/called ICID and PCID included in the service request, and deletes all ICIDs and PCIDs included in the received service request.

 Step 214: The P-CSCF in the IMS to which the terminal B belongs sends the service request for deleting the ICID and the PCID to the terminal B.

 Step 215: After receiving the service request, the terminal B sends an acknowledgment response to the S-CSCF registered by the terminal B through the P-CSCF in the IMS to which the terminal B belongs, and the acknowledgment response includes the identifier of the terminal A and the identifier of the terminal B.

 Step 216: After receiving the acknowledgment response, the S-CSCF sends an acknowledgment response to the PoC Server to which the terminal B belongs.

 Step 217: After receiving the acknowledgment response, the PoC Server to which the terminal B belongs sends an acknowledgment response to the S-CSCF registered by the terminal B.

 Step 218: After receiving the acknowledgment response sent by the PoC server to which the terminal B belongs, the S-CSCF registered by the terminal B, according to the identifier of the terminal A included in the acknowledgment response, is registered with the terminal A in the IMS to which the terminal A belongs. The CSCF sends a confirmation response.

 Step 219: After receiving the acknowledgment response, the S-CSCF registered by the terminal A sends an acknowledgment response to the PoC Server to which the terminal A belongs.

 Step 220: After receiving the acknowledgment response, the PoC Server to which the terminal A belongs adds a PCID in the acknowledgment response, and sends an acknowledgment response to the PCID to the S-CSCF registered by the terminal A in the IMS to which it belongs.

After receiving the acknowledgment response from the PoC Server to which the terminal A belongs, the S-CSCF registered by the terminal A transmits an acknowledgment response to the P-CSCF which is a connection point between the IMS to which the terminal A belongs and the terminal A. Steps 221-222: After receiving the acknowledgment response, the P-CSCF saves the PCID included in the acknowledgment response, deletes the PCID included in the received acknowledgment response, and sends an acknowledgment response with the deleted PCID to the terminal A.

这些功能实体 相同时， 则省去图 2中对应的相同功能实体之间的操作。 Of course, the S-CSCF registered by the terminal A and the S-CSCF registered by the terminal B may be the same or different. The PoC server to which the terminal A belongs and the PoC server to which the terminal B belongs may be the same or different. The above 3 3 ? and / or? 0€

When these functional entities are the same, the operations between the corresponding functional entities in FIG. 2 are omitted.

 In addition, terminal A shown in FIG. 2 may also communicate with other called terminals belonging to the same group in one complete cluster session, and terminal B is only one of a plurality of called terminals. If the terminal A transmits to the plurality of called terminals in the service request, the different called ICIDs are assigned to the sessions of the called terminals in the above step 206. If, during a cluster session, a new terminal joins the cluster session or the terminal that has quit halfway joins the cluster session, only the corresponding calling ICID or called ICID is allocated, and the new PCID is no longer assigned to the cluster session. The CDRs generated by the calling session or the called session are still associated with other calling or called sessions using the PCID of the cluster session. That is, for a complete cluster session, a PCID is assigned when the session is established, and this PCID is released when the entire cluster session is deleted.

 After receiving the acknowledgment response sent from the P-CSCF, the terminal A can establish a session with the terminal B and all other called terminals to perform cluster communication. At the same time, the functional entities in the IMS have already learned the PCID of the current cluster session, the calling/called ICID, and thus the IMS has the ability to generate bills. In subsequent billing operations, this PCID is added to the bills of each terminal in the complete cluster session. In this way, the CDRs generated by all the operations of the terminals participating in the same cluster session include the same PCID, that is, the PCID associates all the CDRs generated by a complete cluster session.

If the terminal does not perform the normal session establishment operation described in this embodiment, The pre-establishment operation, when the terminal completes the session pre-establishment operation and sends a service request to the IMS to which it belongs to establish a session with other terminals, the applied charging association method is associated with the charging shown in FIG. The principle of the method is the same. The difference is that when the session pre-establishment operation is completed, the terminal establishes a session with other terminals by sending a refer message to the IMS to which it belongs; and in the normal session flow shown in FIG. 2, the terminal passes the IMS to which it belongs. Send an invite message to establish a session with other terminals.

 Referring to FIG. 3, FIG. 3 is a flowchart of a second preferred embodiment of the charging association method according to the present invention. In this embodiment, the Controlling PoC server and the called terminal are in the same IMS, and the process includes the following steps:

 Step 301: The terminal A, which is the calling party in the cluster communication, sends a service request to the IMS to which it belongs, and hopes to establish a cluster session with the terminal B for cluster communication.

 The service request in this step is usually an invite message, which includes the identifier of the terminal A as the calling party and the identifier of the terminal B as the called party, and the identifier of the cluster where the terminal A is located. The cluster identifiers of the terminals belonging to the same group are the same, and are used to identify that the current master/called terminal belongs to the same group.

 Step 302: As the first functional entity in the IMS that interacts with the terminal A, after receiving the service request, the P-CSCF allocates a calling ICID to the current caller of the terminal A, and the calling ICID Join the business request.

 Step 303: The P-CSCF sends the service request that has joined the calling ICID to the S-CSCF registered by the terminal A.

 Step 304: After receiving the service request, the S-CSCF saves the calling ICID included in the service request.

 Step 305: The S-CSCF sends a service request including the calling ICID to the PoC server to which the terminal A belongs.

Step 306: The PoC Server to which the terminal A belongs stores the calling ICID. Steps 307-309: The PoC Server to which the terminal A belongs controls the PoC Server to send a service request including the calling ICID through the S-CSCF of the IMS to which the terminal A belongs and the S-CSCF of the IMS to which the terminal B belongs.

 Step 310: After receiving the service request, the PoC Server learns that the terminal A wants to establish a session, and then saves the calling ICID included in the service request, and allocates an ICID to the called party. Of course, if there are multiple called terminals, the PoC Server allocates multiple different called ICIDs according to multiple called terminal identifiers included in the service request; meanwhile, a unique PCID is also assigned to the current cluster session.

 Step 311: After the PoC Server allocates the PCID and the called ICID, the PCID and the called ICID are added to the service request, and are sent to the PoC Server to which the terminal B belongs by using the S-CSCF of the IMS to which the terminal B belongs.

 Step 312: The S-CSCF of the IMS to which the terminal B belongs stores the master/called ICID and the PCID in the service request.

 Step 313: The S-CSCF sends a service request including the master/called ICID and the PCID to the P-CSCF.

 Step 314: The P-CSCF in the IMS to which the terminal B belongs stores the primary/called ICID and PCID included in the service request, and deletes all ICIDs and PCIDs included in the received service request.

 Step 315: The P-CSCF in the IMS to which the terminal B belongs sends the service request for deleting the ICID and the PCID to the terminal B.

 Step 316: After receiving the service request, the terminal B sends an acknowledgment response to the S-CSCF registered by the terminal B through the P-CSCF in the IMS to which the terminal B belongs, and the acknowledgment response includes the identifier of the terminal A and the identifier of the terminal B.

Step 317: After receiving the acknowledgment response, the S-CSCF sends an acknowledgment response to the PoC Server to which the terminal B belongs. Step 318: After receiving the acknowledgment response, the PoC server to which the terminal B belongs sends an acknowledgment response including the PCID to the S-CSCF registered by the terminal B.

 Step 319: After receiving the acknowledgment response sent by the PoC server to which the terminal B belongs, the S-CSCF registered by the terminal B, according to the identifier of the terminal A included in the acknowledgment response, is registered with the terminal A in the IMS to which the terminal A belongs. The CSCF sends an acknowledgment response containing the PCID.

 Step 320: After receiving the acknowledgment response including the PCID, the S-CSCF registered by the terminal A sends an acknowledgment response including the PCID to the PoC Server to which the terminal A belongs.

 Step 321: After receiving the confirmation response, the PoC Server to which the terminal A belongs saves the PCID contained therein.

 Step 322: The PoC Server to which the terminal A belongs sends an acknowledgment response including the PCID to the S-CSCF registered by the terminal A in the IMS to which it belongs.

 After receiving the acknowledgment response from the PoC Server to which the terminal A belongs, the S-CSCF registered by the terminal A sends an acknowledgment response to the P-CSCF which is the connection point between the IMS to which the terminal A belongs and the terminal A.

 Step 323-324: After receiving the acknowledgment response, the P-CSCF saves the PCID included in the acknowledgment response, deletes the PCID included in the received acknowledgment response, and sends an acknowledgment response with the deleted PCID to the terminal A.

 Of course, the S-CSCF registered by the terminal A and the S-CSCF registered by the terminal B may be the same or different. The PoC server to which the terminal A belongs and the PoC server to which the terminal B belongs may be the same or different. When the above-mentioned functional entities of the S-CSCF and/or the PoC Server are the same, the operations between the corresponding functional entities in FIG. 3 are omitted.

In addition, the terminal A shown in FIG. 3 may also communicate with other called terminals belonging to the same group in one complete cluster session, and the terminal B is only one of a plurality of called terminals. If the terminal A sends to the plurality of called terminals in the service request, the different called ICIDs are assigned to the sessions of the called terminals in the above step 206. If you have been in a cluster session In the process, if a new terminal joins the cluster session, it only needs to allocate the corresponding calling ICID or called ICID, and no new PCID is assigned to the cluster session. That is, for a complete cluster session, a PCID is assigned when the session is established, and this PCID is released when the entire cluster session is deleted.

 After receiving the acknowledgment response sent from the P-CSCF, the terminal A can establish a session with the terminal B and all other called terminals to perform cluster communication. At the same time, the functional entities in the IMS have already learned the PCID of the current cluster session, the calling/called ICID, and thus the IMS has the ability to generate bills. In subsequent billing operations, this PCID is added to the bills of each terminal in the complete cluster session. In this way, the CDRs generated by all the operations of the terminals participating in the same cluster session include the same PCID, that is, the PCID associates all the CDRs generated by a complete cluster session.

 If the terminal does not perform the normal session establishment operation described in this embodiment, but performs the session pre-establishment operation, when the terminal completes the session pre-establishment operation, and sends a service request to the IMS to which it belongs to establish a relationship with other terminals. In the session, the charging association method applied is the same as the charging association method shown in FIG. 2. The difference is that when the session pre-establishment operation is completed, the terminal establishes a session with other terminals by sending a refer message to the IMS to which it belongs; and in the normal session flow shown in FIG. 2, the terminal passes the IMS to which it belongs. Send an invite message to establish a session with other terminals.

 In the actual application, if the PoC Server to which the calling terminal belongs is used as the Controlling PoC server, the operations between the corresponding functional entities in FIG. 2 are omitted. If the PoC Server to which the called terminal belongs is used as the Controlling PoC server, the operations between the corresponding functional entities in Figure 3 are omitted.

After the PCID allocation operation shown in the above two embodiments is completed, the non-session operation related to the current group performed by the terminal in the PoC session, such as a user-initiated message, a session attribute setting, and the like, and a functional entity in the PoC system User-initiated status notifications, etc. The IMS to which the terminal belongs will also generate the corresponding bill. In this case, the corresponding bill can also be associated with the PCID. That is, the IMS and the Controlling PoC Server add the PCID to which the current group is assigned in the corresponding terminal service request.

 After the IMS generates the CDR according to the non-session operation, the PCID is added to the CDR, so that the non-session operations of the terminals belonging to the same cluster session can be associated with the group session operation, thereby making the same All bills of each terminal in a cluster session can be charged by a unified method.

 As can be seen from the above, the present invention uses the PCID to associate all sessions in a cluster session in order to achieve unified charging for all sessions in a cluster session. This association method and the prior art application ICID will be in a session. The method of associating all operations has the same principle.

Of course, in addition to the above-mentioned service request and acknowledgment response, the PCID may be transmitted to the IMS to which the master/called party belongs, the PoC server to which the master/called party belongs, or may be used by other applied SIP messages or for transmitting the PPIC. SIP message, the PCID is transmitted to the IMS to which the master/called party belongs, the PoC Server to which the master/called party belongs, or the PCID is respectively transmitted to the IMS to which the master/called party belongs by a relatively independent message, The PoC Server ₀ to which the called party belongs

 In the charging management method provided by the present invention, the Controlling PoC Server uses the above-mentioned charging association method to allocate a unique PCID for a complete cluster session; in the bill generated by the SIP network to which the calling/called terminal belongs, it will have the same The bill of the PCID is billed as a bill generated by the same session.

Specifically, the SIP network to which the calling terminal belongs and the SIP network to which the called terminal belongs transmit the CDR containing the PCID to the charging center respectively; the charging center identifies the PCID included in all the CDRs, and has the same PCID. The bill is determined to be the same full cluster session; the billing policy for the cluster session is used for billing, for example, a unified party can be used. The method charges all terminals participating in this cluster session.

 For bills with different PCIDs, it is possible to apply different methods for billing. The specific billing method is the same depending on the billing logic set in the billing center. The above method of identifying the PCID is the same as the method of identifying the ICID applied in the prior art.

 Referring to FIG. 4, FIG. 4 is a flowchart of an embodiment of a billing management method to which the present invention is applied.

 This embodiment is based on the embodiment shown in FIG. 2. It is assumed that terminal A temporarily quits in the middle of the cluster session, and other cluster users are still performing the cluster session. Before the cluster session is not completed, terminal A needs to rejoin the cluster session. The processing flow is as shown in FIG. 4, and includes the following steps: Step 401: Terminal A sends a service request to the IMS to which it belongs, and hopes to join the established cluster session for cluster communication.

 Step 402: As the first functional entity in the IMS that interacts with the terminal A, after receiving the service request, the P-CSCF allocates a calling ICID to the current calling party of the terminal A, and the calling ICID Join the business request.

 Step 403: The P-CSCF sends the service request that has joined the calling ICID to the S-CSCF registered by the terminal A.

 Step 404: After receiving the service request, the S-CSCF saves the calling ICID included in the service request.

 Step 405: The S-CSCF sends a service request including the calling ICID to the PoC Serve to which the terminal A belongs.

 Step 406-407: The PoC Server to which the terminal A belongs saves the calling ICID, and sends a service request including the calling ICID to the S-CSCF.

 Step 408: The S-CSCF sends a service request including the calling ICID to the controlling PoC Server.

Step 409: Control the PoC Server to perform step 410 or perform steps 206-22 in FIG. 2 according to whether the terminal A is a member of the group of the current cluster session. Controlling the PoC Server to determine whether the terminal A is a member of the current cluster session group. If yes, the PCID of the cluster session is added to the confirmation response, and step 410 is performed; otherwise, the new cluster session processing is performed, that is, the execution is performed in FIG. 2 Steps 206-222.

 The method for determining whether the terminal A is a member of the group of the current cluster session is: determining whether the cluster identifier corresponding to the cluster session is the same as the cluster identifier included in the service request in the cluster session currently managed by the Controlling PoC Server. If there is the same, terminal A is a member of the group of the current cluster session.

 Step 410: Control the PoC Server to send an acknowledgment response including the calling ICID and the PCID to the S-CSCF.

 Step 411-412: The S-CSCF saves the PCID in the acknowledgment response, and forwards the acknowledgment response to the PoC Server to which the terminal A belongs.

 Step 413-414: The PoC Server to which the terminal A belongs stores the PCID in the acknowledgment response, and forwards the acknowledgment response to the P-CSCF through the S-CSCF.

 Step 415-416: After receiving the acknowledgment response, the P-CSCF saves the PCID included in the acknowledgment response, deletes the PCID included in the received acknowledgment response, and sends an acknowledgment response with the deleted PCID to the terminal A.

 When terminal A receives the acknowledgment response from the P-CSCF in the IMS to which it belongs, it can rejoin the session of the group to which it belongs. At the same time, the IMS to which the terminal A belongs and the IMS to which the Controlling PoC Server belongs are all aware of the PCID of the terminal A, and thus the IMS has the capability of generating a bill. In subsequent billing operations, the PCIDs assigned in the cluster session are added to the bill. In this way, the CDRs generated by all the operations of the above terminals all contain the same PCID, that is, the PCID associates all the CDRs generated by the cluster communication.

After the bill is transmitted to the billing center, the billing center will identify the PCID contained in all the bills, and can apply the unified method billing for bills with the same PCID, but it is possible to have bills with different PCIDs. Apply different methods for billing, whether the specific billing method is The same depends on the billing logic set in the billing center. The above method of identifying the PCID is the same as the method of identification applied in the prior art.

 The signaling paths in FIG. 2, FIG. 3, and FIG. 4 are the same as those shown in FIG. 1a, and the terminals belonging to the same group can be associated with the PCIDs after all the operations generated by the operations in the group are associated with the PCID. These bills are billed as bills generated by the same group. When the billing center performs the subsequent billing operation, the billing method can be applied to the bills with the same PCID. However, the operator can also apply different methods to bills of different terminals with the same PCID, such as: For two terminals with the same PCID in the same group, one of the terminals is designated as a gold card user by the operator, and enjoys a 20% credit discount, while the other terminal does not enjoy any discount. Then, the two terminals with the same PCID mentioned above will not be charged by applying a unified method.

 The method for transmitting the primary/called terminal ICID and the PCID in the functional entity of the primary/called IMS domain is generally: inserting the allocated primary/called terminal ICID and PCID into the PoC service in the SIP signaling message. In the header field of the P-Charging-Vector, the IMS domain functional entity is transmitted to the calling/called terminal.

 Since other network networks such as MMD have basically the same network structure as the IMS network, the present invention is also applicable to other SIP networks such as MMD.

 It can be seen from the above that the charging association method of the cluster service provided by the present invention associates each calling session belonging to the same cluster session with the bill generated by the called session in the overall session flow of the PoC communication. . The charging management method for the cluster service provided by the present invention will be used as the same session in the call session generated by each calling session and called session belonging to the same cluster session in the overall session flow of the PoC communication. The generated bills are billed.

The above is only the embodiment of the process and method of the present invention, and is not intended to limit the present invention. Any modifications, equivalents, improvements, etc. made within the spirit and principles of the present invention are It should be included in the scope of protection of the present invention.

Claims

Claim  A charging association method for a trunk voice service, characterized in that the method comprises the following steps:  A. Controlling the cluster voice service server The Controlling PoC Server allocates a unique cluster voice service charging identifier PCID to the cluster service session when a cluster session starts.  B. The Controlling PoC Server transmits the PCID to the SIP network to which the calling terminal belongs and the SIP network to which the called terminal belongs, and the PCID is added to the CDRs of each terminal participating in the current cluster service session to implement the cluster. The charging association of each calling session and called session included in the business session.  2. The method according to claim 1, wherein: in the step B, the Controlling PoC Server transmits the PID to the SIP network to which the calling terminal belongs and the SIP network to which the called terminal belongs by using a dedicated SIP message. .  3. The method according to claim 1, wherein: in the step B, the Controlling PoC Server adds the PCID to the service request message and the acknowledgment response message, and respectively transmits the same to the SIP network and the called party to which the calling terminal belongs. The SIP network to which the terminal belongs.  4. The method of claim 3 wherein said SIP network is an IMS network or an MMD network.  The method of claim 4, wherein when the SIP network is an IMS network, the step A includes:  A1. The calling terminal sends a service request to the Controlling PoC Server through the IMS to which the calling terminal belongs. A2. The Controlling PoC Server assigns a unique PCID to the cluster session. The step B includes:  Bl, the Controlling PoC Server will assign the PCID assigned to the cluster session to the IMS of the calling terminal that is sent to the current session and sent to the current session.  B2, the IMS to which the calling terminal belongs, the service request containing the PCID, and sent to the PoC server to which the calling terminal belongs and the IMS to which the called terminal of the current cluster session belongs;  B3. The IMS to which the called terminal belongs shall send the service request of the PCID to the PoC Server to which the called terminal belongs, and delete the PCID in the service request and send it to the called terminal.  B4, in the process of returning the acknowledgment response from the called terminal to the calling terminal, the PCC belongs to the IMS to which the calling terminal belongs, by the PoC Server to which the calling terminal belongs;  B5. In the current session of the cluster session, the PCID is added to the CDRs of each terminal participating in the current cluster service session.  The method according to claim 5, wherein the step A1 comprises: Al l, the calling terminal sends a service request to the P-CSCF of the IMS to which it belongs;  A12, the P-CSCF of the IMS to which the calling terminal belongs is assigned the calling ICID to the calling session, and the joining request is sent to the S-CSCF signed by the calling user;  A13. The S-CSCF sends a service request including the calling ICID to the PoC Server and the Controlling PoC Server to which the calling terminal belongs.  In the step A2, the Controlling PoC Server also allocates the called ICID to the called session, and joins the service request;  In the step B2, the S-CSCF of the IMS to which the calling terminal belongs sends the service request to the PoC server to which the calling terminal belongs and the IMS to which the called terminal of the current cluster session belongs; In the step B3, the S-CSCF of the IMS to which the called terminal belongs sends a service request including the PCID to the PoC server to which the called terminal belongs, and sends the service request to the S2. The P-CSCF of the IMS to which the called terminal belongs is deleted by the P-CSCF and the PCID and all ICIDs in the service request are sent to the called terminal.  The method of claim 4, wherein when the SIP network is an IMS network, the step A includes:  Al. The calling terminal sends a service request to the IMS to which the called party belongs by using the IMS to which the calling terminal belongs.  A2, the IMS to which the called terminal belongs sends a service request to the Controlling PoC Server; a3. The Controlling PoC Server assigns a unique PCID to the cluster session;  The step B includes:  Bl, Controlling PoC Server will assign the PCID assigned to the cluster session to the service request and send it to the IMS to which the called terminal belongs;  B2, the IMS of the called terminal will send a service request containing the PCID, and send it to the PoC server to which the called terminal belongs, and delete the PCID in the service request and send it to the called terminal; b3 > return to the calling terminal at the called terminal During the acknowledgment response, the PCID of the called terminal belongs to the IMS to which the calling party belongs, along with the acknowledgment response by the IMS to which the called terminal belongs;  B4. The IMS to which the calling terminal belongs includes an acknowledgment response of the PCID, and is sent to the PoC Server to which the calling terminal belongs;  B5. In the current session of the cluster session, the PCID is added to the CDRs of each terminal participating in the current cluster service session. 8. The method according to claim 7, wherein the step a1 comprises: al l, the calling terminal sends a service request to the P-CSCF of the IMS to which it belongs; al2, the P-CSCF of the IMS to which the calling terminal belongs Assigning a calling ICID to the calling session, and sending the joining service request to the S-CSCF signed by the calling user; Al3, the S-CSCF sends the service request including the calling ICID to the PoC server to which the calling terminal belongs and the IMS to which the called party belongs;  In the step a2, the S-CSCF of the IMS to which the called party belongs sends a service request including the calling ICID to the Controlling PoC Server;  In the step a3, the Controlling PoC Server further allocates the called ICID to the called session, and joins the service request;  In the step b2, the S-CSCF of the IMS to which the called terminal belongs sends the service request to the PoC server to which the called terminal belongs, and sends the service request to the P-CSCF of the IMS to which the called terminal belongs, by the P-CSCF. The PCID and all ICIDs in the service request are deleted and sent to the called terminal;  In the step b4, the S-CSCF of the IMS to which the calling terminal belongs sends an acknowledgment response including the PCID to the PoC Server to which the calling terminal belongs.  9. The method according to claim 1, 2, 3, 5, 6, 7, or 8, wherein the Controlling PoC Server is a separate PoC Server; or a PoC Server to which the calling terminal belongs; or called The PoC Serve to which the terminal belongs.  10. The method of claim 5 or 7, wherein:  If a new terminal joins the cluster session or the terminal that has quit halfway joins the cluster session during the cluster session, the PCID of the cluster session and other hosts are still used in the CDRs generated by the calling session or the called session. Call a session or called session association.  A charging management method for a trunked voice service, characterized in that the method comprises the following steps:  A. Controlling the cluster voice service server The Controlling PoC Server allocates a unique cluster voice service charging identifier PCID to the cluster service session when a cluster session starts. B. The Controlling PoC Server transmits the above PCID to the calling terminal. The SIP network and the SIP network to which the called terminal belongs, by adding the PCID to the bills of the terminals participating in the current cluster service session, realize the billing of each calling session and called session included in the current cluster service session. Association  C. At the end of the cluster service session, the CDRs with the same PCID are charged as CDRs generated by the same session in the CDRs generated by the SIP network to which the master/called terminal belongs.  The method according to claim 11, wherein the step C includes: Cl, a SIP network to which the calling terminal belongs, and a SIP network to which the called terminal belongs, respectively transmitting the bill containing the PCID to the billing center. ;  C2. The billing center identifies the PCIDs included in all the bills, and determines the bills with the same PCID as the bills of the same complete cluster session;  C3. The charging center performs charging for the charging policy of the cluster session.  The method according to claim 12, wherein the step C3 is: the charging center adopts a unified method to charge all terminals participating in the current cluster session.  The method according to claim 11, wherein in the step B, the Controlling PoC Server transmits the PID to the SIP network to which the calling terminal belongs and the SIP network to which the called terminal belongs by using a dedicated SIP message. .  The method according to claim 11, wherein in the step B, the Controlling PoC Server adds the PCID to the service request message and the acknowledgment response message, and respectively transmits the same to the SIP network and the called party to which the calling terminal belongs. The SIP network to which the terminal belongs.  16. The method according to claim 15, wherein: the SIP network is an IMS network or an MMD network.  The method of claim 16, wherein: when the SIP network is an IMS network, the step A includes: A1. The calling terminal sends the IMS to the Controlling PoC Server through the IMS of the calling terminal. Send a business request;  A2, Controlling PoC Server assigns a unique PCID to the cluster session;  The step B includes:  Bl, the Controlling PoC Server will assign the PCID assigned to the cluster session to the IMS of the calling terminal that is sent to the current session and sent to the current session.  B2, the IMS to which the calling terminal belongs, the service request containing the PCID, and sent to the PoC server to which the calling terminal belongs and the IMS to which the called terminal of the current cluster session belongs;  B3. The IMS to which the called terminal belongs shall send the service request of the PCID to the PoC Server to which the called terminal belongs, and delete the PCID in the service request and send it to the called terminal.  B4, in the process of returning the acknowledgment response from the called terminal to the calling terminal, the PCC belongs to the IMS to which the calling terminal belongs, by the PoC Server to which the calling terminal belongs;  B5. In the current session of the cluster session, the PCID is added to the CDRs of each terminal participating in the current cluster service session.  The method of claim 16, wherein: when the SIP network is an IMS network, the step A includes:  Al. The calling terminal sends a service request to the IMS to which the called party belongs by using the IMS to which the calling terminal belongs.  A2, the IMS to which the called terminal belongs sends a service request to the Controlling PoC Server; a3. The Controlling PoC Server assigns a unique PCID to the cluster session;  The step B includes: Bl, Controlling PoC Server will assign the PCID assigned to the cluster session to the service request and send it to the IMS of the called terminal; B2. The IMS to which the called terminal belongs shall send the service request including the PCID to the PoC Server to which the called terminal belongs, and delete the PCID in the service request and send it to the called terminal. b3. Return the called terminal to the calling terminal. During the acknowledgment response, the PCID of the called terminal belongs to the IMS to which the calling party belongs, along with the acknowledgment response by the IMS to which the called terminal belongs;  B4. The IMS to which the calling terminal belongs includes an acknowledgment response of the PCID, and is sent to the PoC Server to which the calling terminal belongs;  B5. In the current session of the cluster session, the PCID is added to the CDRs of each terminal participating in the current cluster service session.  The method according to claim 11, 14, 15, 17, or 18, wherein the Controlling PoC Server is a separate PoC Server; or a PoC Server to which the calling terminal belongs; or a PoC to which the called terminal belongs Serve.  20. A method according to claim 17 or 18, characterized by:  If a new terminal joins the cluster session or the terminal that has quit halfway joins the cluster session during the cluster session, the PCID of the cluster session and other hosts are still used in the CDRs generated by the calling session or the called session. Call a session or called session association.  The method of claim 19, wherein the process of rejoining the cluster session by the terminal that is halfway back during the cluster session includes:  D1. The terminal that has quit halfway sends a service request to the controlling PoC Serve through the IMS to which the terminal belongs;  D2, controlling the PoC Serve to determine whether the terminal is a group member of the current cluster session, and if yes, adding the PCID of the cluster session to the acknowledgment response, returning to the IMS to which the terminal belongs, and performing step D3; otherwise, pressing the new cluster Session processing  D3. The IMS to which the terminal belongs sends the acknowledgment response including the PCID to the PoC Serve to which the terminal belongs, and deletes the PCID in the acknowledgment response and sends the acknowledgment to the terminal.