KR101093043B1 - Method and system for processing charge in multi-pdp environment - Google Patents

Abstract

Disclosed are a billing processing method and a system thereof in a multi-PDP environment. According to one or more embodiments of the present invention, a method for processing a charge in a multi-PDP environment may include: receiving an account start request message for a PDP; Determining whether the received account start request message is for a primary PDP or a secondary PDP; And if the account start request message is an account start request message for the primary PDP, charging processing for the PDP is performed; and if the account start request message is an account start request message for the secondary PDP, the account start request. And causing the charging process performed by the message to be dropped.

Multi PDP, Billing, Primary PDP, Secondary PDP

Description

Billing processing method and system therefor in multi-PDP environment {METHOD AND SYSTEM FOR PROCESSING CHARGE IN MULTI-PDP ENVIRONMENT}

The present invention relates to billing processing in a multi-PDP environment. More particularly, the present invention relates to a billing omission for a main PDP that may be generated by a secondary PDP request during the billing process by the main PDP in a multi-PDP (packet data protocol) environment. A billing processing method and a system thereof in a multi-PDP environment that can be prevented.

Wideband Code Division Multiple Access (WCDMA) uses a wider bandwidth than the CDMA scheme that uses a pseudo noise code unique to a subscriber's communication channel.WCDMA is strong in frequency selective fading because it uses a wideband bandwidth. Since this increases the processing gain, there is an advantage that the amount of interference is reduced and the capacity is increased.

In addition, since multipath can be resolved using a RAKE receiver, it is possible to overcome the propagation delay in the indoor environment even in the case of a micro cell, and has an excellent bandwidth efficiency per 1 [MHz] bandwidth, which is advantageous in terms of subscriber capacity and processing gain. The third generation communication system that has been adopted in Korea, Japan, and Europe in that the cost of implementation is reduced by increasing the capacity of the power amplifier and the power consumption and size of the terminal can be reduced by reducing the size of the power amplifier. to be.

Such WCDMA technology guarantees high speed transmission of packet data, and General Packet Radio Service (GPRS) defines a network structure and a service for providing a packet data service.

The mobile station (MS) may receive a packet data service from a WCDMA GPRS network through a PDP context.

On the other hand, WCDMA GPRS network provides a variety of multiple packet data protocol context (Multi PDP context) environment, the multi-PDP context environment is to watch a specific video during the Internet navigation (navigation), or IMS call in the case of IP Multimedia Subsystem (IMS) For example, the separation of the processing signal (SIP signal) and the actual traffic (voice, data, messages, etc.) into a separate PDP context.

In this multi-PDP context environment, the PDP context types share a separate APN (primary access point number) and a primary PDP context for allocating a new IP address, and an IP address assigned to the APN and subscriber. It may be classified as a secondary PDP context.

Packets corresponding to each PDP context are the Serving GPRS Support Node (SGSN) and the Gateway GPRS Support (GGSN) using the subscriber's number (International Mobile Subscriber Identity (IMSI)) and Network Layer Service Access Point Identifier (NSAPI) as keys. Node) is collected.

In the multi-PDP environment, the billing processing system receives an account start request of the PDP for the PDP context requested by the subscriber station from the GGSN, and relays an account start request message for this to the billing server. And a charging server that receives the start request message and processes the charging for the PDP.

When the relay server receives the account start request of the primary PDP or the account start request of the secondary PDP from the GGSN, it relays the account start request message of the PDP to the charging server regardless of the primary PDP or the secondary PDP. Based on the received account start request message, charging processing of the packet service for the corresponding subscriber station is performed.

However, in the charging process in the multi-PDP environment according to the prior art, the charging server is not only the account start request message of the primary PDP from the relay server but also the secondary PDP when the secondary PDP context is performed by the subscriber station during the main PDP context. Since the account start request message of the PDP also receives the account start request message of the secondary PDP may be a situation that should be discarded the charges performed by the account start request message of the primary PDP.

That is, when the accounting request message of the secondary PDP is received, the charging server recognizes the accounting processing performed by the account starting request message of the main PDP as an error and discards the amount charged by the main PDP. The processing may be performed.

This can result in missing charges processed from receiving an account start request message from the primary PDP to an account start request message from the secondary PDP, which can reduce the profitability that can be incurred by the service. There is a problem.

Accordingly, there is a need for a system or method that can prevent leakage of billing that may be caused by a secondary PDP context.

An object according to an embodiment of the present invention, which was devised to solve the above problems, is to charge in a multi-PDP environment that can prevent leakage of charges generated by the use of the main PDP that may be caused by the use of the secondary PDP. It is to provide a processing method and a system thereof.

Furthermore, another object according to an embodiment of the present invention is the complexity and load of the billing server that must determine the main PDP and the secondary PDP by processing the messages generated by the primary PDP and the secondary PDP in the relay server requesting the charging process. The present invention provides a method and system for processing billing in a multi-PDP environment.

In order to achieve the above object, a billing processing method in a multi-PDP environment according to an aspect of the present invention comprises the steps of: receiving an account start request message for a PDP; Determining whether the received account start request message is for a primary PDP or a secondary PDP; And if the account start request message is an account start request message for the primary PDP, charging processing for the PDP is performed; and if the account start request message is an account start request message for the secondary PDP, the account start request. And causing the charging process performed by the message to be dropped.

The determining may include determining whether the account start request message is an account start request message for the primary PDP or an account start request message for the secondary PDP by using an attribute value constituting an account start request message for the PDP. have.

In the billing processing system in a multi-PDP environment according to an aspect of the present invention, the billing processing system in a multi-PDP environment comprising a server for processing an account start request message of the PDP, the server receives the account start request message Determine whether the account start request message is for a primary PDP or a secondary PDP, and if the account start request message is an account start request message for the primary PDP, the billing processing for the PDP is performed. If the account start request message is an account start request message for the secondary PDP, the accounting processing performed by the account start request message may be dropped.

The server may be a relay server that receives the account start request message sent from the GGSN and transmits to the billing server that performs the billing processing, wherein the relay server is an account start request message for the primary PDP When the account start request message is transmitted to the billing server, and if the account start request message is an account start request message for the secondary PDP, it may drop the transmission of the account start request message to the billing server.

 Receiving an account start request message for the PDP; Determining whether the received account start request message is for a primary PDP or a secondary PDP; And if the account start request message is an account start request message for the primary PDP, performs a billing process for the PDP, and if the account start request message is an account start request message for the secondary PDP, the account start request message. Dropping the charging process performed by the.

The determining may include determining whether the account start request message is an account start request message for the primary PDP or an account start request message for the secondary PDP by using an attribute value constituting an account start request message for the PDP. have.

The receiving may receive an account start request message for the PDP from a GGSN, and may receive an account start request message for the PDP transmitted from a GGSN through a relay server.

The billing processing system in a multi-PDP environment according to an aspect of the present invention includes a relay server for receiving an account start request message of the PDP and transmitting it to a billing server that performs billing processing, wherein the relay server starts accounting of the PDP. Receiving the request message, it is determined whether the received account start request message is an account start request message for the primary PDP or an account start request message for the secondary PDP. The account start request message may be transmitted, and in case of an account start request for the secondary PDP, the account start request message may be dropped from the accounting server.

According to another aspect of the present invention, a billing processing system in a multi-PDP environment includes a billing server configured to perform a billing process by receiving an account start request message of a PDP from a relay server, wherein the billing server is received from the relay server. It is determined whether the account start request message is an account start request message for the primary PDP or an account start request message for the secondary PDP, and if the account start request message is for the primary PDP, billing processing is performed, and In the case of an account start request message, a charging processing event performed by the received account start request message may be dropped.

Other objects and features of the present invention in addition to the above objects will be apparent from the description of the embodiments with reference to the accompanying drawings.

Preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In describing the present invention, when it is determined that the detailed description of the related well-known configuration or function may obscure the gist of the present invention, the detailed description thereof will be omitted.

Hereinafter, a charging processing method and a system thereof in a multi-PDP environment according to an embodiment of the present invention will be described in detail with reference to FIGS. 1 to 6.

1 illustrates a billing processing system in a multi-PDP environment according to an embodiment of the present invention.

Referring to FIG. 1, the billing processing system includes a terminal 110, a wireless access network 120, a serving GPRS support node (hereinafter referred to as 'SGSN') 130, a relay server 140, and a gateway GPRS. A gateway GPRS support node (hereinafter referred to as 'GGSN') 150, an authentication server 160, and a charging server 170 are included.

The terminal 110 automatically performs a session establishment procedure and transmits and receives packet data according to a session establishment request from a mobile communication network. The terminal 110 includes a data storage space for transmitting and receiving packet data, using a primary PDP and a secondary PDP. You can request a packet service.

In this case, the terminal may use a wireless application protocol (Wireless Application Protocol), an MIE (Microsoft Internet Explorer) based on HTML using an HTTP protocol, a handheld device transport protocol, and an FTP function. The packet data can be transmitted and received to the mobile communication network.

Radio Access Network (hereinafter referred to as 'RAN') 120 is a Radio Transceiver Subsystem (RTS: Radio Transceiver Subsystem (RTS)) that accommodates the 3rd Generation Partnership Project (3GPP) radio access standard to support the existing WCDMA ( 121) and a radio network controller (RNC) 122.

The RAN 120 receives a communication request signal, a data transmission request signal, and uploading data from the terminal 110 and transmits the received data to the SGSN 130. The RAN 120 receives packet data from the SGSN 130 and transmits the packet data to the terminal 110. Perform the function.

The RTS 121 performs a wireless access termination function with the terminal 110 according to the 3GPP wireless access standard, and transmits and receives voice, video, and data traffic in a WCDMA manner, and a terminal 110 through a transmission and reception antenna. Send and receive information with

In general, the internal subsystem of the RTS 121 is composed of a base-station interconnection subsystem, a base band subsystem, and a radio frequency subsystem. In addition, the RTS 121 is also used under the name 'Node B' in the 3GPP radio access standard.

The RNC 122 manages wired and wireless channels, protocol matching of the terminal 110, protocol matching of a base station, soft handoff processing, protocol matching with a core network, GPRS connection, fault management, system loading ( It is responsible for such functions as Loading).

The SGSN 130 has a function of managing mobility of the terminal 110, a call processing procedure for sending / receiving a call, session management for processing transmission and reception of packet data, and routing processing of packet data for a GPRS service. SGSN 130 is a node that delivers a data packet with the terminal 110 in the service area, and when a data service connection call is received from the terminal 110, a message requesting a PDP context setting (for example, create PDP). context request) to the GGSN 150, and receives a response (eg, create PDP context response) from the GGSN 150 to the message requesting the PDP context settings through the RAN (120) Transfer to the terminal 110.

In this case, the SGSN 130 may determine whether the PDP context setting is successful or a cause of failure by the create PDP context response received from the GGSN 150.

The GGSN 150 is a serving node of an Internet Protocol (IP) -based packet network that provides a high speed packet data service for packet data service of GPRS, and assigns an IP address to the terminal 110 for packet data service. It manages session, manages packet data routing, and provides interface between WCDMA and internet network.

In the present invention, the GGSN 150 receives a message requesting the PDP context setting from the SGSN 130, requests an authentication to the authentication server 160, and responds to the authentication request from the authentication server 160. After receiving the access accept, the response to the message requesting the PDP context setting is transmitted to the SGSN 130.

In addition, when the response to the authentication request is received, the GGSN 150 allocates an IP address to the terminal 110 requesting the data service access call and delivers a response to the message requesting the PDP context setting to the SGSN 130. After that, the relay server 140 transmits an account start request message of the corresponding PDP capable of analyzing and charging the packet volume, and receives a response thereto.

At this time, the GGSN 150 may transmit the account start request message of the secondary PDP to the relay server 140 when the message for requesting setting the secondary PDP context is received after the account start request message of the primary PDP is delivered to the relay server 140. In this case, the account start request message of the PDP transmitted from the GGSN 150 to the relay server 140 may include an attribute value as shown in FIG. 2.

That is, the account start request message may include an account multi-session ID, an account session ID, an accounting ID 3GPP-charging ID, and a frame IP address. And MSISDN, as shown in FIG. 2, the primary PDP and secondary PDP connected to the same call have the same account multi-session ID, frame IP address, and MSISDN, but different account session ID and billing ID. Therefore, it can be seen whether the account start request message or the account start request message received by the relay server 140 or the charging server 170 using this attribute value is for the primary PDP or the secondary PDP, Through this, by dropping the charge processing event performed by the secondary PDP, it is possible to prevent the charge omission that may be caused by the secondary PDP.

As described above, the present invention is to prevent the accounting leak that may be caused by receiving the account start request message for the secondary PDP during the billing processing by the main PDP in the billing server 170, billing for this The leakage prevention will be described by dividing it into 1) the case of processing by the relay server 140 and 2) the case of processing by the charging server 170.

In the case of 1), the relay server 140 receives the account start request message of the PDP received from the GGSN 150, and if the received account start request message is the account start request message of the primary PDP, the account start request of the secondary PDP. If it is determined that the message is an account start request message of the primary PDP, and transmits an account start request message for this to the charging server 170, and if the account start request message is an account start request message of the secondary PDP, to the charging server 170. Drops an account start request message that should be

Here, the account start request message is a message for transferring the account start request message from the relay server 140 to the billing server 170, which is a proxy server, and the message received from the GGSN 150 at the relay server 140 and the billing server ( It is used to distinguish the message delivered to 170), but may be used in the same term, and both messages may include all the attribute values shown in FIG.

That is, when the accounting start request message of the secondary PDP is received, the relay server 140 drops the transmission of the accounting start request message, which is a message for performing the billing processing event in the billing server 170, and thereby, in the billing server 170. The charging processing event by the secondary PDP may be prevented from being performed, and thus, the omission of previously processed charges that may be generated by the charging process of the secondary PDP may be prevented.

Of course, the relay server 140 transmits a response to the account start request message to the GGSN 150.

In this case, the relay server 140 may know whether the account start request message is for the primary PDP or the secondary PDP through the attribute values constituting the account start request message shown in FIG. 2.

When the accounting server 170 receives the account start request message from the relay server 140, the billing server 170 analyzes the packet volume and performs a billing processing event on the terminal 110.

In the case of 2), when the account start request message of the PDP is received from the GGSN 150, the relay server 140 transmits an account start request message to the billing server 170, and the billing server 170 sends the account start request message. Receive a response, and forwards the response to the account start request message to the GGSN 150.

The billing server 170 is a server that analyzes a packet volume and performs billing processing through a fee per packet. When the account start request message is received from the relay server 140, the attribute values constituting the message, for example, FIG. It is determined whether the received message is an account start request message of the primary PDP or an account start request message of the secondary PDP using the attribute values shown in FIG. 2. As a result of the determination, the received account start request message is an account start request message of the primary PDP. If the accounting request message of the secondary PDP by dropping the accounting request event of the secondary PDP, if the accounting request message of the secondary PDP, if the received account start request message is the account start request message of the secondary PDP Do not perform processing functions.

As described above, the billing processing system according to an embodiment of the present invention prevents the billing processing event for the secondary PDP generated by the account start request message of the secondary PDP from being performed, so that the accounting server performs the charging performed by the secondary PDP. It is possible to prevent packet charging omissions that may be caused by processing events.

In addition, when the charging is prevented through the method 1), the relay server determines whether the primary PDP and the secondary PDP are classified and processes the account start request message so that the application level (for example, HTTP URL, video, audio, etc.). It can reduce the complexity and the load of the billing server that needs to perform billing.

FIG. 3 is an operation flowchart of a charging processing method in a multi-PDP environment according to an embodiment of the present invention, and is an operation flowchart of the relay server shown in FIG. 1.

Referring to FIG. 3, the relay server receives an account start request message of a PDP transmitted from a GGSN, and determines whether the received account start request message is an account start request message of a primary PDP or an account start request message of a secondary PDP (S310). , S320).

As a result of the determination in step S320, when the received account start request message is an account start request message of the main PDP, an account start request message of the main PDP is generated and then transmitted to the billing server (S330 and S340).

On the other hand, if it is determined in step S320 that the received account start request message is the account start request message of the secondary PDP, the account start request message for the account start request message of the secondary PDP is dropped (S350).

That is, by dropping the account start request message of the secondary PDP to be transmitted to the charging server, the charging processing event by the secondary PDP is prevented from being performed at the charging server.

The operation of FIG. 3 will be described in detail with reference to FIG. 4.

Referring to FIG. 4, when the SGSN receives a data service call (activate PDP context request) for the primary PDP from the terminal MS, the SGSN transmits a create PDP context request for the primary PDP to the GGSN to set the primary PDP context. Requires.

The GGSN sends the access request to the authentication server by checking the APN configuration information, and in order to manage the data service call of the terminal subscriber from the authentication server, the GGSN includes an access accept including a Filter-ID of the data service management value corresponding to the terminal subscriber. Upon reception, after assigning an IP address to the terminal, it transmits a create PDP context response to SGSN, and SGSN delivers an activate PDP context accept to the terminal. Of course, GGSN delivers create PDP context response (request accepted) if the PDP context is set successfully, and delivers create PDP context response (cause of failure) if it fails (S410).

When the GGSN receives the access accept from the authentication server, the GGSN sends an accounting request message (START) of the main PDP, that is, an accounting request (START), to the relay server to handle the charges incurred by the data service of the terminal assigned the IP address. Receive the accounting response in response.

The relay server generates an accounting request message START for the accounting request START of the main PDP and delivers it to the billing server, and receives an accounting response from the billing server at step S420. .

While providing the data service for the primary PDP through this process, when SGSN receives an activate PDP context request for the secondary PDP from the terminal MS, the SGSN sends a create PDP context request for the secondary PDP to the GGSN. By requesting the secondary PDP context setting, and receives the create PDP context response from the GGSN transfers the activate PDP context accept to the terminal (S430).

In this case, since the GGSN is a data service for the secondary PDP, the terminal receives the data service using the same IP, and thus the authentication process may be omitted.

The GGSN sends an accounting request (START) for the secondary PDP to the relay server and receives an accounting response.

When the relay server receives an account start request message for the secondary PDP from the GGSN, the relay server confirms that the received accounting request (START) is an accounting request (START) for the secondary PDP, and starts the account for the secondary PDP to be delivered to the charging server. By dropping the request message, it is possible to prevent the charging processing event for the secondary PDP from being performed at the charging server, thereby preventing the charging processed by the primary PDP from being missed in advance. The relay server drops the account start request message for the secondary PDP and transfers the accounting response to the accounting request (START) to the GGSN (S440).

In this case, the relay server may determine whether the account start request message received from the GGSN is for the primary PDP or the secondary PDP, which is an example of the attribute values included in the account start request message, for example, shown in FIG. 2. This can be determined using property values such as

As described above, in the charging processing method in the multi-PDP environment according to the embodiment of the present invention shown in FIGS. 3 and 4, by dropping the account start request message for the secondary PDP to be delivered from the relay server to the charging server, It is possible to prevent charge leakage due to the charge processing event of the secondary PDP that may occur in the charge server, and reduce the complexity and load of the charge server by reducing the processing in the charge server. That is, by reducing the load of the charging server that needs to perform application level charging (for example, HTTP URL, video, audio, etc.) in the relay server, the complexity and load of the charging server can be reduced.

FIG. 5 is an operation flowchart of a charging processing method in a multi-PDP environment according to another embodiment of the present invention, and is an operation flowchart of the charging server shown in FIG. 1.

Referring to FIG. 5, the charging server receives an account start request message of a PDP transmitted from a relay server, and determines whether the received account start request message is for a primary PDP or a secondary PDP (S510 and S520).

In step S520, if the received account start request message is an account start request message of the primary PDP, a charging processing event for packet use in the terminal is performed, and the received account start request message is an account start request message of the secondary PDP. In order to prevent charging omission of the primary PDP, which may be caused by the secondary PDP, the charging processing event for the secondary PDP is dropped (S530 and S540).

The operation of FIG. 5 will be described in detail with reference to FIG. 6.

Referring to FIG. 6, steps S610 to S630 shown in FIG. 6 are the same as steps S410 to S430 shown in FIG. 4.

That is, a process of performing a PDP context request for the main PDP and an authentication process for the main PDP from the terminal (S610), a process of performing a charging processing event for the main PDP through an account start request and an account start request message for the main PDP ( S620 and the process (S630) of requesting a context for the secondary PDP from the terminal and receiving a response thereto are the same as steps S410 to S430 shown in FIG. 4, and thus description thereof will be omitted.

In step S630, when the GGSN receives the create PDP context request for the secondary PDP from the SGSN, the GGSN transfers an account start request message for the secondary PDP to the relay server and receives a response message (accounting response) from the relay server. .

The relay server receives the account start request message for the secondary PDP and forwards the account start request message to the charging server, forwards the response message to the account start request message to the GGSN, and sends the account start request message from the charging server to the accounting server. Receive a response message.

The charging server determines whether the account start request message is for the primary PDP or the secondary PDP by using the attribute values of the account start request message received from the relay server, for example, the attribute values as shown in FIG. 2. Since the account start request message is for the secondary PDP, the charging processing event performed when the account start request message is received is dropped, and the response message is transmitted to the relay server (S640).

As described above, the billing processing method according to an embodiment of the present invention shown in Figs. 5 and 6 determines the account start request message for the primary PDP and the secondary PDP in the billing server to request an account start for the primary PDP. By performing the billing processing event only when a message is received, it is possible to prevent the billing omission that may be caused by the secondary PDP, thereby improving the profitability of the data service.

The billing processing method and system thereof in a multi-PDP environment according to the present invention can be modified and applied in various forms within the scope of the technical idea of the present invention and are not limited to the above embodiments. In addition, the embodiments and drawings are merely for the purpose of describing the contents of the invention in detail, not intended to limit the scope of the technical idea of the invention, the present invention described above is common knowledge in the technical field to which the present invention belongs As those skilled in the art can have various substitutions, modifications, and changes without departing from the spirit of the present invention, it is not limited to the embodiments and the accompanying drawings. And should be judged to include equality.

1 illustrates a billing processing system in a multi-PDP environment according to an embodiment of the present invention.

FIG. 2 is an exemplary diagram for an attribute value constituting an account start request message transmitted from a GGSN according to a PDP type.

3 is a flowchart illustrating a charging processing method in a multi-PDP environment according to an embodiment of the present invention.

4 is a flowchart illustrating a detailed operation of an embodiment for describing the charging processing method illustrated in FIG. 3.

5 is a flowchart illustrating a billing processing method in a multi-PDP environment according to another embodiment of the present invention.

FIG. 6 is a flowchart illustrating an example detailed operation for describing the charging processing method illustrated in FIG. 5.

<Explanation of symbols for the main parts of the drawings>

130: SGSN

140: relay server

150: GGSN

160: authentication server

170: billing server

Claims (14)

In the billing processing method in a multi-PDP environment of the server that processes the account start request message of the PDP, Receiving an account start request message for the PDP; Whether the account start request message is an account start request message for a primary PDP (Secondary PDP) or an account start request message for a secondary PDP using an attribute value constituting the received account start request message for the PDP. Determining; And If the account start request message is an account start request message for the primary PDP, the billing processing for the PDP is performed, and if the account start request message is an account start request message for the secondary PDP, the account start request message. Causing the charging process to be performed to be dropped Billing processing method in a multi-PDP environment comprising a. delete The method of claim 1, The attribute value is Multi-Session-ID, Account Session ID (Acct-Session-ID), Accounting ID (3GPP-Charging-ID), Framed-IP Address and Multi-SMS How to handle billing in a PDP environment. The method of claim 1, The determining step And the account start request message for a plurality of the PDPs is the same account multi-session ID or frame IP address. The method of claim 1, The receiving step In the multi-PDP environment charging method for receiving an account start request message for the PDP from GGSN. The method of claim 5, The dropping step In case of an account start request message for the primary PDP, provide the account start request message to a billing server that performs billing processing; and in case of an account start request message for the secondary PDP, send the account start request message to the billing server. How to handle billing in a multi-PDP environment. The method of claim 1, The receiving step The accounting processing method in a multi-PDP environment receiving an account start request message for the PDP transmitted from the GGSN through a relay server. delete In the billing processing system in a multi-PDP environment including a server for processing the account start request message of the PDP, The server is Receiving an account start request message, and determining whether the account start request message is an account start request message for a primary PDP or an account start request message for a secondary PDP by using an attribute value constituting the account start request message; If the account start request message is an account start request message for the main PDP, the charge processing for the PDP is performed, If the account start request message is an account start request message for the secondary PDP, causing the charge processing performed by the account start request message to be dropped. delete 10. The method of claim 9, The server is And a relay server that receives the account start request message transmitted from a GGSN and transmits the same to a billing server that performs billing processing. The method of claim 11, The relay server If the account start request message is an account start request message for the main PDP, send the account start request message to the billing server, If the account start request message is an account start request message for the secondary PDP, dropping the transmission of the account start request message to the charging server. 10. The method of claim 9, The server is A billing processing system in a multi PDP environment that is a billing server that performs billing processing. The method of claim 13, The billing server is If the account start request message is an account start request message for the main PDP, perform a charging processing event; And the charging processing event is dropped when the account starting request message is an account starting request message for the secondary PDP.

Images