WO2010118566A1 - 策略与计费控制的实现方法、设备及策略与计费系统 - Google Patents

策略与计费控制的实现方法、设备及策略与计费系统 Download PDF

Info

Publication number
WO2010118566A1
WO2010118566A1 PCT/CN2009/071248 CN2009071248W WO2010118566A1 WO 2010118566 A1 WO2010118566 A1 WO 2010118566A1 CN 2009071248 W CN2009071248 W CN 2009071248W WO 2010118566 A1 WO2010118566 A1 WO 2010118566A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
entity
rule
identity
cell
Prior art date
Application number
PCT/CN2009/071248
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 华为技术有限公司
Priority to PCT/CN2009/071248 priority Critical patent/WO2010118566A1/zh
Publication of WO2010118566A1 publication Critical patent/WO2010118566A1/zh

Links

Classifications

    • 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
    • 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
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/765—Linked or grouped accounts, e.g. of users or devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/765—Linked or grouped accounts, e.g. of users or devices
    • H04M15/7652—Linked or grouped accounts, e.g. of users or devices shared by users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8083—Rating or billing plans; Tariff determination aspects involving reduced rates or discounts, e.g. time-of-day reductions or volume discounts
    • 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
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/01—Details of billing arrangements
    • H04M2215/0184—Details of billing arrangements involving reduced rates or discounts, e.g. time-of-day reductions, volume discounts, cell discounts, group billing, frequent calling destination(s) or user history list
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/72—Account specifications
    • H04M2215/724—Linked accounts
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2215/00—Metering arrangements; Time controlling arrangements; Time indicating arrangements
    • H04M2215/72—Account specifications
    • H04M2215/724—Linked accounts
    • H04M2215/7245—Shared by users, e.g. group accounts or one account for different users

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method, a device, and a policy and charging system for implementing policy and charging control.
  • Home eNodeB is a new type of base station that is deployed in large numbers in homes, groups, companies or schools.
  • the home base station controls the access of user members through a closed subscriber group (CSG, Closed Subscriber Group).
  • CSG closed subscriber group
  • Each CSG cell has a CSG ID (CSG ID), and multiple CSG cells can share the same CSG ID.
  • CSG ID CSG ID
  • Each user can have a CSG list that allows access to the CSG list. The user's allowed access to the CSG list is used to record the CSG ID information of the closed user group that the user subscribes to.
  • a CSG cell For a CSG cell, it can be mainly divided into closed mode and mixed mode from the perspective of user access restriction.
  • the CSG cell in the closed mode only allows the subscribers of the CSG to normally camp in the CSG cell and apply for services; the CSG cell in the hybrid mode allows the subscribers of the CSG to normally camp in the CSG cell and apply for services.
  • Other non-subscribed users are also allowed to normally reside in the CSG cell and apply for services.
  • PCC policy and charging control
  • PCRF Policy and Charging Rules
  • PCEF Policy and Charging Rules
  • PCEF Policy and Charging Enforcement Function
  • the inventors have found that the existing PCC rule making and executing parties have affected the right of the CSG signing user to preferentially use resources to a certain extent, and also caused the operator's billing loss.
  • the technical problem to be solved by the embodiments of the present invention is to provide a method, a device, and a policy and charging system for implementing policy and charging control, which can ensure that the CSG subscription users preferentially use resource rights. At the same time, try to avoid causing the operator's billing loss.
  • a method for implementing policy and charging control including:
  • a method for implementing policy and charging control including:
  • a rulemaking entity that includes:
  • a determining module configured to determine an identity of the closed subscriber group to which the user belongs in the cell to which the user belongs
  • a rule formulating module configured to determine, according to the closed subscriber group identifier, the closed subscriber group to which the user belongs in the access cell Identity, formulating the policy and charging control rules of the user
  • the notification module is configured to notify the rule execution entity of the policy and charging control rule of the user formulated by the rule formulation module.
  • a rule enforcement entity including:
  • a first sending module configured to send a session establishment request message to the rule formulation entity, where the session establishment request message carries a closed user group identifier of the currently accessed cell of the user;
  • a first receiving module configured to receive a session establishment response message, where the session establishment response message carries the policy and charging control rule of the user, and the policy and charging control rule of the user is determined by the identity of the rule group;
  • a rule execution module configured to perform quality of service and charging control on the service data flow of the user according to the policy and charging control rule of the user received by the first receiving module.
  • a mobility management entity including: An obtaining module, configured to acquire subscription information of a user;
  • a sending module configured to send, according to the subscription information of the user, an identity information providing message to the user equipment when the identity of the closed user group to which the user belongs to the access cell changes, the identity information providing message carrying The changed identity information of the user.
  • a policy and charging system comprising: a rulemaking entity, the rulemaking entity being communicably connected to a rule execution entity,
  • the rule making entity is configured to obtain a closed user group identifier of the user accessing the cell, determine an identity of the closed user group to which the user belongs in the access cell, according to the closed user group identifier and the user accessing the user The identity of the closed subscriber group to which the cell belongs, formulating the policy and charging control rule of the user, and notifying the rule execution entity of the policy and charging control rule of the user.
  • the technical solution provided by the embodiment of the present invention can bring the following beneficial effects:
  • the rule making entity first determines the CSG to which the user belongs in the cell to which the access cell belongs.
  • Identity based on the identity of the user to develop its PCC rules, can ensure that the subscribers of the CSG prioritize the use of resource rights, while avoiding the carrier's billing loss.
  • FIG. 1 is a schematic diagram of a PCC architecture according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of a method for implementing policy and charging control according to Embodiment 1 of the present invention
  • FIG. 3 is a flowchart of a method for implementing policy and charging control according to Embodiment 2 of the present invention
  • FIG. 5 is a flowchart of a method for implementing policy and charging control according to Embodiment 3 of the present invention
  • FIG. 6 is a flowchart of a method for updating PCC rules according to Embodiment 3 of the present invention
  • FIG. 7 is a flowchart of a method for implementing policy and charging control according to Embodiment 4 of the present invention
  • FIG. 8 is a schematic diagram of a rule-making entity according to Embodiment 5 of the present invention.
  • FIG. 9 is a schematic diagram of a rule execution entity according to Embodiment 6 of the present invention.
  • 10 is a schematic diagram of a rule execution entity according to Embodiment 7 of the present invention
  • 11 is a schematic diagram of a mobility management entity according to Embodiment 8 of the present invention
  • FIG. 12 is a schematic diagram of a policy and charging system according to Embodiment 9 of the present invention.
  • the embodiments of the present invention provide a method, a device, and a policy and a charging system for implementing policy and charging control.
  • Different PCC rules are formulated and executed according to different user identities, and the resource rights of the CSG subscription users can be preferentially used. At the same time, try to avoid causing the operator's billing loss.
  • the policy and charging control function may be implemented by a policy and charging control architecture.
  • the PCC architecture may be as shown in FIG. 1.
  • the architecture mainly includes: a PCRF entity 110, a PCEF entity 120, an application function (AF, Application Function) entity 130, SPR (Subscription Profile Repository) 140, Online Charging System (OCS) 150, Offline Charging System (OFCS) 160, etc.
  • the PCRF entity 110 is the core of the PCC architecture. It is mainly used to formulate PCC rules based on service data flows.
  • the PCC rules usually include: data flow monitoring, Gating, and Quality of Service (QoS) control. And the traffic control based on the service data flow, etc.;
  • the PCEF entity 120 is generally located on the gateway of the network, and is mainly used to execute the PCC rules formulated by the PCRF entity 110;
  • the AF entity 130 is mainly used to provide an access point for the service application;
  • the library 140 stores user subscription data related to the PCC; if it is online charging, the PCEF entity 120 and the online charging system 150 perform credit management; if it is offline charging, the PCEF entity 120 and the offline charging system 160 exchange Related billing information.
  • the interface between the PCRF entity 110 and the AF entity 130 is an Rx interface
  • the interface between the PCR specification entity 140 and the subscription specification library 140 is a Sp interface
  • the interface between the PCEF entity and the PCEF entity is a Gx interface
  • the PCEF entity and the online charging system 150 The interface between the interface is a Gy interface
  • the interface between the interface and the offline charging system 160 is a Gz interface.
  • a first embodiment of a method for implementing policy and charging control in an embodiment of the present invention may include:
  • Step 210 Obtain a closed user group identifier of the user accessing the cell.
  • the rule execution entity when the user accesses the CSG cell, can obtain the CSG identification information of the CSG cell that the user currently accesses from the bearer network, and the rule execution entity can carry the CSG identifier information in the
  • the PCC session message is sent to the rulemaking entity.
  • the rule making entity can obtain the above CSG identifier by receiving and parsing the above message.
  • Step 220 Determine the identity of the closed user group to which the user belongs in the access cell; determine the identity of the CSG to which the user belongs in the access cell, that is, determine whether the user belongs to the CSG subscription user, or does not belong to the CSG. User.
  • the rule-making entity may determine the identity of the CSG to which the user belongs in the cell to which the user belongs in a plurality of manners. For example, the rule-making entity may first obtain the allowed access CSG list of the user, and according to the CSG identifier and the CSG list. Determining whether the user is a subscription user of the CSG; the rulemaking entity may also receive a message sent by another entity that carries the identity information of the user, and determine whether the user is the message by parsing the received message.
  • the subscriber of the CSG is not limited to the above-exemplified manner.
  • Step 230 Formulate the policy and charging control rules of the user according to the closed subscriber group identifier and the identity of the closed subscriber group to which the user belongs in the access cell.
  • the rule formulation entity may formulate the policy and charging control rule of the CSG according to the criteria of the CSG subscription user, for example, the user may enjoy the comparison. Low rate, and high quality of service guarantee; if it is determined that the user does not belong to the CSG user, the rule-making entity may formulate the policy and charging control rules of the user according to the criteria of the ordinary cell user, for example, Users enjoy normal rates and quality of service guarantees.
  • Step 240 Notify the rule execution entity of the policy and charging control rule of the user.
  • the rule execution entity obtains the policy and charging control rule of the user, and performs policy and charging control on the service data flow of the user according to the policy and charging control rule of the user.
  • a functional entity that formulates PCC rules such as a PCRF entity, or other body used to formulate PCC rules, such as a PCEF entity, or a Bearer Binding and Event Report Function (BBERF) entity, or other
  • a functional entity for performing PCC rules is not limited to the above examples.
  • the policy and charging rule function entity when a user accesses a CSG cell, the policy and charging rule function entity first determines the identity of the CSG to which the user belongs in the cell to which the cell belongs, and formulates its PCC rule based on the identity of the user. It is possible to ensure that the subscribers of the CSG prioritize the use of resource rights while avoiding the loss of the operator's billing.
  • the rule-making entity is a PCRF entity
  • the rule execution entity is a PCEF entity as an example.
  • the PCEF entity is used as a bearer control and policy enforcement entity, and is generally located on a network gateway. For different networks, where The names of the entities may be different.
  • the PCEF entity may be located on a Gateway GPRS Support Node (GGSN) in a General Packet Radio Service (GPRS) network, or in System Architecture Evolution (SAE, System Architecture Evolution
  • GGSN Gateway GPRS Support Node
  • SAE System Architecture Evolution
  • PDN GW Packet Data Network Gateway
  • the PCRF entity uses the user's allowed access to the CSG list and the CSG identifier to determine the identity of the user, and then the corresponding PCC rule is taken as an example for specific description.
  • the strategy and the embodiment of the present invention are
  • the second embodiment of the method for implementing the charging control may include:
  • Step 301 The PCEF entity sends an IP-CAN session establishment request message to the PCRF entity.
  • IP-CAN IP Connectivity Access Network
  • This example uses the IP-CAN ⁇ tongue interaction information between the PCRF entity and the PCEF entity as an example. Description, of course, is not limited to this.
  • the PCEF entity can obtain the CSG II information of the currently accessed cell of the user from the bearer network before establishing the IP-CAN ⁇ tongue with the PCRF entity.
  • the mobility management entity of the bearer network may carry the CSG ID information of the CSG cell currently accessed by the user in a GPRS Tunneling Protocol (GTP) message, and the GTP may be used.
  • the message is sent to the PCEF entity directly or via the intermediate node.
  • the GTP message may also carry the user identifier (for example, the UE identifier) or the bearer identification information, and the type information of the currently accessed cell of the user.
  • the PCEF entity receives and parses the GTP message. Get the relevant information that it carries.
  • the cell type may be: a large cell, a medium cell, a micro cell, a pico cell, and the like.
  • the PCEF entity may carry the obtained CSG ID information in the IP-CAN session establishment request message, and send the above IP-CAN session establishment request message to the PCRF entity.
  • the above IP-CAN session establishment request message may also carry user identification information, type information of the user accessing the cell, and the like.
  • Step 302 The PCRF entity sends a specification request message to the SP1 ⁇ 2.
  • the PCRF entity may send a rule to the SPRJ ⁇
  • the request message is requested to obtain the user subscription information from the SPR, and the specification request message may carry the user identification information and the like.
  • Step 303 The SPR sends a specification response message to the PCRF entity.
  • the SPR may carry the CSG list information of the user in the specification response message and send it to the PCRF entity.
  • the user's allowed access CSG list records the CSG ID information of the closed subscriber group that the subscriber subscribes to.
  • the CSG ID of the area determines the identity of the CSG to which the user belongs in the access cell, that is, determines whether the user is a CSG user or a non-CSG user in the current cell;
  • step 302 to step 304 are processes for determining the identity of the user by the PCRF entity.
  • the PCRF entity may also determine the identity of the user by the following steps:
  • the PCRF entity carries the identifier of the user and the CSG ID of the currently accessed cell of the user in the specification request message, and sends the message to the SPR.
  • the SPR receives and parses the foregoing specification request message, and obtains the user identifier and the CSG ID of the currently accessed cell of the user.
  • the SPR finds the allowed access CSG list of the user according to the obtained user identifier, and determines that the user is in accordance with the CSG ID. Whether the identity of the CSG is a subscriber of the CSG or a subscriber that does not belong to the CSG; the SPR may carry the identity indication information of the user in the specification response message, and send a specification response message to the PCRF entity;
  • the PCRF entity receives the above-mentioned specification response message, and can determine the identity of the user in the CSG from the above-mentioned specification response message by parsing.
  • the PCRF entity may determine the above by using the CSG ID obtained by the PCRF entity and the user's allowed access closed user group list currently stored by itself. The identity of the closed subscriber group to which the subscriber belongs in his or her access cell.
  • Step 305 The PCRF entity determines a PCC rule of the user according to the identity of the user and the CSG ID of the currently accessed cell of the user.
  • the PCRF entity can formulate different PCC rules according to the difference of the user identity and the CSG to which the user accesses the cell.
  • the PCRF entity may formulate the policy and charging control rule of the user according to the CSG subscription user standard, for example, the user may enjoy the lowering. Rate, and higher quality of service guarantee; if it is determined that the user does not belong to the CSG user, the PCRF entity can follow the normal
  • the criteria of the cell user, the policy and charging control rules of the user are formulated, for example, the user enjoys the normal rate and the quality of service guarantee.
  • the PCRF entity may also formulate a trigger event that requires PCEF entity monitoring.
  • the PCEF entity detects that a trigger event is generated by the PCRF entity, the PCEF entity performs an action corresponding to the triggered event.
  • the triggering event that is generated by the PCRF entity may include: the type of the user accessing the cell is changed, and the CSG to which the user accessing the cell belongs changes, and is not limited to the foregoing example.
  • the type of the user accessing the cell may be changed: the user moves from one type of cell to another type of cell, for example, the user moves from the pico cell to the large cell, and the CSG of the user access cell changes. It may be that the user moves from a cell belonging to a certain CSG to a cell belonging to another CSG.
  • multiple CSGs may form a CSG set. If the subscribers of each CSG in the CSG set have the same priority right, and the identity of each CSG in the CSG set is the same, the user is attributable to When moving within each CSG cell of the CSG set, the PCEF entity may not request a new PCC rule from the PCRF entity.
  • the PCEF entity When the PCEF entity detects that the above trigger event is generated by the PCRF entity, the PCEF entity is triggered to request a new PCC rule from the PCRF entity to perform timely and effective adjustment.
  • Step 306 The PCRF entity sends an IP-CAN session establishment response message to the PCEF entity.
  • the PCRF entity may carry the PCC rule information of the user that is formulated in the IP-CAN session establishment response message, and send the IP-CAN session establishment response message to the PCEF entity.
  • the above-mentioned IP-CAN session request response message may also carry the trigger event information formulated by the PCRF entity, and the identity of the user in the CSG.
  • the PCEF entity receives and parses the IP-CAN session establishment response message, obtains the PCC rules of the user carried by the user, and triggers events and the like, and can store the obtained information.
  • the PCEF entity may perform quality of service and charging control on the service data flow of the user according to the PCC rule of the user defined by the PCRF entity, and perform trigger event monitoring.
  • Step 307 The PCEF entity sends a credit request message to the OCS.
  • the PCEF entity sends a credit request message to the OCS requesting the OCS to authorize the credit for the above user.
  • the credit request message may carry the user identification information, and may also carry the CSG ID that the user currently accesses the CSG cell, and/or the identity of the CSG to which the user belongs in the access cell, and the like. Information.
  • Step 308 The OCS sends a credit response message to the PCEF entity.
  • the OCS receives and parses the above-mentioned credit request message, and obtains information such as the user identifier carried by the user, the CSG ID that the user currently accesses the CSG cell, the identity of the CSG to which the user belongs in the access cell, and the like, and can store the obtained information.
  • the OCS can authorize credit for the user based on the user identification or billing identifier.
  • the OCS may also formulate a credit re-authorization event that requires PCEF entity monitoring.
  • the PCEF entity detects that the credit re-authorization event formulated by the OCS occurs, the PCEF entity may perform an action corresponding to the generated credit re-authorization event.
  • the credit re-authorization event formulated by the OCS may include: a type change of the user access cell, a CSG change to which the user accesses the cell, and a change of the identity of the CSG to which the user belongs in the access cell, but not Limited to the above examples.
  • the identity change of the CSG to which the user belongs in the access cell may be: the user changes from the non-subscribed user of the CSG to its sign-up user, or from its sign-up user to its non-subscriber user.
  • the OCS can carry the credits authorized by the above-mentioned users and the credit reauthorization events it has made in the credit response message and send them to the PCEF entity.
  • the PCEF entity receives and parses the above credit response message, obtains the credit authorized by the OCS for the user, and the information such as the credit reauthorization event, and can store the above information.
  • the credit request message may not carry the identity information of the user in the CSG, and the OCS may access the CSG list according to the permission of the user and the current connection of the user.
  • the CSG ID of the incoming cell determines the identity of the user in the CSG; the OCS establishes a credit reauthorization event that may not include an event in which the identity of the user changes in the CSG.
  • the PCEF entity performs charging processing on the user's service data stream based on the credit obtained from the OCS.
  • the PCEF entity detects that the above-mentioned credit re-authorization event initiated by the OCS occurs, the PCEF entity is triggered to request the OCS to authorize a new credit, so as to make timely and effective adjustment.
  • steps 307-308 may also be performed before steps 301-306, or at other times.
  • the update process of the PCC rule and/or the trigger event is also provided in the embodiment, which may include:
  • Step 401 The PCEF entity sends an IP-CAN session modification indication message to the PCRF entity.
  • the PCEF entity detects that a trigger event formulated by the PCRF entity occurs, or triggered by other conditions, the PCEF entity may send an IP-CAN session modification indication message to the PCRF entity to request to obtain a new PCC rule.
  • the PCEF entity may receive a GTP message sent by the mobility management entity of the bearer network, where the GTP message carries the CSG ID of the new CSG cell currently accessed by the user. Information, or type information of a new cell accessed by the user, and the like.
  • the PCEF entity can monitor the occurrence of the above trigger event by receiving and parsing the above GTP message.
  • the PCEF entity When the PCEF entity detects that the trigger event occurs, the CSG ID information of the new CSG cell that the user currently accesses, or the type information of the user accessing the new cell, is carried in the IP-CAN ⁇ tongue modification indication message.
  • the above IP-CAN ⁇ tongue modification indication message is sent to the PCRF entity.
  • Step 402 The SPR sends a specification providing message to the PCRF entity.
  • the SPR may carry the updated access CSG list of the user in the subscription information providing message.
  • the above specification providing message is sent to the PCRF entity.
  • steps 401 and 402 are in a side-by-side relationship, and there is no necessary time sequence. Steps 401 and 402 can also separately trigger the PCRF entity to formulate a new PCC rule.
  • Step 403 The PCRF entity formulates a new PCC rule and/or a new trigger event.
  • the PCRF entity receives and parses the above IP-CAN session modification indication message, and/or the specification provides a message to obtain related information carried by the PCRF entity.
  • the PCRF entity may re-determine the identity of the CSG to which the user belongs in the current access cell according to the information carried by the PCC rule request message and/or the specification providing message, and according to the identity of the user in the CSG. And its CSG ID, re-engineer the new PCC rules and/or new trigger events.
  • Step 404 The PCRF entity sends an IP-CAN session modification response message to the PCEF entity.
  • the PCRF entity can carry its new PCC rules and/or trigger event information
  • the IP-CAN session modification response message may further carry the CSG to which the user belongs in the current access cell. Identity information, etc.
  • the PCEF entity receives and parses the above IP-CAN session modification response message to obtain the usage carried by the PCEF entity.
  • Information such as new PCC rules, and/or new trigger events, and the above information can be stored.
  • the PCEF entity can perform quality of service and charging control on the service data flow of the user according to the new PCC rule of the user established by the PCRF entity, and perform monitoring of the trigger event.
  • Step 405 The PCEF entity sends a credit request message to the OCS.
  • the PCEF entity When the PCEF entity detects that a credit reauthorization event established by the OCS occurs, the PCEF entity may
  • the OCS sends a credit request message requesting the OCS to authorize the new credit for the above user.
  • the PCEF entity may provide information about the bearer event monitored by the PCC rule and whether the credit reauthorization event established by the OCS occurs. If the credit reauthorization event occurs, the credit is sent to the OCS.
  • the request message, the credit request message may carry the user identifier or the charging identifier, the CSG identifier of the current cell accessing the user, or/and the identity information of the CSG to which the user belongs in the access cell.
  • Step 406 The OCS sends a credit response message to the PCEF entity.
  • the OCS may re-authorize the user according to the user identifier carried in the credit request message or the charging identifier of the user, the CSG ID of the user currently accessing the cell, or/and the identity of the user in the CSG, and The authorized credit is carried in the credit response message and sent to the PCEF entity.
  • the OCS can also re-define the re-authorization event that needs to be monitored by the PCEF entity.
  • the PCEF entity detects that the re-authorization event established by the OCS occurs, the PCEF entity performs an action corresponding to the re-authorization event that occurs.
  • the credit re-authorization event re-established by the OCS may include: a type change of the user access cell, a CSG change to which the user accesses the cell, and a change of the identity of the user in the CSG, and is not limited to the above example.
  • the credit response message may further carry the credit reauthorization event information re-established by the OCS, and the PCEF entity receives and parses the credit response message, obtains information such as credit and credit reauthorization events re-authorized by the OCS for the user, and may obtain the above information. Information is stored.
  • the credit request message may not carry the identity information of the user in the CSG, and the OCS may access the CSG list according to the permission of the user and the current connection of the user.
  • the CSG ID of the incoming cell determines the identity of the user in the CSG; the OCS re-establishment of the credit re-authorization event may not include an event in which the identity of the user changes in the CSG.
  • the PCEF entity performs charging processing on the user's service data stream based on the credit obtained from the OCS.
  • the PCEF entity detects the above-mentioned credit re-authorization event initiated by the OCS, it triggers the PCEF.
  • the body ocs requests authorization of new credits, and then makes timely and effective adjustments.
  • steps 405-406 may also be performed before steps 401-404 or at other times.
  • the PCRF entity when a user accesses a CSG cell, the PCRF entity first determines the identity of the CSG to which the user belongs in the cell to which the user belongs, and formulates its PCC rule based on the identity of the user.
  • the PCEF entity follows the PCC.
  • the rule performs quality of service and charging control on the service data flow of the user, and can ensure that the subscriber of the CSG preferentially uses the resource right while avoiding causing the operator's charging loss.
  • the PCRF entity determines the identity of the user by receiving and parsing the message carrying the user identity information, and then the corresponding PCC rule is taken as an example for specific description. Referring to FIG. 5, the strategy and the method in the embodiment of the present invention are described.
  • the third embodiment of the fee control implementation method may include:
  • Step 501 The PCEF entity sends an IP-CAN session establishment request message to the PCRF entity; the description is of course not limited thereto.
  • the PCEF entity When a user accesses a network from a CSG cell, the PCEF entity obtains the CSG II message of the user's current access cell from the bearer network before the IP-CAN ⁇ tongue is established with the PCRF entity, and the user accesses it.
  • the identity information of the CSG to which the cell belongs The identity information may be any information that can indicate the identity of the CSG to which the user belongs in the cell to which the cell belongs.
  • the mobility management entity of the bearer network may carry the CSG ID of the CSG cell currently accessed by the user, and the identity information of the user in the CSG in the GTP message, and send the GTP message.
  • the GTP message may also be sent to the PCEF entity directly or through the intermediate node.
  • the GTP message may also carry the user identifier or the bearer identification information, and the type information of the currently accessed cell of the user.
  • the type of the cell may be: a large cell, a medium cell, a micro cell, and a pico cell. and many more.
  • the PCEF entity obtains the relevant information carried by the GTP message by receiving and parsing the above GTP message.
  • the PCEF entity may carry the CSG ID information of the currently accessed cell of the user and the identity information of the user in the CSG in the IP-CAN session establishment request message, and send the IP-CAN session establishment request message to the PCRF entity.
  • the above IP-CAN session establishment request message can also carry With user identification information, type information of the user accessing the cell, and the like.
  • Step 502 The PCRF entity formulates the PCC rule of the user according to the CSG ID of the currently accessed cell of the user and the identity of the CSG to which the user belongs in the access cell.
  • the PCRF entity may receive the foregoing IP-CAN session establishment request message, and obtain and obtain the CSG ID information of the currently accessed cell of the user carried by the IP-CAN session establishment request message, and the identity information of the user in the CSG. And, in turn, determining the identity of the CSG to which the user belongs in the cell to which he is accessing.
  • the PCRF entity can formulate different PCC rules for the difference in user identity and the CSG to which the user accesses the cell.
  • the PCRF entity may formulate the policy and charging control rule of the CSG according to the criteria of the CSG subscription user, thereby allowing the user to enjoy the lowering.
  • the rate, and the higher quality of service guarantee if it is determined that the user does not belong to the CSG user, the PCRF entity can formulate the policy and charging control rules of the user according to the standard of the ordinary cell user, thereby allowing the user to enjoy Normal rates and quality of service guarantees.
  • the PCRF entity may also formulate a trigger event that requires PCEF entity monitoring.
  • the PCEF entity detects that a trigger event is generated by the PCRF entity, the PCEF entity performs an action corresponding to the triggered event.
  • the triggering event that is generated by the PCRF entity may include: the type of the user accessing the cell is changed, the CSG of the user accessing the cell is changed, and the identity of the user in the CSG is changed, and is not limited to the foregoing example.
  • the type of the user accessing the cell may be changed: the user moves from one type of cell to another type of cell, for example, the user moves from the pico cell to the large cell, and the CSG of the user access cell changes.
  • the user may move from the cell belonging to a certain CSG to the cell belonging to another CSG; the change of the identity of the user in the CSG may be: the user changes from the non-subscribed user of the CSG to the subscriber, or from the subscriber
  • the signing user becomes a non-subscriber and so on.
  • multiple CSGs may form a CSG set. If the subscribers of each CSG in the CSG set have the same priority right, and the identity of each CSG in the CSG set is the same, the user is attributable to When moving within each CSG cell of the CSG set, the PCEF entity may not request a new PCC rule from the PCRF entity.
  • the PCEF is triggered when the PCEF entity detects that the above trigger event is determined by the PCRF entity.
  • the entity requests a new PCC rule from the PCRF entity to make timely and effective adjustments.
  • Step 503 The PCRF entity sends an IP-CAN session establishment response message to the PCEF entity.
  • the PCRF entity may carry the PCC rule information of the user that is formulated in the IP-CAN session establishment response message, and send the IP-CAN to the PCEF entity.
  • Session establishment response message The above-mentioned IP-CAN session request response message may also carry a trigger event and other information formulated by the PCRF entity.
  • the PCEF entity receives and parses the IP-CAN session establishment response message, obtains the PCC rules of the user carried by the user, and triggers events and the like, and can store the obtained information.
  • the PCEF entity may perform quality of service and charging control on the service data flow of the user according to the PCC rule of the user defined by the PCRF entity, and perform trigger event monitoring.
  • Step 504 The PCEF entity sends a credit request message to the OCS.
  • the PCEF entity sends a credit request message to the OCS requesting the OCS to authorize the credit for the user.
  • the credit request message may carry the user identification information, and may also carry the CSG ID of the current CSG cell, and/or the identity of the CSG to which the user belongs to the cell.
  • Step 505 The OCS sends a credit response message to the PCEF entity.
  • the OCS receives and parses the above-mentioned credit request message, and obtains information such as the user identifier carried by the user, the CSG ID that the user currently accesses the CSG cell, the identity of the CSG to which the user belongs in the access cell, and the like, and can store the obtained information.
  • the OCS can be a user ID or a billing identifier to authorize credit for the user.
  • the OCS may also formulate a credit re-authorization event that requires PCEF entity monitoring.
  • the PCEF entity detects that the credit re-authorization event formulated by the OCS occurs, the PCEF entity performs an action corresponding to the credit re-authorization event that occurs.
  • the credit re-authorization event that is established by the OCS may include: a type change of the user access cell, a CSG change to which the user accesses the cell, and a change of the identity of the user in the CSG, and is not limited to the foregoing example.
  • the OCS can carry the credits authorized by the above-mentioned users and the credit reauthorization events it has made in the credit response message and send them to the PCEF entity.
  • the PCEF entity receives and parses the above credit response message, obtains the credit authorized by the OCS for the user, and the credit reauthorization event and the like, and can store the above information.
  • the credit request message may not carry the identity information of the user in the CSG, and the OCS may access the CSG list according to the permission of the user and the current connection of the user.
  • the CSG ID of the incoming cell determines the identity of the user in the CSG; the OCS establishes a credit reauthorization event that may not include an event in which the identity of the user changes in the CSG.
  • the PCEF entity charges the user's traffic data stream based on the credit obtained from the OCS.
  • the PCEF entity detects that the above-mentioned credit re-authorization event established by the OCS occurs, the PCEF entity is triggered to request the OCS to authorize a new credit, so as to make timely and effective adjustment.
  • the update process of the PCC rule and/or the trigger event is also provided in the embodiment, which may include:
  • Step 601 The PCEF entity sends an IP-CAN session modification indication message to the PCRF entity.
  • the PCEF entity detects that a trigger event formulated by the PCRF entity occurs, or triggered by other conditions, the PCEF entity may send an IP-CAN session to the PCRF entity. Modify the indication message to request a new PCC rule.
  • the PCEF entity may receive a GTP message sent by the mobility management entity of the bearer network, where the GTP message carries the CSG ID of the new CSG cell currently accessed by the user. Information, identity information of the user in the CSG, or type information of a new cell accessed by the user, and the like.
  • the PCEF entity can monitor the occurrence of the above trigger event by receiving and parsing the above GTP message.
  • the PCEF entity When the PCEF entity detects the occurrence of the triggering event, the CSG ID information of the new CSG cell that the user currently accesses, or the identity information of the CSG that the user belongs to in the cell to which the cell is accessed, or the type information of the user accessing the new cell And waiting to be carried in the IP-CAN session modification indication message, and sending the above IP-CAN session modification indication message to the PCRF entity.
  • Step 602 The PCRF entity formulates a new PCC rule and/or a new trigger event.
  • the PCRF entity receives and parses the above IP-CAN session modification indication message to obtain related information carried by the PCRF entity.
  • the PCRF entity may carry the identity information of the user according to the foregoing IP-CAN session modification indication message, and re-determine the identity of the CSG to which the user belongs in the current access cell, and according to the identity of the user in the CSG. And its CSG ID, re-engineer the new PCC rules and/or new trigger events.
  • Step 603 The PCRF entity sends an IP-CAN session modification response message to the PCEF entity.
  • the PCRF entity may carry information such as new PCC rules and/or trigger events formulated in the IP-CAN session modification response message, and send the above IP-CAN session modification response to the PCEF entity.
  • the PCEF entity receives and parses the above IP-CAN session modification response message, obtains the user's new PCC rules carried by the user, and/or new trigger events, and can store the above information.
  • the PCEF entity can perform quality of service and charging control on the service data flow of the user according to the new PCC rule of the user established by the PCRF entity, and perform monitoring of the trigger event.
  • Step 604 The PCEF entity sends a credit request message to the OCS.
  • the PCEF entity may send a credit request message to the OCS requesting to obtain a new credit.
  • the PCEF entity may determine whether a credit re-authorization event formulated by the OCS occurs according to a monitored bearer event. If a credit re-authorization event occurs, a credit request message is sent to the OCS, and the credit request message may be carried.
  • Step 605 The OCS sends a credit response message to the PCEF entity.
  • the OCS may re-authorize the user according to the user identifier carried in the credit request message or the charging identifier of the user, the CSG ID of the user currently accessing the cell, or/and the identity of the user in the CSG, and The authorized credit is carried in the credit response message and sent to the PCEF entity.
  • the OCS can also re-define the re-authorization event that needs to be monitored by the PCEF entity.
  • the PCEF entity detects that the re-authorization event established by the OCS occurs, the PCEF entity performs an action corresponding to the re-authorization event that occurs.
  • the credit re-authorization event re-established by the OCS may include: a type change of the user access cell, a CSG change to which the user accesses the cell, and a change of the identity of the CSG to which the user belongs in the access cell, and It is not limited to the above examples.
  • the above credit response message may also carry the credit reauthorization event information re-established by the OCS.
  • the PCEF entity receives and parses the above credit response message, obtains information such as the credit and credit reauthorization event re-authorized by the OCS for the user, and can store the obtained information.
  • the credit request message may not carry the identity information of the user in the CSG, and the OCS may access the CSG list according to the permission of the user and the current connection of the user.
  • the CSG ID of the incoming cell determines the identity of the user in the CSG;
  • OCS The re-establishment of the credit re-authorization event may not include an event in which the identity of the user changes in the CSG.
  • the PCEF entity performs charging processing on the user's service data stream based on the credit obtained from the OCS.
  • the PCEF entity detects that the above-mentioned credit re-authorization event established by the OCS occurs, the PCEF entity is triggered to request the OCS to authorize a new credit, thereby performing timely and effective adjustment.
  • steps 604-605 may also be performed before steps 601-603, or at other times.
  • the PCRF entity when a user accesses a CSG cell, the PCRF entity first determines the identity of the CSG to which the user belongs in the cell to which the user belongs, and formulates its PCC rule based on the identity of the user.
  • the PCEF entity follows the PCC.
  • the rule performs quality of service and charging control on the service data flow of the user, and can ensure that the contracted user of the CSG uses the resource right while avoiding causing the operator's charging loss.
  • the PCC rules and the authorization credit are adjusted in time, and the real-time effectiveness of the policy and charging control is further improved.
  • the PCRF entity is used as the PCC rule-making entity
  • the PCEF entity is used as the PCC rule execution entity.
  • the present invention is not limited thereto, and may be any other entity.
  • the fourth embodiment of the method for implementing policy and charging control in the embodiment of the present invention may include:
  • Step 701 The mobility management entity acquires user subscription information.
  • the mobility management entity may obtain user subscription information from an entity that stores user subscription information.
  • Step 702 The mobility management entity sends, according to the user subscription information, that the identity of the CSG to which the user belongs to the access cell changes, and sends an identity information providing message to the user equipment.
  • the identity of the CSG in the connected cell changes, for example, if the user accesses the network through the mixed mode CSG cell, the identity of the user is changed from the CSG subscription user to the CSG non-signing. If the user, or the non-subscribed user of the CSG becomes the subscription user of the CSG, or the user accesses the network through the CSG cell in the closed mode, the identity of the user is changed from the subscription user of the CSG to the non-subscribed user of the CSG. , causing the user to be switched to another cell, where the user
  • the reason for the identity change may be a change in its subscription information, or a user's time limit for the user to access the CSG to which the cell belongs, and so on.
  • the user subscription information acquired by the mobility management entity may be the allowed access CSG list of the foregoing user, and the mobility management entity may obtain the CSG ID of the currently accessed cell of the user from the corresponding base station or the base station gateway, and the mobility management entity may be configured according to the CSG.
  • the ID and the allowed access to the CSG list determine whether the identity of the user at the CSG has changed.
  • the information carried by the identity information providing message may include, but is not limited to, the changed identity information of the user.
  • the type of the identity information providing message sent by the mobility management entity may be a non-access stratum (NAS, Non-Access-Stratum) message.
  • NAS Non-Access-Stratum
  • the user equipment can provide a message by receiving and parsing the identity information sent by the mobility management entity, learn the current identity of the user, and can learn its current quality of service and charging information according to its current identity and other application layer information.
  • Step 703 The user equipment sends an identity information response message to the mobility management entity.
  • the user equipment prompts the mobility management entity to successfully receive the identity information providing message sent by the mobility management entity by sending an identity information response message to the mobility management entity.
  • the UE may carry the user identity information according to the identity information providing message, and update its locally stored allowed access CSG list.
  • the mobility management entity when the identity of the CSG to which the user belongs in the access cell changes, the mobility management entity notifies the user of the identity of the user in time, which is beneficial to improving the transparency of the policy and charging control, thereby improving user experience.
  • the mobility management entity may be an Evolved packet system (EPS).
  • EPS Evolved packet system
  • MME Mobility Management Entity, Mobility Management Unit
  • SGSN GPRS Service Support Node
  • GPRS General Packet Radio Service
  • MSC Mobile switching center
  • VLR Visitor Location Registe
  • a rule-making entity is further provided in the embodiment of the present invention. Referring to FIG. 8, the fifth embodiment of the rule-making entity in the embodiment of the present invention may include:
  • the ear block 810 is used to obtain the closed user group identifier of the user accessing the cell.
  • the rule execution entity when the user accesses the CSG cell, can obtain the CSG identification information of the CSG cell that the user currently accesses from the bearer network, and the rule execution entity can carry the CSG identifier information in the
  • the PCC session message is sent to the rulemaking entity.
  • the obtaining module 810 can obtain the above CSG identifier by receiving and parsing the above message.
  • the determining module 820 is configured to determine an identity of the closed user group to which the user belongs in the cell to which the user accesses.
  • the determining module 820 can determine the identity of the CSG to which the user belongs in the cell to which the user belongs.
  • the determining module 820 can obtain the allowed access CSG list of the user first, and according to the CSG identifier. And determining, by the CSG list, whether the user is a subscription user of the CSG; the determining module 820 may also receive a message that is sent by another entity and that carries the identity information of the user, and determine the received message by parsing the received message. Whether the user is a subscription user of the CSG, the embodiment is not limited to the above-exemplified manner.
  • the rule making module 830 is configured to: according to the closed user group identifier acquired by the obtaining module 810, and the identity of the closed user group that the user determines in the access cell determined by the determining module 820, formulating the policy and charging control rule of the user. .
  • the rule formulating module 830 may formulate the policy and charging control rule of the user according to the CSG subscription user standard, for example, the The user enjoys a lower rate, and a higher quality of service guarantee, etc.; if the determining module 820 determines that the user does not belong to the user of the CSG, the rule making module 830 can formulate the policy of the user according to the standard of the ordinary cell user. With billing control rules, for example, let users enjoy normal rates and quality of service guarantees.
  • the notification module 840 is configured to notify the rule execution entity by the rule setting module 830 that the policy and the charging control rule of the user are used.
  • the notification module 840 can notify the rule execution entity of the policy and charging control rule of the user in multiple manners.
  • the notification module 840 may carry the formulated policy and charging control rule of the user in the session request message, and send the message to the rule execution entity.
  • the rule execution entity obtains the policy and charging control rule of the user, and performs policy and charging control on the service data flow of the user according to the policy and charging control rule of the user.
  • the determining module 820 may include: a first sending submodule 821, a first receiving submodule 822, and a first determining submodule 823.
  • the first sending submodule 821 is configured to send a specification request message to the subscription specification library, where the specification request message carries user identification information.
  • the subscription specification database stores the subscription information of the user, and the subscription specification library can carry the CSG list information of the user in the specification response message and send it to the rule formulation entity.
  • the first receiving submodule 822 is configured to receive a specification response message, where the specification response message carries a list of allowed access closed user groups of the user, and the allowed access closed user group list records the CSG ID of the closed user group subscribed by the user. information.
  • the closed subscriber group identifier is determined to determine the identity of the closed subscriber group to which the user belongs in the access cell.
  • the foregoing notification module 840 is further configured to notify the first determining submodule 823 that the user is notified of the identity execution entity by the identity of the closed user group to which the access cell belongs.
  • the determining module 820 may further include: a second receiving submodule 824 and a second determining submodule 825.
  • the second receiving sub-module 824 is configured to receive a session establishment request message sent by the rule execution entity, where the session establishment request message carries the identity information of the closed user group to which the user belongs in the access cell.
  • the second determining submodule 825 is configured to determine, from the session establishment request message received by the second receiving submodule 824, the identity of the closed subscriber group to which the user belongs in the access cell.
  • the above rule making entity may also include:
  • the event setting module 850 is configured to: generate a trigger event that needs to be monitored by the rule execution entity, so that the rule execution entity performs a step corresponding to the trigger event that occurs when the trigger event is detected, and the trigger event includes at least the following One of the events: the type change of the user access cell, the closed subscriber group to which the user access cell belongs, and the identity change of the closed subscriber group to which the user belongs in the access cell.
  • the notification module 840 may be further configured to notify the rule execution entity of the trigger event specified by the event formulation module 850.
  • the above rule making entity may also include:
  • the receiving module 860 is configured to receive a session modification indication message, where the session modification indication message carries the closed user group identification information of the user accessing the new cell, or the type information of the user accessing the new cell, or/or the user in the Accessing the new identity information of the closed subscriber group to which the cell belongs; and/or receiving the specification providing message, the above specification providing message carrying the updated allowed access closed subscriber group list of the above-mentioned user.
  • the rule-making module 830 may be further configured to re-define the policy and the charging control rule of the user according to the session modification indication message received by the receiving module 860 and/or the information carried by the specification providing message, where the event formulating module 850 may further And the triggering event of the user is determined according to the session modification indication message and/or the information carried by the specification providing message received by the receiving module 860.
  • the sending module 870 is configured to send a session modification response message to the rule execution entity, where the session modification response message carries the policy and charging control rule of the user that is re-defined by the rule formulation module 830, and/or the event creation module 850 re-enacts The trigger event of the above user, etc.
  • the rule execution entity may perform the user's new PCC rules according to the rules, perform quality of service and charging control on the user's service data flow, and perform trigger event monitoring.
  • the rule execution entity in this embodiment may be a PCEF entity as described in the second embodiment or the third embodiment
  • the rule-making entity may be the PCRF as described in the second embodiment or the third embodiment.
  • the functions described in the respective functional modules may be specifically implemented according to the method in the second embodiment or the third embodiment. For the specific implementation process, refer to the related description in the second embodiment or the third embodiment. .
  • a rule execution entity is further provided in the embodiment of the present invention.
  • the sixth embodiment of the rule-making entity in the embodiment of the present invention may include:
  • the first sending module 910 is configured to send a credit request message to the online charging system, where the credit request message carries user identification information.
  • the credit request message may also carry information such as the CSG ID of the current CSG cell that the user accesses, and/or the identity of the CSG to which the user belongs to the cell.
  • the first receiving module 920 is configured to receive a credit response message, where the credit response message carries the credit information authorized by the online charging system for the user, and the credit determined by the online charging system.
  • Authorization event information the credit re-authorization event includes at least one of the following events: a type change of the user access cell, a closed user group change to which the user access cell belongs, and a closed user group to which the user belongs in the access cell The identity changed.
  • the OCS can receive and parse the above-mentioned credit request message, obtain the user identifier carried by the user, the CSG ID of the current CSG cell that the user accesses, the identity of the CSG that the user belongs to in the cell to which the cell belongs, and can store the above information obtained by the OCS. .
  • the OCS can authorize credit for the user based on the user identification or billing identifier.
  • the OCS may also formulate a credit re-authorization event that requires rule enforcement entity monitoring.
  • the rule execution entity monitors the credit re-authorization event established by the OCS, the rule execution entity may perform an action corresponding to the credit re-authorization event that occurred.
  • the OCS may carry the credits authorized by the above-mentioned user and the credit re-authorization events it has made in the credit response message and send it to the rule execution entity.
  • the billing processing module 930 is configured to perform charging processing on the service data stream of the user according to the credit authorized by the online charging system received by the first receiving module 920.
  • the event monitoring module 940 is configured to monitor the occurrence of the credit re-authorization event determined by the online charging system received by the first receiving module 920.
  • rule execution entity may further include:
  • the identity obtaining module 950 is configured to obtain identity information of the closed user group to which the user belongs in the access cell from the bearer network or from the policy and charging rule function entity.
  • the 950 may obtain, from the bearer network, the CSG II information of the currently accessed cell of the user, the identity information of the CSG that the user belongs to in the access cell, the type information of the currently accessed cell of the user, and the like.
  • the obtaining module 950 may obtain the user carrying the user identity information sent by the PCRF entity, and obtain the closed subscriber group that the user belongs to in the access cell. identity of.
  • rule execution entity may further include: a second sending module 960 and a second receiving module 970.
  • the second sending module 960 is configured to: when the event monitoring module 940 detects that the credit re-authorization event specified by the online charging system occurs, send a credit request message to the online charging system, where the credit request message carries the user identifier. And the closed user group label of the above user accessing the new cell The information, or the type information of the user accessing the new cell, or the identity information obtained by the acquiring module 950 and the closed user group to which the user belongs in the access cell.
  • the OCS may re-authorize the user according to the user identifier or the charging identifier carried in the credit request message, the CSG ID of the user currently accessing the cell, or/and the identity of the user in the CSG.
  • the OCS may also re-define the re-authorization event that needs to be monitored by the rule execution entity.
  • the rule execution entity detects that the re-authorization event formulated by the OCS occurs, the rule execution entity performs an action corresponding to the re-authorization event that occurs.
  • the credit re-authorization event re-established by the OCS may include: a type change of the user access cell, a CSG change to which the user accesses the cell, and a change of the identity of the CSG to which the user belongs in the access cell, and It is not limited to the above examples.
  • the above credit response message may also carry the credit reauthorization event information re-established by the OCS.
  • the second receiving module 970 is configured to receive a credit response message, where the credit response message carries the credit and/or reauthorization event information authorized by the online charging system for the user.
  • the billing processing module 930 can also be configured to perform billing processing on the service data stream of the user according to the credit authorized by the online billing system to re-authorize the user.
  • the event monitoring module 940 can also be used to monitor the occurrence of re-authorization events that the online charging system re-creates for the above-mentioned users.
  • rule execution entity in this embodiment may be a PCEF entity as described in the second embodiment or the third embodiment, and the functions described in the respective functional modules may be according to the second embodiment or the third embodiment.
  • the specific implementation of the method may be referred to the related description in the second embodiment or the third embodiment, and is not described herein.
  • a rule execution entity is further provided in the embodiment of the present invention.
  • the seventh embodiment of the rule-making entity in the embodiment of the present invention may include:
  • the first sending module 1010 is configured to send a session establishment request message to the rule formulation entity, where the session establishment request message carries a closed user group identifier of the currently accessed cell of the user.
  • the session establishment request may be an IP-CAN session establishment request message.
  • the rule enforcement entity When a user accesses a network from a CSG cell, the rule enforcement entity establishes an IP-CAN session with the rulemaking entity.
  • the CSG ID information of the currently accessed cell of the user and the identity information of the CSG to which the user belongs in the access cell may be obtained from the bearer network.
  • the identity information may be any information that can indicate the identity of the CSG to which the user belongs to the cell to which the cell belongs.
  • the session establishment request message may further carry user identification information, type information of the user accessing the cell, and the like.
  • the first receiving module 1020 is configured to receive a session establishment response message, where the session establishment response message carries the policy and charging control rule of the user, and the policy and charging control rule of the user is determined by the identity of the user group.
  • the rule-making entity may receive and parse the session establishment request message, obtain the CSG ID information of the current cell that the user carries, and the identity information of the user in the CSG, and determine that the user is in the It accesses the identity of the CSG to which the cell belongs.
  • the rule making entity may formulate different PCC rules according to the difference of the user identity and the CSG to which the user accesses the cell.
  • the rule formulation entity may formulate the policy and charging control rule of the CSG according to the criteria of the CSG subscription user, for example, the user may enjoy the comparison. Low rate, and high quality of service guarantee; if it is determined that the user does not belong to the CSG user, the rule-making entity may formulate the policy and charging control rules of the user according to the standard of the ordinary cell user, for example, Users enjoy normal rates and quality of service guarantees.
  • the rulemaking entity may also formulate a trigger event that needs to be monitored by the rule execution entity.
  • the rule execution entity detects that a trigger event formulated by the rule formulation entity occurs, the rule execution entity performs an action corresponding to the triggered event that occurs.
  • the triggering event that is generated by the rule-making entity may include: a change in the type of the user access cell, a change in the CSG to which the user accesses the cell, and a change in the identity of the user in the CSG, and is not limited to the above example.
  • the rule execution module 1030 is configured to perform quality of service, charging control, and the like on the service data flow of the user according to the policy and charging control rule of the user received by the first receiving module 1020.
  • rule execution entity may further include:
  • the identity obtaining module 1040 is configured to obtain, from the bearer network, identity information of the closed subscriber group to which the user belongs in the access cell.
  • the session establishment request message sent by the first sending module 1010 may further carry the identity information obtained by the identity obtaining module 1040 and the identity information of the closed user group that the user belongs to in the cell to which the cell is accessed.
  • the session establishment response message received by the first receiving module 1020 may further include the trigger event information that is generated by the rule-making entity, and the trigger event includes at least one of the following events: the type of the user access cell changes, and the user access cell belongs to the cell.
  • the closed subscriber group changes, the identity change of the closed subscriber group to which the user belongs in the access cell, and the like.
  • the above rule execution entity may further include:
  • the event monitoring module 1050 is configured to monitor the occurrence of a trigger event formulated by the rule making entity.
  • the second sending sub-module 1060 is configured to send a session modification indication message to the rule-making entity when the event monitoring module 1050 detects that the trigger event occurs, where the session modification indication message carries the closed user group identifier of the user accessing the new cell.
  • the rule-making entity may carry the identity information of the user according to the PCC rule request message, and re-determine the identity of the CSG to which the user belongs in the current access cell, and according to the identity of the user in the CSG and CSG ID, re-engineering new PCC rules and/or new trigger events.
  • the second receiving module 1070 is configured to receive a session modification response message, where the session modification response message carries the policy and charging control rule and/or the trigger event of the user that is re-defined by the rule formulation entity.
  • the rule execution module 1030 may be further configured to perform service quality and charging control on the service data flow of the user according to the policy and charging control rule of the user that is re-defined by the rule formulation entity.
  • the event monitoring module 1050 can also be used to monitor the occurrence of the trigger event of the above user re-enacted by the rule making entity.
  • rule-making entity in this embodiment may be the PCRF entity as described in the second embodiment or the third embodiment
  • rule execution entity may be the PCEF as described in the second embodiment or the third embodiment.
  • the functions described in the respective functional modules may be specifically implemented according to the method in the second embodiment or the third embodiment. For the specific implementation process, refer to the related description in the second embodiment or the third embodiment, and details are not described herein.
  • the mobility management entity is further provided in the embodiment of the present invention.
  • the eighth embodiment of the mobility management entity in the embodiment of the present invention may include:
  • the obtaining module 1110 is configured to obtain subscription information of the user.
  • the obtaining module 1110 can obtain the user subscription information from the entity storing the user subscription information in real time or at a time.
  • the sending module 1120 is configured to: when determining, according to the user subscription information acquired by the obtaining module 1110, that the identity of the closed subscriber group to which the user belongs to the access cell changes, sending an identity information providing message to the user equipment, where the identity information providing message carries The identity information of the above user changes.
  • the identity of the CSG in the connected cell changes, for example, if the user accesses the network through the mixed mode CSG cell, the identity of the user is changed from the CSG subscription user to the CSG non-signing. If the user, or the non-subscribed user of the CSG becomes the subscription user of the CSG, or the user accesses the network through the CSG cell in the closed mode, the identity of the user is changed from the subscription user of the CSG to the non-subscribed user of the CSG. The user is switched to another cell, where the user identity change may be due to a change in the subscription information, or the user's time limit for the user to access the CSG to which the cell belongs is expired, and the like.
  • the user subscription information obtained by the obtaining module 1110 may be that the user is allowed to access the CSG list, and the obtained module may also obtain the CSG ID of the currently accessed cell of the user from the corresponding base station or the base station gateway, and the sending module 1120 may be configured according to the CSG.
  • the ID and the allowed access to the CSG list determine whether the identity of the user at the CSG has changed.
  • the information carried by the identity information providing message may include, but is not limited to: the identity information of the user after the change.
  • the type of the identity information providing message sent by the sending module 1120 may be a non-access stratum (NAS, Non-Access-Stratum) message.
  • NAS Non-Access-Stratum
  • the user equipment can obtain the current identity of the user by receiving and parsing the identity information provided by the mobility management entity, and can obtain its current service quality and charging information according to its current identity and other application layer information.
  • the user equipment may carry the user identity information according to the identity information providing message, and update the locally stored allowed access CSG list.
  • the mobility management entity may be in an Evolved packet system (EPS).
  • EPS Evolved packet system
  • MME mobility management entity
  • SGSN GPRS Service Support Node
  • MSC Mobile Switching Centre
  • VLR Visitor Location Registe
  • a policy and charging system is further provided in the embodiment of the present invention.
  • a ninth embodiment of a policy and charging system in the embodiment of the present invention may include: a rulemaking entity 1210 and a rule execution entity. 1220, the rulemaking entity 1210 is communicably coupled to the rule enforcement entity 1220,
  • the rule making entity 1210 is configured to obtain a closed subscriber group identifier of the user accessing the cell, determine the identity of the closed subscriber group to which the user belongs in the access cell, and close the subscriber according to the closed subscriber group identifier and the subscriber in the access cell. The identity of the user group, formulating the policy and charging control rules of the user, and notifying the rule execution entity 1220 of the policy and charging control rules of the user.
  • the rule execution entity 1220 may perform policy and charging control on the service data flow of the user according to the policy and charging control rules of the user.
  • rule-making entity 1210 in this embodiment may be the rule-making entity as described in the fifth embodiment
  • the rule-executing entity 1220 may be the rule-executing entity as described in the seventh embodiment, which is described in this embodiment.
  • the functions of the rule-making entity 1210 and the rule-executing entity 1220 can be implemented according to the method described in the second embodiment or the third embodiment, and are not mentioned here.
  • the rule-making entity when a user accesses a CSG cell, the rule-making entity first determines the identity of the CSG to which the user belongs in the cell to which the cell belongs, and formulates the identity of the user based on the identity of the user.
  • the PCC rule, the rule execution entity performs quality of service and charging control on the service data flow of the user according to the foregoing PCC rule, and can ensure that the subscriber of the CSG preferentially uses the resource right while avoiding causing the operator's charging loss.
  • PCC rules and authorization credits further improve the real-time effectiveness of policy and billing control.
  • the program may be stored in a computer readable storage medium, and the storage medium may include: ROM, RAM, disk or CD, etc.

Description

策略与计费控制的实现方法、 设备及策略与计费系统 技术领域
本发明涉及通信技术领域，具体涉及一种策略与计费控制的实现方法、设 备及策略与计费系统。
背景技术
基于需求的多元化， 家庭基站（Home eNodeB )作为一种新型的基站， 被 大量的部署在家庭、 团体、公司或者学校等场所使用。 家庭基站通过闭合用户 组（CSG, Closed Subscriber Group )来控制用户成员的接入。 每个 CSG小区对 应有一个 CSG标识（CSG ID ) , 多个 CSG小区可以共享同一个 CSG ID。 每个 用户可以对应有一个允许接入 CSG列表，用户的允许接入 CSG列表用于记录了 该用户签约的闭合用户组的 CSG ID信息。
对于一个 CSG小区而言， 若从用户接入权限限制的角度考虑， 可以主要分 为闭合模式和混合模式。 其中， 闭合模式的 CSG小区只允许该 CSG的签约用户 在该 CSG小区内正常驻留以及申请业务； 混合模式的 CSG小区既允许该 CSG的 签约用户在该 CSG小区内正常驻留以及申请业务，也允许其他非签约用户在该 CSG小区内正常驻留以及申请业务。
在现有的策略与计费控制 （PCC, Policy and Charging Control )规则制定 和执行方式中， 当某个用户接入混合模式的 CSG小区时， 策略与计费规则功能 ( PCRF, Policy and Charging Rules Function )实体直接将该用户当成该 CSG的 签约用户， 按照该 CSG的签约用户的标准， 制定该用户的 PCC规则， 并将制定 好的 PCC规则发送给策略与计费执行功能 （PCEF , Policy and Charging Enforcement Function ) 实体， PCEF实体按照 PCRF实体制定的该用户的 PCC规 则， 对该用户的业务数据流进行策略与计费控制。
在实现本发明的过程中， 发明人发现， 在现有的 PCC规则制定和执行方 在一定程度上影响了该 CSG签约用户优先使用资源的权利， 同时也造成了运 营商的计费损失。
发明内容
本发明实施例所要解决的技术问题是，提供一种策略与计费控制的实现方 法、设备及策略与计费系统， 能够在保证 CSG的签约用户优先使用资源权利的 同时， 尽量避免造成运营商的计费损失。
为解决上述技术问题， 本发明实施例中提供的技术方案如下：
一种策略与计费控制的实现方法， 包括：
获取用户接入小区的闭合用户组标识；
确定所述用户在其接入小区所归属闭合用户组的身份；
根据所述闭合用户组标识和所述用户在其接入小区所归属闭合用户组的 身份， 制定所述用户的策略与计费控制规则；
将所述用户的策略与计费控制规则通知规则执行实体。
一种策略与计费控制的实现方法， 包括：
获取用户的签约信息；
在根据所述用户的签约信息判断出所述用户在其接入小区所归属闭合用 户组的身份发生变化时， 向用户设备发送身份信息提供消息， 所述身份信息提 供消息携带所述用户变化后的身份信息。
一种规则制定实体， 包括：
获 ^莫块， 用于获取用户接入小区的闭合用户组标识；
确定模块， 用于确定所述用户在其接入小区所归属闭合用户组的身份； 规则制定模块，用于根据所述闭合用户组标识和所述用户在其接入小区所 归属闭合用户组的身份， 制定所述用户的策略与计费控制规则；
通知模块 ,用于将所述规则制定模块制定的所述用户的策略与计费控制规 则通知规则执行实体。
一种规则执行实体， 包括：
第一发送模块， 用于向规则制定实体发送会话建立请求消息， 所述会话建 立请求消息携带用户当前接入小区的闭合用户组标识；
第一接收模块， 用于接收会话建立响应消息， 所述会话建立响应消息携带 所述用户的策略与计费控制规则 ,所述用户的策略与计费控制规则由所述规则 组的身份制定；
规则执行模块，用于按照所述第一接收模块接收的所述用户的策略与计费 控制规则， 对所述用户的业务数据流进行服务质量和计费控制。
一种移动性管理实体， 包括： 获取模块， 用于获取用户的签约信息；
发送模块，用于在根据所述用户的签约信息判断出所述用户在其接入小区 所归属闭合用户组的身份发生变化时， 向用户设备发送身份信息提供消息， 所 述身份信息提供消息携带所述用户变化后的身份信息。
一种策略与计费系统， 包括： 规则制定实体， 所述规则制定实体以可通信 的方式与规则执行实体相连，
所述规则制定实体用于获取用户接入小区的闭合用户组标识 ,确定所述用 户在其接入小区所归属闭合用户组的身份，根据所述闭合用户组标识和所述用 户在其接入小区所归属闭合用户组的身份，制定所述用户的策略与计费控制规 则， 将所述用户的策略与计费控制规则通知所述规则执行实体。
由上述技术方案可以看出，本发明实施例的提供的技术方案可以带来如下 有益效果： 在用户接入到 CSG小区时， 规则制定实体先确定出该用户在其接 入小区所归属 CSG的身份， 基于该用户的身份制定其 PCC规则， 能够在保证 该 CSG的签约用户优先使用资源权利的同时， 尽量避免造成运营商的计费损 失。
附图说明
为了更清楚地说明本发明实施例中的技术方案 ,下面将对实施例描述中所 需要使用的附图作简单地介绍，显而易见地， 下面描述中的附图仅仅是本发明 的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提 下， 还可以根据这些附图获得其他的附图。
图 1是本发明实施例的一种 PCC架构示意图；
图 2是本发明实施例一的一种策略与计费控制的实现方法流程图； 图 3是本发明实施例二的一种策略与计费控制的实现方法流程图； 图 4是本发明实施例二的一种 PCC规则更新的方法流程图；
图 5是本发明实施例三的一种策略与计费控制的实现方法流程图； 图 6是本发明实施例三的一种 PCC规则更新的方法流程图；
图 7是本发明实施例四的一种策略与计费控制的实现方法流程图； 图 8是本发明实施例五的一种规则制定实体示意图；
图 9是本发明实施例六的一种规则执行实体示意图；
图 10是本发明实施例七的一种规则执行实体示意图； 图 11是本发明实施例八的一种移动性管理实体示意图；
图 12是本发明实施例九的一种策略与计费系统示意图。
具体实施方式
本发明实施例提供一种策略与计费控制的实现方法、设备及策略与计费系 统， 针对用户身份的不同， 制定和执行不同的 PCC规则， 能够在保证该 CSG的 签约用户优先使用资源权利的同时， 尽量避免造成运营商的计费损失。
下面通过具体实施例， 分别进行伴细的说明。
策略与计费控制功能可以由策略与计费控制架构具体实现， PCC架构可以 如图 1所示， 该架构主要包括： PCRF实体 110、 PCEF实体 120、应用功能（AF， Application Function ) 实体 130、 签约规格库 （ SPR , Subscription Profile Repository ) 140、 在线计费系统 ( OCS, Online Charging System ) 150、 离线 计费系统（ OFCS , Offline Charging System ) 160等。
其中， PCRF实体 110是 PCC架构体系的核心， 主要用于制定基于业务数据 流的 PCC规则， PCC规则通常包括： 数据流监测、 门控（Gating ) 、 服务质量 ( QoS, Quality of Service )控制， 以及基于业务数据流的计费控制等； PCEF 实体 120—般位于网络的网关上，主要用于执行 PCRF实体 110制定的 PCC规则； AF实体 130主要用于提供业务应用的接入点； 签约规格库 140中存储了与 PCC 相关的用户签约数据； 若是在线计费， 由 PCEF实体 120和在线计费系统 150— 起进行信用管理； 若是离线计费， 由 PCEF实体 120和离线计费系统 160交换相 关计费信息。 其中， PCRF实体 110与 AF实体 130之间的接口为 Rx接口、 与签约 规格库 140之间的接口为 Sp接口、 与 PCEF实体之间的接口是 Gx接口； PCEF实 体与在线计费系统 150之间的接口为 Gy接口、 与离线计费系统 160之间的接口 为 Gz接口。
请参阅图 2， 本发明实施例中策略与计费控制的实现方法第一实施例可以 包括：
步骤 210、 获取用户接入小区的闭合用户组标识；
在一种应用场景下， 当用户接入到 CSG小区时，规则执行实体能够从承载 网络获取到该用户当前接入到的 CSG小区的 CSG标识信息，规则执行实体可以 将上述 CSG标识信息携带在 PCC的会话消息中， 发送给规则制定实体。 规则制 定实体则可以通过接收和解析上述消息， 获取到上述 CSG标识。 步骤 220、 确定上述用户在其接入小区所归属闭合用户组的身份； 确定用户在其接入小区所归属 CSG的身份，即是确定该用户是属于该 CSG 的签约用户， 还是不属于该 CSG的用户。
规则制定实体可以通过多种方式来确定上述用户在其接入小区所归属 CSG的身份， 例如， 规则制定实体可以先获取到该用户的允许接入 CSG列表， 并根据上述 CSG标识和上述 CSG列表确定出该用户是否为该 CSG的签约用户； 规则制定实体也可以接收其他实体发送的携带该用户身份信息的消息，并通过 解析接收到的上述消息 , 从上述消息中确定出该用户是否为该 CSG的签约用 户， 且不限于上述举例的方式。
步骤 230、 根据上述闭合用户组标识和上述用户在其接入小区所归属闭合 用户组的身份， 制定上述用户的策略与计费控制规则；
在一种应用场景下， 如果确定出该用户属于该 CSG的签约用户， 规则制定 实体可以按照该 CSG签约用户的标准， 制定该用户的策略与计费控制规则， 例 如可以让该用户享受到较低的费率， 以及较高的服务质量保证等； 如果确定出 该用户不属于该 CSG的用户， 规则制定实体可以按照普通小区用户的标准， 制 定该用户的策略与计费控制规则 , 例如让用户享受正常的费率和服务质量保 证。
步骤 240、 将上述用户的策略与计费控制规则通知规则执行实体。
规则执行实体获得该用户的策略与计费控制规则 ,并可以按照该用户的策 略与计费控制规则， 对该用户的业务数据流进行策略与计费控制。 制定 PCC规则的功能实体， 例如 PCRF实体， 或者是其它用于制定 PCC规则的 体，例如 PCEF实体、或者是承载绑定及事件上报功能（BBERF, Bearer Binding and Event Report Function ) 实体、 或者是其它用于执行 PCC规则的功能实体， 本发明不限于上述举例。
由上述技术方案可以看出， 在用户接入到 CSG小区时， 策略与计费规则功 能实体先确定出该用户在其接入小区所归属 CSG的身份，基于该用户的身份制 定其 PCC规则， 能够在保证该 CSG的签约用户优先使用资源权利的同时， 尽量 避免造成运营商的计费损失。 下面， 以规则制定实体是 PCRF实体， 规则执行实体是 PCEF实体为例， 进 行具体说明， 上述 PCEF实体作为承载控制和策略执行实体， 一般位于网络的 网关上， 对于不同的网络而言， 其所在实体的名称不尽相同， 例如， PCEF实 体可以位于通用无线分组业务 ( GPRS, General Packet Radio Service ) 网络中 的网关 GPRS支持节点 （GGSN, Gateway GPRS Support Node )上、 或者位于 系统架构演进（SAE, System Architecture Evolution ) 网络中的分组数据网络 网关（ PDN GW, Packet Data Network Gateway )或者服务网关（ serving Gateway ) 上， 本发明不限于上述举例。 为便于理解， 下面以 PCRF实体利用用户的允许接入 CSG列表和 CSG标识 来确定用户的身份， 进而制定对应的 PCC规则为例， 进行具体说明， 请参阅图 3 , 本发明实施例中策略与计费控制的实现方法第二实施例可以包括：
步骤 301、 PCEF实体向 PCRF实体发送 IP-CAN会话建立请求消息；
IP-CAN ( IP Connectivity Access Network IP连通接入网）会话， 是 PCRF 实体与 PCEF实体之间的一种会话 , 本实施例以 PCRF实体与 PCEF实体通过 IP-CAN^ 舌交互信息为例， 进行说明， 当然不局限于此。
当用户从某个 CSG小区接入到网络时， PCEF实体在和 PCRF实体建立 IP-CAN^ 舌前， 可以从承载网络获取到用户当前接入小区的 CSG II 言息。
举例来说，在一种应用场景下，承载网络的移动性管理实体可以将用户当 前接入的 CSG小区的 CSG ID信息携带在 GPRS隧道协议 ( GTP , GPRS Tunnelling Protocol ) 消息中 , 并将上述 GTP消息直接或经由中间节点发送给 PCEF实体， 上述 GTP消息还可以携带用户标识（例如， UE标识）或承载标识 信息、以及用户当前接入小区的类型信息， PCEF实体通过接收和解析上述 GTP 消息， 获得其携带的相关信息。其中， 小区类型可以是： 大型小区、 中型小区、 微型小区、 微微小区等等。
PCEF实体可以将获得的 CSG ID信息携带在 IP-CAN会话建立请求消息中， 向 PCRF实体发送上述 IP-CAN会话建立请求消息。上述 IP-CAN会话建立请求消 息还可以携带用户标识信息、 以及用户接入小区的类型信息等。
步骤 302、 PCRF实体向 SP½送规格请求消息；
若 PCRF实体上没有保存该用户的签约信息， PCRF实体可以向 SPRJ^送规 格请求消息， 请求从 SPR获取该用户签约信息， 上述规格请求消息可以携带用 户标识信息等。
步骤 303、 SPR向 PCRF实体发送规格响应消息；
SPR可以将该用户的允许接入 CSG列表信息携带在规格响应消息中 , 将其 发送给 PCRF实体。 用户的允许接入 CSG列表记录了该用户签约的闭合用户组 的 CSG ID信息。 区的 CSG ID, 确定出该用户在其接入小区所归属的 CSG的身份， 即确定该用 户在当前小区是 CSG用户还是非 CSG用户；
上述步骤 302至步骤 304为 PCRF实体确定用户身份的过程， 可选的， PCRF 实体还可以通过如下步骤确定用户的身份：
在一种应用场景下， PCRF实体将用户的标识和用户当前接入小区的 CSG ID携带在规格请求消息， 并将其发送给 SPR;
SPR接收并解析上述规格请求消息， 获得用户标识和用户当前接入小区的 CSG ID; SPR根据获得的用户标识， 查找出该用户的允许接入 CSG列表， 并根 据上述 CSG ID判断出该用户在该 CSG的身份是属于该 CSG的签约用户， 还是 不属于该 CSG的用户； SPR可以在规格响应消息中携带该用户的身份指示信 息， 并向 PCRF实体发送规格响应消息；
PCRF实体接收上述规格响应消息， 并可以通过解析从上述规格响应消息 中确定用户在该 CSG的身份。
特别的，如果 PCRF实体当前存储有上述用户的允许接入闭合用户组列表， 则 PCRF实体可以利用其获得的 CSG ID和自身当前存储的所述用户的允许接 入闭合用户组列表， 确定出上述用户在其接入小区所归属闭合用户组的身份。
步骤 305、 PCRF实体根据用户的身份和用户当前接入小区的 CSG ID, 制 定该用户的 PCC规则；
对应用户身份的不同， 以及用户接入小区所归属 CSG的不同， PCRF实体 可以制定出相应不同的 PCC规则。 在一种应用场景下， 若确定出用户身份为该 CSG的签约用户， PCRF实体可以按照该 CSG签约用户的标准， 制定该用户的 策略与计费控制规则， 例如可以让该用户享受到较低的费率， 以及较高的服务 质量保证等； 若确定出该用户不属于该 CSG的用户， PCRF实体可以按照普通 小区用户的标准，制定该用户的策略与计费控制规则，例如让用户享受正常的 费率和服务质量保证。
进一步的， PCRF实体还可以制定需要 PCEF实体监测的触发事件， 当 PCEF 实体监测到 PCRF实体制定的触发事件发生时， PCEF实体执行与发生的触发事 件对应的动作。
在一种应用场景下， PCRF实体制定的触发事件可以包括： 用户接入小区 的类型发生改变、 用户接入小区所归属 CSG发生改变， 且不限于上述举例。
其中， 用户接入小区的类型发生改变可以是： 用户从一种类型的小区移动 到另一种类型的小区， 例如， 用户从微微小区移动到了大型小区等； 用户接入 小区所归属 CSG发生改变可以是：用户从归属于某个 CSG的小区移动到归属于 另一个 CSG的小区。
可选的， 多个 CSG可以组成一个 CSG集合， 若 CSG集合中的各个 CSG的签 约用户拥有相同的优先权利 , 上述用户在 CSG集合中的每个 CSG的身份也相 同， 则上述用户在归属于 CSG集合的各个 CSG小区内移动时， PCEF实体可以 不向 PCRF实体请求新的 PCC规则。
当 PCEF实体监测到 PCRF实体制定的上述触发事件发生时， 会触发 PCEF 实体向 PCRF实体请求新的 PCC规则 , 做到及时有效的调整。
步骤 306、 PCRF实体向 PCEF实体发送 IP-CAN会话建立响应消息；
PCRF实体可以将其制定的该用户的 PCC规则信息携带在建立 IP-CAN会 话建立响应消息中， 向 PCEF实体发送上述 IP-CAN会话建立响应消息。 上述建 立 IP-CAN会话请求响应消息中还可以携带 PCRF实体制定的触发事件信息、 以 及用户在该 CSG的身份等等信息。
PCEF实体接收并解析 IP-CAN会话建立响应消息 , 获得其携带的上述用户 的 PCC规则， 以及触发事件等信息， 并可以将获得的上述信息进行存储。
PCEF实体可以按照 PCRF实体制定的该用户的 PCC规则， 对该用户的业务 数据流进行服务质量和计费控制 , 并进行触发事件监测等。
步骤 307、 PCEF实体向 OCS发送信用请求消息；
如果进行在线计费， PCEF实体向 OCS发送信用请求消息， 请求 OCS为上 述用户授权信用。上述信用请求消息可以携带用户标识信息，还可以携带用户 当前接入 CSG小区的 CSG ID, 和 /或用户在其接入小区所归属 CSG的身份等等 信息。
步骤 308、 OCS向 PCEF实体发送信用响应消息。
OCS接收并解析上述信用请求消息， 获取其携带的用户标识、用户当前接 入 CSG小区的 CSG ID、 用户在其接入小区所归属 CSG的身份等等信息， 并可 以存储其获得的上述信息。
OCS可以根据用户标识或计费标识， 为该用户授权信用。
进一步的， OCS还可以制定需要 PCEF实体监测的信用重授权事件， 当 PCEF实体监测到 OCS制定的信用重授权事件发生时， PCEF实体可以执行与发 生的该信用重授权事件相对应的动作。
在一种应用场景下， OCS制定的信用重授权事件可以包括： 用户接入小区 的类型改变、 用户接入小区所归属的 CSG改变、 用户在其接入小区所归属 CSG 的身份改变， 但不限于上述举例。
其中， 用户在其接入小区所归属 CSG的身份改变可以是： 用户从 CSG的非 签约用户变成了其签约用户、 或者从其签约用户变成了其非签约用户等。
OCS可以将其为上述用户授权的信用、以及其制定的信用重授权事件等信 息携带在信用响应消息中 , 将其发送给 PCEF实体。
PCEF实体接收并解析上述信用响应消息 , 获得 OCS为上述用户授权的信 用， 以及其制定的信用重授权事件等信息， 并可以将上述信息进行存储。
可选的， 如果 OCS中存储有该用户的允许接入 CSG列表， 则上述信用请求 消息可以不携带用户在该 CSG的身份信息， OCS可以根据该用户的允许接入 CSG列表和该用户当前接入小区的 CSG ID确定出用户在该 CSG的身份； OCS 制定信用重授权事件可以不包括用户在 CSG的身份发生改变的事件。
PCEF实体根据从 OCS获得的信用对该用户的业务数据流进行计费处理。 当 PCEF实体监测到 OCS制定的上述信用重授权事件发生时， 触发 PCEF实 体向 OCS请求授权新的信用， 做到及时有效的调整。
需要说明的是， 步骤 307 ~ 308和步骤 301 ~ 306之间没有必然的先后顺序， 步骤 307 ~ 308也可以先于步骤 301 ~ 306执行， 或者在其它时刻执行。
进一步的， 参见图 4， 本实施例中还提供 PCC规则和 /或触发事件等的更新 流程， 具体可以包括：
步骤 401、 PCEF实体向 PCRF实体发送 IP-CAN会话修改指示消息； 当 PCEF实体监测到 PCRF实体制定的触发事件发生时，或者在其它条件的 触发下， PCEF实体可以向 PCRF实体发送 IP-CAN会话修改指示消息， 请求获 得新的 PCC规则。
在一种应用场景下， 当 PCRF实体制定的触发事件发生时， PCEF实体可以 接收到承载网络的移动性管理实体发送的 GTP消息， 该 GTP消息携带有用户当 前接入的新 CSG小区的 CSG ID信息，或用户接入的新小区的类型信息等。 PCEF 实体可以通过接收和解析上述 GTP消息， 监测上述触发事件发生的情况。
当 PCEF实体监测到上述触发事件发生时， 将其获得的用户当前接入的新 CSG小区的 CSG ID信息、 或用户接入新小区的类型信息等携带在 IP-CAN^ 舌 修改指示消息中， 向 PCRF实体发送上述 IP-CAN^ 舌修改指示消息。
步骤 402、 SPR向 PCRF实体发送规格提供消息；
当 SPR存储的该用户的允许接入 CSG列表发生变化时（例如， 用户在某些 CSG的身份发生了变化）， SPR可以将该用户更新的允许接入 CSG列表携带在 签约信息提供消息中， 向 PCRF实体发送上述规格提供消息。
可以理解的是， 步骤 401和步骤 402是并列的关系， 没有必然时间的先后顺 序 , 步骤 401和步骤 402也可以单独触发的 PCRF实体制定新的 PCC规则。
步骤 403、 PCRF实体制定新的 PCC规则和 /或新的触发事件；
PCRF实体接收并解析上述 IP-CAN会话修改指示消息 , 和 /或规格提供消 息， 获得其携带的相关信息。
在一种应用场景下， PCRF实体可以根据上述 PCC规则请求消息和 /或规格 提供消息携带的信息， 重新确定该用户在其当前接入小区所归属 CSG的身份， 并根据用户在该 CSG的身份以及其 CSG ID, 重新制定出与之对应的新的 PCC 规则和 /或新的触发事件。
步骤 404、 PCRF实体向 PCEF实体发送 IP-CAN会话修改回应消息；
PCRF实体可以将其制定的新的 PCC规则和 /或触发事件信息携带在
IP-CAN会话修改回应消息中，并向 PCEF实体发送上述 IP-CAN会话修改回应消 进一步的， 上述 IP-CAN会话修改回应消息中还可以携带该用户在其当前 接入小区所归属的 CSG的身份信息等。
PCEF实体接收并解析上述 IP-CAN会话修改回应消息， 获得其携带的该用 户新的 PCC规则， 和 /或新的触发事件等信息， 并可以将上述信息进行存储。
PCEF实体可以按照 PCRF实体制定的该用户新的 PCC规则， 对该用户的业 务数据流进行服务质量和计费控制 , 并进行触发事件的监测等。
步骤 405、 PCEF实体向 OCS发送信用请求消息；
当 PCEF实体监测到 OCS制定的信用重授权事件发生时， PCEF实体可以向
OCS发送信用请求消息， 请求 OCS为上述用户授权新的信用。
在一种应用场景下， PCEF实体可以根据其监测的承载事件， 以及 PCC规 则提供消息携带的信息， 判断 OCS制定的信用重授权事件是否发生， 若信用重 授权事件发生了， 则向 OCS发送信用请求消息， 上述信用请求消息可以携带用 户标识或计费标识、 用户当前接入小区的 CSG标识， 或 /和用户在其接入小区 所归属的 CSG的身份信息等。
步骤 406、 OCS向 PCEF实体发送信用响应消息；
OCS可以 据信用请求消息携带的用户标识或该用户的计费标识、用户当 前接入小区的 CSG ID、 或 /和用户在该 CSG的身份等信息， 重新对该用户进行 信用授权， 并将新授权的信用携带在信用响应消息中， 发送给 PCEF实体。
进一步的， OCS还可以重新制定需要 PCEF实体监测的重授权事件， 当 PCEF实体监测到 OCS制定的重授权事件发生时， PCEF实体执行与该发生的重 授权事件对应的动作。
在一种应用场景下， OCS重新制定的信用重授权事件可以包括： 用户接入 小区的类型改变、 用户接入小区所归属的 CSG改变、 用户在 CSG的身份改变， 且不限于上述举例。
上述信用响应消息还可以携带 OCS重新制定的信用重授权事件信息 , PCEF实体接收并解析上述信用响应消息 , 获得 OCS为上述用户重新授权的信 用和信用重授权事件等信息， 并可以将获得的上述信息进行存储。
可选的， 如果 OCS中存储有该用户的允许接入 CSG列表， 则上述信用请求 消息可以不携带用户在该 CSG的身份信息， OCS可以根据该用户的允许接入 CSG列表和该用户当前接入小区的 CSG ID确定出用户在该 CSG的身份； OCS 重新制定信用重授权事件可以不包括用户在 CSG的身份发生改变的事件。
PCEF实体根据从 OCS获得的信用对该用户的业务数据流进行计费处理。 当 PCEF实体监测到 OCS制定的上述信用重授权事件发生时， 触发 PCEF实 体向 ocs请求授权新的信用 , 进而做到及时有效的调整。
需要说明的是， 步骤 405 ~ 406和步骤 401 ~ 404之间没有必然的先后顺序， 步骤 405 ~ 406也可以先于步骤 401 ~ 404执行， 或者在其它时刻执行。
由上述技术方案可以看出， 在用户接入到 CSG小区时， PCRF实体先确定 出该用户在其接入小区所归属 CSG的身份， 基于该用户的身份制定其 PCC规 则， PCEF实体按照上述 PCC规则对该用户的业务数据流进行服务质量和计费 控制， 能够在保证该 CSG的签约用户优先使用资源权利的同时， 尽量避免造成 运营商的计费损失。
进一步的，通过监测触发事件和信用重授权事件的发生情况，及时的调整 PCC规则和授权信用， 进一步提高了策略与计费控制的实时有效性。 为便于理解，下面以 PCRF实体通过接收和解析携带用户身份信息的消息， 确定用户的身份， 进而制定对应的 PCC规则为例， 进行具体说明， 请参阅图 5， 本发明实施例中策略与计费控制的实现方法第三实施例可以包括：
步骤 501、 PCEF实体向 PCRF实体发送 IP-CAN会话建立请求消息； 说明， 当然不局限于此。
当用户从某个 CSG小区接入到网络时， PCEF实体在和 PCRF实体建立 IP-CAN^ 舌前， 可以先从承载网络获取用户当前接入小区的 CSG II 言息， 以 及用户在其接入小区所归属 CSG的身份信息。 其中， 身份信息可以是能够指示 用户在其接入小区所归属 CSG的身份的任意信息。
举例来说，在一种应用场景下，承载网络的移动性管理实体可以将用户当 前接入的 CSG小区的 CSG ID、 以及用户在该 CSG的身份信息携带在 GTP消息 中， 并将上述 GTP消息直接或经由中间节点发送给 PCEF实体， 上述 GTP消息 还可以携带用户标识或承载标识信息、 以及用户当前接入小区的类型信息， 小 区的类型可以是： 大型小区、 中型小区、 微型小区、 微微小区等等。 PCEF实 体通过接收和解析上述 GTP消息 , 获得其携带的相关信息。
PCEF实体可以将其获得的用户当前接入小区的 CSG ID信息， 以及用户 在该 CSG的身份信息携带在 IP-CAN会话建立请求消息中， 向 PCRF实体发 送上述 IP-CAN会话建立请求消息。 上述 IP-CAN会话建立请求消息还可以携 带用户标识信息、 以及用户接入小区的类型信息等。
步骤 502、 PCRF实体才艮据用户当前接入小区的 CSG ID和用户在其接入 小区所归属 CSG的身份， 制定该用户的 PCC规则；
PCRF实体可以接收上述 IP-CAN会话建立请求消息， 并通过并解析， 从 上述 IP-CAN会话建立请求消息中获得其携带的用户当前接入小区的 CSG ID 信息， 以及用户在该 CSG的身份信息等， 进而确定出上述用户在其接入小区 所归属 CSG的身份。
对应用户身份的不同， 以及用户接入小区所归属 CSG的不同， PCRF实 体可以制定出相应不同的 PCC规则。 在一种应用场景下， 若确定出用户身份 为该 CSG的签约用户， PCRF实体可以按照该 CSG签约用户的标准， 制定该 用户的策略与计费控制规则，进而可以让该用户享受到较低的费率， 以及较高 的服务质量保证等； 若确定出该用户不属于该 CSG的用户， PCRF实体可以 按照普通小区用户的标准， 制定该用户的策略与计费控制规则，进而让用户享 受正常的费率和服务质量保证。
进一步的， PCRF实体还可以制定需要 PCEF实体监测的触发事件， 当 PCEF 实体监测到 PCRF实体制定的触发事件发生时， PCEF实体执行与发生的触发事 件对应的动作。
在一种应用场景下， PCRF实体制定的触发事件可以包括： 用户接入小区 的类型发生改变、 用户接入小区所归属 CSG发生改变、 用户在 CSG的身份发生 改变， 且不限于上述举例。
其中， 用户接入小区的类型发生改变可以是： 用户从一种类型的小区移动 到另一种类型的小区， 例如， 用户从微微小区移动到了大型小区等； 用户接入 小区所归属 CSG发生改变可以是：用户从归属于某个 CSG的小区移动到归属于 另一个 CSG的小区； 用户在 CSG的身份发生改变可以是： 用户从上述 CSG的非 签约用户变成了其签约用户、 或者从其签约用户变成了其非签约用户等。
可选的， 多个 CSG可以组成一个 CSG集合， 若 CSG集合中的各个 CSG的签 约用户具有相同的优先权利 , 上述用户在 CSG集合中的每个 CSG的身份也相 同， 则上述用户在归属于 CSG集合的各个 CSG小区内移动时， PCEF实体可以 不向 PCRF实体请求新的 PCC规则。
当 PCEF实体监测到 PCRF实体制定的上述触发事件发生时，会触发 PCEF 实体向 PCRF实体请求新的 PCC规则 , 做到及时有效的调整。
步骤 503、 PCRF实体向 PCEF实体发送 IP-CAN会话建立响应消息； PCRF实体可以将其制定的该用户的 PCC规则信息携带在建立 IP-CAN会 话建立响应消息中， 向 PCEF实体发送上述 IP-CAN会话建立响应消息。 上述建 立 IP-CAN会话请求响应消息中还可以携带 PCRF实体制定的触发事件等等信
PCEF实体接收并解析 IP-CAN会话建立响应消息 , 获得其携带的上述用户 的 PCC规则， 以及触发事件等信息， 并可以将获得的上述信息进行存储。
PCEF实体可以按照 PCRF实体制定的该用户的 PCC规则， 对该用户的业务 数据流进行服务质量和计费控制， 并进行触发事件监测等。
步骤 504、 PCEF实体向 OCS发送信用请求消息；
如果进行在线计费， PCEF实体向 OCS发送信用请求消息， 请求 OCS为上 述用户授权信用。上述信用请求消息可以携带用户标识信息，还可以携带用户 当前接入 CSG小区的 CSG ID, 和 /或用户在其接入小区所归属 CSG的身份等等 信息。
步骤 505、 OCS向 PCEF实体发送信用响应消息。
OCS接收并解析上述信用请求消息， 获取其携带的用户标识、用户当前接 入 CSG小区的 CSG ID、 用户在其接入小区所归属 CSG的身份等等信息， 并可 以存储其获得的上述信息。
OCS可以 ^居用户标识或计费标识， 为该用户授权信用。
进一步的， OCS还可以制定需要 PCEF实体监测的信用重授权事件， 当 PCEF实体监测到 OCS制定的信用重授权事件发生时， PCEF实体执行与发生的 该信用重授权事件相对应的动作。
在一种应用场景下， OCS制定的信用重授权事件可以包括： 用户接入小区 的类型改变、 用户接入小区所归属的 CSG改变、 用户在 CSG的身份改变， 且不 限于上述举例。
OCS可以将其为上述用户授权的信用、以及其制定的信用重授权事件等信 息携带在信用响应消息中 , 将其发送给 PCEF实体。
PCEF实体接收并解析上述信用响应消息 , 获得 OCS为上述用户授权的信 用， 以及其制定的信用重授权事件等信息， 并可以将上述信息进行存储。 可选的， 如果 OCS中存储有该用户的允许接入 CSG列表， 则上述信用请求 消息可以不携带用户在该 CSG的身份信息， OCS可以根据该用户的允许接入 CSG列表和该用户当前接入小区的 CSG ID确定出用户在该 CSG的身份； OCS 制定信用重授权事件可以不包括用户在 CSG的身份发生改变的事件。
PCEF实体根据从 OCS获得的信用进行对该用户的业务数据流进行计费。 当 PCEF实体监测到 OCS制定的上述信用重授权事件发生时，触发 PCEF 实体向 OCS请求授权新的信用 , 做到及时有效的调整。
进一步的， 参见图 6， 本实施例中还提供 PCC规则和 /或触发事件等的更新 流程， 具体可以包括：
步骤 601、 PCEF实体向 PCRF实体发送 IP-CAN会话修改指示消息； 当 PCEF实体监测到 PCRF实体制定的触发事件发生时，或者在其它条件的 触发下， PCEF实体可以向 PCRF实体发送 IP-CAN会话修改指示消息， 请求获 得新的 PCC规则。
在一种应用场景下， 当 PCRF实体制定的触发事件发生时， PCEF实体可以 接收到承载网络的移动性管理实体发送的 GTP消息， 该 GTP消息携带有用户当 前接入的新 CSG小区的 CSG ID信息、 用户在该 CSG的身份信息、 或用户接入 的新小区的类型信息等。 PCEF实体可以通过接收和解析上述 GTP消息， 监测 上述触发事件发生的情况。
当 PCEF实体监测到触发事件发生时， 将其获得的用户当前接入的新 CSG 小区的 CSG ID信息、 或用户在其接入小区所归属 CSG的身份信息、 或用户接 入新小区的类型信息等携带在 IP-CAN会话修改指示消息中， 向 PCRF实体发送 上述 IP-CAN会话修改指示消息。
步骤 602、 PCRF实体制定新的 PCC规则和 /或新的触发事件；
PCRF实体接收并解析上述 IP-CAN会话修改指示消息， 获得其携带的相关 信息。
在一种应用场景下， PCRF实体可以根据上述 IP-CAN会话修改指示消息携 带用户的身份信息， 重新确定出该用户在其当前接入小区所归属 CSG的身份， 并根据用户在该 CSG的身份以及其 CSG ID, 重新制定出与之对应的新的 PCC 规则和 /或新的触发事件。
步骤 603、 PCRF实体向 PCEF实体发送 IP-CAN会话修改回应消息； PCRF实体可以将其制定的新的 PCC规则和 /或触发事件等信息携带在 IP-CAN会话修改回应消息中，并向 PCEF实体发送上述 IP-CAN会话修改回应消
PCEF实体接收并解析上述 IP-CAN会话修改回应消息， 获得其携带的该用 户新的 PCC规则， 和 /或新的触发事件等信息， 并可以将上述信息进行存储。
PCEF实体可以按照 PCRF实体制定的该用户新的 PCC规则， 对该用户的业 务数据流进行服务质量和计费控制 , 并进行触发事件的监测等。
步骤 604、 PCEF实体向 OCS发送信用请求消息；
当 PCEF实体监测到 OCS制定的信用重授权事件发生时， PCEF实体可以向 OCS发送信用请求消息， 请求获得新的信用。
在一种应用场景下， PCEF实体可以根据其监测的承载事件， 判断 OCS制 定的信用重授权事件是否发生， 若信用重授权事件发生了， 则向 OCS发送信用 请求消息，上述信用请求消息可以携带用户标识或该用户的计费标识、用户当 前接入小区的 CSG标识， 或 /和用户在其接入小区所归属 CSG的身份信息等。
步骤 605、 OCS向 PCEF实体发送信用响应消息；
OCS可以 据信用请求消息携带的用户标识或该用户的计费标识、用户当 前接入小区的 CSG ID、 或 /和用户在该 CSG的身份等信息， 重新对该用户进行 信用授权， 并将新授权的信用携带在信用响应消息中， 发送给 PCEF实体。
进一步的， OCS还可以重新制定需要 PCEF实体监测的重授权事件， 当 PCEF实体监测到 OCS制定的重授权事件发生时， PCEF实体执行与该发生的重 授权事件对应的动作。
在一种应用场景下， OCS重新制定的信用重授权事件可以包括： 用户接入 小区的类型改变、用户接入小区所归属的 CSG改变、用户在其接入小区所归属 CSG的身份改变， 且不限于上述举例。
上述信用响应消息还可以携带 OCS重新制定的信用重授权事件信息，
PCEF实体接收并解析上述信用响应消息 , 获得 OCS为上述用户重新授权的信 用和信用重授权事件等信息， 并可以将获得的上述信息进行存储。
可选的， 如果 OCS中存储有该用户的允许接入 CSG列表， 则上述信用请求 消息可以不携带用户在该 CSG的身份信息， OCS可以根据该用户的允许接入 CSG列表和该用户当前接入小区的 CSG ID确定出用户在该 CSG的身份； OCS 重新制定信用重授权事件可以不包括用户在 CSG的身份发生改变的事件。
PCEF实体根据从 OCS获得的信用对该用户的业务数据流进行计费处理。 当 PCEF实体监测到 OCS制定的上述信用重授权事件发生时， 触发 PCEF实 体向 OCS请求授权新的信用 , 进而做到及时有效的调整。
需要说明的是， 步骤 604 ~ 605和步骤 601 ~ 603之间没有必然的先后顺序， 步骤 604 ~ 605也可以先于步骤 601 ~ 603执行， 或者在其它时刻执行。
由上述技术方案可以看出， 在用户接入到 CSG小区时， PCRF实体先确定 出该用户在其接入小区所归属 CSG的身份， 基于该用户的身份制定其 PCC规 则， PCEF实体按照上述 PCC规则对该用户的业务数据流进行服务质量和计费 控制， 能够在保证该 CSG的签约用户使用资源权利的同时， 尽量避免造成运营 商的计费损失。
进一步的，通过监测触发事件和信用重授权事件的发生情况，及时的调整 PCC规则和授权信用 , 进一步提高了策略与计费控制的实时有效性。
需要说明的是， 上述实施例二和实施例三是将 PCRF实体作为 PCC规则制 定实体， 将 PCEF实体作为 PCC规则执行实体进行举例说明的， 当然不局限于 此， 也可以是由其他任意的实体来制定 PCC规则， 和 /或由其他任意的实体来 执行 PCC规则。 此外， 请参阅图 7， 本发明实施例中策略与计费控制的实现方法第四实施 例可以包括：
步骤 701、 移动性管理实体获取用户签约信息；
在一种应用场景下，移动性管理实体可以从存储有用户签约信息的实体获 取用户签约信息。
步骤 702、 移动性管理实体在根据用户签约信息判断出用户在其接入小区 所归属 CSG的身份发生变化时， 向用户设备发送身份信息提供消息。
若连接态的用户在其接入小区所归属 CSG的身份改变， 例如， 用户通过混 合模式的 CSG小区接入网络的情况下，上述用户的身份由该 CSG的签约用户变 成该 CSG的非签约用户、 或者由该 CSG的非签约用户变成该 CSG的签约用户、 或者用户通过闭合模式的 CSG小区接入网络的情况下 ,用户的身份由该 CSG的 签约用户变成该 CSG的非签约用户， 导致用户被切换到其它小区， 其中， 用户 身份改变原因可能是其签约信息的改变，或者用户在其接入小区所归属 CSG的 用户时限到期等等。
移动性管理实体获取的用户签约信息可以是，上述用户的允许接入 CSG列 表，移动性管理实体可以从对应基站或基站网关获取用户当前接入小区的 CSG ID, 移动性管理实体可以根据上述 CSG ID和允许接入 CSG列表判断该用户在 该 CSG的身份是否发生变化。
上述身份信息提供消息携带的信息可以包括但不限于上述用户变化后的 身份信息。
移动性管理实体发送的上述身份信息提供消息的类型可以是非接入层 ( NAS, Non-Access-Stratum ) 消息。
用户设备 ( UE )可以通过接收和解析移动性管理实体发送的身份信息提 供消息，获知用户的当前身份， 并可以根据自身的当前身份和其它应用层信息 获知自身的当前服务质量和计费信息。
步骤 703、 用户设备向移动性管理实体发送身份信息响应消息。
用户设备通过向移动性管理实体发送身份信息响应消息，提示移动性管理 实体其成功接收到了移动性管理实体发送的身份信息提供消息。
进一步的， UE可以根据身份信息提供消息携带用户身份信息， 更新其本 地存储的允许接入 CSG列表。
由上述技术方案可以看出，当用户在其接入小区所归属 CSG的身份发生变 化时，移动性管理实体及时的将用户的身份通知用户，有利于提高策略与计费 控制的透明， 进而提升用户体验。
需要说明的是， 上述各个实施例中所述的移动性管理实体在不同的系统的 具体名称可能不尽相同， 例如， 上述移动性管理实体可以是演进分组域系统 ( EPS, Evolved packet system ) 中的 MME ( mobility management entity, 移动 性管理单元）、 或者是通用分组无线业务 (GPRS, General Packet Radio Service) 系统中的 GPRS服务支持节点 （SGSN, Serving GPRS Support Node ) 、 或者 是其他系统中的， 移动交换中心 （MSC、 Mobile Switching Centre )、 访问位 置寄存器（VLR, Visitor Location Registe ) , 但不限于上述举例。 实施例五 相应的， 本发明实施例中还提供一种规则制定实体， 请参阅图 8， 本发明 实施例中规则制定实体第五实施例可以包括：
获耳^莫块 810 , 用于获取用户接入小区的闭合用户组标识。
在一种应用场景下， 当用户接入到 CSG小区时， 规则执行实体能够从承载 网络获取到该用户当前接入到的 CSG小区的 CSG标识信息，规则执行实体可以 将上述 CSG标识信息携带在 PCC的会话消息中， 发送给规则制定实体。 获取模 块 810可以通过接收和解析上述消息， 获取到上述 CSG标识。
确定模块 820, 用于确定上述用户在其接入小区所归属的闭合用户组的身 份。
其中， 确定模块 820可以通过多种方式来确定上述用户在其接入小区所归 属 CSG的身份， 举例来说， 确定模块 820可以先获取到该用户的允许接入 CSG 列表，并根据上述 CSG标识和上述 CSG列表确定出该用户是否为该 CSG的签约 用户； 确定模块 820也可以接收其他实体发送的携带该用户身份信息的消息， 并通过解析接收到的上述消息 ,从上述消息中确定出该用户是否为该 CSG的签 约用户， 本实施例不限于上述举例的方式。
规则制定模块 830， 用于根据获取模块 810获取的闭合用户组标识，和确定 模块 820确定出的上述用户在其接入小区所归属闭合用户组的身份， 制定上述 用户的策略与计费控制规则。
在一种应用场景下， 如果确定模块 820确定出上述用户属于该 CSG的签约 用户， 规则制定模块 830可以按照该 CSG签约用户的标准， 制定该用户的策略 与计费控制规则，例如可以让该用户享受到较低的费率， 以及较高的服务质量 保证等； 如果确定模块 820确定出该用户不属于该 CSG的用户， 规则制定模块 830可以按照普通小区用户的标准， 制定该用户的策略与计费控制规则， 例如 让用户享受正常的费率和服务质量保证。
通知模块 840, 用于将规则制定模块 830制定的，上述用户的策略与计费控 制规则通知规则执行实体。
其中 , 通知模块 840可以通过多种方式将该用户的策略与计费控制规则通 知规则执行实体。 例如， 在一种应用场景下， 通知模块 840可以将制定出的该 用户的策略与计费控制规则携带在会话请求消息中，向规则执行实体发送该消 息。 上述规则执行实体获得上述用户的策略与计费控制规则 ,并可以按照上述 用户的策略与计费控制规则， 对上述用户的业务数据流进行策略与计费控制。
进一步的， 上述确定模块 820可以包括： 第一发送子模块 821、 第一接收子 模块 822、 第一确定子模块 823。
其中， 第一发送子模块 821 , 用于向签约规格库发送规格请求消息， 上述 规格请求消息携带用户标识信息。
签约规格库中存储用户的签约信息，签约规格库可以将该用户的允许接入 CSG列表信息携带在规格响应消息中， 将其发送给规则制定实体。
第一接收子模块 822, 用于接收规格响应消息， 上述规格响应消息携带上 述用户的允许接入闭合用户组列表，上述允许接入闭合用户组列表记录了上述 用户签约的闭合用户组的 CSG ID信息。 述闭合用户组标识， 确定出上述用户在其接入小区所归属闭合用户组的身份。
进一步的 , 上述通知模块 840还可以用于将第一确定子模块 823确定出的， 上述用户在其接入小区所归属闭合用户组的身份通知上述规则执行实体。
此外，上述确定模块 820也还可以包括： 第二接收子模块 824和第二确定子 模块 825。
第二接收子模块 824， 用于接收规则执行实体发送的会话建立请求消息， 上述会话建立请求消息携带上述用户在其接入小区所归属闭合用户组的身份 信息。
第二确定子模块 825 ,用于从第二接收子模块 824接收的会话建立请求消息 中确定出上述用户在其接入小区所归属闭合用户组的身份。
上述规则制定实体还可以包括：
事件制定模块 850， 用于制定需要上述规则执行实体监测的触发事件， 使 得上述规则执行实体在监测到上述触发事件发生时，执行与上述发生的触发事 件相对应的步骤，上述触发事件至少包括如下事件之一： 上述用户接入小区的 类型改变、上述用户接入小区所归属的闭合用户组改变、上述用户在其接入小 区所归属闭合用户组的身份改变。
上述通知模块 840还可以用于，将上述事件制定模块 850制定的上述触发事 件通知上述规则执行实体。 上述规则制定实体还可以包括：
接收模块 860， 用于接收会话修改指示消息， 上述会话修改指示消息携带 上述用户接入新小区的闭合用户组标识信息、或上述用户接入新小区的类型信 息、 或和 /或上述用户在其接入小区所归属闭合用户组的新身份信息； 和 /或接 收规格提供消息，上述规格提供消息携带更新的上述用户的允许接入闭合用户 组列表。
上述规则制定模块 830还可以用于，根据接收模块 860接收到的会话修改指 示消息和 /或规格提供消息携带的信息， 重新制定上述用户的策略与计费控制 规则，上述事件制定模块 850还可以用于，根据接收模块 860接收到的会话修改 指示消息和 /或规格提供消息携带的信息， 制定上述用户的触发事件。
发送模块 870， 用于向上述规则执行实体发送会话修改回应消息， 上述会 话修改回应消息携带规则制定模块 830 重新制定的上述用户的策略与计费控 制规则， 和 /或携带事件制定模块 850重新制定的上述用户的触发事件等
规则执行实体可以按照规则制定实体制定的该用户新的 PCC规则， 对该 用户的业务数据流进行服务质量和计费控制， 并进行触发事件的监测等。
可以理解的是，本实施例所述的规则执行实体可以是如实施例二或实施例 三所述的 PCEF实体，所述的规则制定实体可以是如实施例二或实施例三所述 的 PCRF实体，其各个功能模块所述的功能可以根据实施例二或实施例三所述 的方法具体实现， 其具体实现过程可以参见实施例二或实施例三中的相关描 述， 在此不再赞述。 实施例六
相应的， 本发明实施例中还提供一种规则执行实体， 请参阅图 9, 本发明 实施例中规则制定实体第六实施例可以包括：
第一发送模块 910, 用于向在线计费系统发送信用请求消息， 上述信用请 求消息携带用户标识信息。
上述信用请求消息还可以携带用户当前接入 CSG小区的 CSG ID, 和 /或用 户在其接入小区所归属 CSG的身份等等信息。
第一接收模块 920, 用于接收信用响应消息， 上述的信用响应消息携带所 述在线计费系统为用户授权的信用信息 ,以及上述在线计费系统制定的信用重 授权事件信息，上述信用重授权事件至少包括如下事件之一： 上述用户接入小 区的类型改变、上述用户接入小区所归属的闭合用户组改变、上述用户在其接 入小区所归属闭合用户组的身份改变。
OCS可以接收并解析上述信用请求消息， 获取其携带的用户标识、用户当 前接入 CSG小区的 CSG ID、 用户在其接入小区所归属 CSG的身份等等信息， 并可以存储其获得的上述信息。
OCS可以根据用户标识或计费标识， 为该用户授权信用。
OCS还可以制定需要规则执行实体监测的信用重授权事件，当规则执行实 体监测到 OCS制定的信用重授权事件发生时，规则执行实体可以执行与发生的 该信用重授权事件相对应的动作。
OCS可以将其为上述用户授权的信用、以及其制定的信用重授权事件等信 息携带在信用响应消息中， 将其发送给规则执行实体。
计费处理模块 930 ,用于按照第一接收模块 920接收的上述在线计费系统为 上述用户授权的信用， 对上述用户的业务数据流进行计费处理；
事件监测模块 940 ,用于监测第一接收模块 920接收的上述在线计费系统制 定的上述信用重授权事件的发生情况。
进一步的， 上述规则执行实体还可以包括：
身份获取模块 950， 用于从承载网络或从策略与计费规则功能实体获取上 述用户在其接入小区所归属闭合用户组的身份信息。
在一种应用场景下， 当用户从某个 CSG小区接入到网络后， 身份获 ^莫块
950可以从承载网络获取用户当前接入小区的 CSG II 言息， 以及用户在其接入 小区所归属 CSG的身份信息、 用户当前接入小区的类型信息等等。
若 PCRF实体确定出了在其接入小区所归属闭合用户组的身份， 获取模块 950可通过接收和解析 PCRF实体发送的携带用户身份信息的消息，获得用户在 其接入小区所归属闭合用户组的身份。
进一步的， 上述规则执行实体还可以包括： 第二发送模块 960和第二接收 模块 970。
其中， 第二发送模块 960, 用于在事件监测模块 940监测到上述在线计费系 统制定的信用重授权事件发生时， 向上述在线计费系统发送信用请求消息，上 述信用请求消息携带上述用户标识 ,以及上述用户接入新小区的闭合用户组标 识信息、 或上述用户接入新小区的类型信息、 或获取模块 950获取的上述用户 在其接入小区所归属闭合用户组的身份信息。
OCS可以才 据上述信用请求消息携带的用户标识或计费标识、用户当前接 入小区的 CSG ID、 或 /和用户在该 CSG的身份等信息， 重新对该用户进行信用 授权。
进一步的， OCS还可以重新制定需要规则执行实体监测的重授权事件， 当 规则执行实体监测到 OCS制定的重授权事件发生时，规则执行实体执行与该发 生的重授权事件对应的动作。
在一种应用场景下， OCS重新制定的信用重授权事件可以包括： 用户接入 小区的类型改变、用户接入小区所归属的 CSG改变、用户在其接入小区所归属 CSG的身份改变， 且不限于上述举例。
上述信用响应消息还可以携带 OCS重新制定的信用重授权事件信息等。 第二接收模块 970, 用于接收信用响应消息， 上述信用响应消息携带上述 在线计费系统重新为上述用户授权的信用和 /或重授权事件信息。
计费处理模块 930还可以用于按照上述在线计费系统重新为上述用户授权 的信用， 对上述用户的业务数据流进行计费处理。
事件监测模块 940还可以用于监测在线计费系统重新为上述用户制定的重 授权事件的发生情况。
可以理解的是，本实施例所述的规则执行实体可以是如实施例二或实施例 三所述的 PCEF实体， 其各个功能模块所述的功能可以根据实施例二或实施例 三所述的方法具体实现，其具体实现过程可以参见实施例二或实施例三中的相 关描述， 在此不再赞述。 实施例七
相应的， 本发明实施例中还提供一种规则执行实体， 请参阅图 10, 本发明 实施例中规则制定实体第七实施例可以包括：
第一发送模块 1010, 用于向规则制定实体发送会话建立请求消息，上述会 话建立请求消息携带用户当前接入小区的闭合用户组标识。
其中， 上述会话建立请求可以是 IP-CAN会话建立请求消息。 当用户从某 个 CSG小区接入到网络时， 规则执行实体在和规则制定实体建立 IP-CAN会话 前， 可以先从承载网络获取用户当前接入小区的 CSG ID信息， 以及用户在其 接入小区所归属 CSG的身份信息。 其中， 身份信息可以是能够指示用户在其接 入小区所归属 CSG的身份的任意信息。
上述会话建立请求消息还可以携带用户标识信息、以及用户接入小区的类 型信息等。
第一接收模块 1020, 用于接收会话建立响应消息，上述会话建立响应消息 携带上述用户的策略与计费控制规则，上述用户的策略与计费控制规则由上述 用户组的身份制定。
在一种应用场景下， 规则制定实体可以接收并解析上述会话建立请求消 息， 获得其携带的用户当前接入小区的 CSG ID信息， 以及用户在该 CSG的 身份信息等， 进而确定出上述用户在其接入小区所归属 CSG的身份。
对应用户身份的不同， 以及用户接入小区所归属 CSG的不同， 规则制定 实体可以制定出相应不同的 PCC规则。 在一种应用场景下， 若确定出用户身 份为该 CSG的签约用户， 规则制定实体可以按照该 CSG签约用户的标准， 制 定该用户的策略与计费控制规则， 例如可以让该用户享受到较低的费率， 以及 较高的服务质量保证等； 若确定出该用户不属于该 CSG的用户， 规则制定实 体可以按照普通小区用户的标准， 制定该用户的策略与计费控制规则， 例如让 用户享受正常的费率和服务质量保证。
进一步的， 规则制定实体还可以制定需要规则执行实体监测的触发事件， 当规则执行实体监测到规则制定实体制定的触发事件发生时 ,规则执行实体执 行与发生的触发事件对应的动作。
在一种应用场景下，规则制定实体制定的触发事件可以包括： 用户接入小 区的类型发生改变、 用户接入小区所归属 CSG发生改变、 用户在 CSG的身份发 生改变， 且不限于上述举例。
规则执行模块 1030,用于按照第一接收模块 1020接收的上述用户的策略与 计费控制规则， 对上述用户的业务数据流进行服务质量和计费控制等。
进一步的， 上述规则执行实体还可以包括：
身份获 ^莫块 1040，用于从承载网络获取上述用户在其接入小区所归属闭 合用户组的身份信息。 第一发送模块 1010发送的会话建立请求消息还可以携带身份获取模块 1040获取的上述用户在其接入小区所归属闭合用户组的身份信息等。
第一接收模块 1020接收的会话建立响应消息还可以携带上述规则制定实 体制定的触发事件信息，上述触发事件至少包括如下事件之一： 上述用户接入 小区的类型改变、上述用户接入小区所归属的闭合用户组改变、上述用户在其 接入小区所归属闭合用户组的身份改变等。
上述规则执行实体可以还包括：
事件监测模块 1050,用于监测上述规则制定实体制定的触发事件的发生情 况。
第二发送子模块 1060,用于在事件监测模块 1050监测到上述触发事件发生 时， 向上述规则制定实体发送会话修改指示消息，上述会话修改指示消息携带 上述用户接入新小区的闭合用户组标识信息、或上述用户接入新小区的类型信 息、或上述身份获取模块 1040获取的上述用户在其接入小区所归属闭合用户组 的身份信息。
在一种应用场景下 ,规则制定实体可以根据上述 PCC规则请求消息携带用 户的身份信息， 重新确定出该用户在其当前接入小区所归属 CSG的身份， 并根 据用户在该 CSG的身份以及其 CSG ID，重新制定出与之对应的新的 PCC规则和 /或新的触发事件。
第二接收模块 1070， 用于接收会话修改回应消息，上述会话修改回应消息 携带上述规则制定实体重新制定的上述用户的策略与计费控制规则和 /或触发 事件。
规则执行模块 1030还可以用于按照规则制定实体重新制定的上述用户的 策略与计费控制规则， 对上述用户的业务数据流进行服务质量和计费控制。
事件监测模块 1050还可以用于监测上述规则制定实体重新制定的上述用 户的触发事件的发生情况。
可以理解的是，本实施例所述的规则制定实体可以是如实施例二或实施例 三所述的 PCRF实体， 所述的规则执行实体可以是如实施例二或实施例三所述 的 PCEF实体， 其各个功能模块所述的功能可以根据实施例二或实施例三所述 的方法具体实现， 其具体实现过程可以参见实施例二或实施例三中的相关描 述， 在此不再赘述。 实施例八
相应的， 本发明实施例中还提供一种移动性管理实体， 请参阅图 11 , 本发 明实施例中移动性管理实体第八实施例可以包括：
获取模块 1110, 用于获取用户的签约信息。
在一种应用场景下，获取模块 1110可以实时或定时的从存储有用户签约信 息的实体去获取用户签约信息。
发送模块 1120， 用于在根据获取模块 1110获取的用户签约信息判断出用 户在其接入小区所归属闭合用户组的身份发生变化时，向用户设备发送身份信 息提供消息， 上述身份信息提供消息携带上述用户变化后的身份信息。
若连接态的用户在其接入小区所归属 CSG的身份改变， 例如， 用户通过 混合模式的 CSG小区接入网络的情况下，上述用户的身份由该 CSG的签约用 户变成该 CSG的非签约用户、 或者由该 CSG的非签约用户变成该 CSG的签 约用户、 或者用户通过闭合模式的 CSG小区接入网络的情况下， 用户的身份 由该 CSG的签约用户变成该 CSG的非签约用户 ,导致用户被切换到其它小区 , 其中， 用户身份改变原因可能是其签约信息的改变，或者用户在其接入小区所 归属 CSG的用户时限到期等等。
获取模块 1110获取的用户签约信息可以是， 上述用户的允许接入 CSG列 表，获 ^莫块 1110还可以从对应基站或基站网关获取用户当前接入小区的 CSG ID, 发送模块 1120可以根据上述 CSG ID和允许接入 CSG列表判断该用户在该 CSG的身份是否发生变化。
在一种应用场景下， 上述身份信息提供消息携带的信息可以包括但不限 于： 上述用户变化后的身份信息。
发送模块 1120发送的上述身份信息提供消息的类型可以是非接入层 ( NAS, Non-Access-Stratum ) 消息。
用户设备可以通过接收和解析移动性管理实体发送的身份信息提供消息， 获知用户的当前身份，并可以根据自身的当前身份和其它应用层信息获知自身 的当前服务质量和计费信息。
进一步的， 用户设备可以根据身份信息提供消息携带用户身份信息， 更新 其本地存储的允许接入 CSG列表。
由上述技术方案可以看出，当用户在其接入小区所归属 CSG的身份发生变 化时，移动性管理实体及时的将用户改变后的身份通知用户，有利于提高策略 与计费控制的透明， 进而提升用户体验。
需要说明的是，本实例实施例所述的移动性管理实体在不同的系统的具体 名称可能不尽相同， 例如，上述移动性管理实体可以是演进分组域系统（EPS , Evolved packet system ) 中的 MME ( mobility management entity, 移动性管理 单元）、 或者是通用分组无线业务 (GPRS , General Packet Radio Service)系统中 的 GPRS服务支持节点 （SGSN, Serving GPRS Support Node ) 、 或者是其他 系统中的， 移动交换中心 （MSC、 Mobile Switching Centre )、 访问位置寄存 器（VLR, Visitor Location Registe ) , 但不限于上述举例。
可以理解的是，本实施例所述的移动性管理实体的各个功能模块所述的功 能可以 据实施例四所述的方法具体实现，其具体实现过程可以参见实施例四 中的相关描述。 实施例九
相应的， 本发明实施例中还提供一种策略与计费系统， 请参见图 12， 本 发明实施例中一种策略与计费系统第九实施例可以包括： 规则制定实体 1210 和规则执行实体 1220, 规则制定实体 1210 以可通信的方式与规则执行实体 1220相连，
规则制定实体 1210用于获取用户接入小区的闭合用户组标识， 确定上述 用户在其接入小区所归属闭合用户组的身份，根据上述闭合用户组标识和上述 用户在其接入小区所归属闭合用户组的身份，制定上述用户的策略与计费控制 规则， 将上述用户的策略与计费控制规则通知规则执行实体 1220。
规则执行实体 1220可以按照上述用户的策略与计费控制规则， 对上述用 户的业务数据流进行策略与计费控制等。
可以理解的是， 本实施例所述的规则制定实体 1210可以是如实施例五所 述的规则制定实体， 规则执行实体 1220可以是如实施例七所述的规则执行实 体，本实施例所述的规则制定实体 1210和规则执行实体 1220的功能可以根据 实施例二或实施例三所述的方法具体实现， 在此不再赞述。
需要说明的是， 对于前述的各方法实施例， 为了简单描述， 故将其都表述 为一系列的动作组合，但是本领域技术人员应该知悉，本发明并不受所描述的 动作顺序的限制，因为依据本发明，某些步骤可以采用其他顺序或者同时进行。 其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施 例， 所涉及的动作和模块并不一定是本发明所必须的。
在上述实施例中， 对各个实施例的描述都各有侧重， 某个实施例中没 有详述的部分， 可以参见其他实施例的相关描述。
综上所述， 在本发明实施例的技术方案中， 在用户接入到 CSG小区时， 规则制定实体先确定出该用户在其接入小区所归属 CSG的身份，基于该用户的 身份制定其 PCC规则 , 规则执行实体按照上述 PCC规则对该用户的业务数据流 进行服务质量和计费控制，能够在保证该 CSG的签约用户优先使用资源权利的 同时， 尽量避免造成运营商的计费损失。
进一步的，通过监测触发事件和信用重授权事件的发生情况，及时的调整
PCC规则和授权信用 , 进一步提高了策略与计费控制的实时有效性。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步 骤是可以通过程序来指令相关的硬件来完成，该程序可以存储于一计算机可读 存储介质中， 存储介质可以包括： ROM、 RAM, 磁盘或光盘等。
以上对本发明实施例所提供的一种策略与计费控制的实现方法、设备及策 略与计费系统进行了详细介绍，本文中应用了具体个例对本发明的原理及实施 方式进行了阐述，以上实施例的说明只是用于帮助理解本发明的方法及其核心 思想； 同时， 对于本领域的一般技术人员， 依据本发明的思想， 在具体实施方 式及应用范围上均会有改变之处， 综上所述，本说明书内容不应理解为对本发 明的限制。

Claims

权 利 要 求
1、 一种策略与计费控制的实现方法， 其特征在于， 包括：
获取用户接入小区的闭合用户组标识；
确定所述用户在其接入小区所归属闭合用户组的身份；
根据所述闭合用户组标识和所述用户在其接入小区所归属闭合用户组的 身份， 制定所述用户的策略与计费控制规则；
将所述用户的策略与计费控制规则通知规则执行实体。
2、根据权利要求 1所述的方法， 其特征在于， 所述确定所述用户在其接入 小区所归属闭合用户组的身份， 包括：
向签约规格库发送规格请求消息， 所述规格请求消息携带用户标识信息； 接收规格响应消息 ,所述规格响应消息携带所述用户的允许接入闭合用户组列
所述用户在其接入小区所归属闭合用户组的身份； 或
利用所述闭合用户组标识和自身当前存储的所述用户的允许接入闭合用 户组列表， 确定出所述用户在其接入小区所归属闭合用户组的身份。
3、根据权利要求 1所述的方法， 其特征在于， 所述确定所述用户在其接入 小区所归属闭合用户组的身份， 包括：
接收规则执行实体发送的会话建立请求消息 ,从所述会话建立请求消息中 确定所述用户在其接入小区所归属闭合用户组的身份。
4、 根据权利要求 1所述的方法， 其特征在于， 所述方法还包括： 制定需要所述规则执行实体监测的触发事件 ,使得所述规则执行实体在监 测到所述触发事件发生时，执行与所述发生的触发事件相对应的步骤， 所述触 发事件至少包括如下事件之一： 所述用户接入小区的类型改变、所述用户接入 小区所归属的闭合用户组改变、所述用户在其接入小区所归属闭合用户组的身 份改变；
将制定的所述触发事件通知所述规则执行实体。
5、 根据权利要求 1或 4所述的方法， 其特征在于， 所述方法还包括： 接收会话修改指示消息，所述会话修改指示消息携带所述用户接入新小区 的闭合用户组标识信息、或所述用户接入新小区的类型信息、或所述用户在其 接入小区所归属闭合用户组的新身份信息； 和 /或
接收规格提供消息，所述规格提供消息携带更新的所述用户的允许接入闭 合用户组列表；
根据所述接收到的会话修改指示消息和 /或规格提供消息携带的信息 , 重 新制定所述用户的策略与计费控制规则和 /或触发事件；
向所述规则执行实体发送会话修改回应消息，所述会话修改回应消息携带 重新制定的所述用户的策略与计费控制规则和 /或触发事件。
6、 根据权利要求 2所述的方法， 其特征在于， 所述方法还包括： 将所述用户在其接入小区所归属闭合用户组的身份通知所述规则执行实 体。
7、 根据权利要求 1、 3、 或 6所述的方法， 其特征在于， 所述方法还包括： 所述规则执行实体向在线计费系统发送信用请求消息，所述信用请求消息 携带用户标识信息；
所述规则执行实体接收信用响应消息，所述信用响应消息携带所述在线计 费系统为用户授权的信用信息，以及所述在线计费系统制定的信用重授权事件 信息， 所述在线计费系统制定的重授权事件至少包括如下事件之一： 所述用户 接入小区的类型改变、所述用户接入小区所归属的闭合用户组改变、所述用户 在其接入小区所归属闭合用户组的身份改变；
所述规则执行实体按照所述在线计费系统为所述用户授权的信用，对所述 用户的业务数据流进行计费处理，并监测所述在线计费系统制定的所述信用重 授权事件的发生情况。
8、 根据权利要求 7所述的方法， 其特征在于， 所述方法还包括： 所述规则执行实体在监测到所述在线计费系统制定的信用重授权事件发 生时， 向所述在线计费系统发送信用请求消息， 所述信用请求消息携带所述用 户标识， 以及所述用户接入新小区的闭合用户组标识信息、或所述用户接入新 小区的类型信息、或所述获取的所述用户在其接入小区所归属闭合用户组的身 份信息；
所述规则执行实体接收信用响应消息，所述信用响应消息携带所述在线计 费系统重新为所述用户授权的信用；
所述规则执行实体按照所述在线计费系统重新为所述用户授权的信用 ,对 所述用户的业务数据流进行计费处理。
9、 一种策略与计费控制的实现方法， 其特征在于， 包括：
获取用户的签约信息；
在根据所述用户的签约信息判断出所述用户在其接入小区所归属闭合用 户组的身份发生变化时， 向用户设备发送身份信息提供消息， 所述身份信息提 供消息携带所述用户变化后的身份信息。
10、 一种规则制定实体， 其特征在于， 包括：
获耳 ^莫块， 用于获取用户接入小区的闭合用户组标识；
确定模块， 用于确定所述用户在其接入小区所归属闭合用户组的身份； 规则制定模块，用于根据所述闭合用户组标识和所述用户在其接入小区所 归属闭合用户组的身份， 制定所述用户的策略与计费控制规则；
通知模块 ,用于将所述规则制定模块制定的所述用户的策略与计费控制规 则通知规则执行实体。
11、根据权利要求 10所述的规则制定实体， 其特征在于， 所述确定模块包 括：
第一发送子模块， 用于向签约规格库发送规格请求消息， 所述规格请求消 息携带用户标识信息；
第一接收子模块， 用于接收规格响应消息， 所述规格响应消息携带所述用 户的允许接入闭合用户组列表，所述允许接入闭合用户组列表记录了所述用户 签约的闭合用户组的标识信息； 合用户组标识 , 确定出所述用户在其接入小区所归属闭合用户组的身份。
12、根据权利要求 11所述的规则制定实体， 其特征在于， 所述通知模块还 用于，将所述第一确定子模块确定出的所述用户在其接入小区所归属闭合用户 组的身份通知所述规则执行实体。
13、根据权利要求 10所述的规则制定实体， 其特征在于， 所述确定模块包 括：
第二接收子模块，用于接收规则执行实体发送的会话建立请求消息， 所述 会话建立请求消息携带所述用户在其接入小区所归属闭合用户组的身份信息； 第二确定子模块，用于从所述会话建立请求消息中确定出所述用户在其接 入小区所归属闭合用户组的身份。
14、根据权利要求 10所述的规则制定实体， 其特征在于， 所述规则制定实 体还包括：
事件制定模块， 用于制定需要所述规则执行实体监测的触发事件，使得所 述规则执行实体在监测到所述触发事件发生时，执行与所述发生的触发事件相 对应的步骤， 所述触发事件至少包括如下事件之一： 所述用户接入小区的类型 改变、所述用户接入小区所归属的闭合用户组改变、所述用户在其接入小区所 归属闭合用户组的身份改变；
所述通知模块还用于，将所述事件制定模块制定的触发事件通知所述规则 执行实体。
15、根据权利要求 10或 14所述的规则制定实体， 其特征在于， 所述规则制 定实体还包括：
接收模块， 用于接收会话修改指示消息， 所述会话修改指示消息携带所述 用户接入新小区的闭合用户组标识信息、 或所述用户接入新小区的类型信息、 或所述用户在其接入小区所归属闭合用户组的新身份信息； 和 /或
接收规格提供消息，所述规格提供消息携带更新的所述用户的允许接入闭 合用户组列表；
所述规则制定模块还用于，根据所述接收模块接收到的会话修改指示消息 和 /或规格提供消息携带的信息重新制定所述用户的策略与计费控制规则； 所述事件制定模块还用于 ,根据所述接收模块接收到的会话修改指示消息 和 /或规格提供消息携带的信息重新制定所述用户的触发事件；
发送模块， 用于向所述规则执行实体发送会话修改回应消息， 所述会话修 改回应消息携带重新制定的所述用户的策略与计费控制规则和 /或触发事件。
16、 一种规则执行实体， 其特征在于， 包括：
第一发送模块， 用于向规则制定实体发送会话建立请求消息， 所述会话建 立请求消息携带用户当前接入小区的闭合用户组标识；
第一接收模块， 用于接收会话建立响应消息， 所述会话建立响应消息携带 所述用户的策略与计费控制规则 ,所述用户的策略与计费控制规则由所述规则 组的身份制定； 规则执行模块 ,用于按照所述第一接收模块接收的所述用户的策略与计费 控制规则， 对所述用户的业务数据流进行服务质量和计费控制。
17、根据权利要求 16所述的规则执行实体， 其特征在于， 所述规则执行实 体还包括：
身份获 ^莫块，用于从承载网络获取所述用户在其接入小区所归属闭合用 户组的身份；
所述第一发送模块发送的会话建立请求消息还携带所述身份获取模块获 取的所述用户在其接入小区所归属闭合用户组的身份信息。
18、 根据权利要求 16或 17所述的规则执行实体， 其特征在于，
所述第一接收模块， 用于接收的会话建立响应消息， 所述会话建立响应消 息还携带所述规则制定实体制定的触发事件信息；
事件监测模块， 用于监测所述规则制定实体制定的触发事件的发生情况； 第二发送模块，用于在所述事件监测模块监测到所述规则制定实体制定的 触发事件发生时， 向所述规则制定实体发送会话修改指示消息， 所述会话修改 指示消息携带所述用户接入新小区的闭合用户组标识信息、或所述用户接入新 小区的类型信息、或所述身份获取模块获取的所述用户在其接入小区所归属闭 合用户组的身份信息。
第二接收模块， 用于接收会话修改回应消息， 所述会话修改回应消息携带 所述规则制定实体重新制定的所述用户的策略与计费控制规则和 /或触发事 件；
所述规则执行模块还用于 ,按照所述规则制定实体重新制定的所述用户的 策略与计费控制规则， 对所述用户的业务数据流进行服务质量和计费控制； 所述事件监测模块还用于，监测所述规则制定实体重新制定所述用户的触 发事件。
19、 一种移动性管理实体， 其特征在于， 包括：
获取模块， 用于获取用户的签约信息；
发送模块，用于在根据所述用户的签约信息判断出所述用户在其接入小区 所归属闭合用户组的身份发生变化时， 向用户设备发送身份信息提供消息， 所 述身份信息提供消息携带所述用户变化后的身份信息。
20、 一种策略与计费系统， 其特征在于， 包括： 规则制定实体， 所述规则 制定实体以可通信的方式与规则执行实体相连，
所述规则制定实体用于获取用户接入小区的闭合用户组标识 ,确定所述用 户在其接入小区所归属闭合用户组的身份，根据所述闭合用户组标识和所述用 户在其接入小区所归属闭合用户组的身份，制定所述用户的策略与计费控制规 则， 将所述用户的策略与计费控制规则通知所述规则执行实体。
PCT/CN2009/071248 2009-04-13 2009-04-13 策略与计费控制的实现方法、设备及策略与计费系统 WO2010118566A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2009/071248 WO2010118566A1 (zh) 2009-04-13 2009-04-13 策略与计费控制的实现方法、设备及策略与计费系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2009/071248 WO2010118566A1 (zh) 2009-04-13 2009-04-13 策略与计费控制的实现方法、设备及策略与计费系统

Publications (1)

Publication Number Publication Date
WO2010118566A1 true WO2010118566A1 (zh) 2010-10-21

Family

ID=42982111

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/071248 WO2010118566A1 (zh) 2009-04-13 2009-04-13 策略与计费控制的实现方法、设备及策略与计费系统

Country Status (1)

Country Link
WO (1) WO2010118566A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112969177A (zh) * 2021-01-29 2021-06-15 展讯半导体(南京)有限公司 终端接入方法及装置、存储介质、接入点、核心网、终端

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1968139A (zh) * 2006-06-15 2007-05-23 华为技术有限公司 策略与计费控制中用户签约信息的处理方法及装置
CN101127609A (zh) * 2006-08-14 2008-02-20 华为技术有限公司 一种在演进网络中管理用户策略计费控制签约信息的方法
CN101166101A (zh) * 2007-09-25 2008-04-23 中兴通讯股份有限公司 由用户签约信息更新实时触发网络会话交互的方法
WO2008055541A1 (en) * 2006-11-06 2008-05-15 Telefonaktiebolaget Lm Ericsson (Publ) Devices and method for guaranteeing service requirements per user equipment basis into a bearer

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1968139A (zh) * 2006-06-15 2007-05-23 华为技术有限公司 策略与计费控制中用户签约信息的处理方法及装置
CN101127609A (zh) * 2006-08-14 2008-02-20 华为技术有限公司 一种在演进网络中管理用户策略计费控制签约信息的方法
WO2008055541A1 (en) * 2006-11-06 2008-05-15 Telefonaktiebolaget Lm Ericsson (Publ) Devices and method for guaranteeing service requirements per user equipment basis into a bearer
CN101166101A (zh) * 2007-09-25 2008-04-23 中兴通讯股份有限公司 由用户签约信息更新实时触发网络会话交互的方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112969177A (zh) * 2021-01-29 2021-06-15 展讯半导体(南京)有限公司 终端接入方法及装置、存储介质、接入点、核心网、终端
WO2022161458A1 (zh) * 2021-01-29 2022-08-04 展讯半导体(南京)有限公司 终端接入方法及装置、存储介质、接入点、核心网、终端

Similar Documents

Publication Publication Date Title
EP2515475B1 (en) Charging method, network device and mobility management element
US8644799B2 (en) Charging system and method
WO2009012686A1 (fr) Procédé, équipement et système de mise en œuvre du contrôle des conditions d'utilisation et de facturation
WO2010108356A1 (zh) 一种终端通过多接入网接入的计费方法和系统及上报方法
WO2011097911A1 (zh) 策略和计费规则功能实体的选择方法、装置及系统
WO2012083795A1 (zh) 业务控制方法、装置及系统
WO2013155942A1 (zh) 策略和计费控制方法、v-pcrf及v-ocs
WO2009021462A1 (fr) Procédé et dispositif d'établissement de session ip-can
WO2008022602A1 (fr) Procédé, dispositif et système de commande de conditions d'utilisation et de facturation
WO2012075875A1 (zh) 一种消费限制业务的签约和执行方法及系统
WO2012163284A1 (zh) 策略及计费控制下的重定向方法及重定向装置
WO2009039750A1 (fr) Procédé et système pour une modification de session
WO2011054300A1 (zh) Mtc终端的接入控制方法和系统
WO2006015548A1 (fr) Methode de traitement fondee sur un evenement de declenchement de chargement et sur un evenement de reautorisation de flux de donnees de paquets
WO2011063688A1 (zh) 策略和计费规则功能实体的选择方法及系统
WO2011085614A1 (zh) 在全业务融合网络中控制资源的方法和系统
CN101001402B (zh) 移动通信系统及使用归属网络应用功能业务的方法
WO2011026385A1 (zh) 一种本地疏导漫游场景在线计费的方法和系统
WO2015055063A1 (zh) 应用接入控制方法及应用功能实体装置
WO2013060170A1 (zh) 一种提供基于lipa承载的计费支持的方法及装置
CN106304195A (zh) 第三方应用的策略控制方法、scef和pcrf
WO2014094488A1 (zh) 漫游本地业务的计费策略方法及装置
WO2008043307A1 (fr) Procédé, dispositif et système de taxation commune
WO2014107985A1 (zh) 漫游本地业务的在线计费方法、h-ocs及v-ocs
WO2012083779A1 (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: 09843200

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: 09843200

Country of ref document: EP

Kind code of ref document: A1