WO2007101409A1 - Procédé, dispositif et système de réalisation de notification de paiement dans le domaine des paquets - Google Patents

Procédé, dispositif et système de réalisation de notification de paiement dans le domaine des paquets Download PDF

Info

Publication number
WO2007101409A1
WO2007101409A1 PCT/CN2007/000746 CN2007000746W WO2007101409A1 WO 2007101409 A1 WO2007101409 A1 WO 2007101409A1 CN 2007000746 W CN2007000746 W CN 2007000746W WO 2007101409 A1 WO2007101409 A1 WO 2007101409A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
called
aoc
control unit
call
Prior art date
Application number
PCT/CN2007/000746
Other languages
English (en)
French (fr)
Inventor
Dongjun Wu
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
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2007101409A1 publication Critical patent/WO2007101409A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/141Indication of costs
    • H04L12/1414Indication of costs in real-time

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, apparatus, and system for implementing charging notification in a packet domain.
  • AoC Advanced of Charge
  • SIP Session Initiation Protocol
  • NTN Next Generation Network
  • the billing notification service As a service that has been popularized in traditional telecommunication networks, the billing notification service still needs to be provided to SIP terminal users. However, due to changes in the application environment, the billing notification service provided to SIP terminals in NGN will also be inevitable.
  • the change of the traditional service features provided by the NGN in the NGN is called the Public Switched Telephone Network (PSTN) / Integrated Services Digital Network (ISDN). Services , and define the requirements of the PSTN/ISDN simulation service, as well as the standards for billing notification services.
  • PSTN Public Switched Telephone Network
  • ISDN Integrated Services Digital Network
  • AoC-S service refers to the situation when the call is established, or the rate changes during the call. Rate information for the call sent to the service user. This billing information is provided by the service user's home network.
  • the AoC-D service refers to providing the charging information to the service user during the call, and the charging information may be obtained by interaction between different operators.
  • AoC-E service means at the end of the call, to the service The user provides billing information for the call.
  • the billing information can be valid for each call, and becomes a permanent mode. It can also be valid only for one call and become a temporary mode.
  • the specific process is shown in Figure 1; as shown in Figure 2, the temporary response message, such as 183, is used to transfer the billing.
  • the specific process of the permanent AoC-S is shown in Figure 2.
  • the specific process of the temporary AoC-S is shown in Figure 3.
  • the specific process of calling the permanent AoC-D and the calling temporary AoC-D is shown in Figure 4.
  • the charging information is transmitted using the confirmation ok message, such as 200.
  • the specific process of calling the permanent AoC-E is as shown in Figure 5.
  • Figure 6 when using BYE to deliver billing information, the specific procedure of calling the permanent AoC-E is as follows.
  • Figure 8 shows the specific process of calling the permanent AoC-S service when using MESSAGE to deliver billing information. As shown in Figure 9.
  • the implementation of the prior art charging notification service mainly relies on setting a correspondingly more powerful module in the service control unit, such as a calling permanent charging notification service logic processing module, for performing the main operation when the served user is the calling party.
  • a calling permanent charging notification service logic processing module for performing the main operation when the served user is the calling party.
  • Calling the business logic of the permanent billing notification service; the calling temporary billing notification service processing module is configured to execute the service logic of the calling temporary billing notification service when the serving user is the calling party;
  • the billing notification service logic processing module is configured to execute the service logic of the called permanent billing notification service when the served user is called.
  • Embodiments of the present invention provide a method, device, and system for implementing charging notification in a packet domain.
  • the temporary billing notification service resolution policy is configured on the called side to meet the demand of the called user to solve a large number of temporary billing notification services.
  • Embodiments of the present invention provide a method for implementing charging notification in a packet domain, where the method includes:
  • the #called called user subscribes to the data, and the call request is routed to the service control unit;
  • the service control unit receives an activation/deactivation charging notification service request of the called user terminal, and determines whether to activate the charging notification service according to the user terminal activation/deactivation operation; when the charging notification service is activated, the service The control unit sends the charging information to the called user terminal.
  • An embodiment of the present invention further provides a system for implementing charging notification in a packet domain, which includes a service control unit, a call session control unit, and a session initiation protocol terminal.
  • the call session control unit is configured to provide a call control and a route connection function for a session initiation protocol end user of the access packet core network, and trigger a call to the service control unit; the service control unit is configured to connect The session initiating user of the packet core network provides a service control function, and the called temporary charging notification service processing module is set, and the called temporary charging notification service operation is performed when the served user is called.
  • the embodiment of the present invention further provides an apparatus for implementing a charging notification in a packet domain, which is used to implement a service control function, and is configured with a called temporary charging notification service logic processing module, configured to be called at the served user.
  • a charging notification service logic processing module configured to be called at the served user.
  • the charging notification service when the SIP terminal user acts as a called party, the charging notification service can be temporarily activated or deactivated, and the temporary charging notification service is more completely realized.
  • the terminal When the user is called, the terminal can be based on the terminal. Roaming, importance of calls, and other various situations, choose to activate or deactivate the billing notification service, greatly expanding the scope of adaptation of the temporary billing notification service, and greatly satisfying the needs of users.
  • FIG. 1 is a schematic diagram of a process of calling a permanent AoC-S, calling a permanent AoC-D, calling a temporary AoC-S, and calling a temporary AoC-D using MESSAGE to transmit billing information in the prior art;
  • FIG. 2 is a schematic diagram of a process of calling a permanent AoC-S using 183 to transfer charging information in the prior art
  • FIG. 3 is a flow chart of a calling temporary AoC-S that uses 183 to transmit charging information in the prior art.
  • FIG. 4 is a schematic flow chart of a calling permanent AoC-D and a calling temporary AoC-S using INFO to transmit charging information in the prior art
  • FIG. 5 is a schematic flowchart of a permanent AoC-D of a calling party that uses the 200 to transmit charging information in the prior art
  • FIG. 6 is a schematic flowchart of a caller permanent AoC-E that uses the 200 to transmit charging information in the prior art
  • FIG. 7 is a schematic flow chart of a called persistent AoC-S service using 183 to transmit charging information in the prior art
  • FIG. 8 is a schematic flow chart of a called persistent AoC-D service using INFO to transmit charging information in the prior art
  • FIG. 9 is a schematic flow chart of a persistent AoC-S service of a called party that uses MESSAGE to transmit charging information in the prior art
  • FIG. 10 is a schematic diagram of a network recap structure of a packet core network according to an embodiment of the present invention
  • FIG. 1.1 is a schematic diagram of an implementation process of AoC-S and AoC-D in the embodiment of the present invention
  • FIG. 12 is a schematic diagram of a main embodiment of the present invention. Schematic diagram of the implementation process of AoC-E in both cases of release and dry call;
  • FIG. 13 is a schematic flowchart of an implementation process of activating a AoC service by a called user during a call setup by using a SUBSCRIBER according to an embodiment of the present invention
  • FIG. 14 is a schematic diagram of an implementation process of activating a AoC service by using a SUBSCRIBER after a call is established in the embodiment of the present invention
  • FIG. 15 is a flowchart showing an implementation process of temporarily triggering an AoC service by a called user in an embodiment of the present invention. detailed description
  • a network logical structure of a packet core network using SIP as call control signaling as shown in FIG. 10, wherein the call session control unit provides call control for a SIP terminal user accessing a packet core network And a function such as routing connection, the call session control unit may trigger the call to a different service control unit.
  • the E4 interface between the two call session control units is SIP.
  • the call session control unit is called Call Session Control Function (CSCF, Call Session Control Function) 0
  • the service control unit provides various service logics for SIP terminal users accessing the packet core network.
  • the control function is the host execution environment for various services
  • the call waiting service control unit is a service control unit that provides the SIP terminal user with the logical control function of the call waiting service.
  • the E3 interface between the two is SIP; when the service control unit and the call session control unit are the same network entity, the E3 interface is a SIP or a customized internal interface.
  • the service control unit is called an application server (AS, Application Server).
  • a called temporary charging notification service logic processing module is configured to execute the service logic of the called temporary charging notification service when the served user makes a call.
  • the SIP terminal accesses the call session control unit through the E1 interface, and the interface protocol is SIP, and the other can pass through other proxy servers.
  • the SIP terminal can also access the service control unit through the E2 interface.
  • the E2 interface is the Ut reference point.
  • HTTP Hypertext Transfer Protocol
  • the calling user initiates a call, and the calling side network routes the INVITE message to the call session control unit of the called network; the call session control unit of the called network according to the service triggering rule, If the called user subscribes to the temporary AoC service, the INVITE message is routed to the AoC service control unit;
  • step (2) the AoC service control unit forwards the SIP INVITE message to the call conference control unit;
  • the AoC service control unit may add the current subscription information to the SIP INVITE message for the called user to select whether to temporarily activate the AoC service. To do this, you need to extend the SIP header field as follows:
  • PAoC-Header "P-AoC-Ind” HCOLON P-AoC-para *
  • P-AoC-value "Actived” I "Inactived”
  • AoC-S Actived
  • AoC-D Inactived
  • AoC-All Inactived means that all AoC services are deactivated
  • the AoC Service Control Unit may also not provide the above information.
  • step (3) the service control unit forwards the INVITE message to the call session control unit; in step (4), the call session control unit forwards the INVITE message to the called terminal; in step (5), the calling party and the called party perform the session negotiation operation. , such as media negotiation, resource reservation; ⁇
  • the called terminal rings, and the ringing tone is sent back to the calling party, and the called terminal can ring according to the P-AoC.
  • the value of the value indicates whether the called user is the AoC temporary service and its default value, which is used to prompt the called user to choose to activate or deactivate the AoC service. It can also prompt the called user to select to activate or go by setting in the called terminal. Activate the AoC service;
  • step (11) the called user selects whether the call needs to activate the AoC service and accepts the call; the called terminal provides an operation interface for the called user to select to activate the AoC service; the operation interface may be a menu mode, a command line mode , graphic dialog mode, etc.;
  • step (12) the called terminal sends a 200 OK message to the call session control unit, and the message carries the called user activation option, and the SIP header field extension can be similar to step 2 or use the same SIP header field.
  • PAoC-Header "P-AoC-Ind” HCOLON P-AoC-para * (COMMA
  • AoC-S Actived
  • AoC-D Inactived
  • AoC-All actived means to activate all AoC services.
  • the called terminal can also use the subscription header field to carry the called user activation option; the called terminal can also be in other messages, such as INFO, UPDATE and other response messages.
  • the SIP header field is carried, and the AoC service is activated before the call is established.
  • the called terminal can also establish a call, and use other messages, such as a re-Invite message, a response message, to carry the SIP header field extension, and activate the AoC service.
  • the call session control unit routes the 200 OK message to the service control unit; in (14), the service control unit determines, according to the activation option in the 200 OK message, and the subscription option of the called user temporary AoC service, The secondary call, whether to activate the AoC service; If the AoC service is activated, the service control unit needs to obtain the charging information of the current call from the charging system.
  • the interface between the service control unit and the billing system is the same as the prior art;
  • the service control unit sends the charging information such as the rate of the call to the called terminal through the MESSAGE message, and the service control unit can also respond by other messages, such as INFO, ACK. Message to send billing information;
  • the called terminal displays the charging information to the called user to implement the AoC-S service; in (18) and (19), the called terminal sends a 200 OK message of the MESSAGE message to the service control unit;
  • the service control unit sends a 200 OK message to the calling user, and the message may continue to carry the AoC activation option, or may not carry, complete the call connection, call setup, and (20) and (21) Can be performed before (15);
  • the session is established; in the (23) call process, in the case where the call record is changed, the service control unit obtains the updated billing information from the billing system;
  • the service control unit sends the charging information to the called terminal through the MESSAGE message, and the service control unit may also send the charging information by using other messages, such as INFO, in response to the message;
  • the called terminal displays the charging information to the called user to implement the AoC-D service; in (27) and (28), the called terminal transmits a 200 OK message of the MESSAGE message to the service control unit.
  • the AoC-E service implementation process is as follows: In (1), the calling party releases the call, and the calling side network routes the BYE message to the call session control unit of the called network;
  • the call session control unit routes the BYE message to the service control unit; in (3), the service control unit obtains the charging information of the current call from the charging system; and the service control in (4) and (5)
  • the unit sends the charging information of the call to the called terminal through the MESSAGE message, and the service control unit can also use other messages, such as INFO' BYE, to send billing information in response to the message;
  • the called terminal displays the charging information to the called user to implement the AoC-E service; in (7) and (8), the called terminal sends the MESSAGE message to the service control unit.
  • the service control unit sends a BYE message to the called user, and (9) and (10) ⁇ may also be performed before the (4);
  • the called terminal transmits 200 to the calling side network.
  • the AoC-E service implementation process is as follows: In (1), the calling party releases the call, and the calling side network routes the BYE message to the call session control unit of the called network;
  • the call session control unit routes the BYE message to the service control unit; in (3), the service control unit obtains the charging information of the current call from the charging system; and the service control in (4) and (5)
  • the unit sends the charging information of the call to the called terminal through the MESSAGE message, and the service control unit can also use other messages, such as INFO.
  • the called terminal displays the charging information to the called user to implement the AoC-E service; in (7) and (8), the called terminal sends the MESSAGE message to the service control unit.
  • the service control unit sends a BYE message to the called user, and the (9) and (10) may also be performed before the (4);
  • the called terminal sends a 200 OK message to the calling side network to complete the release of the call.
  • the embodiment includes a complete implementation process of the AoC service temporarily triggered by the called user, and specifically describes the implementation process of the activated user to activate the AoC service by using the SUBSCRIBER during call setup. :
  • the calling user initiates a call
  • the calling side network routes the INVITE message to the call session control unit of the called network, and the call session control unit of the called network according to the service triggering rule, if the called user signs the temporary AoC service, routing the INVITE message to the AoC service control unit;
  • the AoC service control unit forwards the SIP INVITE message to the call session control unit, and the AoC service control unit can add the AoC query flag to the SIP INVITE message. Indicates that the called user needs to select whether to temporarily trigger the AoC service.
  • the AoC service control unit can also check the option of the called user to subscribe to the temporary AoC service. It is activated or not activated by default. The information is added to the SIP INVITE message for notification.
  • the called terminal Its SIP header field extension is the same as the extension of (2) described in Figure 11;
  • the service control unit forwards the INVITE message to the call session control unit;
  • the call session control unit forwards the INVITE message to the called terminal;
  • the calling and called parties perform session negotiation operations, such as media negotiation, resource reservation, etc.;
  • the called terminal rings in (6) and (7), and sends a ring tone to the calling party, and the called terminal can indicate whether the called user is an AoC temporary service according to the P-AoC-value value while ringing.
  • the default value is used to prompt the called user to choose to activate or deactivate the AoC service.
  • the called user selects whether the call needs to activate the AoC service.
  • the called terminal provides an operation interface for the called user to select to activate the AoC service.
  • the menu mode, the command line mode, the graphic dialog mode, etc.; or the called terminal sends a SUBSCRIBER message to the service control unit through the call session control unit, for activating or deactivating the AoC service;
  • an event packet indicating that the AoC service is activated in the SIP message for example, named aoc
  • aoc an event packet indicating that the AoC service is activated in the SIP message
  • the following content is "Event aoc”.
  • D AoC-E service; and cancel the activation of the AoC service by setting Expired in the SUBSCRIBER message to 0, or expanding an event package to identify the temporary cancellation of the AoC service;
  • the DialogID of the session may be used to associate the SUBSCRIBER message with the session to activate/deactivate the AoC service of the session; It is also possible not to carry the DiaglogID or the related information of the calling party and the called party, and indicate that the activation/deactivation operation is related to all the currently existing calls, and activate/deactivate the AoC service of all the calls of the called terminal; in the above xml description, it may also be added.
  • the service control unit sends a 200 OK message of the SUBSCRIBER message to the called terminal;
  • the service control unit determines according to the SUBSCRIBER operation of the user terminal. For this call, whether the AoC service is activated or not, if the AoC service is activated, the service control unit needs to obtain the charging information of the current call from the charging system.
  • the interface between the service control unit and the billing system is the same as the prior art;
  • the service control unit sends the charging information such as the rate of the call to the called terminal through the NOTIFY message, and the service control unit can respond by other messages, such as MESSAGE, INFO.
  • the message is used to send the charging information; wherein, the NOTIFY message can be combined with the MESSAGE, the text mode is used to deliver the charging information, and the MIME type can be extended to deliver the charging information;
  • the called terminal displays the charging information to the called user to implement the AoC-S service; in (14) and (15), the called terminal sends a NOTIFY message to the service control unit.
  • the service control unit obtains the updated billing information from the billing system
  • the service control unit sends the charging information to the called terminal through the NOTIFY message, and the service control unit may also send the charging information by using other messages, such as MESSAGE, INFO, and response message;
  • the called terminal displays the charging information to the called user to implement the AoC-D service;
  • the called terminal sends a NOTIFY message to the service control unit.
  • the service control unit sends the charging information to the called terminal through the NOTIFY message, and the service control unit may also send the charging information through other messages, such as MESSAGE, INFO, BYE, and the response message;
  • the called terminal displays the charging information to the called user to implement the AoC-E service; (33) and (34) the called terminal transmits a 200 ⁇ K message of the NOTIFY message to the service control unit.
  • the implementation process of the called user to activate the AoC service through the SIJBSCRIBER after the call is established is as follows:
  • the calling user initiates a call
  • the calling side network routes the INVITE message to the call session control unit of the called network, and the call session control unit of the called network triggers according to the service.
  • the INVITE message is routed to the AoC service control unit;
  • the AoC service control unit forwards the SIP INVITE message to the call session control unit, and the AoC service control unit may add an AoC query flag to the SIP INVITE message, indicating that the called user needs to select whether to temporarily trigger the AoC service, AoC.
  • the service control unit may also check the option of the called user to subscribe to the temporary AoC service, which is activated or not activated by default, and adds the information to the SIP INVITE message for notifying the called terminal.
  • the extension of its SIP header field is the same as the extension of (2) in Figure 11;
  • the service control unit forwards the INVITE message to the call session control unit; in (4), the call session control unit forwards the INVITE message to the called terminal; in (5), the calling party and the called party perform a session negotiation operation, such as Media negotiation, resource reservation, etc.;
  • the called terminal rings, and the ringing tone is sent back to the calling party, and the called party chooses to accept the call; in (7), (8), (9) and (10), the called user calls the calling party.
  • the side network sends a 200 OK message;
  • the called user selects to activate or deactivate the AoC service through the operation interface of the called terminal, and the operation interface thereof may be menu mode, command line mode, graphic dialog mode, etc.;
  • the session control unit sends a SUBSCRIBER message to the service control unit for activating or deactivating the AoC service.
  • an event indicating a subscription request for "Activating AoC Service" is extended in the SIP message.
  • the packet for example, named aoc, is passed through the Event header field.
  • the SIP SUBSCRIBE message has the following content: "Event: aoc", the activation of the AoC service is cancelled by Expired in the SUBSCRIBER message, and the AoC service can be activated.
  • An event packet to identify the temporary cancellation of the AoC service, and in the SUBSCRIBER message, may carry the Dialog ID of the session, or the relevant information of the calling party and the called, to associate the SUBSCRIBER message with the session, and activate the AoC of the call.
  • Business you can also not carry DiaglogID or related call information , The subscription is currently present and all associated calls, the called terminal activates the AoC service of all calls;
  • the service control unit sends a 200 OK message of the SUBSCRIBER message to the called terminal;
  • the service control unit determines according to the SUBSCRIBER operation of the user terminal. For this call, whether the AoC service is activated or not, if the AoC service is activated, the service control unit needs to obtain the charging information of the current call from the charging system.
  • the interface between the service control unit and the billing system is the same as the prior art;
  • the service control unit sends the charging information such as the rate of the call to the called terminal through the NOTIFY message, and the service control unit may also use other messages, such as MESSAGE, INFO, and the response message.
  • MESSAGE e.g., MESSAGE
  • INFO e.g., INFO
  • the NOTIFY message can be used to communicate billing information in the same way as MESSAGE, or to extend a MIME type to deliver billing information;
  • the called terminal displays the charging information to the called user to implement the AoC-S service; in (20) and (21), the called terminal sends the NOTIFY message to the service control unit.
  • the service control unit obtains the updated billing information from the billing system
  • the service control unit sends the charging information to the called terminal through the NOTIFY message, and the service control unit may also send the charging information through other messages, such as MESSAGE, INPO, and the response message;
  • the called terminal displays the charging information to the called user to implement the AoC-D service; in (26) and (27), the called terminal sends a 200 OK message of the NOTIFY message to the service control unit; In the call release, the call release and the called release are both; in (29), the service control unit obtains the charging information of the current call from the charging system;
  • the service control unit sends the charging information to the called terminal through the NOTIFY message, and the service control unit may also send the charging information through other messages, such as MESSAGE, INFO, BYE, and response messages. ;
  • the called terminal displays the charging information to the called user to implement the AoC-E service; in (33) and (34), the called terminal sends a NOTIFY message to the service control unit.
  • the implementation process of the AoC service activated or deactivated by the called user through the Hypertext Transfer Protocol (HTTP) during call setup is described in FIG. 15, and the specific implementation process is as follows:
  • the calling user initiates a call, and the main The calling side network routes the INVITE message to the call session control unit of the called network, and the call session control unit of the called network, according to the service triggering rule, routes the INVITE message to the AoC service control if the called user subscribes to the temporary AoC service. unit; N2007/000746
  • the AoC service control unit forwards the SIP INVITE message to the call session control unit, and the AoC service control unit may add an AoC query flag to the SIP INVITE message, indicating that the called user needs to be selected to temporarily trigger the AoC.
  • the service, the AoC service control unit can also check the option of the called user to subscribe to the temporary AoC service, which is activated or not activated by default, and adds the information to the SIP INVITE message for notifying the called terminal.
  • the extension of its SIP header field is the same as the extension of (2) in Figure 1;
  • the service control unit forwards the INVITE message to the call session control unit; in (4), the call session control unit forwards the INVITE message to the called terminal; in (5), the caller and the called party perform a session negotiation operation, such as Media negotiation, resource reservation, etc.;
  • the called terminal rings, and the ringing tone is sent back to the calling party, and the called terminal can indicate whether the called user is the AoC temporary service and the P-AoC-value value according to the P-AoC-value value.
  • the default value is used to prompt the called user to choose to activate or deactivate the AoC service. Or the called user selects whether the call needs to activate the AoC service.
  • the called terminal provides an operation interface for the called user to select to activate the AoC service. It can be menu mode, command line mode, graphic dialog mode, etc.; the called terminal activates/deactivates the AoC service through the HTTP protocol to the service control unit, and the operation can also be performed after the call is established.
  • TISPAN uses Ut reference point to define the interface between the terminal and the service control unit, the XCAP protocol is used to implement the business operation through the XML description; the XCAP protocol is a protocol based on the HTTP protocol.
  • the HTTP protocol carries the XCAP protocol
  • the XCAP protocol carries the XML description
  • the XML description contains the actual service activation operations.
  • the service control unit sends a response message to the called terminal to activate the temporary AoC service activation/deactivation operation.
  • the service control unit determines whether to activate the AoC service for the call according to the activation/deactivation operation of the user terminal. If the AoC service is activated, the service control unit needs to obtain the charging information of the current call from the charging system.
  • the interface between the service control unit and the charging system is the same as the prior art;
  • the service control unit sends the charging information such as the rate of the call to the called terminal through the MESSAGE message, and the service control unit may also send the message through other messages, such as INFO, response message.
  • Billing information such as the rate of the call to the called terminal through the MESSAGE message, and the service control unit may also send the message through other messages, such as INFO, response message.
  • the called terminal displays the charging information to the called user to implement the AoC-S service; in (12) and (13), the called terminal sends the MESSAGE message to the service control unit.
  • the session is established; in the case of the call of (20), in the case where the call record is changed, the service control unit obtains the updated billing information from the billing system;
  • the service control unit sends the charging information to the called terminal through the MESSAGE message, and the service control unit may also send the charging information by using other messages, such as INFO, to respond to the message;
  • the called terminal displays the charging information to the called user to implement the AoC-D service; in (24) and (25), the called terminal sends a 200 OK message of the MESSAGE message to the service control unit;
  • the service control unit obtains the charging information of the current call from the charging system; in (28) and (29), the service control unit passes the charging information through the MESSAGE message, Sended to the called terminal, the service control unit can also send the charging information through other messages, such as INK), BYE, and response messages;
  • the called terminal displays the charging information to the called user to implement the AoC-E service; in (31) and (32), the called terminal sends the MESSAGE message to the service control unit.
  • the temporary charging notification service is implemented more completely by using the technical solution provided by the present invention.
  • the user may select to activate according to other conditions such as terminal roaming, call importance, and the like.
  • Deactivation of the billing notification service greatly expands the scope of adaptation of the temporary billing notification service, which greatly satisfies the needs of users.
  • the present invention provides a method and system for implementing charging notification in a packet domain, which greatly expands the scope of adaptation of the temporary charging notification service, and greatly satisfies the needs of users.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

一种在分组域中实现计费通知的方法、 装置及系统 本申请要求于 2006 年 03 月 08 日提交中国专利局、 申请号为
200610034258.9、 发明名称为 "一种在分组域中实现计费通知的系统、 装 置及方法" 的中国专利申请的优先权, 其全部内容通过引用结合在本申请 中。
技术领域
本发明涉及通信技术领域, 尤其涉及一种在分组域中实现计费通知的 方法、 装置及系统。
背景技术
计费通知(AoC, Advice of Charge )是传统电信网络中一种常用的电 信业务, 它用于向用户提供计费信息。 随着分組技术的不断成熟, 基于电 路交换的传统电信网络正在向着基于分组交换的宽带电信网发展, 而使用 会话发起协议 ( SIP , Session Initiation Protocol )作为分组电信核心网的呼 叫控制信令则是当前的技术发展趋势之一, 如 ITU-T和 ETSI对下一代网 络(NGN, Next Generation Network )标准的制订, 在这种新的分析电信 网络中, 新的分组终端 - SIP终端将逐步取代传统的终端话机。
计费通知业务作为一项在传统电信网中业已普及的服务,仍然需要向 SIP终端用户提供, 但由于应用环境发生了变化, 因此在 NGN 中向 SIP 终端提供的计费通知业务也将不可避免的发生变化, 将此类在 NGN中向 SIP 终端用户提供的具有传统业务特征的业务统称为公共电话交换网 ( PSTN, Public Switched Telephone Network ) /综合业务数字网 ( ISDN, Integrated Services Digital Network ) simulation services , 并定义 PSTN/ISDN simulation业务的需求, 以及计费通知业务的标准。
在 TISPAN WI 01002中给出的定义中, AoC业务包括以下业务: 呼叫建立时计费通知 (AoC-S ) : AoC-S业务指在通话建立时, 或者 通话过程中费率发生改变情况下, 向服务用户发送通话的费率信息。 该计 费信息由服务用户的归属网络提供。
通话过程中计费通知(AoC-D ): AoC-D业务指在通话过程中, 向服 务用户提供计费记录信息, 这个计费信息可能在不同的运营商之间交互而 获得。
通话结束时计费通知 (AoC-E ): AoC-E业务指在通话结束时, 向服 务用户提供该通话的计费信息。
根据用户签约业务时的选项, 计费信息可以每次呼叫均有效, 又成为 永久模式, 也可以只对某一次呼叫有效, 又成为临时模式。
在 TISPAN WI 03030中, 提供了 AoC业务的实现方法如下: 如图 1 所示, 使用 MESSAGE来传递计费信息时, 包括主叫永久
AoC-S、 主叫永久 AoC-D、 主叫临时 AoC-S与主叫临时 AoC-D等, 其具 体流程见图 1 ; 如图 2所示的, 使用临时响应消息如 183来传递计费信息 时, 主叫永久 AoC-S的具体流程见图 2; 如图 3所示的, 使用 183来传递 计费信息时,主叫临时 AoC-S的具体流程见图 3;如图 4所示的,使用 INFO 来传递计费信息时, 主叫永久 AoC-D和主叫临时 AoC-D的具体流程见图 4; 如图 5所示的, 使用确认 ok消息如 200来传递计费信息时, 本端先挂 机则主叫永久 AoC-E的具体流程见图 5; 如图 6所示的, 使用 BYE来传 递计费信息时, 对端先挂机则主叫永久 AoC-E 的具体流程见图 6; 使用 183来传递计费信息时, 被叫永久 AoC-S业务的具体流程, 如图 7所示; 使用 INFO来传递计费信息时, 被叫永久 AoC-D业务的具体流程, 如图 8 所示; 使用 MESSAGE来传递计费信息时, 被叫永久 AoC-S业务的具体 流程, 如图 9所示。
现有技术的计费通知业务的实现主要依靠业务控制单元中设置相应 更能的模块, 如主叫永久计费通知业务逻辑处理模块, 用于在所服务用户 作主叫的情况下, 执行主叫永久计费通知业务的业务逻辑; 主叫临时计费 通知业务逍辑处理模块, 用于在所服务用户作主叫的情况下, 执行主叫临 时计费通知业务的业务逻辑; 被叫永久计费通知业务逻辑处理模块, 用于 在所服务用户作被叫的情况下, 执行被叫永久计费通知业务的业务逻辑。
在 NGN网络中, 用户是具有移动性的, 而且可以漫游到不同的接入 网絡, 在不同的接入网络中, 用户作为被叫, 其计费情况是不一样的, 因 此, 被叫用户存在大量的临时 AoC业务的需求, 如在归属域, 用户清楚 的了解计费策略, 不需要 AoC业务, 但如果漫游到其它国家或者城市, 则希望临时触发 AoC业务; 还有接听普通电话时, 触发 AoC业务, 但接 听重要电话时, 则不触发 AoC业务; 但是, 被叫用户的这些需求, 在现 有 TISPAN的 WI3030, 以及其它现有技术中, 均无法实现。 发明内容
本发明实施例提供一种在分组域中实现计费通知的方法、 装置及系 统, 在被叫侧配置了临时计费通知业务解决策略, 满足了被叫用户解决大 量临时计费通知业务的需求。
本发明实施例提供一种在分组域中实现计费通知的方法, 该方法包 括:
被叫侧的呼叫会话控制单元收到呼叫请求后, #居被叫用户签约数 据, 将所述呼叫请求路由到所述业务控制单元;
所述业务控制单元接收被叫用户终端的激活 /去激活计费通知业务请 求, 并根据用户终端激活 /去激活操作, 确定是否激活计费通知业务; 在激活计费通知业务时, 所述业务控制单元向被叫用户终端发送计费信 息。
本发明实施例还提供一种在分组域中实现计费通知的系统, 其包括业 务控制单元、 呼叫会话控制单元与会话发起协议终端 ,
所述呼叫会话控制单元, 用于为接入分组核心网的会话发起协议终端 用户提供呼叫控制与路由接续功能, 并将呼叫触发至所述业务控制单元; 所述业务控制单元, 用于为接入分组核心网的会话发起用户提供业务 控制功能, 其上设置有被叫临时计费通知业务处理模块, 在所服务用户作 被叫的情况下, 执行被叫临时计费通知业务操作。
本发明实施例还提供一种在分组域中实现计费通知的装置, 用于实现 业务控制功能, 其上设置有被叫临时计费通知业务逻辑处理模块, 用于在 所服务用户作被叫的情况下, 执行被叫临时计费通知业务的业务逻辑。
本发明所提供的技术方案中, SIP终端用户在作为被叫时, 可以临时 激活或者去激活计费通知业务, 更完整的实现了临时计费通知业务, 用户 在作为被叫时, 可以根据终端漫游, 通话重要性等其它各种情况, 选择激 活或者去激活计费通知业务, 极大的扩展了临时计费通知业务的适应范 围, 大大满足了用户的需求。 附图说明
图 1 是现有技术中使用 MESSAGE 来传递计费信息的主叫永久 AoC-S、 主叫永久 AoC-D、 主叫临时 AoC-S与主叫临时 AoC-D的流程示 意图;
图 2是现有技术中使用 183来传递计费信息的主叫永久 AoC-S的流程 示意图;
图 3是现有技术中使用 183来传递计费信息的主叫临时 AoC-S的流程 示意图;
图 4是现有技术中使用 INFO来传递计费信息的主叫永久 AoC-D与主 叫临时 AoC-S的流程示意图;
图 5是现有技术中本端先挂机,使用 200来传递计费信息的主叫永久 AoC-D的流程示意图;
图 6是现有技术中本端先挂机,使用 200来传递计费信息的主叫永久 AoC-E的流程示意图;
图 7是现有技术中使用 183来传递计费信息的被叫永久 AoC-S业务的 流程示意图;
图 8是现有技术中使用 INFO来传递计费信息的被叫永久 AoC-D业务 的流程示意图;
图 9是现有技术中使用 MESSAGE来传递计费信息的被叫永久 AoC-S 业务的流程示意图;
图 10是本发明实施例中的分组核心网的网络還辑结构示意图; 图 1.1是本发明实施例中的 AoC-S和 AoC-D的实现流程示意图; 图 12是本发明实施例中的主叫释放与被叫幹放两种情况下 AoC-E的 实现流程示意图;
图 13 是本发明实施例中的被叫用户在呼叫建立期间通过 SUBSCRIBER来激活 AoC业务的实现流程示意图;
图 14是本发明实施例中的被叫用户在呼叫建立后通过 SUBSCRIBER 来激活 AoC业务的实现流程示意图;
图 15是本发明实施例中的被叫用户临时触发 AoC业务的实现流程示 意图。 具体实施方式
以下将结合附图及具体实施例, 对本发明的进行较为详细的说明。 如图 10所示的本发明实施例中适用的以 SIP作为呼叫控制信令的分 组核心网的网络逻辑结构, 其中, 所述呼叫会话控制单元为接入分组核心 网的 SIP终端用户提供呼叫控制、 路由接续等功能, 所述呼叫会话控制单 元可以将呼叫触发至不同的所述业务控制单元。 两个所述呼叫会话控制单 元之间的 E4接口为 SIP。在前述的 TISPAN中, 所述呼叫会话控制单元被 称为呼叫会话控制功能(CSCF, Call Session Control Function )0
所述业务控制单元为接入分组核心网的 SIP终端用户提供各种业务逻 辑控制功能, 是各种业务的宿主执行环境, 呼叫等待业务控制单元即是为 SIP终端用户提供呼叫等待业务的逻辑控制功能的业务控制单元。 业务控 制单元和呼叫会话控制单元为不同的网络实体时, 两者之间的 E3接口为 SIP; 业务控制单元和呼叫会话控制单元为同一个网络实体时, E3接口为 SIP或自定义的内部接口。可以有多个处理不同业务的业务控制单元存在。 在前述的 TISPAN中, 业务控制单元被称为应用服务器(AS, Application Server )。
本发明的业务控制单元中设置了一被叫临时计费通知业务逻辑处理 模块, 用于在所服务用户作被叫的情况下, 执行被叫临时计费通知业务的 业务逻辑。
SIP终端通过 E1接口接入呼叫会话控制单元, 其接口协议为 SIP, 中 间可以经过其它代理服务器; SIP终端还可以通过 E2接口接入业务控制单 元, 如前述的 TISPAN中, E2接口为 Ut参考点, 可以采用基于超文本传 输协议 (HTTP)的 XCAP协议来实现。 可见在被叫侧配置如图 10所描述的 系统极大的扩展了临时计费通知业务的适应范围。
如图 11所示,在步棘(1 )中主叫用户发起呼叫,主叫侧网络将 INVITE 消息路由到被叫网络的呼叫会话控制单元; 被叫网络的呼叫会话控制单元 根据业务触发规则, 如果被叫用户签约了临时 AoC业务,将 INVITE消息 路由到 AoC业务控制单元;
在步骤( 2 ) 中 AoC业务控制单元将 SIP INVITE消息转发到呼叫会 话控制单元;
在所述步骤(2 ) 中 AoC业务控制单元可以在 SIP INVITE消息中加 入当前签约信息, 用于被叫用户选择是否临时激活 AoC业务。 为此, 需 要扩展 SIP头域示例如下:
PAoC-Header = "P-AoC-Ind" HCOLON P-AoC-para *
(COMMA P-AoC-para)
P-AoC-para = P-AoC-S I P-AoC-D I P-AoC-E I P-AoC-All P-AoC-S = "AoC-S"EQUAL P-AoC-value
P-AoC-D = "AoC-D"EQUAL P-AoC-value
P-AoC-E = "AoC-E"EQUAL P-AoC-value
P-AoC-All = "AoC-All"EQUAL P-AoC-value
P-AoC-value = "Actived" I "Inactived" 如: P-AoC-Ind: AoC-S = Actived, AoC-D = Inactived, Aoc-E = Inactived表示 AoC-S业务默认激活, AoC-D和 AoC-E默认去激活;
P-AoC-Ind: AoC-All = Inactived表示所有 AoC业务去激活;
AoC业务控制单元也可以不提供上述信息。
在步驟(3 ) 中业务控制单元转发 INVITE消息到呼叫会话控制单元; 在步骤(4 )呼叫会话控制单元转发 INVITE消息到被叫终端; 在步骤(5 ) 中主叫和被叫进行会话协商操作, 比如媒体协商, 资源 预留; ■
在步驟(6 ) 、 (7 ) 、 (8 ) 、 (9 )与 (10 ) 中被叫终端振铃, 向主 叫送回铃音, 且被叫终端在振铃的同时可以根据 P-AoC- value值来指示被 叫用户是否是 AoC临时业务以及其默认值, 用于提示被叫用户选择激活 或去激活 AoC业务; 也可以通过在被叫终端设置, 来提示被叫用户选择 激活或者去激活 AoC业务;
在步驟(11 ) 中被叫用户选择此次呼叫是否需要激活 AoC业务, 并 接受该呼叫; 被叫终端提供操作界面用于被叫用户选择激活 AoC业务; 操作界面可以是菜单方式, 命令行方式, 图形对话框方式等;
在步骤(12 ) 中被叫终端向呼叫会话控制单元发送 200 OK消息, 消 息中携带被叫用户激活选项, 其 SIP头域扩展可以类似步骤 2或使用相同 的 SIP头域。
PAoC-Header = "P-AoC-Ind" HCOLON P-AoC-para * (COMMA
P-AoC-para)
P-AoC-para = P-AoC-S I P-AoC-D I P-AoC-E I P-AoC-All P-AoC-S = "AoC-S"EQUAL P-AoC-value
P-AoC-D = "AoC-D"EQUAL P-AoC-value
P-AoC-E = "AoC-E"EQUAL P-AoC-value
P-AoC-All = "AoC-All"EQUAL P-AoC-value
P-AoC-value = "Actived"/ "Inactived"
如: P-AoC-Ind: AoC-S = Actived, AoC-D = Inactived, Aoc-E = Inactived表示激活 AoC-S业务, 去激活 AoC-D和 AoC-E业务;
P-AoC-Ind: AoC-All = actived表示激活所有 AoC业务。
被叫终端也可以使用 subscription头域, 来携带被叫用户激活选项; 被叫终端还可以在其它消息中, 如 INFO, UPDATE及其它响应消息中, 携带上述 SIP头域, 在通话建立前激活 AoC业务; 被叫终端也可以在通 话建立 , 通过其它消息, 如 re-Invite消息, 响应消息, 携带上述 SIP头 域扩展, 激活 AoC业务。
在( 13 ) 中呼叫会话控制单元向 200 OK消息路由到业务控制单元; 在(14) 中业务控制单元根据 200 OK消息中的激活选项, 以及被叫用户 临时 AoC业务的订阅选项, 确定对于此次呼叫, 是否激活 AoC业务; 如 果激活 AoC业务, 业务控制单元需要从计费系统获得本次呼叫的计费信 息。 业务控制单元与计费系统的接口同现有技术;
在(15)与 (16) 中业务控制单元将此次呼叫的费率等计费信息, 通 过 MESSAGE消息,发送给被叫终端,业务控制单元也可以通过其它消息, 例如 INFO, ACK, 来响应消息来发送计费信息;
在(17) 中被叫终端向被叫用户显示计费信息, 实现 AoC-S业务; 在(18)与(19)中被叫终端向业务控制单元发送 MESSAGE消息的 200OK消息;
在(20) 与 (21) 中业务控制单元向主叫用户发送 200OK消息, 消 息中可以继续携带 AoC激活选项, 也可以不携带, 完成呼叫接续, 呼叫 建立, 且(20)与 (21)也可以在所述(15)之前进行;
在(22) 中会话建立; 在(23)呼叫过程中, 在呼叫记录发生改变的 情况下, 业务控制单元从计费系统获得更新后的计费信息;
在 (24) 与 (25) 中业务控制单元将计费信息通过 MESSAGE消息, 发送给被叫终端, 业务控制单元也可以通过其它消息, 如 INFO, 来响应 消息来发送计费信息;
在(26) 中被叫终端向被叫用户显示计费信息, 实现 AoC-D业务; 在(27)与(28)中被叫终端向业务控制单元发送 MESSAGE消息的 200OK消息。
正如图 12所示的, 主叫释放呼叫情况下, AoC-E业务实现流程如下: 在( 1 ) 中主叫释放呼叫, 主叫侧网络将 BYE消息路由到被叫网络的 呼叫会话控制单元;
在 (2) 中呼叫会话控制单元将 BYE消息路由到业务控制单元; 在 (3) 中业务控制单元从计费系统获得本次呼叫的计费信息; 在( 4 )与( 5 )中业务控制单元将此次呼叫的计费信息,通过 MESSAGE 消息, 发送给被叫终端, 业务控制单元也可以通过其它消息, 如 INFO' BYE, 来响应消息来发送计费信息;
在(6) 中被叫终端向被叫用户显示计费信息, 实现 AoC-E业务; 在(7)与 (8) 中被叫终端向业务控制单元发送 MESSAGE 消息的
200OK消息;
在(9)与 (10) 中业务控制单元向被叫用户发送 BYE消息, (9) 与 (10)·也可以在所述(4)之前进行;
在(11)、 (12) 、 (13)与 (14)中被叫终端向主叫侧网络发送 200
OK消息, 完成呼叫的释放;
在图 12中被叫释放呼叫情况下, AoC-E业务实现流程如下: 在( 1 ) 中主叫释放呼叫, 主叫侧网络将 BYE消息路由到被叫网络的 呼叫会话控制单元;
在(2) 中呼叫会话控制单元将 BYE消息路由到业务控制单元; 在(3) 中业务控制单元从计费系统获得本次呼叫的计费信息; 在( 4 )与( 5 )中业务控制单元将此次呼叫的计费信息,通过 MESSAGE 消息, 发送给被叫终端, 业务控制单元也可以通过其它消息, 如 INFO,
BYE, 响应消息来发送计费信息;
在(6) 中被叫终端向被叫用户显示计费信息, 实现 AoC-E业务; 在(7)与 (8) 中被叫终端向业务控制单元发送 MESSAGE 消息的
200OK消息;
在(9)与(10)中业务控制单元向被叫用户发送 BYE消息, 所述(9) 与 (10)也可以在所述(4)之前进行;
在(11) (12) (13)与(14)中被叫终端向主叫侧网络发送 200OK 消息, 完成呼叫的释放。
如图 13所示的, 该实施例包括一个完整的被叫用户临时触发 AoC业 务的实现流程,具体的描述了被叫用户在呼叫建立期间通过 SUBSCRIBER 来激活 AoC业务的实现流程, 具体实现流程为:
在( 1 ) 中主叫用户发起呼叫, 主叫侧网络将 INVITE消息路由到被 叫网络的呼叫会话控制单元, 并且被叫网络的呼叫会话控制单元根据业务 触发规则, 如果被叫用户签约了临时 AoC业务, 将 INVITE消息路由到 AoC业务控制单元;
在( 2 ) 中 AoC业务控制单元将 SIP INVITE消息转发到呼叫会话控 制单元,其 AoC业务控制单元可以在 SIP INVITE消息中加入 AoC查询标 志, 表示需要被叫用户来选择是否临时触发 AoC业务, AoC业务控制单 元还可以检查被叫用户订阅临时 AoC业务的选项, 是默认激活或者不激 活, 将该信息加入 SIP INVITE消息, 用于通知被叫终端。 其 SIP头域扩 展同图 11中所述(2 ) 的扩展;
在( 3 )中业务控制单元转发 INVITE消息到呼叫会话控制单元; ( 4 ) 呼叫会话控制单元转发 INVITE消息到被叫终端;
( 5 )主叫和被叫进行会话协商操作, 比如媒体协商, 资源预留等操 作;
在 (6 )与 (7)中 被叫终端振铃, 向主叫送回铃音, 且被叫终端在振 铃的同时可以根据 P-AoC-value值来指示被叫用户是否是 AoC临时业务以 及其默认值, 用于提示被叫用户选择激活或去激活 AoC业务, 被叫用户 选择此次呼叫是否需要激活 AoC业务, 被叫终端提供操作界面用于被叫 用户选择激活 AoC业务, 操作界面可以是菜单方式, 命令行方式, 图形 对话框方式等; 或者被叫终端通过呼叫会话控制单元向业务控制单元发送 SUBSCRIBER消息, 用于激活或者去激活 AoC业务;
为了在 SUBSCRIBER消息中指示激活或者去激活 AoC业务, 在 SIP 消息中扩展一个表示 "激活 AoC业务,,的订阅请求的事件包, 例如命名为 aoc,通过 Event头域传递,在 SIP SUBSCRIBE消息中有如下内容为 "Event aoc",也可以在 SIP消息中分别扩展"激活 AoC-S", "激活 AoC-D"和"激活 AoC-E,,的事件包, 来分别订阅 AoC-S, AoC-D, AoC-E业务; 并通过 SUBSCRIBER消息中的 Expired设置为 0, 来取消 AoC业务的激活操作, 或者另扩一个事件包, 来标识临时取消 AoC业务;
在( 6 )与( 7 )的 SUBSCRIBER消息中,可以携带此次会话的 DialogID, 或者主被叫相关信息, 用于将 SUBSCRIBER消息和此次会话关联起来, 激活 /去激活该会话的 AoC业务; 也可以不携带 DiaglogID或者主被叫相 关信息, 表示该激活 /去激活操作和当前存在的所有呼叫相关, 激活 /去激 活该被叫终端所有呼叫的 AoC业务; 上述 xml描迷中, 也可以增加对 AoC-S, AoC-D, AoC-E的分別描述, 用于分别激活 AoC-S, AoC-D和 AoC-E业务;
在( 8 ) 与 ( 9 ) 中业务控制单元向被叫终端发送 SUBSCRIBER消息 的 200 OK消息;
在(10 ) 中业务控制单元根据用户终端的 SUBSCRIBER操作, 确定 对于此次呼叫, 是否激活 AoC业务, 若激活 AoC业务, 业务控制单元需 要从计费系统获得本次呼叫的计费信息。 业务控制单元与计费系统的接口 同现有技术;
在(11)与 (12) 中业务控制单元将此次呼叫的费率等计费信息, 通 过 NOTIFY消息, 发送给被叫终端, 业务控制单元也可以通过其它消息, 如 MESSAGE, INFO, 来响应消息来发送计费信息; 其中, NOTIFY消息 可以和 MESSAGE—样,使用文本方式来传递计费信息, 也可以扩展一个 MIME类型, 来传递计费信息;
在(13) 中被叫终端向被叫用户显示计费信息, 实现 AoC-S业务; 在 (14) 与 (15) 中被叫终端向业务控制单元发送 NOTIFY消息的
200 OK消息;
在(16) 、 (17) 、 (18) 、 ( 19)与 (20) 中被叫用户接受此次呼 叫, 向主叫发送 200 OK消息;
在(21) 中会话建立; 在(22)呼叫过程中, 在呼叫记录发生改变的 情况下, 业务控制单元从计费系统获得更新后的计费信息;
在(23)与 (24)中业务控制单元将计费信息通过 NOTIFY消息, 发 送给被叫终端,业务控制单元也可以通过其它消息,如 MESSAGE, INFO, 响应消息来发送计费信息; (25)被叫终端向被叫用户显示计费信息, 实 现 AoC-D业务;
在 (26) 与 (27) 中被叫终端向业务控制单元发送 NOTIFY消息的
200OK消息; 在(28) 中呼叫释放, 包括主叫释放和被叫舞放两种情况; 在 (29) 中业务控制单元从计费系统获得本次呼叫的计费信息;
在(30)与 (31) 中业务控制单元将计费信息通过 NOTIFY消息, 发 送给被叫终端,业务控制单元也可以通过其它消息,如 MESSAGE, INFO, BYE, 响应消息来发送计费信息;
在(32) 中被叫终端向被叫用户显示计费信息, 实现 AoC-E业务; 在(33)与 (34)被叫终端向业务控制单元发送 NOTIFY消息的 200 ◦K消息。
如图 14所示的,描述被叫用户在呼叫建立后通过 SIJBSCRIBER来激 活 AoC业务的实现流程, 具体流程为:
在( 1 )中主叫用户发起呼叫, 主叫侧网络将 INVITE消息路由到被叫 网络的呼叫会话控制单元且被叫网络的呼叫会话控制单元根据业务触发 规则, 如果被叫用户签约了临时 AoC业务, 将 INVITE消息路由到 AoC 业务控制单元;
在(2 ) 中 AoC业务控制单元将 SIP INVITE消息转发到呼叫会话控 制单元,其 AoC业务控制单元可以在 SIP INVITE消息中加入 AoC查询标 志, 表示需要被叫用户来选择是否临时触发 AoC业务, AoC业务控制单 元还可以检查被叫用户订阅临时 AoC 业务的选项, 是默认激活或者不激 活, 将该信息加入 SIP INVITE消息, 用于通知被叫终端。 其 SIP头域扩 展同图 11中 (2 ) 的扩展;
在(3 ) 中业务控制单元转发 INVITE消息到呼叫会话控制单元; 在( 4 ) 中呼叫会话控制单元转发 INVITE消息到被叫终端; 在(5 ) 中主叫和被叫进行会话协商操作, 比如媒体协商, 资源预留 等操作;
在(6 ) 中被叫终端振铃, 向主叫送回铃音, 被叫选择接受此次呼叫; 在(7 )、 (8 )、 (9 )与( 10 )中被叫用户向主叫侧网络发送 200 OK 消息;
在( 11 ) 中会话建立;
在(12 )与 (13 ) 中 被叫用户通过被叫终端的操作界面选择激活或 者去激活 AoC业务, 其操作界面可以是菜单方式, 命令行方式, 图形对 话框方式等; 被叫终端通过呼叫会话控制单元向业务控制单元发送 SUBSCRIBER消息,用于激活或者去激活 AoC业务,为了在 SUBSCRIBER 消息中指示激活或者去激活 AoC业务, 在 SIP消息中扩展一个表示 "激活 AoC业务"的订阅请求的事件包, 例如命名为 aoc, 通过 Event头域传递, 在 SIP SUBSCRIBE消息中有如下内容: "Event: aoc", 通过 SUBSCRIBER 消息中的 Expired设置为 0, 来取消 AoC业务的激活操作, 也可以另扩一 个事件包, 来标识临时取消 AoC业务, 且在 SUBSCRIBER消息中, 可以 携带此次会话的 Dialog ID, 或者主被叫相关信息, 用于将 SUBSCRIBER 消息和此次会话关联起来, 激活该呼叫的 AoC 业务, 也可以不携带 DiaglogID或者主被叫相关信息,表示该订阅和当前存在的所有呼叫相关, 激活该被叫终端所有呼叫的 AoC业务;
在 ( 14 )与 ( 15 ) 中业务控制单元向被叫终端发送 SUBSCRIBER消 息的 200 OK消息;
在 (16 ) 中业务控制单元根据用户终端的 SUBSCRIBER操作, 确定 对于此次呼叫, 是否激活 AoC业务, 若激活 AoC业务, 业务控制单元需 要从计費系统获得本次呼叫的计费信息。 业务控制单元与计费系统的接口 同现有技术;
在(17)与 (18) 中业务控制单元将此次呼叫的费率等计费信息, 通 过 NOTIFY消息, 发送给被叫终端, 业务控制单元也可以通过其它消息, 如 MESSAGE, INFO, 响应消息来发送计费信息, 而且 NOTIFY消息可 以和 MESSAGE—样, 使用文本方式来传递计费信息, 也可以扩展一个 MIME类型, 来传递计费信息;
在(19) 中被叫终端向被叫用户显示计费信息, 实现 AoC-S业务; 在(20)与 (21) 中被叫终端向业务控制单元发送 NOTIFY消息的
200OK消息;
在(22)呼叫过程中, 在呼叫记录发生改变的情况下, 业务控制单元 从计费系统获得更新后的计费信息;
在(23)与(24)中业务控制单元将计费信息通过 NOTIFY消息, 发 送给被叫终端,业务控制单元也可以通过其它消息,如 MESSAGE, INPO, 响应消息来发送计费信息;
在(25) 中被叫终端向被叫用户显示计费信息, 实现 AoC-D业务; 在 (26) 与 (27) 中被叫终端向业务控制单元发送 NOTIFY消息的 200OK消息; 在(28)呼叫释放中, 包括主叫释放和被叫释放两种情况; 在(29) 中业务控制单元从计费系统获得本次呼叫的计费信息;
在(.30)与(31)中业务控制单元将计费信息通过 NOTIFY消息, 发 送给被叫终端,业务控制单元也可以通过其它消息,如 MESSAGE, INFO, BYE, 响应消息来发送计费信息;
在 (32) 中被叫终端向被叫用户显示计费信息, 实现 AoC-E业务; 在 (33) 与 (34) 中被叫终端向业务控制单元发送 NOTIFY 消息的
200OK消息。
在图 15 中描述了被叫用户在呼叫建立期间通过超文本传输协议 (HTTP)来激活或去激活 AoC业务的实现流程, 其具体实现流程为: 在 ( 1 )中主叫用户发起呼叫,主叫侧网络将 INVITE消息路由到被叫网络的 呼叫会话控制单元, 且被叫网络的呼叫会话控制单元根据业务触发规则, 若被叫用户签约了临时 AoC业务, 则将 INVITE消息路由到 AoC业务控 制单元; N2007/000746
- 13 - 在(2 ) 中 AoC业务控制单元将 SIP INVITE消息转发到呼叫会话控 制单元,其 AoC业务控制单元可以在 SIP INVITE消息中加入 AoC查询标 志, 表示需要被叫用户来选择是否临时触发 AoC业务, AoC业务控制单 元还可以检查被叫用户订阅临时 AoC业务的选项, 是默认激活或者不激 活, 将该信息加入 SIP INVITE消息, 用于通知被叫终端。 其 SIP头域扩 展同图 1 1中 (2 ) 的扩展;
在(3 ) 中业务控制单元转发 INVITE消息到呼叫会话控制单元; 在(4 ) 中呼叫会话控制单元转发 INVITE消息到被叫终端; 在 (5 ) 中主叫和被叫进行会话协商操作, 比如媒体协商, 资源预留 等操作;
在(6 ) 中 被叫终端振铃, 向主叫送回铃音, 且被叫终端在振铃的同 时可以才艮据 P-AoC-value值来指示被叫用户是否是 AoC临时业务以及其默 认值, 用于提示被叫用户选择激活或去激活 AoC业务; 或者被叫用户选 择此次呼叫是否需要激活 AoC 业务, 被叫终端提供操作界面用于被叫用 户选择激活 AoC业务, 其操作界面可以是菜单方式, 命令行方式, 图形 对话框方式等;被叫终端通过 HTTP协议到业务控制单元激活 /去激活 AoC 业务, 该操作也可以在呼叫建立后再进行。 如采用 TISPAN使用 Ut参考 点来定义终端到业务控制单元之间的接口, 采用 XCAP协议, 通过 XML 描述来实现业务操作; XCAP协议是基于 HTTP协议的一个协议。
HTTP、 XCAP, XML之间的关系: HTTP协议承载 XCAP协议, XCAP 协议承载 XML描述, XML描述中包含了实际的业务激活操作。
为了实现 AoC业务的激活和去激活操作, 在(6 ) 中还可以通过一个 XML文本来实现, 其 XML的具体实施例如下:
<?xml version-" 1.0" encoding="UTF-8"?>
<simservs
xmlns=''um:org:etsi:tispan:ngn:params:xml:ns:simservsn
xmlns:cp="urn:ietf:params:xml:ns:common-policy"
xmlns :ocp="urn:oma:params :xml: ns: common-policy ">
<tempory advice of charge default="inactive">
<operation ="active">
< dialog ιά="31381819328923"> < cp identity— 'caUingparty@example. com">
</simservs>
并且在该可以通过 XML描述在设置激活,或者去激活临时 AoC业务, 在 XML描述中,还可以携带此次会话的 DialogID,或者主被叫相关信息, 用于将该激活 /去激活操作和此次会话关联起来,激活该呼叫的 AoC业务; 也可以不携带 DiaglogID或者主被叫相关信息, 表示该订阅和当前存在的 所有呼叫相关, 激活该被叫终端所有呼叫的 AoC业务;
在(7)中业务控制单元向被叫终端发送临时 AoC业务激活 /去激活操 作的响应消息
在 (8) 中业务控制单元根据用户终端的激活 /去激活操作, 确定对于 此次呼叫, 是否激活 AoC业务, 若激活 AoC业务, 业务控制单元需要从 计费系统获得本次呼叫的计费信息, 其业务控制单元与计费系统的接口同 现有技术;
在 (9) 与 (10) 中业务控制单元将此次呼叫的费率等计费信息, 通 过 MESSAGE消息,发送给被叫终端,业务控制单元也可以通过其它消息, 如 INFO, 响应消息来发送计费信息;
在 (11) 中被叫终端向被叫用户显示计费信息, 实现 AoC-S业务; 在(12)与 (13)中被叫终端向业务控制单元发送 MESSAGE消息的
200OK消息;
在 (14) 、 (15) 、 (16) 、 (17)与 (18) 中被叫用户接受此次呼 叫, 向主叫发送 200 OK消息;
在(19) 中会话建立; 在(20) 的呼叫过程中, 在呼叫记录发生改变 的情况下, 业务控制单元从计费系统获得更新后的计费信息;
在 (21)与 (22) 中业务控制单元将计费信息通过 MESSAGE消息, 发送给被叫终端, 业务控制单元也可以通过其它消息, 如 INFO, 响应消 息来发送计费信息;
在 (23) 中被叫终端向被叫用户显示计费信息, 实现 AoC-D业务; 在(24)与 (25)中被叫终端向业务控制单元发送 MESSAGE消息的 200 OK消息;
在 (26) 中呼叫释放, 包括主叫释放和被叫释放两种情况;
在(27) 中业务控制单元从计费系统获得本次呼叫的计费信息; 在 (28) 与 (29) 中业务控制单元将计费信息通过 MESSAGE消息, 发送给被叫终端, 业务控制单元也可以通过其它消息, 如 INK), BYE, 响应消息来发送计费信息;
在(30 ) 中被叫终端向被叫用户显示计费信息, 实现 AoC-E业务; 在(31 )与 (32 )中被叫终端向业务控制单元发送 MESSAGE消息的
200 OK消息。 可见, 采用本发明所提供的技术方案, 大大的满足了用户 的需求。
综上所述, 釆用本发明所提供的技术方案, 更完整的实现了临时计费 通知业务, 用户在作为被叫时, 可以根据终端漫游, 通话重要性等其它各 种情况, 选择激活或者去激活计费通知业务, 极大的扩展了临时计费通知 业务的适应范围, 大大满足了用户的需求。
本发明所提供的是一种在分組域中实现计费通知的方法及系统,极大 的扩展了临时计费通知业务的适应范围, 大大满足了用户的需求。
应当理解的是, 上述针对实施例的描述并不能理解为本发明的保护范 围的限制 , 本发明的保护范围应以所附权利要求为准。

Claims

权 利 要 求
1、 一种在分組域中实现计费通知的方法, 其特征在于, 该方法包括: 被叫侧的呼叫会话控制单元收到呼叫请求后, 根据被叫用户签约数 据, 将所述呼叫请求路由到所述业务控制单元;
所述业务控制单元接收被叫用户终端的激活 /去激活计费通知业务请 求, 并根据用户终端激活 /去激活操作, 确定是否激活计费通知业务;
在激活计费通知业务时, 所述业务控制单元向被叫用户终端发送计费 信息。
2、 根据权利要求 1所述的方法, 其特征在于, 进一步包括: 将所述呼叫请求路由到所述业务控制单元之后, 在所述呼叫请求中的 会话发起协议消息上加入计费通知业务当前签约信息, 并发送给被叫用户 终端;
所述被叫用户终端根据该签约信息确定是否选择激活计费通知业务。
3、 根据权利要求 1所述的方法, 其特征在于, 所述用户终端激活 /去 激活操作中,被叫终端通过会话发起协议消息或超文本传输协议消息进行 激活 /去激活计费通知业务。
4、 根据权利要求 1所述的方法, 其特征在于, 所述被叫终端的激活 / 去激活计费通知业务在通话建立过程中或通话建立后进行。
5、 根据权利要求 3或 4所述的方法, 其特征在于,
通话建立过程中,所述进行激活 /去激活计费通知业务的消息包括: 与 呼叫相关的 INFO, UPDATE, 或响应消息。
6、 根据权利要求 3或 4所述的方法, 其特征在于, 所述会话发起协 议消息包括与呼叫无关的 SUBSCRIBER消息。
7、 根据权利要求 3或 4所述的方法, 其特征在于, 所述被叫终端激 活 /去激活指定对话或当前所有对话; 或者
分别激活 /去激活 AoC-S, AoC-D, AoC-E; 或者
同时激活 /去激活所有计费通知业务。
8、 根据权利要求 1 所述的方法, 其特征在于, 所述向被叫用户终端 发送计费信息的步骤中, 所述业务控制单元下述消息向被叫终端发送计费 信息: MESSAGE, INFO, NOTIFY, BYE, 响应消息或 ACK。
9、 一种在分组 i¾中实现计费通知的系统, 其包括业务控制单元、 呼 叫会话控制单元与会话发起协议终端, 其特征在于,
所述呼叫会话控制单元, 用于为接入分组核心网的会话发起协议终端 用户提供呼叫控制与路由接续功能, 并将呼叫触发至所述业务控制单元; 所述业务控制单元, 用于为接入分组核心网的会话发起用户提供业务 控制功能, 其上设置有被叫临时计费通知业务处理模块, 在所服务用户作 被叫的情况下, 执行被叫临时计费通知业务操作。
10、 ^居权利要求 9所述的系统, 其特征在于, 所述业务控制单元设 置才艮据所处理业务不同设置多个, 用于分别处理对应的业务。
11、 一种在分組域中实现计费通知的装置, 用于实现业务控制功能, 其特征在于, 其上设置有被叫临时计费通知业务逻辑处理模块, 用于在所 服务用户作被叫的情况下, 执行被叫临时计费通知业务的业务逻辑。
PCT/CN2007/000746 2006-03-08 2007-03-08 Procédé, dispositif et système de réalisation de notification de paiement dans le domaine des paquets WO2007101409A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610034258A CN100589513C (zh) 2006-03-08 2006-03-08 一种在分组域中实现计费通知的方法
CN200610034258.9 2006-03-08

Publications (1)

Publication Number Publication Date
WO2007101409A1 true WO2007101409A1 (fr) 2007-09-13

Family

ID=38474610

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/000746 WO2007101409A1 (fr) 2006-03-08 2007-03-08 Procédé, dispositif et système de réalisation de notification de paiement dans le domaine des paquets

Country Status (2)

Country Link
CN (1) CN100589513C (zh)
WO (1) WO2007101409A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013091687A1 (en) * 2011-12-21 2013-06-27 Nokia Siemens Networks Oy Charging mechanism for communication network

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106034033A (zh) * 2015-03-20 2016-10-19 中兴通讯股份有限公司 一种cats计费方法、计费消息请求发送方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1267432A (zh) * 1997-06-20 2000-09-20 艾利森电话股份有限公司 提供移动无线电话呼叫计费通知参数的方法和设备
US6529726B1 (en) * 1998-12-24 2003-03-04 At&T Wireless Services, Inc. Method of notifying a wireless subscriber as to call payment responsibilities
CN1633147A (zh) * 2003-12-22 2005-06-29 华为技术有限公司 一种主被叫付费的智能业务实现方法
CN1642091A (zh) * 2004-01-09 2005-07-20 华为技术有限公司 个人虚拟号码业务的认证计费方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1225862C (zh) * 2002-08-09 2005-11-02 华为技术有限公司 基于初始会话协议的网络终端实现计费通知的方法
GB0311004D0 (en) * 2003-05-13 2003-06-18 Nokia Corp Charging in communication networks

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1267432A (zh) * 1997-06-20 2000-09-20 艾利森电话股份有限公司 提供移动无线电话呼叫计费通知参数的方法和设备
US6529726B1 (en) * 1998-12-24 2003-03-04 At&T Wireless Services, Inc. Method of notifying a wireless subscriber as to call payment responsibilities
CN1633147A (zh) * 2003-12-22 2005-06-29 华为技术有限公司 一种主被叫付费的智能业务实现方法
CN1642091A (zh) * 2004-01-09 2005-07-20 华为技术有限公司 个人虚拟号码业务的认证计费方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013091687A1 (en) * 2011-12-21 2013-06-27 Nokia Siemens Networks Oy Charging mechanism for communication network
US9820129B2 (en) 2011-12-21 2017-11-14 Nokia Solutions And Networks Oy Charging mechanism for communication network

Also Published As

Publication number Publication date
CN101035176A (zh) 2007-09-12
CN100589513C (zh) 2010-02-10

Similar Documents

Publication Publication Date Title
EP1829306B1 (en) Method and apparatus for providing emergency calls to a disabled endpoint device
US7738638B1 (en) Voice over internet protocol call recording
US7986775B2 (en) Method for realizing ring back tone in communication system
CN101217601B (zh) 盲转业务方法和装置
CN101217598B (zh) 遇忙回叫方法及系统
WO2008086690A1 (fr) Procédé de services de déviation de requête et dispositif correspondant
US20080273671A1 (en) Method, system and application server for preventing crosstalk of color ring back tone
WO2014101436A1 (zh) 一号双机关联呼叫方法、装置和应用服务器
WO2009152699A1 (zh) Sip终端及其上报状态的方法、系统以及sip服务器
WO2007098706A1 (fr) Procédé permettant de transmettre des données de service et terminal de paquets utilisé dans ce procédé
US20070288600A1 (en) Telecommunications system and method of initiating file transfers from voice endpoints
EP1959608A1 (en) A method, a application server and a system for implementing the third party control service
US8897436B2 (en) Method and apparatus for providing emergency ring tones for urgent calls
WO2011153752A1 (zh) 在ctd业务中实现呼叫转接的方法、系统及应用服务器
CN111431866B (zh) 一种基于语音通话的业务权限控制方法及系统
WO2007093116A1 (fr) Procédé et système de fourniture de service de simulation et entité adaptative de signalisation d&#39;accès
WO2013082894A1 (zh) 一种话务员呼叫转接的方法和总机业务应用服务器
CN101365016A (zh) 实现回叫业务的方法及装置
CN1968317B (zh) 一种在分组域中实现呼叫等待的方法
WO2007101409A1 (fr) Procédé, dispositif et système de réalisation de notification de paiement dans le domaine des paquets
WO2011153753A1 (zh) 在ctd业务中实现呼叫等待的方法、系统及应用服务器
US8737271B2 (en) Graphical user-interface for terminals with visual call progress indicator
CN101286951B (zh) 一种会话抢占方法
WO2012089055A1 (zh) 在ip多媒体子系统网络实现被叫付费业务的方法和装置
KR100640289B1 (ko) 통화 서비스를 제공 받기 위한 ip 단말기의 동작 방법및 그 ip 단말기

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07720351

Country of ref document: EP

Kind code of ref document: A1