WO2010003359A1 - 区别用户计费规则的计费方法和系统 - Google Patents

区别用户计费规则的计费方法和系统 Download PDF

Info

Publication number
WO2010003359A1
WO2010003359A1 PCT/CN2009/072645 CN2009072645W WO2010003359A1 WO 2010003359 A1 WO2010003359 A1 WO 2010003359A1 CN 2009072645 W CN2009072645 W CN 2009072645W WO 2010003359 A1 WO2010003359 A1 WO 2010003359A1
Authority
WO
WIPO (PCT)
Prior art keywords
user group
new
internal user
charging
gateway
Prior art date
Application number
PCT/CN2009/072645
Other languages
English (en)
French (fr)
Inventor
孙扬
周晓云
卢飞
王静
梁爽
朱进国
王志海
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2010003359A1 publication Critical patent/WO2010003359A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1428—Invoice generation, e.g. customization, lay-out, database processing, algorithms for calculating the bill or formatting invoices as WWW pages
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1485—Tariff-related aspects

Definitions

  • FIG. 1 is a schematic diagram showing a system structure of an evolved system according to the related art. As shown in FIG.
  • EPC Evolved Universal Terrestrial Radio Access Network
  • HSS Home Subscriber Server
  • MME Mobility Management Entity
  • PCRF Policy and Charging Rule Function
  • S-GW Serving Gateway
  • PDN Gateway PDN Gateway
  • the subscriber server is the permanent storage location of the user's subscription data.
  • the home network the mobility management unit is the location where the user subscription data is stored in the current network, responsible for terminal-to-network non-access layer signaling management, terminal security verification function, terminal mobility management, and user idle mode.
  • monthly service gateway is the core network to the wireless system
  • the gateway is responsible for the user side load of the terminal to the core network, the data buffer in the idle mode of the terminal, the function of initiating the service request by the network side, the lawful interception and the packet data routing and forwarding function
  • the service gateway is responsible for counting the use of the wireless network by the user terminal, And generating a CDR of the terminal using the wireless network, and transmitting the CDR to the charging gateway
  • the packet data gateway is a gateway of the evolved system and the external packet data network of the system. It is connected to the Internet and the packet data network, and is responsible for the Internet Protocol (IP) address allocation, charging function, and packet filtering of the terminal. , policy control and other functions.
  • IP Internet Protocol
  • the branch data gateway is responsible for counting the CDRs of the user terminal using the packet data network and transmitting it to the charging gateway.
  • the policy charging rule function entity is responsible for providing charging control, online credit control, threshold control, and monthly service quality in the evolved system.
  • the service is referred to as the QoS policy.
  • the operator's IP service network is the operator's service network.
  • the network provides IP services to users through the evolution system.
  • the accounting gateway is used to collect users.
  • the bills generated on the service gateway and the packet data gateway are transmitted to the billing system;
  • the billing system is configured to generate detailed bills according to the bills configured by the operator and the bills sent by the billing gateway; It consists of an E-UTRAN NodeB (eNB), which is mainly responsible for the transmission and reception of wireless signals, and communicates with the terminal through the air interface, and manages the radio resources, resource scheduling, and access control of the air interface.
  • eNB E-UTRAN NodeB
  • the terminal is in the evolved system. There are two types of status, one is mobility management status, and the other is connection management status.
  • the mobility management state is used to monitor the mobility management information of the terminal in the network. It has two states, a registration state and a non-registration state.
  • the registration status indicates that the terminal has been registered in the evolved system, the network has its context information, location information, etc., and the terminal can use the service through the evolved system; the non-registration status indicates that the terminal is not registered in the evolved system, and the evolved system does not have its context information and location. Information, the terminal cannot use the service in the evolved system.
  • the connection management state is used for the registration state terminal to monitor the signaling connection status between the registered terminal and the mobility management unit. It has two states, "idle" and "connection". The "idle” state indicates that there is no non-access stratum signaling connection between the terminal and the mobility management unit, and the non-access stratum signaling cannot be transmitted.
  • the terminal cannot send and receive data through the evolved system; the "connected" state indicates the terminal and the mobility management unit. There is a non-access stratum signaling connection, which can transmit non-access stratum signaling, and the terminal can send and receive data through the evolved system.
  • the terminal in the registered state if its connection management state is idle, the terminal must initiate a service request procedure to turn it into a connected state.
  • a home base station (Home eNB, abbreviated as HeNB) is a type of evolved base station, as some The user's exclusive resources are deployed in private places such as homes, groups, companies, or schools. The home base station belongs to only some users and can only be used by these users and other users.
  • the owner of the home base station and the user of the owner 4 are composed of a group called Closed Subscriber Group (CSG). These home base stations belong to the exclusive resources of the internal user group, and only the internal user group can access the user. Into use. In the evolution system where the home base station is deployed, there is also a configuration server (Configuration Server, abbreviated as CS).
  • the configuration server stores all data about the internal user group, including: internal user group identifier (CSG Identity, CSG ID for each internal user group), list of all users included in the internal user group, internal user group The device number (HeNB ID) of all home base stations and their administrator ID.
  • the configuration server also includes information such as charging rules and service quality corresponding to the internal user group. There may be different user types within the internal user group.
  • the configuration server also stores information such as charging rules and quality of service for different user types of the same internal user group.
  • the configuration server can be set separately or in combination with the contracted user server according to the needs of the operator.
  • the configuration server and the policy charging rule server have an interworking interface.
  • the policy charging rule server can query the configuration server for related charging and service quality information.
  • Each internal user group is identified by a unique identifier in the Public Land Mobile Network (PLMN). This identifier is called the internal user group identifier (CSG Identity, CSG ID for short).
  • the coverage area of the internal user group consists of the home base station cells it owns.
  • the cell of the home base station is called an internal subscriber group cell.
  • the evolution system assigns a white list (allowed CSG list) to the internal user group users, and the white list contains users.
  • the ID of the internal user group that is allowed to access Only the identity of the internal user group is in this white list, and the internal user group allows access to the user. In this way, it can effectively ensure that the resources of the internal user group can only be used by users of the internal user group.
  • the evolved system controls the user's access to the home base station through a white list.
  • the terminal When the terminal detects the wireless signal of the internal user group cell, it first receives the cell broadcast information, and checks that the internal user group identifier in the broadcast information is not in the white list in the terminal. If not, the cell is not selected as the serving cell of the terminal; if so, the cell is selected as the serving cell.
  • the network charging may be different, and the charging for different categories of members in the same internal user group may also be different.
  • the use of internal user group resources by terminals of certain guest members in the internal user group may cause internal user group managers to obtain credits. Discounts or offers on the list. Therefore, for terminal charging of internal user group members, the network needs to know which internal user group is used when the terminal initiates the service.
  • the evolved system when the terminal is in an idle state, to initiate a service through the evolved system, a service request process must be initiated to establish a bearer from the terminal to the core network for transmitting the service.
  • the evolved system re-establishes all the wireless bearers and S1 interfaces between the terminal and the base station for all activated bearers of the terminal.
  • the terminal When the terminal is in an idle state, the terminal may register multiple internal user groups in the evolved system, and when the terminal moves between the cells to which the registered internal user groups belong, the 3 trace area update process is not initiated. The evolved system does not know which terminal of the internal user group the terminal in the idle state is in.
  • the base station when the base station forwards the service request message, the base station sends the cell identifier of the message source to the mobility management unit, and the evolved network charges the terminal according to the cell identifier.
  • the exact bill for customer dialogue fees is now getting higher and higher. Because different customers in different internal user groups will generate different phone bills according to different user categories, the customer hopes to display their consumption in different internal user groups in the bill of charge.
  • the mobility management unit cannot learn the internal user group of the terminal from the cell identifier, and therefore cannot allow the evolved network to perform differentiated charging for the terminal to distinguish the internal user group.
  • the present invention is directed to a charging method and system for distinguishing user charging rules to solve the problem that the prior art cannot perform differential charging for an internal user group to which a user belongs and its user category.
  • a charging method for distinguishing user charging rules is provided.
  • the charging method for distinguishing user charging rules includes the following steps: after the terminal initiates a service request, the mobility management unit obtains an internal user group identifier of the home base station to which the terminal belongs. And a user category in the internal user group; the policy charging function entity selects a corresponding charging rule according to the home base station internal user group identifier and the user category; the service gateway or the packet data gateway will The home base station internal user group identifier, the user category information, and the corresponding charging rule are added to the bill of the requested service for charging.
  • the obtaining, by the mobility management unit, the internal user group identifier of the home base station to which the terminal belongs and the user category information in the internal user group specifically includes: the home base station receiving the service request from the terminal; The home base station determines that the internal user group to which the terminal belongs is an internal user group to which the terminal belongs, and sends the home base station internal user group identifier to the mobility management unit; the mobility management unit queries the terminal for the subscription Data, from which the user category of the terminal in the internal user group is known.
  • the obtaining, by the mobility management unit, the internal user group identifier of the home base station to which the terminal belongs and the user category information in the internal user group specifically includes: the home base station receiving the service request from the terminal; The home base station determines that the internal user group to which it belongs is the internal user group to which the terminal belongs, and the user category in the internal user group; the home base station identifies the internal user group and the user category information Sent to the mobility management unit.
  • the selecting, by the policy charging function entity, the corresponding charging rule according to the internal user group identifier and the user category information comprises: the mobility management unit identifying the internal user group identifier and the user category The information is sent to the monthly service gateway; the monthly service gateway sends the internal user group identifier and the user category information to the packet data gateway; the packet data gateway retrieves the information from the policy charging rule function entity The charging rule corresponding to the internal user group identifier and the user category information.
  • the monthly service gateway or the packet data gateway adds the internal user group identifier, the user category information, and the corresponding charging rule to the bill for charging, and the method includes: The internal user group identifier and the user category information are added to the bill for the requested service, and the bill is sent to the charging gateway; the packet data gateway identifies the internal user group, the user category The information and the charging rule are added to its bill for the requested service, and the bill is sent to the charging gateway.
  • the handover occurs in the connection process of the requested service, and the mobility management unit obtains a new internal user group identifier of the home base station to which the terminal belongs and a new one in the new internal user group.
  • the policy charging function entity selects a corresponding new charging rule according to the new internal user group identifier and the new user category information;
  • the packet data gateway adds the new internal user group identifier, the new user category information, and the new charging rule to the bill of the requested service for charging.
  • the mobility management unit obtains the new home base station internal user group identifier to which the terminal belongs and the new user category information in the new internal user group, specifically: the new home base station receives the a handover request of the terminal; the new home base station determines that the internal user group to which it belongs is a new internal user group to which the terminal belongs, and transmits the new internal user group identifier to the mobility management unit; The sex management unit queries the subscription data of the terminal, and learns the new user category of the terminal in the user group of the new home base station.
  • the mobility management unit obtains the new home base station internal user group identifier to which the terminal belongs and the new user category information in the new internal user group, specifically: the new home base station receives the a handover request of the terminal; the new home base station determines that the internal user group to which it belongs is a new internal user group to which the terminal belongs, and a new user category in the new internal user group; The base station transmits the new internal user group identifier and the new user category information to the mobility management unit.
  • the policy charging function entity # locating the new internal user group identifier and the new user category information to select a corresponding new charging rule specifically includes: the mobility management unit to use the new group identifier Transmitting the new category information to the serving gateway; the serving gateway transmitting the new group identifier and the new category information to a packet data gateway; the packet data gateway retrieving from a policy charging rule function entity To the new charging rule corresponding to the new group identification and the new category information.
  • the monthly service gateway or the packet data gateway adds the new internal user group identifier, the new user category information, and the new charging rule to the bill of the requested service for charging.
  • the monthly service gateway adds the new internal user group identifier and the new user category information to its bill for the requested service, and sends the bill to the charging gateway; the packet data gateway Adding the new internal user group identifier, the new user category information, and the new charging rule to their CDRs for the requested service, and sending the CDR to the charging gateway.
  • the charging gateway performing charging specifically includes: the charging gateway collecting a bill from the serving gateway and the packet data gateway; and the charging gateway combines the collected bills and sends the bills to the billing system. And the billing system performs a charging operation on the merged bill to generate a detailed bill, wherein the billing operation is performed according to the charging rule merged into the bill.
  • a charging method for distinguishing user charging rules is provided.
  • the charging method for distinguishing user charging rules according to the present invention is used when the terminal performs handover in the process of performing the connection of the requested service, and includes the following steps:
  • the mobility management unit obtains a new internal user group of the home base station to which the terminal belongs Identifying and new user category information in the new internal user group to which it belongs;
  • the policy charging function entity selects a corresponding new charging rule according to the new internal user group identifier and the new user category information;
  • the packet data gateway adds the new internal user group identifier, the new user category information, and the new charging rule to the bill of the requested service for charging.
  • a charging method for distinguishing user charging rules includes the following steps: when a user accesses a core network through a home base station, the mobility management unit sends the home base station internal user group identifier and user category information to the serving gateway; The gateway sends the home base station internal group identifier and the user category information to the packet data gateway; the packet data gateway interacts with the policy charging rule function entity, and obtains the internal user group identifier and the user category information. Corresponding to the charging rules.
  • a billing system for distinguishing user billing rules is provided.
  • the charging system for distinguishing user charging rules includes: a home base station, configured to receive a request message from the terminal, determine an internal user group to which the terminal belongs, and a mobility management unit, configured to receive from the family The internal user group identifier of the base station, querying the subscription data of the terminal, and knowing the user category of the terminal in the internal user group; the monthly service gateway, configured to receive and forward from the mobility management unit The internal user group identifier and the user category information, and adding the internal user group identifier and the user category information to a bill for the requested service; a packet data gateway, configured to receive the service gateway The internal user group identifier and the user type information, interacting with the policy charging rule function entity to obtain the charging rule corresponding to the internal user group identifier and the user category information, and the internal The user group identifier, the user category information, and the charging rule are added to the bill for the requested service; a billing rule function entity, configured to store various billing rules; a billing gateway, configured to collect bills from the service gateway and
  • FIG. 1 is a schematic diagram showing a system configuration of an evolved system according to the related art
  • FIG. 2 is a flowchart showing a charging method for distinguishing user charging rules according to an embodiment of the present invention
  • FIG. 4 shows a message for switching between a mobile management unit and a monthly service gateway according to the second embodiment of the present invention.
  • FIG. 5 is a signaling flow chart showing a handover of a mobility management unit unchanged but a service gateway is changed according to Embodiment 3 of the present invention
  • FIG. 6 is a diagram showing a mobility management unit according to Embodiment 4 of the present invention;
  • FIG. 5 is a signaling flow chart showing a handover of a mobility management unit unchanged but a service gateway is changed according to Embodiment 3 of the present invention
  • FIG. 6 is a diagram showing a mobility management unit according to Embodiment 4 of the present invention
  • FIG. 7 is a signaling flowchart of a packet data gateway taking a charging rule from a policy charging rule server according to Embodiment 5 of the present invention.
  • FIG. BEST MODE FOR CARRYING OUT THE INVENTION will be described in detail with reference to the accompanying drawings in conjunction with the embodiments. It should be noted that In the case of no conflict, the embodiments in the present application and the features in the embodiments may be combined with each other.
  • Step S10 A mobility management unit obtains an internal user group identifier of a home base station to which a terminal belongs and an internal user The user category in the group; in step S20, the policy charging function entity selects a corresponding charging rule according to the internal user group identifier and the user category of the home base station; Step S30, the serving gateway or the packet data gateway identifies the internal user group identifier of the home base station, and the user category.
  • the information and corresponding charging rules are added to the bill of the requested service for charging. After the deployment of the home base station, both the operator and the customer hope to have a flexible charging method.
  • the differential charging method of the above embodiment is capable of knowing which internal user group resource is used by the terminal because the internal user group identifier and the user category information are notified to the monthly service gateway and the packet data gateway, and the terminal belongs to the internal user group.
  • the step S10 specifically includes: the home base station receives the service request from the terminal; the home base station determines that the internal user group to which the terminal belongs belongs to the internal user group to which the terminal belongs, and sends the home base station internal user group identifier to the mobility management unit.
  • the mobility management unit queries the subscription data of the terminal, and learns the user category of the terminal in the internal user group.
  • the step S10 specifically includes: the home base station receives the service request from the terminal; the home base station determines that the internal user group to which the terminal belongs belongs to the internal user group to which the terminal belongs, and the user category in the internal user group; The internal user group identification and user category information is sent to the mobility management unit.
  • the above preferred embodiment provides two schemes for determining the internal user group and user category of the terminal.
  • step S20 specifically includes: the mobility management unit identifies the internal user group and the user The category information is sent to the service gateway; the service gateway sends the internal user group identifier and the user category information to the packet data gateway; the packet data gateway interacts with the policy charging rule function entity to obtain a corresponding identifier corresponding to the internal user group identifier and the user category information.
  • Fee rules Preferably, the step S30 specifically includes: the service gateway adds the internal user group identifier and the user category information to the bill for the requested service, and sends the bill to the charging gateway; the packet data gateway identifies the internal user group, User category information and charging rules are added to their bills for the requested service, and the bill is sent to the billing gateway.
  • the home base station if the home base station receives the service request of the terminal of the user, the home base station sends the internal user group identifier to which the base station belongs to the mobility management unit.
  • the mobility management unit queries the subscription data of the user, learns the user category of the user in the current internal user group, and then sends the internal user group identifier and the user category to the service gateway, so that the service gateway sets the internal user group identifier and the user category information.
  • the charging method further comprises: obtaining, by the mobility management unit, a new home base station internal user group identifier to which the terminal belongs and new user category information in the new internal user group; the policy charging rule function entity The corresponding new charging rule is selected according to the new internal user group identifier and the new user category information; the service gateway or the packet data gateway adds the new internal user group identifier, new user category information, and new charging rules to the location.
  • Billing is performed in the bill for requesting services. If the terminal is in the connected state, moving between different cells triggers the handover process. After the handover process, the tracking area update process is initiated according to the situation, and the location information of the terminal in the core network is updated. This preferred embodiment addresses the differential charging problem in the handover process.
  • the mobility management entity obtains the new home base station internal user group identifier to which the terminal belongs and the new user category in the new internal user group, specifically: the new home base station (ie, the switched target base station) To the handover request from the terminal; the new home base station determines that the internal user group to which it belongs is the new internal user group to which the terminal belongs, and transmits the new internal user group identity to the mobility management unit; the mobility management unit queries the terminal Signing data, from which the new user category of the terminal in the new internal user group is known.
  • the new home base station ie, the switched target base station
  • the new home base station determines that the internal user group to which it belongs is the new internal user group to which the terminal belongs, and transmits the new internal user group identity to the mobility management unit
  • the mobility management unit queries the terminal Signing data, from which the new user category of the terminal in the new internal user group is known.
  • the mobility management unit obtains the new internal user group identifier to which the terminal belongs and the new user category in the new internal user group, specifically: the new home base station receives the handover request from the terminal; the new home base station Determining that the internal user group to which it belongs is the new internal user group to which the terminal belongs, and its new user category in the new internal user group; the home base station will identify the new internal user group and the new category of the new user category
  • the information is sent to the mobility management unit.
  • the policy charging rule function entity selects a corresponding new charging rule according to the new internal user group identifier and the new user category information, and specifically includes: the mobility management unit identifies the new internal user group identifier and the new user category information.
  • the service gateway sends the new internal user group identifier and the new user category information to the packet data gateway; the packet data gateway interacts with the policy charging rule function entity to obtain the new internal user group identifier and the new user category.
  • the new billing rules corresponding to the information.
  • the monthly service gateway and the packet data gateway add the new internal user group identifier, the new user category information, and the new charging rule to the bill of the requested service for charging, including: the service gateway will be a new internal The user group identifier and the new user category information are added to their bills for the requested service, and the bill is sent to the billing gateway; the packet data gateway identifies the new internal user group identifier, the new user category information, and the new one.
  • the charging rule is added to its bill for the requested service, and the bill is sent to the charging gateway.
  • the billing gateway performs billing specifically: the billing gateway collects bills from the service gateway and the packet data gateway; the billing gateway merges the collected bills and sends the bills to the billing system; and the billing system performs billing on the merged bills. Operation, to generate a detailed bill, wherein the billing operation is performed according to the charging rule incorporated into the bill.
  • the above switching process transmits the internal user group identifier and user type currently used by the user to the serving gateway and the packet data gateway. If the policy charging rule server is deployed in the evolved system, the packet data gateway interacts with the policy charging rule server, and the personalized charging mode is saved in the packet data according to the internal user group and user category of the user.
  • An embodiment of the present invention provides a charging system for distinguishing user charging rules, including: a home base station, configured to receive a request message from a terminal, determine an internal user group to which the terminal belongs, and a mobility management unit, configured to: Receiving an internal user group identifier from the home base station, querying the subscription data of the terminal, and knowing the user category of the terminal in the internal user group;
  • the monthly service gateway is configured to receive and forward internal user group identification and user category information from the mobility management unit, and add the internal user group identifier and user category information to the bill for the requested service; the packet data gateway, And receiving the internal user group identifier and user type information from the service gateway, interacting with the policy charging rule function entity to obtain charging rules corresponding to the internal user group identifier and the user category information, and the internal user group identifier, the user category
  • the information and charging rules are added to the bills of the requested service;
  • the policy charging rule function entity is used to store various charging rules;
  • the charging gateway is used to collect the bills from the
  • the billing system is configured to perform a billing operation on the merged bills from the billing gateway to generate a detailed bill, wherein the billing operation is based on the billing rules merged into the bill. Calculation. Because the above charging system notifies the monthly user gateway and the user category information to the monthly service gateway and the packet data gateway, the prior art cannot distinguish the internal user group and the user category to which the user belongs. The problem, in turn, distinguishes between different internal user groups and different user categories for flexible and accurate billing. The following is a detailed flow chart of an example of a business request process that distinguishes user categories. Embodiment 1 FIG.
  • Step 301 After the terminal accesses the home base station, the home base station needs to The terminal performs a 3 certificate process, and determines the identity of the terminal by comparing the identifier of the terminal with the internal user group list. At this time, the home base station knows the internal user group identifier and the user class of the terminal (eg, the owner or the guest).
  • Step 302 The network may have downlink data or signaling corresponding to a terminal under the home base station, and the network pages the terminal, triggering the terminal to initiate a service request process, and the terminal may also send uplink data or signaling, but The network has no signaling connection and is in an idle state. At this time, the terminal initiates a service request process.
  • Step 304 After verifying that the identity of the terminal is successful, the home base station succeeds.
  • Step 305 After receiving the service request message sent in step 304, the mobility management unit determines whether to initiate security verification on the terminal according to the data saved by the terminal in the mobility management unit, and if necessary, performs a verification process on the terminal. .
  • Step 306 After confirming that the terminal has been verified, the mobility management unit sends an S1 application protocol initial context setup request message to the home base station, where the message includes the address of the serving gateway, the tunnel identifier of the uplink of the S1 interface, and the quality of the service , security context, mobility management unit signaling connection identifier, switching restriction list and other parameters.
  • This step activates the wireless and S1 interface bearers for all active bearers of the terminal.
  • the home base station After receiving the initial context setup request message, the home base station saves all the parameters in the message to the context of the terminal.
  • Step 307 The home base station performs a radio bearer establishment procedure, and establishes a secure channel of the user plane for the user.
  • Step 308 At this time, the home base station can forward the uplink data sent by the terminal to the serving gateway.
  • Step 309 The home base station sends an S1 application protocol initial context setup complete message to the mobility management unit, where the message includes an address of the home base station, an S1 interface downlink tunnel identifier, and other necessary parameters.
  • Step 310 The mobility management unit queries the locally saved subscription data of the terminal, and determines the user category of the terminal in the current internal user group.
  • the mobile management unit sends an update request message to the monthly service gateway, where the message includes the home base station address, the S1 interface downlink tunnel identifier, the radio access technology type, the delayed downlink data notification identifier, the internal user group identifier, and the user type.
  • the terminal When the terminal is charging the terminal, if the terminal still uses the current internal user group identifier, the internal user group identifier and the user type identifier currently used by the terminal are added to the bill generated by the terminal, The specified time is sent to the charging gateway, and the charging gateway and the background program perform differentiated charging, call charge compensation, etc. according to the internal user group identifier and the user type of the CDR, and are generated as The detailed bill of a single user, including which internal user group the user has used before, and the cost incurred by the business. If the user terminal switches to the resources of other internal user groups other than the current internal user group during the call, the target home base station reports a new internal user group identifier and user category to the mobility management unit, mobility.
  • Step 311 The serving gateway sends an update bearer request message to the packet data gateway, where the message includes the identifier of the terminal, an internal user group identifier, and a user type.
  • Step 312 If dynamic policy charging control is deployed in the network, the packet data gateway and the policy charging rule server interact to obtain charging policies for different internal user groups and user types. This step is explained in detail in the fifth embodiment.
  • Step 313 The packet data gateway sends an update bearer response to the monthly service gateway.
  • Step 314 The monthly service gateway sends an update load response to the mobility management unit.
  • Step 401 When the terminal is in the connection state, if the cell enters the target home base station cell from the source base station cell, the handover process is initiated, and the cell is accessed in the home base station cell.
  • Step 402 If the source base station is a macro base station, the destination home base station triggers the terminal to initiate a 3-tracking area update procedure by using air interface signaling.
  • Step 403 The terminal sends a tracking area update request message to the mobility management unit, where the message includes an identifier of the terminal, an internal user group identifier of the currently used cell, and other information.
  • Step 404 The mobility management unit verifies the terminal.
  • Step 405 The mobility management unit queries the subscriber type to which the terminal belongs from the subscription data of the terminal stored locally according to the identifier of the terminal and the identifier of the internal user group used.
  • the mobility management unit sends an update bearer request message to the service gateway, where the message includes information such as an identifier of the terminal, an internal user group identifier, and a user type.
  • Step 406 After receiving the update bearer request message sent in step 405, the serving gateway saves the user group identifier and the user type information of the terminal locally, and generates a bill for the user under the internal user group cell. Then, the serving gateway sends an update bearer request message to the packet data gateway, where the message includes information such as an identifier of the terminal, an internal user group identifier, and a user type.
  • Step 407 After receiving the update bearer request message sent in step 406, the packet data gateway saves the internal user group identifier and the user type of the user locally for generating a bill.
  • the packet data gateway interacts with the server, and the personalized charging policy obtained according to the internal user group identifier and the user type of the user is saved in the packet data gateway. See step 5 for details of this step.
  • Step 408 The packet data gateway sends an update bearer response message to the serving gateway.
  • Step 409 The serving gateway sends an update bearer response message to the mobility management unit.
  • Step 410 The evolved system and the terminal complete the subsequent 3 track area update process.
  • the above procedure provides a handover procedure from a base station cell of a non-home base station to a home base station cell, mainly to the service gateway and the packet data gateway knowing the internal user group of the incoming home base station cell and the type of the user.
  • FIG. 5 is a signaling flowchart of a handover when a mobility management unit is unchanged but a service gateway is changed according to Embodiment 3 of the present invention.
  • Step 501 When the terminal is in the connected state, if the cell enters the target home base station cell from the source base station cell, initiates a handover procedure and accesses the home base station cell.
  • Step 502 If the source base station is a macro base station, the destination home base station triggers the terminal to initiate a 3-tracking area update process by using air interface signaling.
  • Step 503 The terminal sends a tracking area update request message to the mobility management unit, where the message includes an identifier of the terminal, an internal user group identifier of the currently used cell, and other information.
  • Step 504 The mobility management unit verifies the terminal.
  • Step 505 The mobility management unit queries the user type to which the terminal belongs from the subscription data of the terminal that is stored locally according to the identifier of the terminal and the identifier of the internal user group used.
  • the mobility management unit sends an update bearer request message to the service gateway, where the message includes information such as an identifier of the terminal, an internal user group identifier, and a user type.
  • Step 506 After receiving the update bearer request message sent in step 505, the serving gateway saves the user group identifier and the user type information of the terminal locally, and generates a bill for the user under the internal user group cell.
  • the serving gateway sends an update bearer request message to the packet data gateway, where the message includes information such as an identifier of the terminal, an internal user group identifier, and a user type.
  • the packet data gateway After receiving the update bearer request message sent in step 506, the packet data gateway saves the internal user group identifier and the user type of the user locally for generating a bill. If the policy rule accounting server is deployed in the evolved system, the packet data gateway interacts with the server, and the personalized charging policy obtained according to the internal user group identifier and the user type of the user is saved in the packet data gateway. See step 5 for details of this step.
  • Step 508 The packet data gateway sends an update bearer response message to the serving gateway.
  • Step 509 The serving gateway sends an update bearer response message to the mobility management unit.
  • Step 510 The evolved system and the terminal complete the subsequent 3 track area update process.
  • the above procedure provides a handover procedure from a base station cell of a non-home base station to a home base station cell, mainly to the service gateway and the packet data gateway knowing the internal user group of the incoming home base station cell and the type of the user.
  • This embodiment can also be used in the scenario where the terminal switches from the home base station of one internal user group to the home base station of another internal user group.
  • FIG. 6 is a signaling flowchart of a handover when both the mobility management unit and the monthly service gateway according to Embodiment 4 of the present invention are changed. When the process occurs, the service gateway and the mobility management unit of the terminal are changed.
  • the mobility management unit needs to update the internal user group identifier and user type information to the monthly service gateway. Specifically, the steps are as follows: Step 601: When the terminal is in the connection state, if the cell enters the target home base station cell from the source base station cell, the handover process is initiated, and the cell is accessed in the home base station cell. Step 602: If the source base station is a macro base station, the destination home base station triggers the terminal to initiate a 3-tracking area update procedure by using air interface signaling. Step 603: The terminal sends a tracking area update request message to the mobility management unit, where the message includes an identifier of the terminal, an internal user group identifier of the currently used cell, and other information. Step 604: The mobility management unit verifies the terminal.
  • Step 605 The mobility management unit queries the user type to which the terminal belongs from the subscription data of the terminal that is stored locally according to the identifier of the terminal and the identifier of the internal user group used.
  • the mobility management unit sends an update bearer request message to the service gateway, where the message includes information such as an identifier of the terminal, an internal user group identifier, and a user type.
  • Step 606 After receiving the update bearer request message sent in step 605, the serving gateway saves the user group identifier and the user type information of the terminal locally, and generates a bill for the user under the internal user group cell.
  • the serving gateway sends an update bearer request message to the packet data gateway, where the message includes information such as an identifier of the terminal, an internal user group identifier, and a user type.
  • the packet data gateway After receiving the update bearer request message sent in step 606, the packet data gateway saves the internal user group identifier and the user type of the user locally for generating a bill. If the policy rule accounting server is deployed in the evolved system, the packet data gateway interacts with the server, and the personalized charging policy obtained according to the internal user group identifier and the user type of the user is saved in the packet data gateway. See step 5 for details of this step.
  • Step 608 The packet data gateway sends an update bearer response message to the serving gateway.
  • Step 609 The serving gateway sends an update bearer response message to the mobility management unit.
  • Step 610 The evolved system and the terminal complete a subsequent 3 track area update process.
  • the above procedure provides a handover procedure from a base station cell of a non-home base station to a home base station cell, mainly to the service gateway and the packet data gateway knowing the internal user group of the incoming home base station cell and the type of the user.
  • This embodiment can also be used in the scenario where the terminal switches from the home base station of one internal user group to the home base station of another internal user group.
  • the core network sends the tracking area identifier to the serving gateway and the packet data gateway in the following step 605, 606 in the subsequent tracking area update process, so that the service gateway and the packet data
  • the gateway detects that the terminal has left the cell of the internal user group, the gateway stops the operation of charging the terminal according to the original internal user group identifier.
  • Step 701 A packet data gateway detects a certain After the current internal user group identifier of the connection state terminal is changed, the server is prepared to interact with the policy charging rule server to obtain the charging policy of the user terminal under the current internal user group.
  • Step 702 The packet data gateway sends a policy charging rule request message to the policy charging rule server, where the message includes the identifier of the terminal, an internal user group identifier currently used by the terminal, and a user type. If the policy charging rule server currently holds the current internal user group for the terminal For related billing information, step 705 is directly initiated.
  • Step 703 The policy charging rule server sends a query request message to the configuration server, where the query request includes an identifier of the terminal, an internal user group identifier currently used by the terminal, and user type information of the terminal, and the message may also include other queries. Information.
  • Step 704 After the server is configured to query the terminal for the charging related information of the current internal user group, the server sends an inquiry response message to the policy charging rule server, where the message includes the charging rule of the current internal user group of the terminal, Information about service quality and other necessary information.
  • Step 705 After receiving the query response message, the policy charging rule server saves the data in the query response.
  • Step 706 Then send a policy charging rule response message to the packet data gateway, where the message includes the terminal identifier, the charging rule of the terminal in the current internal user group, the quality of service related information, and other necessary information.
  • Step 707 The packet data gateway saves related information about the charging rule, the quality of service, and the like of the terminal in the current internal user group.
  • a computer readable medium having stored thereon computer executable instructions for causing a computer or processor to perform, for example, when executed by a computer or processor
  • the processing of each step shown in FIGS. 2 to 7 preferably performs one or more of the above-described first to fifth embodiments.
  • the present invention provides a flexible charging method for users of different internal user groups.
  • the evolved network can use the current current used by the user.
  • the internal user group ID and user type are sent to the service gateway and the packet data gateway to facilitate differential accounting.
  • 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.
  • 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.
  • the invention is not limited to any specific combination of hardware and software.
  • 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.
  • 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.
  • 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.
  • the present invention can be variously modified and modified. Any modifications, equivalent substitutions, improvements, etc. made therein are intended to be included within the scope of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Description

区别用户计费规则的计费方法和系统 技术领域 本发明涉及通信领域， 具体而言， 涉及一种区别用户计费规则的计费方 法和系统。 背景技术 为了保持第三代移动通信系统在通信领域的竟争力，为用户提供速率更 快、 时延更低、 更加个性化的移动通信服务， 同时， 为了降低运营商的运营 成本， 3GPP ( 3rd Generation Partnership Project, 第三 4弋合作伙伴计划）标准 工作组正致力于演进分组系统 （ Evolved Packet System, 简称 EPS ) 的研究。 图 1示出了根据相关技术的演进系统的系统结构的示意图， 如图 1所示， 整 个 EPS系统分为无线网 ( Evolved Universal Terrestrial Radio Access Network, 简称为 E-UTRAN ) 和核心网 （ Evolved Packet Core, 简称为 EPC ) 两部分。 在核心网中， 包含了签约用户服务器（ Home Subscriber Server, 简称为 HSS )、 移动性管理单元 （Mobility Management Entity , 简称为 MME )、 策略计费规 则功能（ Policy and Charging Rule Function ,简称为 PCRF )、月艮务网关（ Serving Gateway , 简称为 S-GW ), 和分组数据网关（ PDN Gateway, 简称为 P-GW )„ 在核心网中， 月艮务网关和分组数据网关都和计费网关 （Charging Gateway , 简称为 CG )相连， 计费网关和账单系统（ Billing System, 简称为 BS )相连。 下面详细描述各部分功能： 签约用户 艮务器， 是用户签约数据的永久存放地点， 位于用户签约的归 属网； 移动性管理单元， 是用户签约数据在当前网络的存放地点， 负责终端到 网络的非接入层信令管理、 终端的安全验证功能、 终端的移动性管理、 用户 空闲模式下的跟踪和寻呼管理功能、 和承载管理； 月艮务网关， 是核心网到无线系统的网关， 负责终端到核心网的用户面 载、 终端空闲模式下的数据緩存、 网络侧发起业务请求的功能、 合法监听和 分组数据路由和转发功能； 服务网关负责统计用户终端使用无线网的情况， 并产生终端使用无线网的话单， 传送给计费网关； 分组数据网关， 是演进系统和该系统外部分组数据网络的网关， 它连接 到因特网和分组数据网络上， 负责终端的互联网协议 （ Internet Protocol , 简 称为 IP )地址分配、 计费功能、 分组包过滤、 策略控制等功能。 分局数据网 关负责统计用户终端使用分组数据网络的话单， 传送给计费网关； 策略计费规则功能实体， 是演进系统中负责提供计费控制、 在线信用控 制、 门限控制、 月艮务质量 ( Quality of Service, 简称为 QoS )策略方面规则的 月艮务器； 运营商的 IP业务网络， 是运营商的业务网络， 该网络通过演进系统为 用户提供 IP服务； 计费网关， 用于收集用户在服务网关和分组数据网关上产生的话单， 并 传送到账单系统中； 账单系统，用于才艮据运营商配置的费率和计费网关发来的话单生成详细 的话费账单； 无线网， 是由演进基站 （ E-UTRAN NodeB , 简称 eNB ) 组成， 它主要 负责无线信号的收发，通过空中接口和终端联系， 管理空中接口的无线资源、 资源调度、 接入控制； 终端， 在演进系统中的状态分为两种， 一种是移动性管理状态， 另一种 是连接管理状态。 移动性管理状态用来监测终端在网络的移动性管理相关的 信息， 它有两个状态， 注册状态和非注册状态。 注册状态表明终端已经在演 进系统中注册， 网络有其的上下文信息， 位置信息等， 终端可以通过演进系 统使用业务； 非注册状态表明终端未在演进系统中注册， 演进系统没有其上 下文信息和位置信息， 终端不能在演进系统中使用业务。 连接管理状态用于 注册 态的终端， 用来监控注册 态的终端和移动性管理单元之间的信令连 接状态， 它有两个状态， "空闲" 和 "连接 "。 "空闲" 状态表明终端和移动性 管理单元之间没有非接入层信令连接， 不能传送非接入层信令， 终端不能通 过演进系统收发数据； "连接"状态表明终端和移动性管理单元之间有非接入 层信令连接， 可以传送非接入层信令， 终端可以通过演进系统收发数据。 注 册状态的终端， 如果它的连接管理状态为空闲状态， 则该终端必须要发起业 务请求流程来将其转为连接状态。 家庭基站 （Home eNB , 简称为 HeNB ) 是演进基站的一种， 作为某些 用户的专属资源， 部署在家庭、 团体、 公司或者学校等私人场所使用， 家庭 基站只属于一些用户所有， 只能为这些用户和其他^ U曼权的用户使用。 家庭 基站的拥有者和拥有者 4曼权的用户组成一个团体， 叫故内部用户组 ( Closed Subscriber Group , 简称 CSG ), 这些家庭基站都属于内部用户组的专属资源， 只有内部用户组用户才能接入使用。 在部署家庭基站的演进系统里面， 还有配置服务器 （ Configuration Server, 简称为 CS )。 配置服务器里面存储有关于内部用户组的所有数据， 这些数据包括： 每个内部用户组的内部用户组标识 ( CSG Identity, 简称为 CSG ID )、 内部用户组包括的所有用户的列表、 内部用户组所有的家庭基站 的设备号 （HeNB ID ) 及其管理员标识。 配置服务器还包括内部用户组对应 的计费规则、 服务质量等信息。 内部用户组内部可能还有不同的用户类型， 这时， 配置服务器还会保存针对同一内部用户组不同用户类型的计费规则、 服务质量等信息。 配置服务器可以单独设置， 也可以根据运营商需要， 和签 约用户服务器合设。 配置服务器和策略计费规则服务器有互通的接口， 策略 计费规则 艮务器可以到配置 艮务器上查询相关计费和艮务质量信息。 每个内部用户组用一个在移动网络 ( Public Land Mobile Network, 简称 为 PLMN ) 里面唯一的标志进行标识， 这个标识叫内部用户组标识 （CSG Identity, 简称为 CSG ID )。 内部用户组的覆盖区域由它所拥有的家庭基站小 区组成。 家庭基站的小区叫内部用户组小区。 用户可能会属于多个内部用户组，所以用户需要知道哪些内部用户组所 属的资源允许其接入， 因此， 演进系统为内部用户组用户分配一个白列表 ( allowed CSG list ) , 白列表里面包含用户被允许接入的内部用户组的标识。 只有内部用户组的标识在这个白列表中，该内部用户组才允许该用户的接入。 这样，就可以有效地保证内部用户组的资源只有内部用户组的用户才能使用。 演进系统通过白列表来控制用户对家庭基站的接入。 当终端检测到内部用户组小区的无线信号时，首先要接收该小区广播信 息，检查广播信息中的内部用户组标识在不在终端中的白列表中。如果不在， 则不选择该小区作为终端的服务小区； 如果在， 就选择该小区作为服务小区。 对于不同内部用户组的成员， 网络计费可能是不同的， 对于同一个内部 用户组中不同类别成员的计费也可能是不同的。 另外， 内部用户组中某些客 人成员的终端对内部用户组资源的使用有可能让内部用户组管理者获得话费 上的减免或者优惠。 所以， 对于内部用户组成员的终端计费， 网络需要知道 在该终端发起业务时， 使用的是哪个内部用户组。 在演进系统中， 当终端处于空闲状态时， 要通过演进系统发起业务， 必 须要发起业务请求流程， 建立终端到核心网的承载， 用于传输业务。 在业务 请求流程中， 演进系统为该终端的所有激活的承载重建终端到基站之间的所 有无线 7|载和 S 1接口 载。 终端在处于空闲状态时，终端在演进系统中注册的可能是多个内部用户 组， 终端在这些注册后的内部用户组所属的小区之间移动时， 不会发起 3艮踪 区更新流程， 因此， 演进系统不知道空闲状态的终端到底在哪个内部用户组 的小区之中。 同时， 在现有技术的业务请求流程中， 基站在转发业务请求消息时， 会 将该消息来源的小区标识也一起发送给移动性管理单元， 演进网络会根据该 小区标识对终端进行计费。 现在客户对话费的精确账单的要求越来越高。因为不同客户在不同的内 部用户组中， 根据不同用户类别会产生不同的话费， 所以， 客户希望能在话 费账单中显示出其在不同内部用户组中的消费。 然而， 所以移动性管理单元 不能从该小区标识获知终端的内部用户组， 因此无法让演进网络对该终端实 施区别内部用户组的区别计费。 另外， 在现有流程中， 无法让演进网络知道 该终端的用户类别， 也不能对同一内部用户组的不同成员进行区别计费， 这 样， 就做不到让运营商根据客人成员的用户类别使用业务的话费情况， 减免 管理者成员的话费。 发明内容 本发明旨在提供一种区别用户计费规则的计费方法和系统，以解决上述 现有技术中不能针对用户所属的内部用户组及其用户类别进行区别计费的问 题。 为了实现上述目的， 才艮据本发明的一个方面， 提供了一种区别用户计费 规则的计费方法。 根据本发明的区别用户计费规则的计费方法包括以下步骤：在终端发起 业务请求后， 移动性管理单元获得所述终端所属家庭基站的内部用户组标识 及其在所述内部用户组中的用户类别； 策略计费功能实体才艮据所述家庭基站 内部用户组标识和所述用户类别选择相应的计费规则； 服务网关或者分组数 据网关将所述家庭基站内部用户组标识、 所述用户类别信息和所述相应的计 费规则加入到所请求业务的话单中进行计费。 尤选地，移动性管理单元获得所述终端所属家庭基站的内部用户组标识 及其在所述内部用户组中的用户类别信息具体包括： 家庭基站收到来自所述 终端的所述业务请求； 所述家庭基站确定其所属的内部用户组为所述终端所 属的内部用户组 ,并将所述家庭基站内部用户组标识发送给移动性管理单元； 所述移动性管理单元查询所述终端的签约数据， 从中获知所述终端在所述内 部用户组中的用户类别。 优选地，移动性管理单元获得所述终端所属家庭基站的内部用户组标识 及其在所述内部用户组中的用户类别信息具体包括： 家庭基站收到来自所述 终端的所述业务请求； 所述家庭基站确定其所属的内部用户组为所述终端所 属的内部用户组， 及其在所述内部用户组中的用户类别； 所述家庭基站将所 述内部用户组标识和所述用户类别信息发送给移动性管理单元。 优选地 ,策略计费功能实体才艮据所述内部用户组标识和所述用户类别信 息选择相应的计费规则具体包括： 所述移动性管理单元将所述内部用户组标 识和所述用户类别信息发送给月艮务网关； 所述月艮务网关将所述内部用户组标 识和所述用户类别信息发送给分组数据网关； 所述分组数据网关从策略计费 规则功能实体中检索到与所述内部用户组标识和所述用户类别信息相对应的 所述计费规则。 尤选地 , 月艮务网关或者分组数据网关将所述内部用户组标识、 所述用户 类别信息和所述相应的计费规则加入到话单中进行计费具体包括： 所述服务 网关将所述内部用户组标识和所述用户类别信息加入到其关于所请求业务的 话单中， 并将该话单发送给计费网关； 所述分组数据网关将所述内部用户组 标识、所述用户类别信息和所述计费规则加入到其关于所请求业务的话单中， 并将该话单发送给所述计费网关。 优选地， 所述终端在执行所请求业务的连接过程中发生切换， 还包括： 移动性管理单元获得所述终端所属家庭基站的新内部用户组标识及其在所属 新的内部用户组中的新用户类别信息； 策略计费功能实体才艮据所述新的内部 用户组标识和所述新的用户类别信息选择相应的新的计费规则； 服务网关或 者分组数据网关将所述新的内部用户组标识、 所述新的用户类别信息和所述 新的计费规则加入到所请求业务的话单中进行计费。 优选地，移动性管理单元获得所述终端所属的新的家庭基站内部用户组 标识及其在所述新的内部用户组中的新的用户类别信息具体包括： 新的家庭 基站收到来自所述终端的切换请求； 所述新的家庭基站确定其所属的内部用 户组为所述终端所属的新的内部用户组， 并将所述新的内部用户组标识发送 给移动性管理单元； 所述移动性管理单元查询所述终端的签约数据， 从中获 知所述终端在所述新的家庭基站内部用户组中的新的用户类别。 优选地，移动性管理单元获得所述终端所属的新的家庭基站内部用户组 标识及其在所述新的内部用户组中的新的用户类别信息具体包括： 新的家庭 基站收到来自所述终端的切换请求； 所述新的家庭基站确定其所属的内部用 户组为所述终端所属的新的内部用户组， 及其在所述新的内部用户组中的新 的用户类别； 所述家庭基站将所述新的内部用户组标识和所述新的用户类别 信息发送给移动性管理单元。 优选地，策略计费功能实体 #居所述新的内部用户组标识和所述新的用 户类别信息选择相应的新的计费规则具体包括： 所述移动性管理单元将所述 新的组标识和所述新的类别信息发送给服务网关； 所述服务网关将所述新的 组标识和所述新的类别信息发送给分组数据网关； 所述分组数据网关从策略 计费规则功能实体中检索到与所述新的组标识和所述新的类别信息相对应的 所述新的计费规则。 优选地， 月艮务网关或者分组数据网关将所述新的内部用户组标识、 所述 新的用户类别信息和所述新的计费规则加入到所请求业务的话单中进行计费 具体包括： 所述月艮务网关将所述新的内部用户组标识和所述新的用户类别信 息加入到其关于所请求业务的话单中， 并将该话单发送给计费网关； 所述分 组数据网关将所述新的内部用户组标识、 所述新的用户类别信息和所述新的 计费规则加入到其关于所请求业务的话单中， 并将该话单发送给所述计费网 关。 优选地， 所述计费网关进行计费具体包括： 所述计费网关收集来自所述 服务网关和所述分组数据网关的话单；所述计费网关将收集的话单进行合并， 发送到账单系统； 所述账单系统对所述合并的话单执行计费操作， 以生成详 细话单， 其中， 所述计费操作才艮据所述合并到话单中的计费规则来进行计算。 为了实现上述目的， 才艮据本发明的另一个方面， 提供了一种区别用户计 费规则的计费方法。 根据本发明的区别用户计费规则的计费方法，用于终端在执行所请求业 务的连接过程中发生切换时， 包括以下步骤： 移动性管理单元获得所述终端 所属家庭基站的新内部用户组标识及其在所属新的内部用户组中的新用户类 别信息； 策略计费功能实体根据所述新的内部用户组标识和所述新的用户类 别信息选择相应的新的计费规则； 服务网关或者分组数据网关将所述新的内 部用户组标识、 所述新的用户类别信息和所述新的计费规则加入到所请求业 务的话单中进行计费。 为了实现上述目的， 才艮据本发明的又一个方面， 提供了一种区别用户计 费规则的计费方法。 根据本发明的区别用户计费规则的计费方法包括以下步骤：用户通过家 庭基站接入核心网时， 移动性管理单元将家庭基站内部用户组标识和用户类 别信息发送给服务网关； 所述服务网关将所述家庭基站内部组标识和所述用 户类别信息发送给分组数据网关； 所述分组数据网关与策略计费规则功能实 体进行交互， 获取与所述内部用户组标识和所述用户类别信息相对应的所述 计费规则。 为了实现上述目的， 才艮据本发明的再一个方面， 提供了一种区别用户计 费规则的计费系统。 根据本发明的区别用户计费规则的计费系统包括： 家庭基站， 用于收到 来自终端的请求消息， 确定所述终端所属的内部用户组； 移动性管理单元， 用于接收来自所述家庭基站的所述内部用户组标识， 查询所述终端的签约数 据， 获知所述终端在所述内部用户组中的用户类别； 月艮务网关， 用于接收和 转发来自所述移动性管理单元的所述内部用户组标识和所述用户类别信息， 并将所述内部用户组标识和所述用户类别信息加入到其关于所请求业务的话 单中； 分组数据网关， 用于接收来自所述服务网关的所述内部用户组标识和 所述用户类型信息， 与策略计费规则功能实体交互获得与所述内部用户组标 识和所述用户类别信息相对应的所述计费规则， 并将所述内部用户组标识、 所述用户类别信息和所述计费规则加入到其关于所请求业务的话单中； 策略 计费规则功能实体， 用于保存各种计费规则； 计费网关， 用于收集来自所述 服务网关的话单和来自所述分组数据网关的话单， 将收集的话单进行合并； 账单系统， 用于对来自所述计费网关的所述合并的话单执行计费操作， 以生 成详细话单， 其中， 所述计费操作才艮据所述合并到话单中的计费规则来进行 计算。 上述的区别计费方法和系统因为将内部用户组标识和用户类别信息通 知到服务网关和分组数据网关， 所以解决了现有技术中不能针对用户所属的 内部用户组及其用户类别进行区别计费的问题， 进而能区别不同内部用户组 和不同用户类别， 以实现灵活精确的计费。 附图说明 此处所说明的附图用来提供对本发明的进一步理解 ,构成本申请的一部 分， 本发明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的 不当限定。 在附图中： 图 1示出了根据相关技术的演进系统的系统结构的示意图； 图 2 示出了根据本发明实施例的区别用户计费规则的计费方法的流程 图； 图 3 示出了根据本发明实施例一的区别用户类别的业务请求流程的信 令流程图； 图 4 示出了才艮据本发明实施例二的移动管理单元和月艮务网关都不变时 切换的信令流程图； 图 5 示出了根据本发明实施例三的移动管理单元不变但服务网关改变 时切换的信令流程图； 图 6 示出了才艮据本发明实施例四的移动管理单元和月艮务网关都改变时 切换的信令流程图； 图 7 示出了根据本发明实施例五的分组数据网关从策略计费规则服务 器取计费规则的信令流程图。 具体实施方式 下面将参考附图并结合实施例， 来详细说明本发明。 需要说明的是， 在 不冲突的情况下， 本申请中的实施例及实施例中的特征可以相互组合。 图 2 示出了根据本发明实施例的区别用户计费规则的计费方法的流程 图， 包括以下步骤： 步骤 S10, 移动性管理单元获得终端所属家庭基站的内部用户组标识及 其在内部用户组中的用户类别； 步骤 S20, 策略计费功能实体根据家庭基站内部用户组标识和用户类别 选择相应的计费规则； 步骤 S30 , 服务网关或者分组数据网关将家庭基站内部用户组标识、 用 户类别信息和相应的计费规则加入到所请求业务的话单中进行计费。 家庭基站部署之后， 运营商和客户都希望能有灵活的计费方法， 如果没 有能区别不同内部用户组和不同用户类别的方法， 就无法故到灵活计费。 现 有技术是根据 'J、区标识来区别计费的， 而小区标识里面不会包含内部用户组 标识信息，所以不能针对用户所属的内部用户组及其用户类别进行区别计费。 上述实施例的区别计费方法因为将内部用户组标识和用户类别信息通 知到月艮务网关和分组数据网关， 从而能够知道终端在使用哪个内部用户组的 资源， 该终端属于内部用户组中的哪个用户类别， 所以克服了现有技术中不 能针对用户所属的内部用户组及其用户类别进行区别计费的问题， 进而能区 别不同内部用户组和不同用户类别以实现灵活 4青确的计费。 优选地， 步骤 S 10具体包括： 家庭基站收到来自终端的业务请求； 家庭 基站确定其所属的内部用户组为终端所属的内部用户组， 并将家庭基站内部 用户组标识发送给移动性管理单元； 移动性管理单元查询终端的签约数据， 从中获知终端在内部用户组中的用户类别。 优选地， 步骤 S 10具体包括： 家庭基站收到来自终端的业务请求； 家庭 基站确定其所属的内部用户组为终端所属的内部用户组， 及其在内部用户组 中的用户类别； 家庭基站将内部用户组标识和用户类别信息发送给移动性管 理单元。 上述优选实施例给出了确定终端的内部用户组和用户类别的两种方案。 优选地， 步骤 S20具体包括： 移动性管理单元将内部用户组标识和用户 类别信息发送给服务网关； 服务网关将内部用户组标识和用户类别信息发送 给分组数据网关； 分组数据网关与策略计费规则功能实体交互从中获得与内 部用户组标识和用户类别信息相对应的计费规则。 优选地， 步骤 S30具体包括： 服务网关将内部用户组标识和用户类别信 息加入到其关于所请求业务的话单中， 并将该话单发送给计费网关； 分组数 据网关将内部用户组标识、 用户类别信息和计费规则加入到其关于所请求业 务的话单中， 并将该话单发送给计费网关。 在上述实施例的流程中， 家庭基站如果收到某个用户的终端的业务请 求， 该家庭基站要将该基站所属的内部用户组标识发送给移动性管理单元。 移动性管理单元查询该用户的签约数据， 获知该用户在当前内部用户组中的 用户类别， 然后将内部用户组标识和用户类别发送给服务网关， 让服务网关 将内部用户组标识和用户类别信息加入到该用户的话单中。 由于用户在通话过程中时， 终端处于连接状态， 当终端在不同小区之间 移动的时候， 要发起切换流程。 优选地， 该计费方法还包括： 移动性管理单元获得终端所属的新的家庭基站内部用户组标识及其在 新的内部用户组中的新的用户类别信息； 策略计费规则功能实体才艮据新的内部用户组标识和新的用户类别信息 选择相应的新的计费规则； 服务网关或者分组数据网关将新的内部用户组标识、新的用户类别信息 和新的计费规则加入到所请求业务的话单中进行计费。 如果终端处于连接状态， 在不同的小区之间移动会触发切换流程， 在切 换流程之后， 会根据情况发起跟踪区更新流程， 更新核心网中终端的位置信 息。 该优选实施例解决了切换过程中的区别计费问题。 优选地，移动性管理实体获得终端所属的新的家庭基站内部用户组标识 及其在新的内部用户组中的新的用户类别具体包括： 新的家庭基站 （即， 切 换后的目标基站） 收到来自终端的切换请求； 新的家庭基站确定其所属的内 部用户组为终端所属的新的内部用户组， 并将新的内部用户组标识发送给移 动性管理单元； 移动性管理单元查询终端的签约数据， 从中获知终端在新的 内部用户组中的新的用户类别。 优选地，移动性管理单元获得终端所属的新的内部用户组标识及其在新 的内部用户组中的新的用户类别具体包括： 新的家庭基站收到来自终端的切 换请求； 新的家庭基站确定其所属的内部用户组为终端所属的新的内部用户 组， 及其在新的内部用户组中的新的用户类别； 家庭基站将新的内部用户组 标识和新的用户类别的新的类别信息发送给移动性管理单元。 优选地，策略计费规则功能实体根据新的内部用户组标识和新的用户类 别信息选择相应的新的计费规则具体包括： 移动性管理单元将新的内部用户 组标识和新的用户类别信息发送给服务网关； 服务网关将新的内部用户组标 识和新的用户类别信息发送给分组数据网关； 分组数据网关与策略计费规则 功能实体交互获得与新的内部用户组标识和新的用户类别信息相对应的新的 计费规则。 优选地， 月艮务网关和分组数据网关将新的内部用户组标识、新的用户类 别信息和新的计费规则加入到所请求业务的话单中进行计费具体包括： 服务 网关将新的内部用户组标识和新的用户类别信息加入到其关于所请求业务的 话单中， 并将该话单发送给计费网关； 分组数据网关将新的内部用户组标识、 新的用户类别信息和新的计费规则加入到其关于所请求业务的话单中， 并将 该话单发送给计费网关。 优选地， 计费网关进行计费具体包括： 计费网关收集来自服务网关和分 组数据网关的话单； 计费网关将收集的话单进行合并， 发送到账单系统； 账 单系统对合并的话单执行计费操作， 以生成详细话单， 其中， 计费操作根据 合并到话单中的计费规则来进行计算。 以上的切换流程将用户当前所使用的内部用户组标识和用户类型传送 给服务网关和分组数据网关。 如果演进系统中部署策略计费规则服务器， 那 么分组数据网关会和策略计费规则服务器交互， 根据用户的内部用户组和用 户类别从策略计费规则服务器取个性化的计费方式保存在分组数据网关中以 生成个性化的话单。 本发明的一个实施例提供了一种区别用户计费规则的计费系统， 包括： 家庭基站，用于收到来自终端的请求消息，确定终端所属的内部用户组； 移动性管理单元， 用于接收来自家庭基站的内部用户组标识， 查询终端 的签约数据， 获知终端在内部用户组中的用户类别； 月艮务网关，用于接收和转发来自移动性管理单元的内部用户组标识和用 户类别信息， 并将内部用户组标识和用户类别信息加入到其关于所请求业务 的话单中； 分组数据网关，用于接收来自服务网关的内部用户组标识和用户类型信 息， 与策略计费规则功能实体交互获得与内部用户组标识和用户类别信息相 对应的计费规则， 并将内部用户组标识、 用户类别信息和计费规则加入到其 关于所请求业务的话单中； 策略计费规则功能实体， 用于保存各种计费规则； 计费网关， 用于收集来自服务网关的话单和来自分组数据网关的话单， 将收集的话单进行合并； 账单系统， 用于对来自计费网关的合并的话单执行计费操作， 以生成详 细话单， 其中， 计费操作根据合并到话单中的计费规则来进行计算。 以上的计费系统因为将内部用户组标识和用户类别信息通知到月艮务网 关和分组数据网关， 所以克服了现有技术中不能针对用户所属的内部用户组 及其用户类别进行区别计费的问题， 进而能区别不同内部用户组和不同用户 类别以实现灵活精确的计费。 下面详细阐述区别用户类别的业务请求流程的实例流程图。 实施例一 图 3 示出了才艮据本发明实施例一的区别用户类别的业务请求流程的信 令流程图， 具体包括如下步骤： 步骤 301 , 在终端接入家庭基站之后， 家庭基站要对该终端执行 3 证流 程， 通过对比终端的标识和内部用户组列表， 确定终端的身份； 这时， 家庭 基站知道该终端所在的内部用户组标识和用户类另 ij(例如，拥有者或者客人 )„ 步骤 302, 网络可能对应该家庭基站下面的某终端有下行数据或者信 令， 则网络寻呼该终端， 触发终端发起业务请求流程， 终端也可能由于有上 行数据或者信令发送， 但是却和网络没有信令连接， 处于空闲状态， 这时终 端发起业务请求流程。 步骤 303 , 终端向移动性管理单元发送业务请求消息。 该业务请求消息 封装在无线资源控制消息中传送到家庭基站。 步骤 304, 家庭基站如果验证该终端的身份成功后。 将该终端在 S1接 口上的标识、 从终端收到的业务请求消息、 收到该消息的小区的小区标识、 该终端当前使用的内部用户组标识等数据封装到 S1 接口应用协议的初始终 端消息中， 然后将该初始终端消息发送给移动性管理单元。 步骤 305 , 移动性管理单元收到步骤 304发送来的业务请求消息之后， 根据该终端在移动性管理单元中保存的数据判断是否对该终端发起安全验 证， 如果需要， 就对该终端执行验证流程。 步骤 306, 移动性管理单元在确认该终端已经被验证之后， 向家庭基站 发送 S1 应用协议初始上下文建立请求消息， 消息中包含服务网关的地址、 S1接口上行的隧道标识、 7|载 艮务质量、 安全上下文、 移动性管理单元信令 连接标识、 切换限制列表等参数。 这个步骤为该终端的所有的激活的承载激 活无线和 S1 接口承载。 家庭基站收到初始上下文建立请求消息后， 保存该 消息中的所有参数到终端的上下文中。 步骤 307 , 家庭基站执行无线承载建立流程， 并为用户建立用户面的安 全通道。 步骤 308 , 这时家庭基站可以将终端发来的上行数据转发到服务网关。 步骤 309, 家庭基站向移动性管理单元发送 S1应用协议初始上下文建 立完毕消息， 消息中包含家庭基站的地址、 S1接口下行隧道标识以及其他必 要参数。 步骤 310, 移动性管理单元查询本地保存的该终端的签约数据， 确定该 终端在当前内部用户组中的用户类别。 移动管理单元向月艮务网关发送更新 载请求消息， 消息中包含家庭基站地址、 S1接口下行隧道标识、 无线接入技 术类型、 延迟下行数据通知标识、 内部用户组标识、 用户类型等数据。 月艮务网关在对该终端计费的时矣，如果该终端还在使用当前的内部用户 组标识就将该终端当前使用的内部用户组标识和用户类型标识加入该终端产 生的话单中， 在规定的时间发送给计费网关， 计费网关和后台程序根据该话 单的内部用户组标识和用户类型进行区别计费， 话费补偿等操作， 并生成为 单个用户的详细话单， 包括该用户在哪个内部用户组下面使用过业务， 以及 业务产生的费用。 如果用户终端在通话的过程中，切换到了非当前内部用户组的其他内部 用户组的资源的时候， 目标家庭基站就会上报一个新的内部用户组标识和用 户类别给移动性管理单元， 移动性管理单元将这个新的内部用户组标识和用 户类别通知月艮务网关。 步骤 311 , 服务网关向分组数据网关发送更新承载请求消息， 消息中包 含该终端的标识、 内部用户组标识、 用户类型等数据。 步骤 312, 如果网络中部署动态的策略计费控制， 那么分组数据网关和 策略计费规则月艮务器交互获得针对不同内部用户组和用户类型的计费策略。 本步骤在实施例五中故详细说明。 步骤 313 , 分组数据网关向月艮务网关发送更新 载响应。 步骤 314, 月艮务网关向移动性管理单元发送更新 载响应。 实施例二 图 4 示出了根据本发明实施例二的移动管理单元和服务网关都不变时 切换的信令流程图。本流程发生时， 终端的服务网关和移动管理单元都不变， 移动性管理单元需要向月艮务网关更新内部用户组标识和用户类型信息。 具体 包括的步骤如下： 步骤 401 , 终端在连接状态的时候， 如果从源基站小区进入目的家庭基 站小区， 发起切换流程， 接入到家庭基站小区中。 步骤 402, 如果源基站为宏基站， 目的家庭基站通过空中接口信令触发 终端发起 3艮踪区更新流程。 步骤 403 , 终端向移动管理单元发送跟踪区更新请求消息， 该消息中包 含该终端的标识、 当前使用小区的内部用户组标识以及其他信息。 步骤 404, 移动管理单元对该终端进行验证。 步骤 405 , 移动管理单元才艮据该终端的标识、 所使用的内部用户组的标 识， 从保存在本地的该终端的签约数据中查询到该终端所属的用户类型。 移动管理单元向服务网关发送更新承载请求消息，该消息中包含该终端 的标识、 内部用户组标识、 用户类型等信息。 步骤 406 , 服务网关收到步骤 405发来的更新承载请求消息之后， 将该 终端的用户组标识、 用户类型信息保存在本地， 用于生成该用户在该内部用 户组小区下面的话单。 然后， 服务网关向分组数据网关发送更新承载请求消 息， 该消息中包含该终端的标识、 内部用户组标识、 用户类型等信息。 步骤 407, 分组数据网关收到步骤 406发来的更新承载请求消息之后， 将该用户的内部用户组标识和用户类型保存在本地用于生成话单。 如果演进 系统中部署策略规则计费服务器， 那么分组数据网关就和该服务器交互， 根 据用户的内部用户组标识和用户类型获得个性化的计费策略保存在分组数据 网关中。 本步骤详细见实施例五。 步骤 408 , 分组数据网关向服务网关发送更新承载响应消息。 步骤 409 , 服务网关向移动管理单元发送更新承载响应消息。 步骤 410, 演进系统和终端完成后续的 3艮踪区更新流程。 上述流程提供了从非家庭基站的基站小区进入家庭基站小区的切换流 程， 主要是要服务网关和分组数据网关知道进入的家庭基站小区的内部用户 组以及用户的类型。 本实施例也可以用于终端从一个内部用户组的家庭基站切换到另外一 个内部用户组的家庭基站的场景。 如果终端从家庭基站切换到宏基站，那么核心网在随后发起的跟踪区更 新流程中会在以上的步骤 405 , 406 里面将跟踪区标识发送给服务网关和分 组数据网关， 这样服务网关和分组数据网关检测到终端已经离开了内部用户 组的小区， 艮务网关和分组数据网关就停止按原有的内部用户组标识对该终 端的计费的操作。 实施例三 图 5 示出了根据本发明实施例三的移动管理单元不变但服务网关改变 时切换的信令流程图， 本流程发生时， 终端的服务网关改变了， 移动性管理 单元需要向服务网关更新内部用户组标识和用户类型信息。 具体包括的步骤 ^口下： 步骤 501 , 终端在连接状态的时候， 如果从源基站小区进入目的家庭基 站小区， 发起切换流程， 接入到家庭基站小区中。 步骤 502, 如果源基站为宏基站， 目的家庭基站通过空中接口信令触发 终端发起 3艮踪区更新流程。 步骤 503 , 终端向移动管理单元发送跟踪区更新请求消息， 该消息中包 含该终端的标识、 当前使用小区的内部用户组标识以及其他信息。 步骤 504, 移动管理单元对该终端进行验证。 步骤 505 , 移动管理单元才艮据该终端的标识、 所使用的内部用户组的标 识， 从保存在本地的该终端的签约数据中查询到该终端所属的用户类型。 移动管理单元向服务网关发送更新承载请求消息，该消息中包含该终端 的标识、 内部用户组标识、 用户类型等信息。 步骤 506, 服务网关收到步骤 505发来的更新承载请求消息之后， 将该 终端的用户组标识、 用户类型信息保存在本地， 用于生成该用户在该内部用 户组小区下面的话单。 然后， 服务网关向分组数据网关发送更新承载请求消 息， 该消息中包含该终端的标识、 内部用户组标识、 用户类型等信息。 步骤 507, 分组数据网关收到步骤 506发来的更新承载请求消息之后， 将该用户的内部用户组标识和用户类型保存在本地用于生成话单。 如果演进 系统中部署策略规则计费服务器， 那么分组数据网关就和该服务器交互， 根 据用户的内部用户组标识和用户类型获得个性化的计费策略保存在分组数据 网关中。 本步骤详细见实施例五。 步骤 508 , 分组数据网关向服务网关发送更新承载响应消息。 步骤 509, 服务网关向移动管理单元发送更新承载响应消息。 步骤 510, 演进系统和终端完成后续的 3艮踪区更新流程。 上述流程提供了从非家庭基站的基站小区进入家庭基站小区的切换流 程， 主要是要服务网关和分组数据网关知道进入的家庭基站小区的内部用户 组以及用户的类型。 本实施例也可以用于终端从一个内部用户组的家庭基站切换到另外一 个内部用户组的家庭基站的场景。 如果终端从家庭基站切换到宏基站，那么核心网在随后发起的跟踪区更 新流程中会在以上的步骤 505 , 506 里面将跟踪区标识发送给服务网关和分 组数据网关， 这样服务网关和分组数据网关检测到终端已经离开了内部用户 组的小区， 艮务网关和分组数据网关就停止按原有的内部用户组标识对该终 端的计费的操作。 实施例四 图 6 示出了才艮据本发明实施例四的移动管理单元和月艮务网关都改变时 切换的信令流程图，本流程发生时， 终端的服务网关和移动管理单元改变了， 移动性管理单元需要向月艮务网关更新内部用户组标识和用户类型信息。 具体 包括的步骤如下： 步骤 601 , 终端在连接状态的时候， 如果从源基站小区进入目的家庭基 站小区， 发起切换流程， 接入到家庭基站小区中。 步骤 602, 如果源基站为宏基站， 目的家庭基站通过空中接口信令触发 终端发起 3艮踪区更新流程。 步骤 603 , 终端向移动管理单元发送跟踪区更新请求消息， 该消息中包 含该终端的标识、 当前使用小区的内部用户组标识以及其他信息。 步骤 604, 移动管理单元对该终端进行验证。 步骤 605 , 移动管理单元才艮据该终端的标识、 所使用的内部用户组的标 识， 从保存在本地的该终端的签约数据中查询到该终端所属的用户类型。 移动管理单元向服务网关发送更新承载请求消息，该消息中包含该终端 的标识、 内部用户组标识、 用户类型等信息。 步骤 606 , 服务网关收到步骤 605发来的更新承载请求消息之后， 将该 终端的用户组标识、 用户类型信息保存在本地， 用于生成该用户在该内部用 户组小区下面的话单。 然后， 服务网关向分组数据网关发送更新承载请求消 息， 该消息中包含该终端的标识、 内部用户组标识、 用户类型等信息。 步骤 607, 分组数据网关收到步骤 606发来的更新承载请求消息之后， 将该用户的内部用户组标识和用户类型保存在本地用于生成话单。 如果演进 系统中部署策略规则计费服务器， 那么分组数据网关就和该服务器交互， 根 据用户的内部用户组标识和用户类型获得个性化的计费策略保存在分组数据 网关中。 本步骤详细见实施例五。 步骤 608 , 分组数据网关向服务网关发送更新承载响应消息。 步骤 609 , 服务网关向移动管理单元发送更新承载响应消息。 步骤 610, 演进系统和终端完成后续的 3艮踪区更新流程。 上述流程提供了从非家庭基站的基站小区进入家庭基站小区的切换流 程， 主要是要服务网关和分组数据网关知道进入的家庭基站小区的内部用户 组以及用户的类型。 本实施例也可以用于终端从一个内部用户组的家庭基站切换到另外一 个内部用户组的家庭基站的场景。 如果终端从家庭基站切换到宏基站，那么核心网在随后发起的跟踪区更 新流程中会在以上的步骤 605 , 606 里面将跟踪区标识发送给服务网关和分 组数据网关， 这样服务网关和分组数据网关检测到终端已经离开了内部用户 组的小区， 就停止按原有的内部用户组标识对该终端的计费的操作。 实施例五 图 7 示出了根据本发明实施例五的分组数据网关从策略计费规则服务 器取计费规则的信令流程图， 具体包括的步骤如下： 步骤 701 , 分组数据网关检测到某个连接状态终端的当前使用的内部用 户组标识变化之后， 准备和策略计费规则服务器交互获得该用户终端在当前 内部用户组下面的计费策略。 步骤 702, 分组数据网关向策略计费规则服务器发送策略计费规则请求 消息， 消息中包含有该终端的标识、 该终端当前使用的内部用户组标识、 用 户类型等信息。 如果策略计费规则月艮务器当前保存有关于该终端的当前内部用户组的 相关计费信息， 那就直接发起步骤 705。 如果没有， 就继续步骤 703。 步骤 703 , 策略计费规则服务器向配置服务器发送查询请求消息， 查询 请求中包含该终端的标识、 该终端当前使用的内部用户组标识、 该终端的用 户类型信息， 该消息也可以包含其他要查询的信息。 步骤 704, 配置月艮务器查询到该终端在当前内部用户组的计费相关信息 之后， 向策略计费规则服务器发送查询响应消息， 消息中包含该终端在当前 内部用户组的计费规则、 服务质量相关信息以及其他必要信息。 步骤 705 , 策略计费规则服务器收到查询响应消息后， 保存查询响应中 的数据。 步骤 706, 然后向分组数据网关发送策略计费规则响应消息， 消息中包 含该终端标识、 该终端在当前内部用户组内的计费规则、 服务质量相关信息 以及其他必要信息。 步骤 707 , 分组数据网关保存该终端在当前内部用户组内的计费规则、 服务质量等相关信息。 才艮据本发明实施例， 还提供了一种计算机可读介质， 该计算机可读介质 上存储有计算机可执行的指令， 当该指令被计算机或处理器执行时， 使得计 算机或处理器执行如图 2至图 7所示的各步骤的处理， 优选地， 可以执行上 述的实施例一至实施例五中的一个或多个。 本发明为不同的内部用户组的用户提供了一种灵活的计费方式，在用户 发起业务以进行通话或者发送数据和在使用业务的时候发起切换的时候， 演 进网络可以将用户所使用的当前内部用户组标识和用户类型发送给服务网关 和分组数据网关， 方便进行区别计费。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布 在多个计算装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程 序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 或 者将它们分别制作成各个集成电路模块， 或者将它们中的多个模块或步骤制 作成单个集成电路模块来实现。 这样， 本发明不限制于任何特定的硬件和软 件结合。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布 在多个计算装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程 序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 或 者将它们分别制作成各个集成电路模块， 或者将它们中的多个模块或步骤制 作成单个集成电路模块来实现。 这样， 本发明不限制于任何特定的硬件和软 件结合。 以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本 领域的技术人员来说， 本发明可以有各种更改和变^^ 凡在本发明的^^申和 原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护 范围之内。

Claims

权 利 要 求 书
1. 一种区别用户计费规则的计费方法， 其特征在于， 包括以下步骤： 在终端发起业务请求后，移动性管理单元获得所述终端所属家庭基 站的内部用户组标识及其在所述内部用户组中的用户类别；
策略计费功能实体才艮据所述家庭基站内部用户组标识和所述用户 类别选择相应的计费规则；
月艮务网关或者分组数据网关将所述家庭基站内部用户组标识、所述 用户类别信息和所述相应的计费规则加入到所请求业务的话单中进行计 费。
2. 根据权利要求 1所述的计费方法， 其特征在于， 移动性管理单元获得所 述终端所属家庭基站的内部用户组标识及其在所述内部用户组中的用户 类别信息具体包括：
家庭基站收到来自所述终端的所述业务请求；
所述家庭基站确定其所属的内部用户组为所述终端所属的内部用 户组， 并将所述家庭基站内部用户组标识发送给移动性管理单元； 所述移动性管理单元查询所述终端的签约数据 ,从中获知所述终端 在所述内部用户组中的用户类别。
3. 根据权利要求 1所述的计费方法， 其特征在于， 移动性管理单元获得所 述终端所属家庭基站的内部用户组标识及其在所述内部用户组中的用户 类别信息具体包括：
家庭基站收到来自所述终端的所述业务请求；
所述家庭基站确定其所属的内部用户组为所述终端所属的内部用 户组， 及其在所述内部用户组中的用户类别；
所述家庭基站将所述内部用户组标识和所述用户类别信息发送给 移动性管理单元。
4. 根据权利要求 2或 3所述的计费方法， 其特征在于， 策略计费功能实体 才艮据所述内部用户组标识和所述用户类别信息选择相应的计费规则具体 包括：
所述移动性管理单元将所述内部用户组标识和所述用户类别信息 发送给服务网关；
所述月艮务网关将所述内部用户组标识和所述用户类别信息发送给 分组数据网关； 所述分组数据网关与策略计费规则功能实体交互从中获 得与所述内部用户组标识和所述用户类别信息相对应的所述计费规则。
5. 根据权利要求 4所述的计费方法， 其特征在于， 服务网关或者分组数据 网关将所述内部用户组标识、 所述用户类别信息和所述相应的计费规则 加入到话单中进行计费具体包括：
所述月艮务网关将所述内部用户组标识和所述用户类别信息加入到 其关于所请求业务的话单中， 并将该话单发送给计费网关；
所述分组数据网关将所述内部用户组标识、所述用户类别信息和所 述计费规则加入到其关于所请求业务的话单中， 并将该话单发送给所述 计费网关。
6. 根据权利要求 1所述的计费方法， 其特征在于， 所述终端在执行所请求 业务的连接过程中发生切换， 还包括：
移动性管理单元获得所述终端所属家庭基站的新内部用户组标识 及其在所属新的内部用户组中的新用户类别信息； 策略计费功能实体根据所述新的内部用户组标识和所述新的用户 类别信息选择相应的新的计费规则；
月艮务网关或者分组数据网关将所述新的内部用户组标识、所述新的 用户类别信息和所述新的计费规则加入到所请求业务的话单中进行计 费。
7. 根据权利要求 6所述的计费方法， 其特征在于， 移动性管理单元获得所 述终端所属的新的家庭基站内部用户组标识及其在所述新的内部用户组 中的新的用户类别信息具体包括：
新的家庭基站收到来自所述终端的切换请求； 所述新的家庭基站确定其所属的内部用户组为所述终端所属的新 的内部用户组， 并将所述新的内部用户组标识发送给移动性管理单元； 所述移动性管理单元查询所述终端的签约数据 ,从中获知所述终端 在所述新的家庭基站内部用户组中的新的用户类别。
8. 才艮据权利要求 6所述的计费方法， 其特征在于， 移动性管理单元获得所 述终端所属的新的家庭基站内部用户组标识及其在所述新的内部用户组 中的新的用户类别信息具体包括：
新的家庭基站收到来自所述终端的切换请求；
所述新的家庭基站确定其所属的内部用户组为所述终端所属的新 的内部用户组， 及其在所述新的内部用户组中的新的用户类别；
所述家庭基站将所述新的内部用户组标识和所述新的用户类别信 息发送给移动性管理单元。
9. 根据权利要求 7或 8所述的计费方法， 其特征在于， 策略计费功能实体 才艮据所述新的内部用户组标识和所述新的用户类别信息选择相应的新的 计费规则具体包括：
所述移动性管理单元将所述新的内部用户组标识和所述新的用户 类别信息发送给服务网关；
所述月艮务网关将所述新的内部用户组标识和所述新的用户类别信 息发送给分组数据网关；
所述分组数据网关与策略计费规则功能实体交互获得与所述新的 内部用户组标识和所述新的用户类别信息相对应的所述新的计费规则。
10. 根据权利要求 9所述的计费方法， 其特征在于， 服务网关或者分组数据 网关将所述新的内部用户组标识、 所述新的用户类别信息和所述新的计 费规则加入到所请求业务的话单中进行计费具体包括：
所述月艮务网关将所述新的内部用户组标识和所述新的用户类别信 息加入到其关于所请求业务的话单中， 并将该话单发送给计费网关； 所述分组数据网关将所述新的内部用户组标识、所述新的用户类别 信息和所述新的计费规则加入到其关于所请求业务的话单中， 并将该话 单发送给所述计费网关。
11. 根据权利要求 5或 10所述的计费方法， 其特征在于，所述计费网关进行 计费具体包括：
所述计费网关收集来自所述月艮务网关和所述分组数据网关的话单； 所述计费网关将收集的话单进行合并， 发送到账单系统； 所述账单系统对所述合并的话单执行计费操作 , 以生成详细话单 , 其中， 所述计费操作根据所述合并到话单中的计费规则来进行计算。
12. 一种区别用户计费规则的计费方法， 用于终端在执行所请求业务的连接 过程中发生切换时， 其特征在于， 包括以下步骤：
移动性管理单元获得所述终端所属家庭基站的新内部用户组标识 及其在所属新的内部用户组中的新用户类别信息； 策略计费功能实体根据所述新的内部用户组标识和所述新的用户 类别信息选择相应的新的计费规则；
月艮务网关或者分组数据网关将所述新的内部用户组标识、所述新的 用户类别信息和所述新的计费规则加入到所请求业务的话单中进行计 费。
13. 一种区别用户计费规则的计费方法， 其特征在于， 包括以下步骤：
用户通过家庭基站接入核心网时，
移动性管理单元将家庭基站内部用户组标识和用户类别信息发送 给月艮务网关；
所述月艮务网关将所述家庭基站内部组标识和所述用户类别信息发 送给分组数据网关；
所述分组数据网关与策略计费规则功能实体进行交互，获取与所述 内部用户组标识和所述用户类别信息相对应的所述计费规则。
14. 一种区别用户计费规则的计费系统， 其特征在于， 包括：
家庭基站， 用于收到来自终端的请求消息， 确定所述终端所属的内 "^用户组； 移动性管理单元，用于接收来自所述家庭基站的所述内部用户组标 识， 查询所述终端的签约数据， 获知所述终端在所述内部用户组中的用 户类别； 月艮务网关，用于接收和转发来自所述移动性管理单元的所述内部用 户组标识和所述用户类别信息， 并将所述内部用户组标识和所述用户类 别信息加入到其关于所请求业务的话单中；
分组数据网关，用于接收来自所述服务网关的所述内部用户组标识 和所述用户类型信息， 与策略计费规则功能实体交互获得与所述组标识 和所述类别信息相对应的所述计费规则， 并将所述内部用户组标识、 所 述用户类别信息和所述计费规则加入到其关于所请求业务的话单中； 策略计费规则功能实体， 用于保存各种计费规则；
计费网关，用于收集来自所述服务网关的话单和来自所述分组数据 网关的话单， 将收集的话单进行合并；
账单系统，用于对来自所述计费网关的所述合并的话单执行计费操 作， 以生成详细话单， 其中， 所述计费操作才艮据所述合并到话单中的计 费规则来进行计算。
PCT/CN2009/072645 2008-07-07 2009-07-06 区别用户计费规则的计费方法和系统 WO2010003359A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810130560.3 2008-07-07
CN2008101305603A CN101583113B (zh) 2008-07-07 2008-07-07 区别用户计费规则的计费方法和系统

Publications (1)

Publication Number Publication Date
WO2010003359A1 true WO2010003359A1 (zh) 2010-01-14

Family

ID=41365014

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/072645 WO2010003359A1 (zh) 2008-07-07 2009-07-06 区别用户计费规则的计费方法和系统

Country Status (2)

Country Link
CN (1) CN101583113B (zh)
WO (1) WO2010003359A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112448823A (zh) * 2019-08-30 2021-03-05 中国电信股份有限公司 计费方法、系统以及存储介质
CN114845257A (zh) * 2022-04-07 2022-08-02 中国联合网络通信集团有限公司 基于嵌入式脚本的多量纲计费方法、装置和存储介质

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102104859A (zh) * 2009-12-21 2011-06-22 中兴通讯股份有限公司 离线计费方法及系统
CN102014362A (zh) * 2009-12-28 2011-04-13 大唐移动通信设备有限公司 一种csg信息的发送方法、系统和设备
CN102123368A (zh) * 2010-01-08 2011-07-13 中兴通讯股份有限公司 一种通过家用基站接入的计费策略同步调整方法和系统
CN101800824A (zh) * 2010-03-04 2010-08-11 中兴通讯股份有限公司 一种计费方法和装置
CN102202281B (zh) * 2010-03-24 2015-05-13 中兴通讯股份有限公司 话单处理方法及系统
WO2011109992A1 (zh) * 2010-08-06 2011-09-15 华为技术有限公司 一种信息获取方法、装置及系统
CN103179616A (zh) * 2011-12-20 2013-06-26 华为技术有限公司 策略与计费规则功能模块选择方法及系统、设备
CN103686877B (zh) * 2012-09-25 2018-08-07 中国电信股份有限公司 确定服务质量策略的方法和系统、保障服务质量的系统
CN105493534B (zh) * 2013-04-11 2019-05-03 华为技术有限公司 计费方法及设备
CN104683939A (zh) * 2015-01-14 2015-06-03 中兴通讯股份有限公司 一种临近发现中区分移动终端不同属性的方法及网元
CN109936460B (zh) * 2017-12-18 2021-11-02 中兴通讯股份有限公司 一种流量计费的方法及设备
CN116545777B (zh) * 2023-07-05 2023-09-26 中国电信股份有限公司 用户类别切换方法、装置、存储介质与电子设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20030027483A (ko) * 2001-09-28 2003-04-07 주식회사 케이티 차별화된 서비스를 제공하는 ｉｐ ｖｐｎ 네트워크에서음성 서비스를 위한 과금 산정 방법
CN1716863A (zh) * 2004-06-14 2006-01-04 华为技术有限公司 一种分组业务计费方法
CN1859137A (zh) * 2006-03-30 2006-11-08 华为技术有限公司 计费装置和方法

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100387093C (zh) * 2004-04-30 2008-05-07 华为技术有限公司 一种实现漫游计费的方法及系统
CN1889619A (zh) * 2005-12-27 2007-01-03 华为技术有限公司 第三代移动通信系统中的计费方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20030027483A (ko) * 2001-09-28 2003-04-07 주식회사 케이티 차별화된 서비스를 제공하는 ｉｐ ｖｐｎ 네트워크에서음성 서비스를 위한 과금 산정 방법
CN1716863A (zh) * 2004-06-14 2006-01-04 华为技术有限公司 一种分组业务计费方法
CN1859137A (zh) * 2006-03-30 2006-11-08 华为技术有限公司 计费装置和方法

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112448823A (zh) * 2019-08-30 2021-03-05 中国电信股份有限公司 计费方法、系统以及存储介质
CN112448823B (zh) * 2019-08-30 2023-06-27 天翼云科技有限公司 计费方法、系统以及存储介质
CN114845257A (zh) * 2022-04-07 2022-08-02 中国联合网络通信集团有限公司 基于嵌入式脚本的多量纲计费方法、装置和存储介质
CN114845257B (zh) * 2022-04-07 2024-04-12 中国联合网络通信集团有限公司 基于嵌入式脚本的多量纲计费方法、装置和存储介质

Also Published As

Publication number Publication date
CN101583113B (zh) 2011-11-30
CN101583113A (zh) 2009-11-18

Similar Documents

Publication Publication Date Title
WO2010003359A1 (zh) 区别用户计费规则的计费方法和系统
US20220248318A1 (en) Control of Network Slice
CN103444148B (zh) 控制部署的业务检测功能节点的路由选择或绕过的网络节点和方法
US9271165B2 (en) Method for establishing connection by HNB
US8811984B2 (en) Area-based access control method for terminals which carry out M2M communications in a wireless communication system
JP6084035B2 (ja) パケットデータ網ゲートウェイ選択方法
US8824365B2 (en) Method for establishing connection by HNB
US20100216484A1 (en) Method and apparatus for bearer processing
US20230122010A1 (en) Policy and Charging Control for a Vehicle Terminal
WO2011050737A1 (zh) 一种实现本地接入的方法及系统
WO2014000265A1 (zh) 在线签约数据配置方法、装置及系统
WO2022152238A1 (zh) 一种通信方法及通信装置
CN105306519A (zh) 用于处理网络环境中的杂散会话请求的系统和方法
WO2012094957A1 (zh) 一种对mtc终端进行移动性管理的方法和系统
WO2011134327A1 (zh) 确定策略和计费规则功能的方法及系统
JP5972467B2 (ja) アクセスネットワークの位置情報を通知する方法及びシステム
WO2010108352A1 (zh) 接入网策略发送方法、归属接入网络发现和选择功能单元
WO2012062183A1 (zh) 一种实现数据流服务质量和计费策略控制的方法及系统
WO2013060170A1 (zh) 一种提供基于lipa承载的计费支持的方法及装置
US10219309B2 (en) D2D service authorizing method and device and home near field communication server
KR20140131676A (ko) 플랫 네트워크 구조에서 정책 및 과금 제어를 위한 장치 및 방법
WO2013067744A1 (zh) 一种终端组的服务网关选择方法及系统
CN101998515B (zh) 控制pcrf负载均衡的实现方法和实现系统
WO2013091705A1 (en) Methods and apparatuses for session establishment with policy control between mobile and fixed networks
WO2012024997A1 (zh) 一种控制业务接纳的方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09793834

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09793834

Country of ref document: EP

Kind code of ref document: A1