WO2011066780A1

WO2011066780A1 - Charging method and prepaid client based on home base station system

Info

Publication number: WO2011066780A1
Application number: PCT/CN2010/079124
Authority: WO
Inventors: 骆文; 宋建全
Original assignee: 中兴通讯股份有限公司
Priority date: 2009-12-01
Filing date: 2010-11-25
Publication date: 2011-06-09
Also published as: CN102083039A

Abstract

A charging method and prepaid client based on a home base station system are provided in the invention. Therein, the method includes that a prepaid client sends base station type information of a service base station for a terminal and/or subscriber type information of the terminal to a prepaid server, so that the prepaid server executes a charging strategy for the terminal according to the base station type information and/or the subscriber type information; wherein, the base station type information includes one of the followings: macro base station, home base station, and the subscriber type information includes one of the followings: closed subscriber group member, non-closed subscriber group member. With the invention, the problem that the experience of the subscriber is poor to the home base station is solved, and the service of the home base station can be realized to be developed smoothly.

Description

The present invention relates to the field of communications, and in particular to a charging method based on a home base station system and a prepaid client. BACKGROUND OF THE INVENTION In order to provide mobile users with higher service rates and lower the cost of using high-rate services, and reduce the investment in carrier network deployment, at the same time, in order to make up for the shortage of existing distributed cellular wireless communication systems, it is usually A home base station is deployed in an existing communication network as a supplement to the macro base station. The home base station is generally installed in a home, an office area or the like. The home base station is a small, low-power base station with practical, convenient, low-power output and the like. 1 is a schematic diagram of a communication network model including a home base station according to the related art. As shown in FIG. 1, a communication network model of a home base station includes a home base station, a security gateway, an access gateway, an authentication authorization charging server, and anchor point data. Channel function, Prepaid Server (PPS). The home base station can access the access gateway through the security gateway. The security gateway can be set up with the access gateway or with the access gateway. The main function of the security gateway is to ensure link security between the home base station and the access gateway. Authentication Authorization and Accounting Server (AAA) is an important function in the communication network. It is used to implement network operator control and management of data and users. , account services and billing services, usually work in conjunction with network access control, gateway servers, databases, and user information directories. The main function of the Anchor Authenticator (AA) is to provide access authentication to the mobile terminal when the mobile terminal accesses the network. After the mobile terminal accesses the network and before the network is retired, it is responsible for managing and maintaining the mobile terminal. Contextual information. Usually the anchor authenticator is placed in the access gateway. The Anchor Data Path Function (A-DPF for short) is another important function of the communication network. Regardless of how the mobile terminals in the network switch in each base station, all data (uplink data) from the terminal will eventually be aggregated to the anchor data channel function of the terminal, and then further forwarded (for example, sent to the Internet); Number of terminals According to (downstream data), it will also be sent to the anchor data channel function first, and then further sent to the terminal by the anchor data channel function. Usually the anchor data channel function is also placed in the access gateway. The anchor authenticator and anchor data channel functions can be located in the same access gateway or in different access gateways (as shown in Figure 1). The billing function is an important core function in the communication system. The billing can be divided into online billing (ie, prepaid) and offline billing (ie, postpaid). Online billing also includes a variety of billing modes, such as billing, billing, and billing by business (for example, two different billing methods for voice and video telephony).

PPS and Prepaid Client (PPC) are two important functional entities that implement online charging. The two cooperate to complete online charging for users: PPS first converts the real-time user account balance into a certain number of quotas. (The quota refers to the data traffic that the user can use or the duration of the call that the user can use, etc.), and then allocates some of the above quotas to the terminal, and notifies the part of the quota to the PPC; the PPC is responsible for obtaining the data. Quotas to monitor user traffic, when the portion of the quota is about to run out (for example, the user has currently used 80% of the available data traffic or 80% of the available call duration), PPC will notify the PPS; thereafter, PPS will Redistribute a portion of the quota to the terminal. This is repeated until PPS finds that all quotas have been used up (ie, the real-time user account balance is insufficient). At this point, the PPS will notify the PPC to interrupt the user's business and notify the user of the insufficient user account balance. When deploying the online charging function, the PPS is generally set up with the AAA server. In this case, it can be understood that the AAA server itself has the function of PPS; the PPS can also be separated from the AAA server, and an appropriate interface is needed between them. The PPC resides on the anchor authenticator. When the anchor authenticator and the anchor data channel function are located in the same access gateway, the PPC also resides on the data channel function. At this time, the PPC can use the data channel function to provide other services, and monitor the user according to the quota. Service usage (eg, traffic, duration, etc.); When the anchor authenticator and anchor data channel functions are placed in different access gateways, in order to implement the prepaid function, an anchor data channel function needs to reside in the anchor channel. A functional entity called PPA (Prepaid Agent, PPA for short) (not identified in Figure 1). At this time, the PPA is responsible for monitoring the user's service usage according to the quota, and transmitting the related information to the PPS through PPC transit. In the existing home base station system, there are three different types of home base stations, namely: closed mode (CSG-CLOSDE) home base station, mixed mode (CSG-OPEN) home base station, and open mode (OPEN) home base station. The closed mode home base station means that only the user of the Closed Subscriber Group (CSG) member of the home base station can access the home. The base station enjoys the service provided by the home base station; the open mode home base station refers to any user can access the home base station; the hybrid mode home base station refers to allowing CSG users and other users to access, but according to whether the user belongs to the CSG list. Differentiate user types and achieve differentiated quality of service processing (eg, CSG users have higher business priorities, better monthly service quality and business categories). In order to achieve the investment cost of reducing the deployment of the operator's network, and to achieve the satisfaction of the user's use of the service (higher service rate, lower service usage rate), the operator needs to use the home base station system. Since the home base station needs to be purchased and placed by the user (the macro base station does not require the user to purchase and install), in order to attract the user and encourage the user to widely use the home base station, the operator needs to provide a differential charging service for the user who uses the home base station. The difference is reflected in: the tariff standard for accessing the home base station is lower than the tariff standard for accessing the network by using the macro base station; using different types of home base station accessing the network corresponds to different charging policies, for example, using different types of home base stations corresponding to different tariffs The standard corresponds to different charging modes (for example, the closed mode home base station corresponds to the time-based charging, and the open mode home base station corresponds to the charging fee). However, the existing charging system does not pay attention to the type of the base station used by the terminal user to access the network (there is only a macro base station in the current network). Therefore, after the home base station system is introduced in the existing network, the existing charging system cannot know the terminal user. The type of base station currently used cannot support operators to provide differentiated charging services for users. In this way, the user will be less satisfied with the use of the home base station to access the network, or lose interest (no one will be willing to purchase the home base station to install in their own home, but still need to pay the same cost as when using the macro base station), can not effectively The purpose of attracting users and encouraging users to widely use home base stations is achieved, and the home base station service cannot be smoothly carried out until it cannot be carried out. SUMMARY OF THE INVENTION The present invention is directed to the related art in which a charging system cannot provide differential charging services according to different base station types and/or different user types, thereby causing a problem that a user has a poor experience with a home base station. The purpose is to provide a charging scheme based on a home base station system to solve the above problem. In order to achieve the above object, according to an aspect of the present invention, a charging method based on a home base station system is provided. According to the charging method of the home base station system according to the present invention, the prepaid client transmits the base station type information of the serving base station of the terminal and/or the user type information of the terminal to the prepaid server, so that the prepaid server according to the base station type information and The user type information is used to perform the charging policy for the terminal. The base station type information includes one of the following: a macro base station and a home base station, and the user type information includes one of the following: a closed user group member and a non-closed user group member. Preferably, the prepaid client sends the base station type information of the serving base station of the terminal and/or the user type information of the terminal to the prepaid server, including: the prepaid client sends the base station type information, and/or the user by using the access request message. The type information is sent to the prepaid server, where the access request message includes one of the following: an access request message in the RADIUS protocol, an access request message in the Diameter protocol, and a credit control request message. Preferably, the triggering condition for the prepaid client to send the base station type information and/or the user type information to the prepaid server includes one of the following: the initial network access of the terminal, and the quota allocated by the prepaid server for the terminal. End or near to run, the terminal's service base station or service base station type changes, the terminal's user type changes, and the prepaid client receives the prepaid agent's prepaid request. Preferably, after the prepaid client sends the base station type information of the serving base station of the terminal and/or the user type information of the terminal to the prepaid server, the method further includes: the prepaid server receiving the base station type information and/or the user type. The prepaid server performs a charging policy for the terminal according to the base station type information and/or the user type information. The charging policy for the terminal includes: selecting a charging rate for the terminal, and/or selecting a charging mode for the terminal. Preferably, after the charging rate is selected for the terminal, the method further includes: the prepaid server selecting a charging rate for the terminal according to the base station type information and/or the user type information, and performing according to the charging rate. Quota conversion. Preferably, before the prepaid client sends the base station type information of the serving base station of the terminal and/or the user type information of the terminal to the prepaid server, the method further includes: the prepaid client receiving the prepaid from one of the following messages: The proxy obtains base station type information, and/or user type information: a prepaid request message, a mobile IP registration message. Preferably, before the prepaid client obtains the base station type information and/or the user type information from the prepaid agent through the prepaid request message, the method further includes: the prepaid agent acquiring the base station from the home base station/base station by using one of the following messages: Type information, and/or user type information: data channel pre-establishment request message, data channel setup request message; prepaid agent will base station type information, and / Or user type information is sent to the prepaid client. Preferably, before the prepaid client sends the base station type information of the serving base station of the terminal and/or the user type information of the terminal to the prepaid server, the method further includes: the prepaid client from the home base station by using one of the following messages: / Base station acquires base station type information and/or user type information: terminal pre-attach request message, extensible authentication protocol forward message, CMAC key count update request message, context request message, data channel pre-establishment request message, data channel establishment request Message. Preferably, when the prepaid client sends the base station type information and/or the user type information to the prepaid server, the method further includes: the prepaid client transmitting the current remaining quota of the terminal to the prepaid server. Preferably, before the prepaid client sends the remaining quota to the prepaid server, the method further includes: the prepaid client acquiring the remaining quota from the local or prepaid agent. Preferably, the home base station comprises one of the following: a closed mode home base station, a hybrid mode home base station, an open mode home base station. In order to achieve the above object, according to another aspect of the present invention, a prepaid client is provided. The prepaid client according to the present invention includes: a sending module, configured to send base station type information of the serving base station of the terminal and/or user type information of the terminal to the prepaid server, so that the prepaid server according to the base station type information and/or The user type information is a terminal performing a charging policy, where the base station type information includes one of the following: a macro base station, a home base station, and user type information includes one of the following: a CSG member, a non-CSG member. Through the present invention, the PPC is used to send the base station type information of the terminal's base station and/or the user type information of the terminal to the PPS, so that the PPS performs the charging policy for the terminal according to the base station type information and/or the user type information. The invention solves the problem that the charging system cannot provide differential charging service according to different base station types and/or different user types in the related art, thereby causing the user to experience poor experience of the home base station, and the operator effectively attracts the user and encourages the user to be widely used. The purpose of using the home base station is achieved, and the home base station service is smoothly carried out. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate, illustrate, Improperly qualified. 1 is a schematic diagram of a communication network model including a home base station according to the related art; FIG. 2 is an interaction flowchart of Embodiment 1 of the present invention; FIG. 3 is an interaction flowchart of Embodiment 2 of the present invention; 4 is an interaction flowchart of Embodiment 3 of the present invention; FIG. 5 is an interaction flowchart of Embodiment 4 of the present invention; FIG. 6 is an interaction flowchart according to Embodiment 5 of the present invention; FIG. The interaction flow chart of the sixth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. Before describing the embodiments of the present invention in detail, the network elements involved are explained as follows: The PPC is located in the anchor authenticator of the terminal; the PPS is located in the AAA server of the terminal, or has an interface with the AAA server for both Communication between. The interaction between the PPC and the PPS is implemented by means of communication between the anchor authenticator and the AAA server (for example, by means of AAA messages, including RADIUS messages, Diameter messages); when the PPS and the AAA server are separated, the AAA is responsible for Transfer information between the PPC and the PPS. In the following embodiments of the present invention, when it comes to the interaction between the PPC and the PPS, it refers to the above interaction mode. According to an embodiment of the present invention, a charging method based on a home base station system is provided, the method comprising: transmitting, by a PPC, base station type information of a serving base station of a terminal and/or user type information of a terminal to a PPS, so that the PPS is based on The base station type information and/or the user type information is used by the terminal to perform the charging policy. The base station type information includes one of the following: a macro base station and a home base station, and the user type information includes one of the following: a closed user group member and a non-CSG member. The home base station includes one of the following: a closed mode home base station, a hybrid mode home base station, and an open mode home base station. Specifically, the PPC sends the base station type information, and/or the user type information, to the PPS through an access request message or other messages. The access request message includes one of the following: RADIUS An access request message in the protocol, an access request message in the Diameter protocol, and a credit control request message.

The triggering condition for the PPC to send the base station type information, and/or the user type information to the PPS, includes one of the following: the initial network access of the terminal, the quota allocated by the prepaid server for the terminal is used up or is about to be used up, and the serving base station of the terminal Or the service base station type changes, the terminal user type changes, and the prepaid client receives the prepaid request; for example, the PPC finds that the PPS allocates the quota for the terminal or is about to run out (for example, 80% of the quota is used, Threshold), PPC finds that the current serving base station or serving base station type of the terminal changes, and the user type of the PPC discovery terminal changes. Before the PPC sends the base station type information of the serving base station of the terminal and/or the user type information of the terminal to the PPS, the method further includes: the PPA pre-establishes the request message or the data channel establishment request message from the home base station/base station through the data channel. Obtaining base station type information, and/or user type information; the PPA sends the base station type information, and/or the user type information to the PPC; specifically, when initially entering the network, the PPA obtains the base station type information and/or the user type information from the serving base station. When performing handover, the PPA acquires base station type information and/or user type information from the target base station. In addition, the PPC may also obtain the base station type information, and/or the user type information from the home base station/base station by using one of the following messages: a terminal pre-attach request message, an Extensible Authentication Protocol (EAP) forwarding message, The CMAC key count update request message, the context information request message, the data channel pre-establishment request message, and the data channel setup request message. The terminal pre-attach request message and the EAP forward message are used to correspond to the serving base station in the initial network access process; the CMAC key count update request message, the context request message, the data channel pre-establishment request message, and the data channel setup request message are For the handover process, corresponding to the target base station, where the data channel pre-establishment request message and the data channel setup request message correspond to a scenario in which the PPC and the PPA are unified. Then, the PPC sends the acquired base station type information, and/or user type information to the PPS through the access request message. After the PPC sends the base station type information of the serving base station of the terminal and/or the user type information of the terminal to the PPS, the PPS receives the base station type information and/or the user type information, and uses the base station type information and/or the user type information as the terminal. Executing a charging policy, where performing a charging policy for the terminal includes: selecting a charging rate for the terminal (performing quota conversion), and/or selecting a different charging mode for the terminal. In addition, when the PPC sends the base station type information and/or the user type information to the PPS, the PPC also sends the current remaining quota of the terminal to the PPS. Where the remaining quota is PPC from the local or PPA acquired. With this embodiment, the PPC sends the base station type of the current serving base station of the terminal user, and/or the current user type of the terminal user to the PPS; the PPS may perform the terminal user according to the type of the monthly service base station and/or the user type information. The corresponding charging policy can attract and encourage users to widely use the home base station, and can use the home base station according to the type of the base station currently used by the terminal user, that is, the type of the serving base station (macro base station, different types of home base stations). The user provides a differential billing service, which can solve the problem that the user cannot provide the above-mentioned differential billing service after the home network system is introduced on the live network, and thus the user's satisfaction with using the home base station to access the network is reduced until the user loses. Interest, and ultimately the home base station business could not be carried out smoothly, and even could not be carried out. In the actual application process, the user can also provide differentiated charging services by notifying the user type (CSG member or non-CSG member) to which the current terminal user belongs. For example, when a CSG member accesses a network through a closed mode home base station or a hybrid mode home base station, a lower tariff standard or a time-based charging is obtained; when a non-CSG member accesses the network through an open mode home base station or a hybrid mode home base station, High tariffs, or metering fees, etc. The implementation process of the embodiment of the present invention will be described in detail below with reference to examples. Embodiment 1 FIG. 2 is an interaction flowchart of a method for a PPC to notify a current base station type of a PPS terminal, and/or a current user type of the terminal according to the first embodiment of the present invention, as shown in FIG. 2, including the following Step S202 to step S206: Step S202: The PPC sends an access request message (AAA message) to the PPS. During the initial network access process, the PPC needs to send the foregoing access request message to the PPS, where the message carries the prepaid function supported by the PPC, and is used to negotiate the prepaid capability method with the PPS, and requires the PPS to be the terminal (end user). The initial quota (Quota) is allocated; at this time, the message also carries the service base station type of the terminal acquired by the PPC, and/or the current user type of the terminal acquired by the PPC. After the terminal accesses the network, the PPC can also send the access request message to the PPS when the quota allocated by the PPS for the user is about to be exhausted (for example, 80% of the quota is used). At this time, the message carries the quota that can be specified. The indication that needs to be supplemented; at this time, the message also carries the type of the serving base station acquired by the PPC, and/or the type of the user; in addition, the message may also carry the terminal (for the terminal) Household) The current remaining quota. After the terminal accesses the network, the PPC may also send the foregoing access request message to the PPS when the current serving base station of the terminal is found, or the type of the serving base station changes (for example, the terminal switches from the macro base station to the home base station); The type of the serving base station acquired by the PPC, and/or the type of the user are also carried; in addition, the message may also carry the current remaining quota of the terminal. After the terminal accesses the network, the PPC can also change the current user type of the terminal (end user). For example, the serving base station of the terminal is a hybrid mode home base station, and the user type of the terminal is changed from a non-CSG member to a CSG. The member sends the foregoing access request message to the PPS. At this time, the message also carries the type of the serving base station acquired by the PPC, and/or the type of the user. In addition, the message may also carry the current remaining quota of the terminal. When the PPC sends the base station type information of the serving base station to the PPS, the parameter BSTYPE may be added to the AAA message, and BSTYPE=0 indicates that the macro base station (Macs); BSTYPE=1 indicates the open mode (OPEN) home base station; BSTYPE= 2 indicates mixed mode (CSG-OPEN) home base station; BSTYPE=3 indicates closed mode (CSG-CLOSED) home base station. It is also possible to make BSTYPE=0 the default value, that is, if the AAA message does not carry the parameter BSTYPE, the default serving base station type is a macro base station. Alternatively, in another manner, a parameter BSTYPE=0 is added to the AAA message to indicate a macro base station (Mac BS); BSTYPE=1, SUBTYPE=1 indicates an open mode (OPEN) home base station; BSTYPE=1, SUBTYPE=2 Indicates the hybrid mode (CSG-OPEN) home base station; BSTYPE=1, SUBTYPE=3 indicates the closed mode (CSG-CLOSED) home base station. Similarly, you can also make BSTYPE=0 the default value, with the same meaning as above. When the PPC sends the user type information to the PPS, the parameter USERTYPE may be added to the AAA message, and USERTYPE=0 indicates a non-CSG member; USERTYPE=1 indicates a CSG member (CSG Member) „ USERTYPE=0 is the default value, that is, if the AAA message does not carry the parameter USERTYPE, the default user type is a non-CSG member. The above access request message (AAA message), such as the Access-Request message in the RADIUS protocol, The AA-Request message in the discussion, or the Credit-Control-Request. It should be noted that, according to actual needs, the above-mentioned service base station type information, user type information They can be used alone or in combination. Step S204: The PPS obtains the type of the monthly service base station, and/or the user type, and applies (executes, selects) different charging policies to the terminal (end user). In the process of the terminal performing the initial network access, the PPS may acquire the type of the terminal serving base station, and/or the user type from the foregoing access request. At this time, the PPS may select different charging policies for the terminal according to the type of the serving base station, and/or the type of the user. For example, the terminal (end user) selects to perform the flow-based fee, and the time-based billing; or/and, selects a different billing rate for the terminal (end user). According to the charging policy, the PPS performs quota conversion for the terminal (end user); after the terminal accesses the network, the PPS may also receive the access request from the PPC. As described in step S202, there are multiple conditions for triggering the PPC. An access request message is sent to the PPS. The PPS can obtain the above-mentioned serving base station type, and/or user type. At this time, the PPS may change the charging policy according to the type of the serving base station, and/or the type of the user, and perform quota conversion for the terminal again. For example, the PPS may perform the above operations when the type of serving base station is discovered, and/or the type of user is relatively changed from the previously recorded status. In addition, when the PPS re-executes the quota conversion for the terminal, the PPS may also perform the acquisition of the current remaining quota of the terminal from the foregoing access request. In the following, when the PPS is used for the terminal based on the duration of the accounting, the quota conversion is performed as an example. The PPS performs different charging policy methods for the user according to the type of the serving base station and/or the user type. Provide the purpose of differentiated billing services. Assume that the current user account balance is 100 units. The above PPS performs quota conversion for the terminal according to the type of the serving base station, as follows:

A. In the case of a macro base station, PPS converts the balance into 100 units (rate 1 is higher); in the case of a home base station, PPS converts the balance into 200 units (rate 1/2, lower).

B. In the case of a macro base station, the PPS converts the balance into 100 units (the rate is 1 and the highest); if it is an open mode home base station, the PPS converts the balance into 150 units (the rate is 2/3); if it is a mixed mode home Base station, PPS converts the balance into 200 units (the rate is 1/2); if it is a closed mode home base station, PPS converts the balance into 300 units (rate 1/3, lowest). Assuming that the current user account balance is 100 units, the above PPS performs quota conversion for the terminal according to the user type, as in the following example:

C. If the end user accesses the network as a non-CSG member role (for example, using a non-CSG member The role is accessed by the macro base station, the open mode home base station, and the hybrid mode home base station. The PPS converts the balance into 100 units of time (rate 1 is higher); if the end user accesses the network as a CSG member role (for example, using CSG) The member role accesses the network through the closed mode home base station and the hybrid mode home base station. The PPS converts the balance into 200 units (the rate is 1/2, lower). Suppose the current user account balance is 100 units. The above PPS is combined with the service base station type. And user type to perform quota conversion for the terminal, as in the following example:

D. The serving base station of the terminal is a macro base station. In this case, the user type must be a non-CSG member, then the user type can be classified as a non-CSG member, and the PPS converts the balance into 100 units (the rate is 1 and the highest); The base station is an open mode home base station. In this case, the user type must be a non-CSG member, and the PPS converts the balance into 150 units (the rate is 2/3); the terminal's monthly base station is a mixed mode home base station, if the terminal is not the The CSG member of the home base station (ie, the user type is a non-CSG member), and the PPS converts the balance into 150 units of time (a rate of 2/3). If the terminal is a CSG member of the home base station (ie, the user type is a CSG member), the PPS converts the balance into 300 units of time (a rate of 1/3); the serving base station of the terminal is a closed mode home base station, at this time, the user The type must be a CSG member, and the PPS converts the balance to 300 units (rate 1/3, lowest). As can be seen from the above examples (A to D), the conversion of the quota is actually performed according to the rate currently specified for the terminal, and the rate is specified by the charging policy. Step S206: The PPS returns an access success message to the PPC. The access success message may carry the quota allocated by the PPS to the terminal (end user). The assigned quota is typically part of all the quotas owned by the user. For example, the PPS converts the balance of 100 units into 100 unit durations (step S204, instance C), that is, all quotas owned by the user are 100 unit durations; and in this step, the PPS allocates quotas of 10 units of time to the terminal. And passed to the PPC.

When the PPS returns to the PPC, the PPS allocates quotas to the terminal. It is generally used in the following scenarios (using the above example, the PPS allocates a quota of 10 units for the terminal):

E. Assign an initial quota to the terminal, which usually occurs when the terminal performs initial access. At this point, the PPC will know that the terminal is allowed to access the network service in the next 10 units (for example, 10 hours);

F. Supplement the current remaining quota for the terminal. Generally, when the PPC finds that the current terminal quota is running out (for example, there are still 4 hours remaining), the PPC applies for a supplementary quota to the PPS. PPS subdivided With a quota of 10 units for the terminal, the PPC has a quota of 14 units. Of course, in the present invention, as described in step S202, the PPC also sends an access request to the PPS when the type of the serving base station of the terminal is discovered, and/or the type of the user changes. At this time, after performing step S204 (quota conversion), the PPS may also supplement the quota for the terminal. It should be noted that the examples in the examples A to D in the step S204 can be regarded as the terminal user performing the initial network access process, and the PPS is based on the service base station type of the terminal, and/or the user type. The account balance is converted to an instance of the quota by quota conversion. In fact, the same principle can be applied to other scenarios. For example, when the PPC finds that the current terminal quota is insufficient, or the PPC finds that the above-mentioned monthly service base station, and/or the user type changes. At this time, the PPC needs to send the current remaining quota of the terminal, and the above-mentioned service base station type, and/or user type to the PPS; the PPS takes out the current rate, and the current remaining quota (including the remaining quota of the PPC notification, and the PPS) The retained quota that has not been allocated is converted into the user account balance; the PPS determines the current rate (as described in Examples A to D in step S204), and converts the account balance into a quota according to the new rate; PPS is The terminal supplements the quota (as described in example F in step S206). The above method will be described below based on the scenario described in the above example C. The current user type of the terminal is a non-CSG member. The quota of the user is 100 units when the network is initially accessed (the rate is 1 and the user account balance is 100 units;); the PPS allocates 10 units for the terminal when the network is initially connected, PPS The local level is also 90 units.

G. After a period of time, the terminal uses 6 units of time; at this time, the user type of the terminal changes, from a non-CSG member to a CSG member (for example, switching from a macro base station to a home base station, and the terminal is the home base station) The CSG member); as mentioned above, the PPC needs to send relevant information to the PPS, including the current remaining quota of the terminal is 4 units of duration. PPS can know that the current terminal remaining quota is 94 units, and the corresponding account balance is 94 units (rate is 1); since the current terminal user type becomes a CSG member, PPS converts the above 94 unit balance into 188 unit duration. (The rate is 1/2). At this time, the total quota of the terminal is 184 units of time; the PPS can also supplement the quota for the terminal at this time, for example, by adding a quota of 10 units of time, then the quota owned by the PPC is 14 units. Of course, the method described in the above example (G) is also applicable to the above examples A to D, the principle is the same, and the processing method is similar, and will not be described here. The above examples (A to G) are all described in terms of time-based billing. The same principle can be applied to other billing modes. For example, according to Volume Based Accounting, the principle is the same and will not be described again. It should be noted that the foregoing examples are applicable to the embodiments of the present invention, except that in some embodiments, the function of the PPC is replaced by the PPA, and the PPC acts as a proxy for the interaction between the PPA and the PPS (for example, the second embodiment). But the essence and principle are the same. Embodiment 2 FIG. 3 is a flow chart of interaction between a PPA to notify a PPS terminal user of a current serving base station type and/or an end user current user type according to Embodiment 2 of the present invention, as shown in FIG. 3, when an anchor authentication device and When the anchor data channel function is configured on different access gateways, the PPA is responsible for monitoring the service usage of the user according to the quota, and the related information is transmitted to the PPS through the PPC, and the following steps S302 to S310 are performed: Step S302 : The PPA sends a prepaid request message to the PPC. As described in step S202, there are multiple events that can trigger the PPC to send an access request message to the PPS. In this step, the same event can also trigger the PPA to send a Prepaid Request message to the PPC. For example, when PPS found PPA quota allocated for user ¹ ^ i.e. run; or, when the PPA was found in the current serving base station (serving base station or type) is changed; or, when the terminal is currently found PPA When the user type changes, the PPA can send a prepaid request to the PPC. At this time, the prepaid request message carries the type of the serving base station acquired by the PPA, and/or the type of the user. In addition, the message may also carry the current remaining quota of the terminal. Step S304: The PPC sends an access request message to the PPS. At this time, the role of the PPC is to act as a proxy for the interaction between the PPA and the PPS (Proxy) „ When the PPC receives the prepaid request from the PPA, the PPC puts the content (parameter) in the message into the access request message (the same In the access request message in the first embodiment, the access request message is sent to the PPS. Step S306: Synchronization 4 S204, which is not described in jt. Step S308: The PPS returns an access success message to the PPC. In the same manner as the method described in the step S206, the PPS returns the access to the PPC successfully, and the message may also carry the quota allocated by the PPS for the terminal. At this point, the role of the PPC is still to act as a proxy for the interaction between the PPA and the PPS. Step S310: The PPC returns a prepaid notification message to the PPA.

After receiving the access success message from the PPS, the PPC puts the content (parameter) in the message into the prepaid notification message, and sends the message to the PPA. The prepaid notification message may include the quota allocated by the PPS for the terminal. The function of the above-mentioned quota allocated for the terminal is the same as that described in the step S206, except that the PPC in the step S206 is represented by the PPA in this step, and the principle is the same. The example (A to G) of the first embodiment is applicable to the present embodiment, except that in the present embodiment, the function of the PPC is replaced by the PPA, and the PPC acts as a proxy for the interaction between the PPA and the PPS (for example, the PPA is responsible for The above base station type, user type, and remaining quota are sent to the PPS, but the essence and principle are the same, and will not be described again in jt. Embodiment 3 FIG. 4 is an interaction flowchart of a method for a home base station/base station (as a serving base station of a terminal) to notify a PPC base station type and/or a user type of a terminal according to Embodiment 3 of the present invention. As shown in FIG. 4, the terminal passes The home base station/base station (the serving base station) performs the initial network access process, and includes the following steps S402 to S420: Step S402: The air interface parameter synchronization and ranging are completed between the terminal and the base station. The base station includes a macro base station, a home base station, and the like. Step S404: The terminal sends a basic capability negotiation request to the base station to negotiate the authentication capability (such as the user's authentication policy, etc.) with the network. Step S406: The base station (including the home base station, the macro base station) sends a terminal pre-attachment request to the access gateway; after the access gateway processes the request, the terminal pre-attach response is returned to the base station. The purpose of the terminal pre-attach request message is to notify the Authenticator located in the access gateway that a new terminal is about to enter the network, and also assist the terminal to negotiate with the access gateway for some subsequent parameters to be used. The terminal pre-attach request may also carry the type of the terminal service base station and/or the user type of the terminal. First, the base station (home base station, macro base station) that sends the terminal pre-attach request is the current serving base station of the terminal, so the serving base station knows the type of the base station, and the manner of expressing the base station type according to the first embodiment: The macro base station, in the foregoing terminal pre-attach request message, may carry an indication that the base station type is a macro base station; or does not carry the indication, at this time, the receiver PPC will default the base station type to a macro base station; The base station is a home base station, and in the foregoing terminal pre-attach request message, an indication is required to indicate that the base station type is a home base station, and further may indicate which type of home base station is used (closed mode home base station, mixed mode home Base station, open mode home base station, etc.). Secondly, the base station that sends the terminal pre-attach request can also obtain the user type of the terminal, according to the manner of expressing the user type described in the first embodiment: If the current base station is a macro base station, there is no concept of closing the user group CSG member. The macro base station will ignore this parameter, and the receiving PPC will default the user type to a non-CSG member; if the current base station is a home base station, the home base station will first determine whether the terminal is a CSG member of its own, and use the judgment result as an indication. , used to indicate the current terminal user type (CSG member, non-CSG member). It is worth noting that if the home base station also ignores this parameter (for example, an open mode home base station;), then the receiver will also default the user type to a non-CSG member. As described above, the PPC is located in the anchor authenticator. At this time, the PPC may acquire the base station type of the terminal monthly base station from the terminal pre-attach request, and/or the user type of the terminal, and cache it. locally. Step S408: The base station returns a basic capability negotiation response to the terminal. Step S410: The access gateway (anchor authenticator) starts an EAP authentication process, and sends a user identity request to the base station, and the base station forwards the request to the terminal. Step 4: S412: After receiving the user identification request, the terminal replies with the user identity response to the base station, and the base station forwards the response to the access gateway (anchor authenticator). In this step, the base station transmits the user table identifier response of the terminal to the access gateway (anchor authenticator) by using an EAP Forwarding message (EAP-Transfer). If in the above steps (step S406) The base station does not have the above-mentioned monthly service base station type, and/or the user type is sent to the access gateway. In this case, the service base station type and/or the user type may be sent to the access according to the method described in step S406. Gateway. At this time, the PPC may acquire the base station type of the foregoing terminal serving base station from the EAP forwarding message, and/or the user type of the foregoing terminal. Step S414: After receiving the user identity response, the access gateway (anchor authenticator, PPC) sends an access request message to the AAA server (PPS). In the method of step S202, the foregoing access request message (transmitted by the PPC to the PPS) further carries a serving base station type, and/or a user type. Step S416: Synchronize 4 to S204. Step S418: The EAP access authentication process is performed between the AAA server and the terminal, and after the access authentication succeeds, the AAA server (PPS) returns an access success message to the access gateway (an anchor authenticator, PPC). In the same manner as the method described in step S206, the foregoing access success message needs to carry the PPS as the end.

Step S420: Continue to execute other processes related to user access. Embodiment 4 FIG. 5 is an interaction flowchart according to Embodiment 4 of the present invention. As shown in FIG. 5, a process in which a terminal performs handover between base stations is notified by a new serving base station (also referred to as a target base station) to PPA/PPC ( The type of the service base station, and/or the user type of the terminal, and the interaction flowchart of the method for the PPC to notify the PPS, including the following steps S502 to S520: Step S502: The mobile terminal sends a handover to the monthly service base station Instructions. After the mobile terminal determines the new service base station (target base station) to be switched in, the mobile terminal needs to send a mobile indication message (MOB_HO-IND) to its current monthly base station, where the message carries the identity of the target base station. Step S504: The serving base station sends a handover confirmation (HO_Cnf) message to the target base station, informing the mobile terminal that the handover is to be performed to the target base station; and the target base station responds to the service base station by using a handover consent (HO_Ack) message. Step S506: The target base station sends a context request message to the anchor authenticator of the terminal; the anchor authenticator responds to the target base station by using a context response message. If the target base station does not already have the context information of the terminal (for example, Authorization Key (AK) context information), then the target base station may send a context request (Context_Req) to the anchor authenticator of the terminal. Used to obtain context information of the terminal. According to the method described in step S406, the target base station (home base station, macro base station) can know the base station type of the serving base station of the terminal, and/or the user type of the terminal after becoming the serving base station of the terminal. At this time, the target base station may send the base station type, and/or user type to the PPC (anchor authenticator) using the above context request; at this time, the PPC will cache these parameters locally. Step S508: The target base station sends a data channel pre-establishment request to the anchor access gateway (anchor data channel function) of the terminal; the anchor access gateway (anchor data channel function) uses the data channel pre-establishment response to respond to the target base station. If the target base station has not pre-established a data channel between the terminal and the anchor access gateway (anchor data channel function), the target base station may also send a data channel pre-establishment request (Path_Prereg_Req) to the anchor data channel function. , used to pre-establish data channels. In the method of synchronizing the quad-S506, the target base station can acquire the above-mentioned base station type, and/or user type. The target base station can use the data channel pre-establishment request message to send it to the PPA (Anchor Data Channel Function), which will cache these parameters locally. Step S510: The terminal sends a ranging request to the target base station, indicating that the terminal is to be handed over to the target base station. Step S512: The target base station responds to the ranging response to the terminal, and at the same time, performs a terminal re-entry procedure. Step S514: The target base station (new serving base station) sends a data channel establishment request to the anchor access gateway (anchor data channel function) of the terminal; the anchor access gateway (anchor data channel function) uses the data channel to establish a response response. Target base station. The target base station needs to formally establish a data channel between the terminal and the anchor data channel function. At this time, the target base station sends a data channel establishment request ( Path_Reg_Req ) to the anchor data channel function. In the same step S508, the target base station can acquire the above-mentioned base station type, and/or user type. The target base station can send a request to the PPA (Anchor Data Channel Function) using a data channel setup request. PPA caches these parameters locally. Step S516: The target base station (new serving base station) sends a CMAC key count update request to the anchor authenticator; the anchor authenticator uses the CMAC key count update confirmation to respond to the service base station. The target base station needs to synchronize the counting parameter of the CMAC key with the anchor authenticator of the terminal, and the parameter is used to calculate a key for generating security for protecting the wireless air interface. The target base station implements CMAC key count synchronization by transmitting a CMAC Key Count Update Request (CMAC_Key_Count_Update) to the anchor authenticator. In the same step S506, the target base station can acquire the above-mentioned base station type, and/or user type. The target base station can send it to the PPC (Anchor Authenticator) using the CMAC Key Count Update Request, which the PPC caches locally. Step S518: Performing a data channel removal process between the anchor access gateway (anchor data channel function) and the old serving base station of the terminal. Step S520: An interaction switching completion confirmation is performed between the target base station (new serving base station) and the old serving base station of the terminal. Through the method described in this embodiment, in the process of performing handover by the terminal, the PPA/PPC may acquire the base station type of the new monthly service base station of the terminal, and/or the user type of the terminal on the new monthly service base station. In this embodiment, if the target base station directly sends the foregoing information (base station type, and/or user type) to the PPC (step S506, step S516), the information may not be sent to the PPA again (step 4 is S508, Step 4 gathers S514), at this time, the PPC will be responsible for transmitting the information to the PPS; otherwise, the PPA is responsible for transmitting the information to the PPS through the PPC. After obtaining the above information (base station type, and/or user type), the PPA/PPC can send the information to the PPS at any time (using the methods described in Embodiments 1 and 2). For example, after the execution of step S514 is completed, the information may be sent to the PPS by the PPA; or, after the execution of step S516, the PPC may be triggered to send the information to the PPS; or, after the step S520 is executed, (ie, after the entire handover process is completed), the target base station then uses a separate message to notify the PPC (Anchor Authentication) /PPA) (anchor data channel function;), which in turn triggers the PPC/PPA to send the above information to the PPS. . Embodiment 5 6 is an interaction flowchart according to Embodiment 5 of the present invention. As shown in FIG. 6, the terminal performs a process of preparing handover between base stations, and the PAP/PPC is notified by the candidate target base station (potential new serving base station). When the candidate target base station becomes the new serving base station of the terminal, the type of the serving base station, and/or the user type of the terminal on the serving base station, the method includes the following steps S602 to S614: Step S602: The mobile terminal sends the signal to the serving base station. Switch the request. The mobile terminal has already accessed the mobile communication network and is ready to perform the handover operation; during the handover preparation phase, the mobile terminal initiates a mobility request to the serving base station currently serving it. At this time, the mobile terminal determines a set of candidate target base stations. Step S604: The serving base station sends a preparation handover request to each candidate target base station, where the request carries the identifier of the anchor identifier of the terminal and the identifier of the anchor access gateway. Step S606: After receiving the preparation handover request, the candidate target base station sends a context request message to the anchor authenticator of the terminal; the anchor authenticator responds to the candidate target base station by using a context response message. The purpose of the interaction between the candidate target base station and the anchor authenticator is to obtain context information (eg, AK context information) of the terminal. In the same manner as the method described in step S506, the candidate target base station (home base station, macro base station) can also know the base station type of the serving base station of the terminal, and/or the user type of the terminal, after becoming the serving base station of the terminal. It is sent to the PPC (Anchor Authenticator) via a Context Request ( Context_Req ) message. Step S608: The candidate target base station sends a data channel pre-establishment request to the anchor access gateway (anchor data channel function) of the terminal; the anchor access gateway (anchor data channel function) uses the data channel pre-establishment response to respond to the target base station. In the same manner as the method in step S506, the candidate target base station may acquire the foregoing base station type, and/or user type, and send the data channel pre-establishment request message to the PPA (anchor data channel function), and the PPA will cache these parameters. locally. Step S610: The candidate target base station returns a preparation handover request response to the serving base station, where the response indicates whether the candidate target base station accepts the handover request of the mobile terminal. Step S612: The monthly service base station returns a handover request response to the mobile terminal, where one or more potential target base stations are included. Step S614: The serving base station sends a preparation handover confirm message to the potential target base station to prepare for performing handover of the subsequent mobile terminal from the serving base station to the potential target base station. It is worth noting that, due to the handover preparation phase, there are generally multiple candidate target base stations involved in the process. Therefore, during the handover preparation phase, multiple candidate target base stations send the above-mentioned monthly service base station type, and/or user type to the PPC/PPA, and the PPC/PPA caches multiple sets of such information locally. However, PPC/PPA will not send this information to PPS at this time. After the handover execution phase, after determining the new serving base station of the terminal (which is one of the candidate base stations), the PPA/PPC takes out the above-mentioned monthly service base station type and/or user type sent by the candidate base station, and It is then sent to the PPS using the method described in the fourth embodiment. Embodiment 6 FIG. 7 is an interaction flowchart of Embodiment 6 of the present invention. As shown in FIG. 7, an example of an uncontrolled handover performed by a terminal is performed by a new serving base station (also referred to as a new serving base station). The method of notifying the PPA/PPC of the serving base station, and/or the user type of the terminal, and then notifying the PPS to the PPS, includes the following steps S702 to S716: Step S702: The mobile terminal sends the target terminal to the target base station. Ranging request. In the process, the mobile terminal has accessed the home base station system, and starts to perform the handover operation; all neighboring base stations in the home base station system can serve as the target base station, and the mobile terminal directly sends a handover request to the target base station to initiate the handover. In an embodiment, the handover request is a ranging request to initiate an uncontrolled handover procedure. Step S704: The target base station sends a context information request to the monthly base station to request information such as an identifier of the anchor identifier of the mobile terminal and an identifier of the anchor access gateway. Step S706: The target base station requests the context information of the terminal from the anchor authenticator of the terminal. At this time, the target base station certainly does not know the context information of the terminal, so the target base station must request the context information of the terminal from the anchor authenticator of the terminal. In the same manner as the method described in step S506, the target base station (home base station, macro base station) can also obtain the above-mentioned base station type, and/or the user type of the terminal, and send it to the PPC through the context request message. Authority). Step S708: The terminal re-enters the network process. Then, steps S710 to S716 are the same as steps S614 to S620. Through the method described in this embodiment, in the process of performing uncontrolled handover by the terminal, the PPA/PPC can acquire the base station type of the new service base station of the terminal, and/or the user type of the terminal on the new service base station.

The timing at which the PPA/PPC sends the above information to the PPS is the same as the method described in the fourth embodiment, and is not mentioned. Further, in the fourth to sixth embodiments of the present invention, an example is given in which the anchor authenticator and the anchor data channel function are located in different access gateways. In fact, when the two are located in the same access gateway, Embodiments 4 to 6 are also applicable, except that the PPA in the embodiment is replaced by PPC (for example, step S508, step 4 is S514), and the principle is the same. No longer. In the system connection diagram including the home base station shown in FIG. 1, there is also a network element called Home Agent (HA), which is mainly used in the mobile communication network. Mobile IP (Mobile IP) feature. As can be seen from the above description, all upstream data will eventually be aggregated to the anchor data channel function; all downlink data will also be sent to the anchor data channel function first. After the introduction of HA, all uplink data is further sent to the HA after being aggregated to the anchor data channel function; and all downlink data is first sent to the HA and then further sent to the anchor data channel function. At this point, it can be seen that the anchor data channel function is combined with a foreign agent (FA).

The PPC can be located on the HA and the PPA will be located in the FA. The first and second embodiments of the present invention are applicable to this scenario; and in the third to sixth embodiments, the above-mentioned anchor authenticator will no longer contain a PPC, and the above-mentioned serving base station type, and/or user The type will be first obtained by the PPA and further sent to the PPC. Communication between the PPA and the PPC can be accomplished by means of communication between the FA and the HA. In addition to the prepaid request message described above, the PPA may also use the Mobile IP (Mobile IP, abbreviated as ΜΙΡ) protocol defined message to convey the above-mentioned serving base station type, and/or user type, such as a registration message. It should be noted that the steps shown in the flowchart of the accompanying drawings may be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, In some cases, the steps shown or described may be performed in an order different than that described herein. According to an embodiment of the present invention, a PPC is provided, and the PPC may be used to implement a charging method based on a home base station system in the foregoing method embodiment, where the PPC includes: a sending module, configured to serve a base station of the terminal The base station type information and/or the user type information of the terminal are sent to the PPS, so that the PPS performs the charging policy for the terminal according to the base station type information and/or the user type information, where the base station type information includes one of the following: The base station, the home base station includes one of the following: a closed mode home base station, a hybrid mode home base station, and an open mode home base station, and the user type information includes one of the following: a CSG member, a non-CSG member. Specifically, the sending module sends the base station type information, and/or the user type information, to the PPS by using an access request message or other messages. The access request message includes one of the following: an access request message in the RADIUS protocol, an access request message in the Diameter protocol, and a credit control request message; the PPC uses the access request message to set the base station type information, and/or the user type. Information, the trigger condition sent to the PPS includes one of the following: the initial network access of the terminal, the quota allocated by the prepaid server for the terminal is used up or is about to be used up, the type of the monthly base station or the monthly base station of the terminal changes, and the user type of the terminal The change, the prepaid client receives the prepaid request; for example, the PPC finds that the PPS allocates the quota for the terminal or is about to run out (for example, 80% of the quota is used, the threshold is reached), and the PPC discovers the current monthly account of the terminal. The type of the base station or the monthly base station changes, and the type of the user of the PPC discovery terminal changes. Before the sending module sends the base station type information of the serving base station of the terminal and/or the user type information of the terminal to the PPS, the PPA obtains the base station type information, and/or the user type information from the home base station/base station through the data channel pre-establishment request message. ; PPA sends base station type information, and/or user type information to the PPC. In addition, the PPC may also acquire base station type information, and/or user type information from the home base station by one of the following messages: a terminal pre-attach request message, a CMAC key count update request message, and a terminal context request message. The PPC then obtains base station type information, and/or user type information from the PPA through a prepaid request message. After the sending module sends the base station type information of the serving base station of the terminal and/or the user type information of the terminal to the PPS, the PPS will receive the base station type information and/or the user type information, and according to the base station type information and/or the user type information. Executing a charging policy for the terminal, where performing a charging policy for the terminal includes: selecting a charging rate for the terminal (performing quota conversion), and/or selecting a different charging mode for the terminal. In addition, the sending module is further configured to send the current remaining quota of the terminal to the PPS. Among them, the remaining The remaining quota is obtained by the PPC from the local or PPA. It should be noted that the PPC described in the device embodiment corresponds to the foregoing method embodiment, and the specific implementation process has been described in detail in the method embodiment, and is not described herein. The foregoing embodiments of the present invention solve the problem that the charging system cannot provide differential charging services according to different base station types and/or different user types in the related art, thereby causing the user to have a poor risk to the home base station. The PPC is used to send the base station type information of the base station of the terminal and/or the user type information of the terminal to the PPS, so that the PPS performs the charging policy for the terminal according to the base station type information and/or the user type information, which is effective for the operator. The purpose of attracting users, encouraging users to widely use home base stations, and realizing the smooth development of home base station services. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claims A charging method based on a home base station system, characterized in that it comprises:

The prepaid client sends the base station type information of the serving base station of the terminal and/or the user type information of the terminal to the prepaid server, so that the prepaid server according to the base station type information and/or the user type information Performing a charging policy for the terminal;

The base station type information includes one of the following: a macro base station and a home base station, where the user type information includes one of the following: a closed user group member and a non-closed user group member. The method according to claim 1, wherein the prepaid client transmitting the base station type information of the serving base station of the terminal and/or the user type information of the terminal to the prepaid server comprises:

And the pre-paid client sends the base station type information, and/or the user type information, to the pre-paid server by using an access request message, where the access request message includes one of the following:

An access request message in the RADIUS protocol, an access request message in the Diameter protocol, and a credit control request message. The method according to claim 1, wherein the triggering condition that the prepaid client sends the base station type information and/or the user type information to the prepaid server comprises one of the following:

The terminal is initially connected to the network, the quota allocated by the pre-paid server for the terminal is used up or is about to be exhausted, the type of the monthly base station or the monthly base station of the terminal is changed, and the user type of the terminal is The change, the prepaid client receives the prepaid request. The method according to claim 1, wherein after the prepaid client sends the base station type information of the serving base station of the terminal and/or the user type information of the terminal to the prepaid server, The method further includes:

The prepaid server receives the base station type information and/or the user type information; the prepaid server performs a charging policy for the terminal according to the base station type information and/or the user type information; The performing a charging policy for the terminal includes: selecting a charging rate for the terminal, and/or selecting a charging mode for the terminal.

The method according to claim 4, wherein after the charging rate is selected for the terminal, the method further includes:

The prepaid server selects a charging rate for the terminal according to the base station type information and/or the user type information, and performs quota conversion according to the charging rate.

The method according to claim 1, wherein the prepaid client transmits base station type information of the serving base station of the terminal and/or user type information of the terminal to the prepaid server Previously, the method further includes:

The prepaid client obtains the base station type information, and/or the user type information from a prepaid agent by one of the following messages:

Prepaid request message, mobile IP registration message.

7. The method of claim 6, wherein before the prepaid client obtains the base station type information from a prepaid agent through a prepaid request message, and/or the user type information, The method also includes:

The prepaid agent acquires the base station type information, and/or the user type information from a home base station/base station by one of the following messages: a data channel pre-establishment request message, a data channel setup request message;

The prepaid agent transmits the base station type information, and/or the user type information to the prepaid client.

The method according to claim 1, wherein the prepaid client sends the base station type information of the serving base station of the terminal and/or the user type information of the terminal to the prepaid server. Previously, the method further includes:

The prepaid client acquires the base station type information and/or the user type information from a home base station/base station by one of the following messages:

The terminal pre-attach request message, the extensible authentication protocol forwarding message, the CMAC key count update request message, the context request message, the data channel pre-establishment request message, and the data channel setup request message.

The method according to any one of claims 1 to 8, characterized in that the prepaid customer When the terminal sends the base station type information and/or the user type information to the prepaid server, the method further includes:

The prepaid client sends the current remaining quota of the terminal to the prepaid server.

The method of claim 9, wherein the method further comprises: before the prepaid client sends the remaining quota to the prepaid server, the method further comprises:

The prepaid client obtains the remaining quota from a local or prepaid agent.

The method according to any one of claims 1 to 8, wherein the home base station comprises one of the following:

Closed mode home base station, mixed mode home base station, open mode home base station.

12. A prepaid client, comprising:

a sending module, configured to send, to the prepaid server, base station type information of the terminal base station and/or user type information of the terminal, so that the prepaid server is configured according to the base station type information and/or the user Type information is used to perform a charging policy for the terminal.

The base station type information includes one of the following: a macro base station and a home base station, where the user type information includes one of the following: a CSG member and a non-CSG member.