WO2011026440A1 - Method, device and communication system for processing group policy and charging rules - Google Patents

Method, device and communication system for processing group policy and charging rules Download PDF

Info

Publication number
WO2011026440A1
WO2011026440A1 PCT/CN2010/076617 CN2010076617W WO2011026440A1 WO 2011026440 A1 WO2011026440 A1 WO 2011026440A1 CN 2010076617 W CN2010076617 W CN 2010076617W WO 2011026440 A1 WO2011026440 A1 WO 2011026440A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
user equipment
policy
attribute information
identifier
Prior art date
Application number
PCT/CN2010/076617
Other languages
French (fr)
Chinese (zh)
Inventor
周汉
吴问付
陈中平
孙晓姬
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2011026440A1 publication Critical patent/WO2011026440A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403Architecture for metering, charging or billing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/62Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on trigger specification
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/64On-line charging system [OCS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66Policy and charging system
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70Administration or customization aspects; Counter-checking correct charges
    • H04M15/765Linked or grouped accounts, e.g. of users or devices
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70Administration or customization aspects; Counter-checking correct charges
    • H04M15/765Linked or grouped accounts, e.g. of users or devices
    • H04M15/7652Linked or grouped accounts, e.g. of users or devices shared by users
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70Administration or customization aspects; Counter-checking correct charges
    • H04M15/77Administration or customization aspects; Counter-checking correct charges involving multiple accounts per user
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70Administration or customization aspects; Counter-checking correct charges
    • H04M15/77Administration or customization aspects; Counter-checking correct charges involving multiple accounts per user
    • H04M15/771Administration or customization aspects; Counter-checking correct charges involving multiple accounts per user per terminal or location, e.g. mobile device with multiple directory numbers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24Accounting or billing

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a group policy and charging rule processing method, apparatus, and communication system. Background technique
  • the prior art Policy and Charging Control (PCC) mechanism establishes that when a user conducts a service, it needs to establish an independent policy control mechanism for each service data flow of all users.
  • the IP CAN session establishment process includes the following steps. First, after receiving the IP-CAN session establishment request message initiated by the user equipment (assigning an IP address visible to the network PDN network), the gateway sends the UEF, including the UE identifier, the IP address, and the PCRF. The IP CAN session establishment message of the APN information notifies the PCRF that the IP CAN session is established. If the user needs to sign the related information, the PCRF sends a user subscription information request message (Prof i le Reques t ) message to the SPR, and the SPR returns the user subscription information response message.
  • Profile i le Reques t user subscription information request message
  • the information including the current subscription service and charging mode of the user is generated; the PCRF generates a new charging rule, and returns the PCC rule to the gateway (GW) through the IP CAN session establishment confirmation message, and the gateway installs the rule, and opens or closes the corresponding according to the rule.
  • the gateway then sends an IP CAN Session Setup Response message to the UE.
  • MTC Machine Type Communication
  • M2M Machine to Machine
  • traffic control and management traffic control and management
  • factory control and remote meter reading applications operators based on the characteristics of the above M2M applications
  • MTC devices into groups For example, for remote meter reading applications, the operator will group the meter devices in a certain area into a group.
  • the MTC devices in the group all have the same M2M device attribute information, such as low mobility and delay insensitivity.
  • Each service establishment initiated by the MTC device needs to execute and deliver the corresponding PCC rules.
  • the existing PCC processing mechanism is used, a large amount of overhead will be incurred on the performance of the network.
  • some M2M devices are simple to apply, and have the same M2M device attribute information for the MTC devices belonging to the same group, that is, their service types are consistent, such as the above-mentioned remote meter reading service, for the above group
  • the group of MTC devices can share the same PCC control strategy. If the existing PCC processing mechanism is used, there are disadvantages such as inefficient policy control and complicated policy maintenance. Summary of the invention
  • An object of the embodiments of the present invention is to provide a group policy and charging rule processing method, apparatus, and communication system to improve policy control efficiency.
  • an embodiment of the present invention provides a group policy and a charging rule processing method, including:
  • the embodiment of the present invention further provides a group policy and charging rule processing device, including: an obtaining module, configured to acquire at least one of a group identifier or device attribute information of a user equipment;
  • a rule generating module configured to generate a policy and charging rule or a trigger event according to at least one of a group identifier or a device attribute information of the user equipment.
  • the embodiment of the invention further provides a communication system, comprising the group policy and charging rule processing device described above.
  • a group policy and charging rule processing method, device and communication system provided by an embodiment of the present invention, By acquiring the group identifier or the device attribute information of the user equipment, and generating the group policy and the charging rule or the triggering event according to the obtained information, the group user equipment or the user equipment having the same device feature can be effectively improved. Control efficiency and reduce the complexity of policy maintenance and management.
  • FIG. 1 is a schematic flowchart of Embodiment 1 of a method for processing a group policy and a charging rule according to the present invention
  • FIG. 1 is a schematic flowchart of a first embodiment of a method for processing a group policy and a charging rule according to the present invention
  • FIG. 3 is a schematic flow chart of a second embodiment of a group policy and charging rule processing method according to the present invention.
  • FIG. 4 is a schematic flow chart of PCC optimization processing in the embodiment shown in FIG. 3;
  • FIG. 5 is a schematic flow chart of a third embodiment of a group policy and charging rule processing method according to the present invention.
  • FIG. 6 is a schematic structural diagram of an embodiment of a group policy and charging rule processing apparatus according to the present invention. detailed description
  • FIG. 1 is a schematic flowchart of a first embodiment of a method for processing a group policy and a charging rule according to the present invention. As shown in FIG. 1, the method includes the following steps:
  • Step 101 Obtain at least one of a group identifier or a device attribute information of the user equipment; that is, obtain the group identifier or the device attribute information of the user equipment in this step, or obtain the foregoing two items at the same time.
  • the group identifier of the user equipment is a user group identifier (which may also be described as a user group user identifier) or a group identifier (which may also be described as a group user identifier) for the user group or the group user.
  • the identifier of the group or the user group to which the user equipment belongs for example, the group or the user group to which the user equipment belongs is identified by the APN (Aces s Point Name), and the APN is the identifier of the group or user group to which the user equipment belongs.
  • APN Acces s Point Name
  • the group or the user group may be a user equipment group or an M2M industry user (MTC User) or an M2M application subscription user (MTC Subscr iber) or other group of multiple devices, which is not limited in this embodiment.
  • the device attribute information is attribute information shared by the user equipments having the same characteristics, and is different device feature information obtained according to different applications of different industry users (MTC User) or M2M application subscription users (MTC Subscr iber). It can also be called a Machine Feature or a Machine Type or a Service Category (Servi ce Cla ss). For example, if the user equipment in the remote meter reading system has the characteristics of low mobility, delay insensitivity, etc., the device attribute information is low mobility, delay insensitive, and the like; in this embodiment, the content and device attributes included in the device attribute information are not included in this embodiment. The name of the information is restricted.
  • Step 102 Generate a policy and charging rule or a trigger event according to at least one of a group identifier or a device attribute information of the user equipment.
  • the application scope of the policy and the charging rule or the triggering event is a group or a user group to which the user equipment belongs. That is, the policy and charging rule or trigger event is also applied to the group to which the user equipment belongs or other users in the user group.
  • the triggering event in this embodiment is a rule for reporting the behavior of the PCEF or the BBERF event
  • the application scope is for the user group to which the user equipment belongs or all user equipments under the user group. For example, when the triggering event is that the location of a certain user equipment in the group is changed, the PCEF or the BBERF is notified, and the event of the user equipment location change needs to be reported to the policy and charging rule function entity.
  • the group identifier or the device attribute information of the user equipment is obtained, and the group policy and the charging rule or the triggering event are generated according to the obtained information, which can effectively improve the user equipment of the group or have the same device characteristics.
  • the policy of the user equipment controls the efficiency and reduces the complexity of policy maintenance and management.
  • acquiring at least one of a group identity or device attribute information (MTC Feature) of the user equipment includes: a service gateway, a packet data network gateway, or a gateway GPRS support node acquires a user equipment in an access request.
  • MTC Feature group identity or device attribute information
  • Messages eg, A 11 a ch Reque st
  • P ⁇ Connect connection request PDN Connect ivi ty Es tabl i shment Reques t
  • activate the PDP Context Reques t create a PDP Context Reques t
  • create a session request Crea es Res s Re Res
  • the network element acquiring at least one of a group identifier or device attribute information of the user equipment subscribed to the home subscriber server (HLR or HSS) or the group subscription database; or the foregoing network element
  • the identifier of the user equipment can be obtained through an existing process, according to the identifier of the user equipment, Membered user device information acquired pre-configured user equipment device group identifier or the at least one of the attribute information.
  • a policy and charging rule or triggering event according to at least one of a group identifier or a device attribute information of the user equipment, including: a service gateway, a packet data network gateway, or a group GPRS support node according to the obtained group identifier or device of the user equipment.
  • At least one of the attribute information generates a policy and a charging rule or a triggering event, and indicates that the application scope of the policy and the charging rule or the triggering event is a group or a group of users described by the user equipment. Specifically, it may include:
  • the specific service gateway, the packet data network gateway or the gateway GPRS support node generates a policy and charging rule or a method for triggering an event as follows:
  • One method is that the service gateway, the packet data network gateway or the gateway GPRS support node is obtained according to The device attribute information of the user equipment, such as low mobility, delay is not sensitive, and the corresponding PCC rules or trigger events are formulated according to the statically configured PCC rules or trigger events.
  • the service gateway, the packet data network gateway, or the gateway GPRS support node formulates the group identifier with the user equipment according to the statically configured PCC rule or the trigger event according to the obtained group identification information of the user equipment. Corresponding PCC rules or trigger events.
  • the specific method may be: adding a PCC rule or triggering in the generated PCC rule or the triggering event
  • the cell of the event application scope for example, Apply Scope
  • the generated PCC rule or trigger event is applied to the group or user group described by the user equipment.
  • the generated PCC rule or the trigger event includes the identifier of the group or the user group described by the user equipment, and the service gateway, the packet data network gateway, or the gateway GPRS support node according to the identifier of the group or the user group.
  • a PCC rule or triggering event is applied to the group or group of users described by the user equipment.
  • obtaining at least one of the group identifier or the device attribute information of the user equipment includes: one way, the policy and charging rule function entity acquires the service gateway, the packet data network gateway, or the gateway GPRS support node.
  • At least one of a group identifier or device attribute information carried in an IP CAN session message (eg, an Indicating IP CAN Ses s ion Es tab): another manner is based on the identifier of the user equipment
  • a request message eg, Prof.
  • the configuration request message carries the user equipment identifier
  • the service subscription database or the group subscription database acquires the group identifier or device attribute information of the user equipment according to the user equipment identifier. At least one of them, and in the configuration response message ( Prof i le Resp Returned to the policy and accounting control function entity in onse).
  • the policy and charging rule function entity is configured according to the obtained group identifier or device attribute information of the user equipment. At least one of the following generates a policy and a charging rule or a triggering event, and indicates in the policy and charging rule or the triggering event that the application scope is a group or a user group to which the user equipment belongs. Specifically, it may include:
  • the policy and charging rule function entity generates a policy and charging rule or a method for triggering an event, which may be as follows.
  • One method is: the policy and charging rule function entity is based on the obtained user equipment. At least one of group ID and device attribute information, such as low mobility, delay is not sensitive, and corresponding
  • the policy and charging rule function entity formulates a group with the user equipment according to at least one of a group identifier and a device attribute information of the user equipment according to a pre-configured PCC rule or a trigger event.
  • the PCC rule or trigger event corresponding to the group ID or device attribute information.
  • the process of generating the policy and the charging rule or the triggering event includes: assigning, to the DHCP device, the IP address of the group or user equipment group for the user equipment according to the group identifier of the user equipment. address.
  • the foregoing steps may be specifically: assigning an IPv6 address prefix of a group or a user group granularity according to the group identifier of the user equipment or the DHCP request to the user equipment of the group or the user group to which the user equipment belongs; or according to The group identity assignment of the user equipment or the DHCP request to the user equipment under the group or user group to which the user equipment belongs is assigned a common IPv4 address.
  • the specific method may be: adding a PCC rule or triggering in the generated PCC rule or the triggering event
  • the cell of the event application scope for example, App ly Scope
  • the generated PCC rule or trigger event is applied to the group or user group described by the user equipment.
  • the generated PCC rule or the trigger event includes the identifier of the group or the user group described by the user equipment, and the service gateway, the packet data network gateway, or the gateway GPRS support node according to the identifier of the group or the user group.
  • a PCC rule or triggering event is applied to the group or group of users described by the user equipment.
  • Another embodiment of the present invention may further include: performing the step of optimizing the policy and charging rules according to the group identifier of the user equipment.
  • the policy and charging rule or the application scope of the triggering event is the group or user group to which the user equipment belongs, and the policy and charging rule are also applied to the group to which the user equipment belongs or other users in the user group. trigger event.
  • another new user equipment requests access (for example, an attach procedure or a P ⁇ connection establishment procedure)
  • at least one of the group identifier or the device attribute information of the new user equipment is compared with the user equipment in step 101.
  • the foregoing step may specifically allocate, to the new user equipment, the generated policy and charging rule or the triggering event of the group to which the user equipment belongs in the step 101 (ie, the policy and charging rule or the triggering event in step 102).
  • the foregoing step may specifically allocate, to the new user equipment, the generated policy and charging rule or the triggering event of the group to which the user equipment belongs in the step 101 (ie, the policy and charging rule or the triggering event in step 102).
  • the PGW, SGW or GGSN performs PCC optimization.
  • Another embodiment of the present invention may further include: terminating a policy and a charging rule or a triggering event of a group generated for the group to which the user equipment belongs according to the group identifier of the user equipment.
  • a user equipment under the group initiates a process of de-connecting (eg, initiating a separation process or a P-to-connection process)
  • a packet data network gateway or a GPRS support node or a policy and charging control function entity according to the user equipment
  • the group identifier determines whether there are other user equipments in the group that remain connected, and if yes, retains the policy and charging rules or trigger events of the group generated by the group to which the user equipment belongs, otherwise, the termination is The policy and charging rule or trigger event of the group generated by the group to which the user equipment belongs.
  • Another embodiment of the present invention may further include: the policy and the charging rule or the triggering event for allocating the generated group of the user equipment to the user equipment, which may be specifically corresponding to the P ⁇ connection initiated by the user equipment.
  • the APN information allocates the generated policy and charging rule or triggering event of the group to which the user equipment belongs to the user equipment.
  • the PGW, SGW or GGSN performs PCC optimization.
  • Another embodiment of the present invention may further include: the policy and the charging rule or the triggering event of the group that is generated according to the group identifier of the user equipment that is to be generated by the group to which the user equipment belongs may be specifically the P initiated according to the user equipment.
  • the APN information corresponding to the connection is terminated as a policy and charging rule or a trigger event of the group generated by the group to which the user equipment belongs.
  • the PGW, the SGW, or The GGSN performs a description of the processing steps.
  • FIG. 1 is a schematic flowchart of a first embodiment of a method for processing a group policy and a charging rule according to the present invention. As shown in FIG. 2, the method includes the following steps:
  • Step 201 Acquire at least one of a group identifier of the user equipment or device attribute information.
  • the PGW or the SGW or the GGSN or the PCRF can learn that the group identifier of the user equipment can be implemented as follows:
  • the solid E or the SGSN is in the message (for example, the Create Session Request sent by the MME to the S-GW or the Create PDP Context Request message sent by the SGSN to the GGSN, etc.) method) carries the group identifier, an alternative, the MME or the SGSN carrying device attribute information (MTC Feature) user equipment in the message or the SGSN E 0 fixed known user identification device or device attribute information comprises a user equipment
  • the access request message (for example, the Attach Request or the TAU Request or the PDN Connectivity Establishment Request or the Active PDP Context Request) carries the group identifier or device attribute information of the user equipment.
  • the HSS or the group subscription database provides the MME or the SGSN with the group identifier or the device attribute information of the user equipment, for example, after receiving the Update Location Request message sent by the solid E, according to the identifier of the user equipment carried in the message.
  • the Update Location Ack message returned by the MME carries the group identifier or device attribute information of the user equipment.
  • the PCRF obtains a configuration information request message (Profile Request) to the SPR, where the PCRF obtains a group identifier or a device attribute information (Machine Feature) of the user equipment, where the message carries the user The identifier of the device, the SPR returns a configuration information response message (Profile Response), and the identifier of the user equipment carried in the message is sent, and the configuration information response message carries the group identification information or device attribute information of the user equipment (MTC Feature). At least one of them.
  • Profile Request configuration information request message
  • MTC Feature device attribute information
  • the PCRF may further provide the group identifier of the user equipment or the device attribute information of the user equipment to the PGW or the SGW (eg, in Acknowledge IP CAN). Session Establishment or Acknowledge IP CAN Session Modification or carried in messages such as Pol icy and Charging Rules Provision).
  • PCRF obtains a group of user equipments
  • Another method for identifying at least one of the device attribute information of the user equipment may be that the PCRF receives an IP CAN session message sent by the PGW or the GGSN or the SGW (eg, Ind i i t t t t t s s s s s s s s s s s s s s s s s s s s
  • IP CAN session message carries the group identifier of the user equipment or the device attribute information of the user equipment.
  • the identifier of the user equipment (such as the IMS I of the user equipment, the IMEI of the user equipment or the IMS I and IME I of the user equipment) and the user equipment may also be configured on the PGW, the SGW or the GGSN. Correspondence between the group identifiers to which the group identifiers belong, or the correspondence between the identifiers of the user equipments and the device attribute information corresponding to the user equipments.
  • the PGW, the SGW, or the GGSN obtains the identifier of the user equipment, and obtains the identifier of the group or the user group to which the user equipment belongs according to the configuration information, or obtains the device attribute information corresponding to the user equipment.
  • Step 202 Generate a PCC rule or a trigger event (Event Tr i gger ) shared by the group, and specifically include the following methods:
  • the PGW or the SGW or the GGSN obtains at least one of the group identifier of the user equipment and the device attribute information of the user equipment according to the description in step 201.
  • the PGW or the SGW or the GGSN formulates a PCC rule or a trigger event according to at least one of a group identity or device attribute information of the user equipment.
  • the M2M application of the remote meter reading, the PGW or the SGW or the GGSN according to the obtained device attribute information of the user equipment, such as low mobility, delay insensitive, according to the statically configured PCC rules or trigger events, formulate corresponding PCC rules or trigger events.
  • Another method for the PGW or the SGW or the GGSN to formulate a PCC rule or a trigger event according to at least one of the group identifier or the device attribute information of the user equipment is a PGW or an SGW or a GGSN according to the group identifier of the user equipment. And formulating a PCC rule or a trigger event corresponding to the group identifier of the user equipment according to the statically configured PCC rule or the trigger event.
  • the PGW or the SGW or the GGSN indicates that the application scope of the PCC rule or the trigger event that is set for the user equipment is a group or a user group to which the user equipment belongs.
  • the specific method may be: adding, in the generated PCC rule or the trigger event, a cell indicating a PCC rule or a trigger application range, for example, App ly Scope, when the Apply Scope is set to a group range, the generated PCC A rule or triggering event is applied to the group or group of users described by the user equipment.
  • the generated PCC rule or the trigger event includes the identifier of the group or the user group described by the user equipment, and the service gateway, the packet data network gateway, or the gateway GPRS support node according to the identifier of the group or the user group.
  • a PCC rule or triggering event is applied to the group or group of users described by the user equipment.
  • the PGW, the SGW, or the GGSN obtains the group identifier of the user equipment according to the description in step 201, and may also obtain the device attribute information of the user equipment.
  • the PGW, the SGW, or the GGSN sends an IP CAN session establishment indication message to the PCRF, where the message may carry the group identifier of the user equipment or device attribute information of the user equipment.
  • the PCRF may carry the group identifier of the user equipment in a configuration information request message (Prof ile Reques t ) sent to the SPR.
  • Profile ile Reques t configuration information request message
  • the PCRF may also obtain the foregoing group identifier or device attribute information by receiving a configuration information response message (Profed Response) returned by the SPR, that is, the configuration information response message carries the group identifier of the user equipment or Device attribute information.
  • the PCRF formulates a PCC rule or a trigger event according to at least one of a group identifier or device attribute information to which the user equipment belongs or service subscription data of the user equipment.
  • the PCRF formulates corresponding PCC rules or trigger events according to the obtained device attribute information of the user equipment, such as low mobility and delay insensitivity.
  • the PCRF formulates a PCC rule or a trigger event according to at least one of the group identifier or the device attribute information of the user equipment or the service subscription data of the user equipment. Another method is that the PCRF is based on the group identifier of the user equipment. And at least one item of the device attribute information, according to the pre-configured PCC rule or the trigger event, formulating a PCC rule or a trigger event corresponding to the group identifier or the device attribute information of the user equipment.
  • the PCRF may indicate, in the PCC rule that is set up for the user equipment, that the PCC rule applies to a group or a user group to which the user equipment belongs, or carries a group of the group to which the user equipment belongs in the PCC rule.
  • the PCC rule obtained by the PGW, the SGW, or the GGSN according to the application scope indication in the PCC rule or the group identifier of the group to which the user equipment belongs in the PCC rule is applied to the group to which the user equipment belongs. Group or user group.
  • the PCRF may not provide a service data flow template (Service Da te Flow Templa te) in the PCC rule, that is, the PCRF is determined according to at least one of a group identifier or a device attribute information of the user equipment.
  • the application scope is a PCC policy of a group or a user equipment group, so that the service data flow template is not provided in the PCC rule.
  • the PCRF formulates a PCC policy whose application scope is a group or a user equipment group according to at least one of a group identifier or a device attribute information of the user equipment, but the PCRF further provides a service data flow template in the PCC rule.
  • the method for the service data flow template generated by the PCRF in the PCC rule includes: a), when the user equipment initiates a P ⁇ connection establishment process (for example, an At tach process or a PDN connection establishment process), and the PGW is the above user.
  • the device assignment or the PGW requests the DHCP device to allocate an IPv4 address or an IPv6 address to the user equipment.
  • the PGW learns the group identifier of the user equipment, and the PGW allocates an IP address to the user equipment according to the group identifier of the user equipment or allocates a group or user group granularity to the user equipment according to the DHCP request, and the specific method includes: The PGW allocates an IPv6 address prefix of a group or a user group granularity according to the group identity of the user equipment or the DHCP request to the user equipment of the group or the user group to which the user equipment belongs (a complete IPv6 address is The two components are the IPv6 address prefix and the IPv6 interface identifier.
  • the IPv6 address prefix is a group or user group granularity, that is, when the second user equipment that belongs to the same group as the user equipment (the first user equipment) initiates a PDN connection establishment procedure for the same APN, the PGW is the second.
  • the user equipment allocates an IPv6 address prefix to be the same as the IPv6 address prefix allocated by the PGW for the user equipment (the first user equipment) (ie, the PGW allocates the IPv6 address prefix allocated for the first user equipment as the PGW to the second user equipment. IPv6 address prefix).
  • the PGW allocates a public IPv4 address to the user equipment in the group or the user group to which the user equipment belongs according to the group identifier of the user equipment.
  • the public IPv4 address is a group or user group granularity.
  • the PGW obtains an IPv6 prefix or a public IPv4 address of the user equipment, and the PGW sends an IP CAN session establishment indication message to the PCRF, where the IP CAN session establishment indication message includes the PGW obtained.
  • the IPv6 prefix or the public IPv4 address of the user equipment includes the IPv6 prefix or the public IPv4 address of the user equipment.
  • PCRF generates a service data flow template (Service Date Flow Template) 0 c ) according to the known public IPv4 address or IPv6 prefix, PCRF transmits setup confirmation message to the PGW IP CAN session message It contains the PCC rules and the PCC rule contains a service data flow template (service Date flow template) 0 PGW for each different user equipment generates a packet filter (packet Fi l ter, for matching service data
  • the method of the relationship between the flow and the bearer includes, for example, the feature a) describing when the user equipment initiates a P ⁇ connection establishment procedure (eg, an At tach flow or a PDN connection establishment procedure), and the PGW allocates or PGW to the user equipment.
  • DHCP Dynamic Hos t Conf igurat Protocol
  • the PGW assigns different interface identifiers to each different user equipment of the group or the user group.
  • the PGW allocates different interface identifiers for each different user equipment. Restricting, for example, the PGW assigns a different interface identifier according to the IMEI identifier or the IMSI identifier of the user equipment, and the PGW generates a complete IPv6 address according to the obtained IPv6 address prefix and the interface identifier assigned to the user equipment, and the PGW 4 full IPv6 address of the user device generates a packet filter (packet Fi l ter) 0
  • the PGW allocates different IPv4 addresses for each different user equipment of the group or the user group (the PGW assigns different IPv4 addresses to each different user equipment. Restricting, if the PGW allocates different IPv4 addresses according to the IMEI identifier or the IMSI identifier of the user equipment, the PGW generates a packet filter of the user equipment according to assigning different IPv4 addresses to each different user equipment (Packet Fi l ter ).
  • Step 203 Perform PCC optimization processing according to the group identifier of the user equipment.
  • the PGW or the SGW or the GGSN or the PCRF generates a PCC rule or a trigger event shared by the group or the user group.
  • the network side performs PCC optimization according to the group identifier of the second user equipment (which belongs to the same group as the first user equipment), and specifically includes:
  • the second user equipment initiates a PDN connection establishment process (such as an At tach process or a PDN connection establishment process), and the PGW or the SGW or the GGSN or the PCRF generates a PCC rule for the second user equipment.
  • the method of performing the PCC optimization by the PGW or the SGW or the GGSN includes: the PGW or the SGW or the GGSN according to the group identifier of the second user equipment, and the specific method includes: when the static PCC is applied, the PGW or the SGW or the GGSN learns a group identifier of the second user equipment, if the group identifier of the second user equipment is the same as the group identifier of the first other user equipment, the second user equipment is allocated the generated The policy and charging rules or triggering events of the group to which the first user equipment belongs.
  • the method may further include: configuring at least one of the group identity or the device attribute information of the first user equipment, and establishing the PDN connection of the first user equipment
  • the APN information carried in the request generates a PCC rule or a trigger event.
  • the PGW or the SGW or the GGSN further determines the APN information corresponding to the P ⁇ connection initiated by the second user equipment, and the first other user.
  • the PGW or the SGW or the GGSN If the APN information corresponding to the device-initiated PDN connection is the same, the PGW or the SGW or the GGSN generates the same PCC rule or trigger event (ie, PGW or the same as the PCC rule or the trigger event generated for the first other user equipment.
  • the SGW or the GGSN uses the learned PCC rules or trigger events generated for a certain APN by the group or group of users to which the user equipment belongs.
  • the PGW or the SGW or the GGSN learns the group identifier of the second user equipment, and if the group identifier of the second user equipment is the same as the group identifier of the first other user equipment, The second user equipment allocates the generated policy and charging rule or trigger event of the group to which the first user equipment belongs.
  • the method may further include: at least one of the group identifier or the device attribute information of the first user equipment, and the P ⁇ connection of the first user equipment
  • the APN information carried in the request is established, and a PCC rule or a trigger event is generated.
  • the PGW or the SGW or the GGSN When the second user equipment initiates an access request (for example, a P ⁇ connection request or an attach request), the PGW or the SGW or the GGSN further determines the APN information corresponding to the P ⁇ connection initiated by the second user equipment, and the first other user. If the APN information corresponding to the device-initiated P-connection is the same, the PGW or the SGW or the GGSN generates, for the second user equipment, a PCC rule or a trigger event that is the same as the obtained PCC rule or trigger event generated by the first other user equipment. PGW or The SGW or the GGSN does not use the learned PCC rule or trigger event generated for the APN by the group or group of users to which the user equipment belongs, and does not send an IP CAN session establishment indication message to the PCRF.
  • an access request for example, a P ⁇ connection request or an attach request
  • the user equipment initiates a PDN de-connection process (eg, a Detach process or a PDN de-connection process), and the PGW or the SGW or the GGSN receives a message for deleting a PDN connection request (eg, De 1 ete Se ssi on Reques t Or the PGW or the SGW or the GGSN determines whether the group identifier corresponding to the other user equipment is the same as the group identifier of the user equipment, and the PGW may further determine whether there is another user equipment corresponding to the
  • the APN information corresponding to the P ⁇ connection established by the group identifier and the other user equipment is the same as the APN information corresponding to the group identifier of the user equipment and the PDN connection deleted by the user equipment.
  • the PGW or SGW or The GGSN does not delete the PCC rule or trigger event, or the PGW or SGW or GGSN does not send an IP CAN Session Termination Indication message to the PCRF. If not, the PGW or SGW or GGSN will delete the PCC rule or trigger event, or the PGW or SGW or GGSN sends an IP CAN Session Termination Indication message to the PCRF.
  • the PCRF initiates an IP CAN session termination procedure for a group or a user group, and the PCRF sends an IP CAN session termination indication message to the PGW, where the message carries the group identifier, optionally, the PCRF needs The terminated P ⁇ identifier, such as the APN information.
  • the network side According to the description of steps 202 and 203, the network side generates a PCC rule or a trigger event shared by the group, and the network side performs PCC optimization according to the group identifier of the user equipment, which solves the problem of inefficient network policy control and the strategy. Maintenance and management of complex issues, etc., also reduces the signaling interaction between GW and PCRF, achieving the effect of signaling optimization.
  • FIG. 3 is a schematic flowchart of a second embodiment of a method for processing a group policy and a charging rule according to the present invention.
  • a group policy and a charging rule are processed in an attach request (At tach) process, according to a user.
  • At least one of the group identifier or the device attribute information of the device acquires a PCC rule or a trigger event.
  • the following steps are included:
  • Step 301 The M2ME sends an attach request message to the solid E.
  • M2ME carries in the attach request message
  • the M2ME identity information is optional.
  • the M2ME may carry the group charging identifier in the attach request message.
  • the M2ME may carry its device attribute information (MTC Feature) in the attach request message;
  • Step 302 perform a process of authentication and authentication;
  • Step 303 The solid E sends an update location area request message to the HSS or the group subscription database. If the E is obtained in the attach request message, the E is carried in the update location area request message;
  • Step 304 the HSS or the Group subscription database returns an update location area confirmation message.
  • the HSS returns the subscription data information in the update location area confirmation message.
  • the update location area confirmation message includes group identification information.
  • the update location area confirmation message includes device attribute information of the M2ME.
  • Step 305 The solid E sends a create session request message to the SGW. If the MME obtains the group identity or the device attribute information of the M2ME, the MME may carry the group identification information or the device attribute information in the creation session request message.
  • Step 306 The SGW sends a create session request message to the PGW. If the SGW obtains the group identity or the device attribute information of the M2ME, the group identification information or the device attribute information may be carried in the creation session request message;
  • the following steps 307 to 310 are performed for the dynamic PCC application and are not executed during the static PCC application.
  • Step 307 The PGW sends an IP CAN session establishment indication message to the PCRF. If the PGW obtains the group identity of the M2ME, the group identity may be carried in the IP CAN session establishment indication message. Optionally, if the PGW obtains the device attribute information of the M2ME in step 306, the PGW carries the device attribute information of the M2ME in the IP CAN session establishment indication message;
  • Step 308 The PCRF sends a configuration information request message to the SPR or the group subscription database. If the PCRF obtains the group identifier of the M2ME, the PCRF carries the group identifier in the configuration information request message;
  • Step 309 The SPR or the group subscription database returns a configuration information response message.
  • SPR or The Group subscription database returns the service subscription data of the M2ME in the configuration information response message.
  • the message includes an M2ME group identifier, or device attribute information of the M2ME.
  • Step 31 The PCRF formulates a PCC rule or a trigger event according to at least one of the group identifier or the device attribute information of the user equipment or the service subscription data of the user equipment, and sends an IP CAN session establishment confirmation message to the PGW.
  • the specific method is as described in step 202 of the first embodiment.
  • the PCRF indicates, in the PCC rule that is specified for the user equipment, that the PCC rule application range is a group or a user group to which the user equipment belongs, or in the PCC.
  • the rule carries the group identifier of the group to which the user equipment belongs, and the PGW obtains the PCC rule according to the application scope in the PCC rule or the group identifier of the group to which the user equipment belongs in the PCC rule.
  • the PCRF generates a trigger event, where the trigger event is applied to a group or a user group granularity, for example, when the PGW counts the data traffic used by the user equipment of the group or the user group to reach a certain threshold, the PGW sends the event.
  • Step 31 The PGW sends a Create Session Response message to the SGW, where the message includes the PGW to obtain a PCC rule or a trigger event.
  • the PGW formulates a PCC rule or a trigger event according to at least one of the group identifier or the device attribute information of the user equipment.
  • the specific method is as described in the feature (1) of the step 202 in the first embodiment, and is not described in this embodiment.
  • the PCGW rules or triggering events that are set by the PGW for the user equipment are applied to the group or user group to which the user equipment belongs;
  • Step 312 The SGW sends a session creation response message to the solid E.
  • Step 31 3 The solid E sends an attach accept message to the M2ME.
  • the PGW or the PCRF performs PCC optimization according to the group identifier of the M2ME.
  • the specific method is as described in step 203 in the first embodiment: the PGW is configured according to the group identifier of the M2ME, and optionally, according to the P2 connection initiated by the M2ME, the corresponding APN letter. It is determined whether to use the learned PCC rules or trigger events generated for the group or group of users to which the M2ME belongs.
  • the specific method is described in the feature (1) of the step 203 of the first embodiment, and is not described in this embodiment.
  • Another embodiment of the present invention provides the M2ME initiating a P-to-connection process (such as a Detach process or a PDN de-connection process), as described in feature (2) of step 203 in the first embodiment, and the PGW receives the deletion.
  • the PDN connection request message (De le te Ses s ion Reques t ), as shown in FIG. 4: Step 40
  • the PGW receives the delete IP CAN session request message, such as a De 1 ete Se ssi on Reque st message.
  • the PGW determines whether the group identifier corresponding to the other user equipment is the same as the group identifier of the user equipment, and optionally, the PGW establishes the P identifier corresponding to the other user equipment and the P established by the other user equipment.
  • the APN information corresponding to the ⁇ connection is the same as the APN information corresponding to the group identifier of the user equipment and the P ⁇ connection deleted by the user equipment. If yes, the PGW does not delete the PCC rule or the trigger event, or the PGW.
  • the IP CAN Session Termination Indication message is not sent to the PCRF. If not, the PGW will delete the PCC rule or trigger event, or the PGW sends an IP CAN session termination indication message to the PCRF;
  • Step 402 If the PCRF receives the termination IP CAN session indication message.
  • the message carries the group identifier of the group to which the user equipment belongs, and the optional APN information corresponding to the PDN connection deleted by the user equipment, and the PCRF is based on the group of the group to which the user equipment belongs.
  • Step 403 The PCRF sends an acknowledgement to the PGW to terminate the IP CAN session message.
  • Step 404 The PGW sends a delete IP CAN session response message.
  • Step 405 According to the description in step 402, the PCRF sends a cancel subscription data notification request to the SPR.
  • Step 406 If the cancel subscription data notification request message is received, the SPR returns a cancellation subscription data notification response to the PCRF.
  • Step 407 The PGW sends a final threshold report to the 0CS.
  • the optional message carries the group identifier of the group to which the user equipment belongs.
  • Steps 408 and 0CS return a threshold confirmation message.
  • FIG. 5 is a schematic flowchart of a method for processing a group policy and a charging rule according to a third embodiment of the present invention.
  • a group policy and a charging rule are processed in a PDN connection process, according to a group of user equipments.
  • At least one of the identification or device attribute information acquires a PCC rule or a trigger event.
  • the following steps are included:
  • Step 501 The M2ME sends a PDN connection establishment request message to the solid E.
  • the message carries information such as APN;
  • Step 502 The solid E sends a create session request message to the SGW. If the MME obtains the group identity or the device attribute information of the M2ME, the MME may carry the group identification information or the device attribute information in the creation session request message.
  • Step 503 The SGW sends a create session request message to the PGW. If the SGW obtains the group identity or the device attribute information of the M2ME, the group identification information or the device attribute information may be carried in the creation session request message;
  • steps 504 through 507 described below are skipped.
  • Step 504 When the dynamic PCC is applied, the PGW sends an IP CAN session establishment indication message to the PCRF. If the PGW obtains the group identity of the M2ME, the group identity may be carried in the IP CAN session establishment indication message. Optionally, if the PGW obtains the device attribute information of the M2ME in step 503, the PGW carries the device attribute information of the M2ME in the IP CAN session establishment indication message;
  • Step 505 The PCRF sends a configuration information request message to the SPR or the group subscription database. If the PCRF obtains the group identifier of the M2ME, the PCRF carries the group identifier in the configuration information request message; Step 506: The SPR or the Group subscription database returns a configuration information response message. The SPR or the group subscription database returns the service subscription data of the M2ME in the configuration information response message.
  • the message includes an M2ME group identifier, or device attribute information of the M2ME.
  • Step 507 The PCRF formulates a PCC rule or a trigger event according to at least one of a group identifier or device attribute information of the user equipment or service subscription data of the user equipment, and sends an IP CAN session establishment confirmation message to the PGW.
  • the specific method may be as described in step 302 of the first embodiment.
  • the PCRF indicates, in the PCC rule that is specified for the user equipment, that the PCC rule application range is a group or a user group to which the user equipment belongs, or in the PCC.
  • the rule carries the group identifier of the group to which the user equipment belongs, and the PGW obtains the PCC rule according to the application scope in the PCC rule or the group identifier of the group to which the user equipment belongs in the PCC rule.
  • the PCRF generates a trigger event, where the trigger event is applied to a group or a user group granularity, for example, when the PGW counts the data traffic used by the user equipment of the group or the user group to reach a certain threshold, the PGW sends the event.
  • Step 508 The PGW sends a create session response message to the SGW, where the message includes the PGW to obtain a PCC rule or a trigger event.
  • the PGW formulates a PCC rule or a trigger event according to at least one of the group identifier or the device attribute information of the user equipment.
  • the specific method is as described in the feature (1) of the step 202 in the first embodiment, and is not described in this embodiment.
  • the PCGW rules or triggering events that are set by the PGW for the user equipment are applied to the group or user group to which the user equipment belongs;
  • Step 509 The SGW sends a session creation response message to the solid E.
  • Step 51 The E sends an E-RAB setup request message to the eNodeB, where the message carries an active default bearer request message sent to the M2ME.
  • Step 51 The eNodeB sends an RRC connection reconfiguration message to the M2ME.
  • Step 514 The M2ME sends a direct transmission message to the eNodeB, where the message carries an active default bearer response message.
  • Step 515 The eNodeB delivers an activation default bearer response message to the MME.
  • Step 516 The solid E sends a modify bearer request message to the SGW.
  • Step 517 The SGW returns a modify bearer response message to the solid E.
  • FIG. 6 is a schematic structural diagram of an embodiment of a group policy and charging rule processing device according to the present invention. As shown in FIG. 6, the acquiring module 1 1 is included. And a rule generating module 12, wherein the obtaining module 1 is configured to acquire at least one of a group identifier or a device attribute information of the user equipment; the rule generating module 12 is configured to use the group identifier or the device attribute information of the user equipment. At least one of the generated policy and charging rules or trigger events.
  • the group policy and the charging rule processing device provided by the embodiment of the present invention can obtain the group identifier or the device attribute information of the user equipment, and generate a policy and a charging rule or a trigger event according to the obtained information, thereby effectively improving the group. Policy control efficiency of user equipment or user equipment with the same device characteristics reduces the complexity of policy maintenance and management.
  • the acquiring module in the foregoing embodiment includes a first acquiring unit, where the first acquiring unit is configured to acquire at least one of a group identifier or device attribute information carried by the user equipment in the access request message; or At least one of a group identifier or a device attribute information of the user equipment for obtaining a home subscriber server or a group subscription database subscription; or an identifier for acquiring the user equipment, from the pre-configured user according to the identifier of the user equipment Obtaining at least one of a group identifier or a device attribute information of the user equipment in the device information; the corresponding rule generating module includes a first rule generating unit, where the first rule generating unit is configured to use the acquired group identifier of the user equipment or At least one of the device attribute information generates a policy and a charging rule or a triggering event, and indicates that the application scope of the policy and the charging rule or the triggering event is a group or a user to which the user equipment belongs. Group.
  • the group policy and charging rule processing apparatus in this embodiment may be disposed in a serving gateway, a packet data network gateway, or a gateway GPRS support node.
  • the acquiring module includes a second obtaining unit, where the second obtaining unit is configured to acquire at least one of a group identifier or device attribute information carried in the IP CAN session message, or used according to the user equipment. Identifying at least one of a group identifier or device attribute information of the user equipment obtained from the service subscription database or the group subscription database.
  • the corresponding rule generating module includes a second rule generating unit, configured to generate a policy and a charging rule or a trigger event according to at least one of a group identifier or a device attribute information of the acquired user equipment, and in the policy and In the charging rule or triggering event, the application scope is indicated as the group or user group to which the user equipment belongs.
  • the apparatus in the foregoing embodiment may further include an optimization processing module, where the module is configured to: when at least one of the group identifier or the device attribute information of the second user equipment is the same as the first user equipment, The second user equipment allocates the generated policy and charging rule or trigger event of the group to which the first user equipment belongs.
  • the embodiment of the invention further provides a communication system, comprising the group policy and charging rule processing device described above.
  • the group policy and charging rule processing device described above is disposed on the service gateway, the packet data network gateway, the gateway GPRS support node, or the policy and charging rule function entity.
  • the communication system provided by the embodiment of the present invention includes a group policy and a charging rule processing device, which acquires a group identity or device attribute information of a user equipment, and generates a group policy and a charging rule or a trigger event according to the obtained information. It can effectively improve the policy control efficiency of the user equipment of the group or the user equipment with the same equipment characteristics, and reduce the complexity of policy maintenance and management.
  • the group policy and the charging rule processing method, the device, and the communication system provided by the embodiment of the present invention obtain the group identity or the device attribute information of the user equipment, and generate a group policy and charging rule or trigger according to the obtained information.
  • the event can effectively improve the policy control efficiency of the user equipment of the group or the user equipment with the same equipment feature, and reduce the complexity of policy maintenance and management.
  • Further performing PCC optimization according to the group identifier of the user equipment which can be reduced
  • the signaling interaction between the GW and the PCRF achieves the effect of signaling optimization.

Abstract

A method, a device and a communication system for processing group policy and charging rules are provided. The method for processing group policy and charging rules comprises: obtaining at least one of the group identifier or the equipment attribute information of a user equipment; generating policy and charging rules or a trigger event according to at least one of the group identifier or the equipment attribute information of the user equipment. The device comprises: an obtaining module for obtaining at least one of the group identifier or the equipment attribute information of the user equipment; a rule generation module for generating the policy and charging rules or the trigger event according to at least one of the group identifier or the equipment attribute information of the user equipment. The communication system comprising the device as described above is also provided. With the provided method, device and communication system, the efficiency of policy control can be improved, and the complexity of policy maintenance and management is reduced.

Description

群组策略与计费规则处理方法、 装置以及通信*** 本申请要求于 2009 年 09 月 04 日提交中国专利局、 申请号为 200910091997. 5 , 发明名称为 "群组策略与计费规则处理方法、 装置以及通 信***" 的中国专利申请的优先权, 其全部内容通过引用结合在本申请中。 技术领域  Group policy and charging rule processing method, device and communication system The application is submitted to the Chinese Patent Office on September 4, 2009, and the application number is 200910091997. 5 , and the invention name is "group policy and charging rule processing method, The priority of the Chinese Patent Application, the entire disclosure of which is incorporated herein by reference. Technical field
本发明实施例涉及通信技术领域, 特别涉及一种群组策略与计费规则处 理方法、 装置以及通信***。 背景技术  The embodiments of the present invention relate to the field of communications technologies, and in particular, to a group policy and charging rule processing method, apparatus, and communication system. Background technique
现有技术的策略与计费控制 (Pol icy Charg ing Cont rol,以下简称: PCC ) 机制制定了用户在开展业务时, 需要为所有用户的每一业务服务数据流建立 独立的策略控制机制, 在 IP CAN会话建立流程中包括如下的步骤, 首先网关 在接收到用户设备发起的 IP-CAN会话建立请求消息(分配一个网络 PDN网络 可见的 IP地址)后, 向 PCRF发送包括 UE标识、 IP地址和 APN信息的 IP CAN 会话建立消息, 通知 PCRF IP CAN会话建立, PCRF如果需要用户签约相关信 息, 则向 SPR发送用户签约信息请求消息 (Prof i le Reques t ) 消息, SPR返 回用户签约信息响应消息, 包括用户当前签约的业务、计费模式等信息; PCRF 生成新的计费规则, 并通过 IP CAN会话建立确认消息将 PCC规则返回给网关 ( GW ) ,网关安装规则, 并根据规则打开或者关闭对应的业务数据流, 执行相 应的 QoS及计费规则, 随后 GW向 UE发送 IP CAN会话建立响应消息。  The prior art Policy and Charging Control (PCC) mechanism establishes that when a user conducts a service, it needs to establish an independent policy control mechanism for each service data flow of all users. The IP CAN session establishment process includes the following steps. First, after receiving the IP-CAN session establishment request message initiated by the user equipment (assigning an IP address visible to the network PDN network), the gateway sends the UEF, including the UE identifier, the IP address, and the PCRF. The IP CAN session establishment message of the APN information notifies the PCRF that the IP CAN session is established. If the user needs to sign the related information, the PCRF sends a user subscription information request message (Prof i le Reques t ) message to the SPR, and the SPR returns the user subscription information response message. The information including the current subscription service and charging mode of the user is generated; the PCRF generates a new charging rule, and returns the PCC rule to the gateway (GW) through the IP CAN session establishment confirmation message, and the gateway installs the rule, and opens or closes the corresponding according to the rule. Business data flow, implementing the corresponding QoS and charging rules, The GW then sends an IP CAN Session Setup Response message to the UE.
发明人在实现本发明的过程中发现: 对于机器类型通信(Machine Type Commun i ca t i on,以下筒称: MTC )应用, 即一个或多个网元或设备之间不需要 认为参与的情况下进行的网络通信, 也可称为机器对机器 (Machine to Machine , 以下筒称: M2M )应用, 例如在交通控制和管理、 工厂控制和远程 抄表的应用, 运营商根据上述的 M2M应用的特点将 MTC设备组成群组。 例如 对于远程抄表的应用, 运营商会将某个区域的电表设备组成一个群组, 而上 述群组中的 MTC设备都具有相同的 M2M设备属性信息, 如低移动、 时延不敏 感等特点, 当上述 MTC设备接入网络后, 如果按照现在的 PCC的处理机制, 网络侧对每个 MTC设备发起的每一个业务建立都需要执行并下发相应的 PCC 规则, 但是由于 MTC设备数量众多, 所以如果按照现有的 PCC的处理机制, 必将会对网络的性能造成大量的开销。 另外, 某些 M2M设备应用简单, 且对 于属于同一个群组的 MTC设备来讲, 具有相同的 M2M设备属性信息, 即其业 务类型是一致的, 如上述的远程抄表业务, 对于上述的群组的 MTC设备可以 共享相同的 PCC控制策略, 如果按照现有的 PCC的处理机制, 存在策略控制 效率低下、 策略维护复杂的缺点。 发明内容 The inventor found in the process of implementing the present invention: For the Machine Type Communication (MTC) application, that is, one or more network elements or devices do not need to be considered to participate in the case Network communication, also known as Machine to Machine (M2M) applications, such as traffic control and management, factory control and remote meter reading applications, operators based on the characteristics of the above M2M applications Group MTC devices into groups. For example, for remote meter reading applications, the operator will group the meter devices in a certain area into a group. The MTC devices in the group all have the same M2M device attribute information, such as low mobility and delay insensitivity. After the MTC device accesses the network, if the current PCC processing mechanism is followed, the network side pairs each. Each service establishment initiated by the MTC device needs to execute and deliver the corresponding PCC rules. However, due to the large number of MTC devices, if the existing PCC processing mechanism is used, a large amount of overhead will be incurred on the performance of the network. In addition, some M2M devices are simple to apply, and have the same M2M device attribute information for the MTC devices belonging to the same group, that is, their service types are consistent, such as the above-mentioned remote meter reading service, for the above group The group of MTC devices can share the same PCC control strategy. If the existing PCC processing mechanism is used, there are disadvantages such as inefficient policy control and complicated policy maintenance. Summary of the invention
本发明实施例的目的是提供一种群组策略与计费规则处理方法、 装置以 及通信***, 以提高策略控制效率。  An object of the embodiments of the present invention is to provide a group policy and charging rule processing method, apparatus, and communication system to improve policy control efficiency.
为实现上述目的, 本发明实施例提供了一种群组策略与计费规则处理方 法, 包括:  To achieve the above objective, an embodiment of the present invention provides a group policy and a charging rule processing method, including:
获取用户设备的群组标识或者设备属性信息中的至少一项;  Obtaining at least one of a group identifier or device attribute information of the user equipment;
根据所述用户设备的群组标识或者设备属性信息中的至少一项生成策略 与计费规则或者触发事件。  Generating a policy and charging rule or a triggering event according to at least one of a group identity or device attribute information of the user equipment.
本发明实施例还提供了一种群组策略与计费规则处理装置, 包括: 获取模块, 用于获取用户设备的群组标识或者设备属性信息中的至少一 项;  The embodiment of the present invention further provides a group policy and charging rule processing device, including: an obtaining module, configured to acquire at least one of a group identifier or device attribute information of a user equipment;
规则生成模块, 用于根据所述用户设备的群组标识或者设备属性信息中 的至少一项生成策略与计费规则或者触发事件。  And a rule generating module, configured to generate a policy and charging rule or a trigger event according to at least one of a group identifier or a device attribute information of the user equipment.
本发明实施例还提供了一种通信***, 包括上述的群组策略与计费规则 处理装置。  The embodiment of the invention further provides a communication system, comprising the group policy and charging rule processing device described above.
本发明实施例提供的群组策略与计费规则处理方法、装置以及通信***, 通过获取用户设备的群组标识或者设备属性信息, 并根据上述获取的信息生 成群组策略与计费规则或者触发事件, 能够有效提高群组的用户设备或者具 有相同的设备特征的用户设备的策略控制效率, 并降低策略维护和管理的复 杂度。 附图说明 A group policy and charging rule processing method, device and communication system provided by an embodiment of the present invention, By acquiring the group identifier or the device attribute information of the user equipment, and generating the group policy and the charging rule or the triggering event according to the obtained information, the group user equipment or the user equipment having the same device feature can be effectively improved. Control efficiency and reduce the complexity of policy maintenance and management. DRAWINGS
图 1为本发明群组策略与计费规则处理方法实施例一的流程示意图; 图 1为本发明群组策略与计费规则处理方法第一具体实施例的流程示意 图;  1 is a schematic flowchart of Embodiment 1 of a method for processing a group policy and a charging rule according to the present invention; FIG. 1 is a schematic flowchart of a first embodiment of a method for processing a group policy and a charging rule according to the present invention;
图 3为本发明群组策略与计费规则处理方法第二具体实施例的流程示意 图;  3 is a schematic flow chart of a second embodiment of a group policy and charging rule processing method according to the present invention;
图 4为图 3所述实施例中 PCC优化处理的流程示意图;  4 is a schematic flow chart of PCC optimization processing in the embodiment shown in FIG. 3;
图 5为本发明群组策略与计费规则处理方法第三具体实施例的流程示意 图;  5 is a schematic flow chart of a third embodiment of a group policy and charging rule processing method according to the present invention;
图 6为本发明群组策略与计费规则处理装置实施例的结构示意图。 具体实施方式  FIG. 6 is a schematic structural diagram of an embodiment of a group policy and charging rule processing apparatus according to the present invention. detailed description
下面通过附图和实施例, 对本发明的技术方案做进一步的详细描述。 本发明实施例提供了一种群组策略与计费规则处理方法, 图 1 为本发明 群组策略与计费规则处理方法实施例一的流程示意图, 如图 1 所示, 包括如 下的步骤:  The technical solution of the present invention will be further described in detail below through the accompanying drawings and embodiments. An embodiment of the present invention provides a group policy and a charging rule processing method. FIG. 1 is a schematic flowchart of a first embodiment of a method for processing a group policy and a charging rule according to the present invention. As shown in FIG. 1, the method includes the following steps:
步骤 101、获取用户设备的群组标识或者设备属性信息中的至少一项; 即 本步骤中获取用户设备的群组标识或者设备属性信息, 或者是同时获取上述 两项。  Step 101: Obtain at least one of a group identifier or a device attribute information of the user equipment; that is, obtain the group identifier or the device attribute information of the user equipment in this step, or obtain the foregoing two items at the same time.
用户设备的群组标识对于用户组或者群组用户来说, 是用户组标识 (也 可以描述为用户组用户标识)或者群组标识(也可以描述为群组用户标识), 或者其他指示用户设备所属群组或者用户组的标识, 例如, 通过 APN ( Acces s Point Name )标识用户设备所属群组或者用户组, 则 APN就是用户设备所属 群组或者用户组的标识, 本实施例中对群组标识不做限制。 所述群组或者用 户组可以是用户设备组或者 M2M行业用户 (MTC User )或者 M2M应用签约用 户 (MTC Subscr iber )或者其他由多个设备组成的群组, 本实施例中不作限 制。 The group identifier of the user equipment is a user group identifier (which may also be described as a user group user identifier) or a group identifier (which may also be described as a group user identifier) for the user group or the group user. Or the identifier of the group or the user group to which the user equipment belongs, for example, the group or the user group to which the user equipment belongs is identified by the APN (Aces s Point Name), and the APN is the identifier of the group or user group to which the user equipment belongs. In the example, there is no restriction on the group identifier. The group or the user group may be a user equipment group or an M2M industry user (MTC User) or an M2M application subscription user (MTC Subscr iber) or other group of multiple devices, which is not limited in this embodiment.
其中, 设备属性信息为具有相同特性的用户设备所共有的属性信息, 是 根据不同的行业用户 (MTC User )或者 M2M应用签约用户 (MTC Subscr iber ) 不同的应用而获得的不同的设备特征信息, 也可以称为是设备特征(Machine Fea ture )或者设备类型 (Machine Type )或者服务类别 (Servi ce Cla s s )。 例如对于远程抄表***中的用户设备具有低移动、 时延不敏感等特点, 则其 设备属性信息是低移动、 时延不敏感等; 本实施例不对设备属性信息所包含 的内容和设备属性信息的名称做限制。  The device attribute information is attribute information shared by the user equipments having the same characteristics, and is different device feature information obtained according to different applications of different industry users (MTC User) or M2M application subscription users (MTC Subscr iber). It can also be called a Machine Feature or a Machine Type or a Service Category (Servi ce Cla ss). For example, if the user equipment in the remote meter reading system has the characteristics of low mobility, delay insensitivity, etc., the device attribute information is low mobility, delay insensitive, and the like; in this embodiment, the content and device attributes included in the device attribute information are not included in this embodiment. The name of the information is restricted.
步骤 102、根据所述用户设备的群组标识或者设备属性信息中的至少一项 生成策略与计费规则或者触发事件。  Step 102: Generate a policy and charging rule or a trigger event according to at least one of a group identifier or a device attribute information of the user equipment.
其中, 该策略与计费规则或者触发事件的应用范围为所述用户设备所属 的群组或者用户组。 即对后续该用户设备所属的群组或者用户组下的其他用 户也应用该策略与计费规则或者触发事件。  The application scope of the policy and the charging rule or the triggering event is a group or a user group to which the user equipment belongs. That is, the policy and charging rule or trigger event is also applied to the group to which the user equipment belongs or other users in the user group.
本实施例中的触发事件为一种 PCEF或者 BBERF事件上报行为的规则, 其 应用范围是针对用户设备所属的群组或者用户组下的所有用户设备。 例如, 当触发事件是该群组下某个用户设备位置改变, 则 PCEF或者 BBERF获知后, 则需要将用户设备位置改变的事件上报给策略与计费规则功能实体。  The triggering event in this embodiment is a rule for reporting the behavior of the PCEF or the BBERF event, and the application scope is for the user group to which the user equipment belongs or all user equipments under the user group. For example, when the triggering event is that the location of a certain user equipment in the group is changed, the PCEF or the BBERF is notified, and the event of the user equipment location change needs to be reported to the policy and charging rule function entity.
本实施例中通过获取用户设备的群组标识或者设备属性信息, 并根据上 述获取的信息生成群组策略与计费规则或者触发事件, 能够有效提高群组的 用户设备或者具有相同的设备特征的用户设备的策略控制效率, 并降低策略 维护和管理的复杂度。 本发明上述实施例中可分为动态 PCC应用和静态 PCC应用两种情况:In this embodiment, the group identifier or the device attribute information of the user equipment is obtained, and the group policy and the charging rule or the triggering event are generated according to the obtained information, which can effectively improve the user equipment of the group or have the same device characteristics. The policy of the user equipment controls the efficiency and reduces the complexity of policy maintenance and management. The above embodiments of the present invention can be divided into two situations: dynamic PCC application and static PCC application:
1、对于进行静态 PCC应用,获取用户设备的群组标识或设备属性信息( MTC Fea ture ) 中的至少一项包括: 服务网关、 分组数据网络网关或网关 GPRS 支 持节点获取用户设备在接入请求消息 (如, 附着请求( A 11 a ch Reque s t )、 位 置区更新请求 ( Route ing Area Upda te Reques t 或 Tracking Area Upda te Reques t ), P匪连接建立请求 ( PDN Connect ivi ty Es tabl i shment Reques t ), 激活 PDP上下文请求 ( Act ive PDP Context Reques t )、 创建 PDP上下文请求 ( Crea te PDP Context Reques t )或创建会话请求 ( Crea te Ses s ion Reques t ) ) 中携带的群组标识或者设备属性信息中的至少一项; 或者上述网元获取在归 属用户服务器( HLR或者 HSS )或群组签约数据库签约的用户设备的群组标识 或者设备属性信息中的至少一项; 或者上述网元可以通过现有流程获取用户 设备的标识, 根据所述用户设备的标识从上述网元预先配置的用户设备信息 中获取用户设备的群组标识或者设备属性信息中的至少一项。 1. For performing a static PCC application, acquiring at least one of a group identity or device attribute information (MTC Feature) of the user equipment includes: a service gateway, a packet data network gateway, or a gateway GPRS support node acquires a user equipment in an access request. Messages (eg, A 11 a ch Reque st ), Location ing Area Upda te Reques t or Tracking Area Upda te Reques t, P匪 Connect connection request (PDN Connect ivi ty Es tabl i shment Reques t), activate the PDP Context Reques t, create a PDP Context Reques t, or create a session request (Crea es Res s Re Res) or At least one of the device attribute information; or the network element acquiring at least one of a group identifier or device attribute information of the user equipment subscribed to the home subscriber server (HLR or HSS) or the group subscription database; or the foregoing network element The identifier of the user equipment can be obtained through an existing process, according to the identifier of the user equipment, Membered user device information acquired pre-configured user equipment device group identifier or the at least one of the attribute information.
根据用户设备的群组标识或者设备属性信息中的至少一项生成策略与计 费规则或者触发事件包括: 服务网关、 分组数据网络网关或网关 GPRS支持节 点根据获取的用户设备的群组标识或者设备属性信息中的至少一项生成策略 与计费规则或者触发事件, 并指示所述策略与计费规则或者触发事件的应用 范围为所述用户设备所述的群组或者用户组。 具体可以包括:  Generating a policy and charging rule or triggering event according to at least one of a group identifier or a device attribute information of the user equipment, including: a service gateway, a packet data network gateway, or a group GPRS support node according to the obtained group identifier or device of the user equipment. At least one of the attribute information generates a policy and a charging rule or a triggering event, and indicates that the application scope of the policy and the charging rule or the triggering event is a group or a group of users described by the user equipment. Specifically, it may include:
a )具体服务网关、 分组数据网络网关或网关 GPRS 支持节点生成策略与 计费规则或者触发事件的方法可以如下所述: 一种方法是, 服务网关、 分组 数据网络网关或网关 GPRS支持节点根据获得的用户设备的设备属性信息, 如 低移动性, 时延不敏感, 根据其上静态配置的 PCC规则或者触发事件, 制定 相应的 PCC规则或者触发事件。 另一种方法是, 服务网关、 分组数据网络网 关或网关 GPRS支持节点根据获得的用户设备的群组标识信息, 根据其上静态 配置的 PCC规则或者触发事件, 制定与所述用户设备群组标识对应的 PCC规 则或者触发事件。 b )指示所述策略与计费规则或者触发事件的应用范围为所述用户设备所 述的群组或者用户组具体方法可以是: 在生成的 PCC规则或者触发事件中, 增加指示 PCC规则或者触发事件应用范围的信元, 如, Apply Scope , 当设置 Apply Scope为群组范围时, 则生成的 PCC规则或者触发事件应用于所述用户 设备所述的群组或用户组。 另外一种方法是, 生成的 PCC规则或者触发事件 中包含用户设备所述的群组或者用户组的标识, 则服务网关、 分组数据网络 网关或网关 GPRS支持节点根据群组或者用户组的标识将 PCC规则或者触发事 件应用于所述用户设备所述的群组或用户组。 a) The specific service gateway, the packet data network gateway or the gateway GPRS support node generates a policy and charging rule or a method for triggering an event as follows: One method is that the service gateway, the packet data network gateway or the gateway GPRS support node is obtained according to The device attribute information of the user equipment, such as low mobility, delay is not sensitive, and the corresponding PCC rules or trigger events are formulated according to the statically configured PCC rules or trigger events. In another method, the service gateway, the packet data network gateway, or the gateway GPRS support node formulates the group identifier with the user equipment according to the statically configured PCC rule or the trigger event according to the obtained group identification information of the user equipment. Corresponding PCC rules or trigger events. b) indicating that the application of the policy and the charging rule or the triggering event is the group or the user group of the user equipment, the specific method may be: adding a PCC rule or triggering in the generated PCC rule or the triggering event The cell of the event application scope, for example, Apply Scope, when the Apply Scope is set to the group scope, the generated PCC rule or trigger event is applied to the group or user group described by the user equipment. In another method, the generated PCC rule or the trigger event includes the identifier of the group or the user group described by the user equipment, and the service gateway, the packet data network gateway, or the gateway GPRS support node according to the identifier of the group or the user group. A PCC rule or triggering event is applied to the group or group of users described by the user equipment.
2、 对于动态 PCC应用, 获取用户设备的群组标识或者设备属性信息中的 至少一项包括: 一种方式为, 策略与计费规则功能实体获取服务网关、 分组 数据网络网关或网关 GPRS支持节点在 IP CAN会话消息 (如, Ind ica t ion IP CAN Ses s ion Es tab l i shment ) 中携带的群组标识或者设备属性信息中的至少 一项; 另一种方式为根据所述用户设备的标识从业务签约数据库或者群组签 约数据库中获取用户设备的群组标识或者设备属性信息中的至少一项, 即是 策略与计费控制功能实体向业务签约数据库(SPR )或者群组签约数据库发送 配置请求消息 (如, Prof i le Reques t ), 所述配置请求消息中携带所述用户 设备标识, 业务签约数据库或者群组签约数据库根据所述用户设备标识获取 用户设备的群组标识或者设备属性信息中的至少一项, 并在配置响应消息 ( Prof i le Response ) 中返回给策略与计费控制功能实体。  2. For the dynamic PCC application, obtaining at least one of the group identifier or the device attribute information of the user equipment includes: one way, the policy and charging rule function entity acquires the service gateway, the packet data network gateway, or the gateway GPRS support node. At least one of a group identifier or device attribute information carried in an IP CAN session message (eg, an Indicating IP CAN Ses s ion Es tab): another manner is based on the identifier of the user equipment Obtaining at least one of a group identity or device attribute information of the user equipment from the service subscription database or the group subscription database, that is, the policy and charging control function entity sends the configuration to the service subscription database (SPR) or the group subscription database. a request message (eg, Prof. Le Reques), where the configuration request message carries the user equipment identifier, and the service subscription database or the group subscription database acquires the group identifier or device attribute information of the user equipment according to the user equipment identifier. At least one of them, and in the configuration response message ( Prof i le Resp Returned to the policy and accounting control function entity in onse).
根据用户设备的群组标识或者设备属性信息中的至少一项生成群组策略 与计费规则或者触发事件包括: 策略与计费规则功能实体根据获取的用户设 备的群组标识或者设备属性信息中的至少一项生成策略与计费规则或者触发 事件, 并在所述策略与计费规则或触发事件中指示其应用范围为用户设备所 属的群组或用户组。 具体可以包括:  Generating a group policy and a charging rule or a triggering event according to at least one of a group identifier or a device attribute information of the user equipment, where: the policy and charging rule function entity is configured according to the obtained group identifier or device attribute information of the user equipment. At least one of the following generates a policy and a charging rule or a triggering event, and indicates in the policy and charging rule or the triggering event that the application scope is a group or a user group to which the user equipment belongs. Specifically, it may include:
a )策略与计费规则功能实体生成策略与计费规则或者触发事件的方法可 以如下所述, 一种方法是, 策略与计费规则功能实体根据获得的用户设备的 群组标识和设备属性信息至少一项, 如低移动性, 时延不敏感, 制定相应的a) The policy and charging rule function entity generates a policy and charging rule or a method for triggering an event, which may be as follows. One method is: the policy and charging rule function entity is based on the obtained user equipment. At least one of group ID and device attribute information, such as low mobility, delay is not sensitive, and corresponding
PCC规则或者触发事件。 另外一种方法是, 策略与计费规则功能实体根据所述 用户设备的群组标识和设备属性信息至少一项, 根据其上预配置的 PCC规则 或者触发事件, 制定与所述用户设备的群组标识或设备属性信息对应的 PCC 规则或者触发事件。 PCC rules or trigger events. In another method, the policy and charging rule function entity formulates a group with the user equipment according to at least one of a group identifier and a device attribute information of the user equipment according to a pre-configured PCC rule or a trigger event. The PCC rule or trigger event corresponding to the group ID or device attribute information.
另外: 生成策略与计费规则或者触发事件的过程中包括: 根据所述用户 设备的群组标识为所述用户设备分配或者向 DHCP请求为所述用户设备分配群 组或用户设备组粒度的 IP地址。 上述步骤可具体为: 根据所述用户设备的群 组标识分配或向 DHCP请求为所述用户设备所属的群组或用户组下的用户设备 分配群组或者用户组粒度的 IPv6地址前缀; 或者根据所述用户设备的群组标 识分配或向 DHCP请求为所述用户设备所属的群组或用户组下的用户设备分配 一个公共的 IPv4地址。  In addition, the process of generating the policy and the charging rule or the triggering event includes: assigning, to the DHCP device, the IP address of the group or user equipment group for the user equipment according to the group identifier of the user equipment. address. The foregoing steps may be specifically: assigning an IPv6 address prefix of a group or a user group granularity according to the group identifier of the user equipment or the DHCP request to the user equipment of the group or the user group to which the user equipment belongs; or according to The group identity assignment of the user equipment or the DHCP request to the user equipment under the group or user group to which the user equipment belongs is assigned a common IPv4 address.
b )指示所述策略与计费规则或者触发事件的应用范围为所述用户设备所 述的群组或者用户组具体方法可以是: 在生成的 PCC规则或者触发事件中, 增加指示 PCC规则或者触发事件应用范围的信元, 如, App ly Scope , 当设置 App ly Scope为群组范围时, 则生成的 PCC规则或者触发事件应用于所述用户 设备所述的群组或用户组。 另外一种方法是, 生成的 PCC规则或者触发事件 中包含用户设备所述的群组或者用户组的标识, 则服务网关、 分组数据网络 网关或网关 GPRS支持节点根据群组或者用户组的标识将 PCC规则或者触发事 件应用于所述用户设备所述的群组或用户组。  b) indicating that the application of the policy and the charging rule or the triggering event is the group or the user group of the user equipment, the specific method may be: adding a PCC rule or triggering in the generated PCC rule or the triggering event The cell of the event application scope, for example, App ly Scope, when the App ly Scope is set to the group scope, the generated PCC rule or trigger event is applied to the group or user group described by the user equipment. In another method, the generated PCC rule or the trigger event includes the identifier of the group or the user group described by the user equipment, and the service gateway, the packet data network gateway, or the gateway GPRS support node according to the identifier of the group or the user group. A PCC rule or triggering event is applied to the group or group of users described by the user equipment.
本发明的另一个实施例还可以包括: 根据用户设备的群组标识执行策略 与计费规则的优化处理的步骤。 由于策略与计费规则或者触发事件的应用范 围为所述用户设备所属的群组或者用户组, 对后续该用户设备所属的群组或 者用户组下的其他用户也应用该策略与计费规则或者触发事件。 当另一个新 的用户设备请求接入时(如, 发起附着流程或者 P匪连接建立流程), 新的用 户设备的群组标识或者设备属性信息中至少一项与步骤 101 中的用户设备相 同时, 上述步骤可具体为新的用户设备分配已生成的所述步骤 101 中的用户 设备所属群组的策略与计费规则或者触发事件(即步骤 102 中的策略与计费 规则或者触发事件)。 具体方法可以参考第一具体实施例的步骤 203中关于第 二用户设备发起 P匪连接建立流程, PGW, SGW或 GGSN执行 PCC优化的方法描 述。 Another embodiment of the present invention may further include: performing the step of optimizing the policy and charging rules according to the group identifier of the user equipment. The policy and charging rule or the application scope of the triggering event is the group or user group to which the user equipment belongs, and the policy and charging rule are also applied to the group to which the user equipment belongs or other users in the user group. trigger event. When another new user equipment requests access (for example, an attach procedure or a P匪 connection establishment procedure), at least one of the group identifier or the device attribute information of the new user equipment is compared with the user equipment in step 101. In addition, the foregoing step may specifically allocate, to the new user equipment, the generated policy and charging rule or the triggering event of the group to which the user equipment belongs in the step 101 (ie, the policy and charging rule or the triggering event in step 102). . For a specific method, refer to the method description in step 203 of the first embodiment for the second user equipment to initiate a P匪 connection establishment procedure, and the PGW, SGW or GGSN performs PCC optimization.
本发明的另一个实施例还可以包括: 根据所述用户设备的群组标识终止 为所述用户设备所属群组生成的群组的策略与计费规则或者触发事件。 当群 组下的某个用户设备发起去连接的流程时(如, 发起分离流程或者 P匪去连 接流程), 分组数据网络网关或者 GPRS 支持节点或者策略与计费控制功能实 体根据所述用户设备群组标识确定是否存在所述群组下的其他的用户设备保 持连接, 如果存在则保留为所述用户设备所属群组生成的群组的策略与计费 规则或者触发事件, 否则, 则终止为所述用户设备所属群组生成的群组的策 略与计费规则或者触发事件。 具体方法可以参考第一具体实施例的步骤 203 中关于用户设备发起 P匪去连接建立流程时, PGW、 SGW或 GGSN进行处理步骤 描述。  Another embodiment of the present invention may further include: terminating a policy and a charging rule or a triggering event of a group generated for the group to which the user equipment belongs according to the group identifier of the user equipment. When a user equipment under the group initiates a process of de-connecting (eg, initiating a separation process or a P-to-connection process), a packet data network gateway or a GPRS support node or a policy and charging control function entity according to the user equipment The group identifier determines whether there are other user equipments in the group that remain connected, and if yes, retains the policy and charging rules or trigger events of the group generated by the group to which the user equipment belongs, otherwise, the termination is The policy and charging rule or trigger event of the group generated by the group to which the user equipment belongs. For a specific method, reference may be made to the PGW, the SGW, or the GGSN for processing step description when the user equipment initiates a P-to-connection establishment procedure in step 203 of the first embodiment.
本发明的另一个实施例还可以包括: 上述为所述用户设备分配已生成的 所述用户设备所属群组的策略与计费规则或者触发事件可以具体为根据用户 设备发起的 P匪连接对应的 APN信息为所述用户设备分配已生成的所述用户 设备所属群组的策略与计费规则或者触发事件。 具体方法可以参考第一具体 实施例的步骤 203中关于第二用户设备发起 PDN连接建立流程, PGW, SGW或 GGSN执行 PCC优化的方法描述。  Another embodiment of the present invention may further include: the policy and the charging rule or the triggering event for allocating the generated group of the user equipment to the user equipment, which may be specifically corresponding to the P匪 connection initiated by the user equipment. The APN information allocates the generated policy and charging rule or triggering event of the group to which the user equipment belongs to the user equipment. For a specific method, refer to the method description in step 203 of the first embodiment for the second user equipment to initiate a PDN connection establishment procedure, and the PGW, SGW or GGSN performs PCC optimization.
本发明的另一个实施例还可以包括: 上述根据用户设备的群组标识终止 为所述用户设备所属群组生成的群组的策略与计费规则或者触发事件可以具 体为根据用户设备发起的 P匪连接对应的 APN信息终止为所述用户设备所属 群组生成的群组的策略与计费规则或者触发事件。具体方法可以参考第一具体 实施例的步骤 203中关于用户设备发起 PDN去连接建立流程时, PGW、 SGW或 GGSN进行处理步骤描述。 Another embodiment of the present invention may further include: the policy and the charging rule or the triggering event of the group that is generated according to the group identifier of the user equipment that is to be generated by the group to which the user equipment belongs may be specifically the P initiated according to the user equipment. The APN information corresponding to the connection is terminated as a policy and charging rule or a trigger event of the group generated by the group to which the user equipment belongs. For a specific method, refer to the step 203 of the first embodiment, when the user equipment initiates a PDN de-connection establishment process, the PGW, the SGW, or The GGSN performs a description of the processing steps.
图 1 为本发明群组策略与计费规则处理方法第一具体实施例的流程示意 图, 如图 2所示, 包括如下步骤:  FIG. 1 is a schematic flowchart of a first embodiment of a method for processing a group policy and a charging rule according to the present invention. As shown in FIG. 2, the method includes the following steps:
步骤 201、 获取用户设备的群组标识或者设备属性信息中的至少一项。 PGW或 SGW或 GGSN或 PCRF获知用户设备的群组标识可以如下实现: 固 E或者 SGSN在消息中 (如, MME向 S-GW发送的 Create Session Request或者 SGSN 向 GGSN发送的 Create PDP Context Request消息等)携带群组标识, 可选 的, MME或者 SGSN在所述消息中携带用户设备的设备属性信息( MTC Feature )0 固 E或者 SGSN获知用户设备的标识或者设备属性信息的方法包括, 用户设备 在接入请求消息 (如, Attach Request或者 TAU Request或者 PDN Connectivity Establishment Request 或者 Active PDP Context Request ) 中携带用户设 备的群组标识或者设备属性信息。 或者, HSS或者 Group签约数据库向 MME或 者 SGSN提供所述用户设备的群组标识或者设备属性信息, 如在接收到固 E发 送的 Update Location Request 消息后, 根据消息中携带的用户设备的标识 在向 MME返回的 Update Location Ack消息中携带所述用户设备的群组标识 或者设备属性信息。 Step 201: Acquire at least one of a group identifier of the user equipment or device attribute information. The PGW or the SGW or the GGSN or the PCRF can learn that the group identifier of the user equipment can be implemented as follows: The solid E or the SGSN is in the message (for example, the Create Session Request sent by the MME to the S-GW or the Create PDP Context Request message sent by the SGSN to the GGSN, etc.) method) carries the group identifier, an alternative, the MME or the SGSN carrying device attribute information (MTC Feature) user equipment in the message or the SGSN E 0 fixed known user identification device or device attribute information comprises a user equipment The access request message (for example, the Attach Request or the TAU Request or the PDN Connectivity Establishment Request or the Active PDP Context Request) carries the group identifier or device attribute information of the user equipment. Or, the HSS or the group subscription database provides the MME or the SGSN with the group identifier or the device attribute information of the user equipment, for example, after receiving the Update Location Request message sent by the solid E, according to the identifier of the user equipment carried in the message. The Update Location Ack message returned by the MME carries the group identifier or device attribute information of the user equipment.
或者动态 PCC应用时, PCRF获得用户设备的群组标识或者设备属性信息 (Machine Feature ) 中至少一项的具体方法包括, PCRF向 SPR发送配置信息 请求消息 ( Profile Request ), 该消息中携带有用户设备的标识, SPR返回配 置信息响应消息 (Profile Response), 才艮据消息中携带的用户设备的标识, 所述配置信息响应消息中携带用户设备的群组标识信息或者设备属性信息 (MTC Feature) 中至少一项。 PCRF获得用户设备的群组标识和用户设备的设 备属性信息至少一项后, PCRF另外还可以向 PGW或 SGW提供用户设备的群组 标识或者所述用户设备的设备属性信息 (如在 Acknowledge IP CAN Session Establishment或者 Acknowledge IP CAN Session Modification或者 Pol icy and Charging Rules Provision等消息中携带)。 PCRF获得用户设备的群组 标识和用户设备的设备属性信息至少一项的另一种方法可以是 PCRF收到 PGW 或者 GGSN或者 SGW发送的 IP CAN会话消息(如, Ind i ca t ion of IP CAN Se s s ion Es tab l i shment ), 所述 IP CAN会话消息中携带用户设备的群组标识或者所述 用户设备的设备属性信息。 Or, in the case of the dynamic PCC application, the PCRF obtains a configuration information request message (Profile Request) to the SPR, where the PCRF obtains a group identifier or a device attribute information (Machine Feature) of the user equipment, where the message carries the user The identifier of the device, the SPR returns a configuration information response message (Profile Response), and the identifier of the user equipment carried in the message is sent, and the configuration information response message carries the group identification information or device attribute information of the user equipment (MTC Feature). At least one of them. After the PCRF obtains at least one of the group identifier of the user equipment and the device attribute information of the user equipment, the PCRF may further provide the group identifier of the user equipment or the device attribute information of the user equipment to the PGW or the SGW (eg, in Acknowledge IP CAN). Session Establishment or Acknowledge IP CAN Session Modification or carried in messages such as Pol icy and Charging Rules Provision). PCRF obtains a group of user equipments Another method for identifying at least one of the device attribute information of the user equipment may be that the PCRF receives an IP CAN session message sent by the PGW or the GGSN or the SGW (eg, Ind i i t t t t t s s s s s s s s The IP CAN session message carries the group identifier of the user equipment or the device attribute information of the user equipment.
也可以在 PGW、 SGW或 GGSN上配置所述用户设备的标识 (如所述用户设备 的 IMS I、 所述用户设备的 IMEI或者是所述用户设备的 IMS I和 IME I )和所述 用户设备所属的群组标识之间的对应关系, 或者所述用户设备的标识和所述 用户设备对应的设备属性信息之间的对应关系。 PGW、 SGW或 GGSN获得用户设 备的标识, 根据其上的配置信息, 得到所述用户设备所属的群组或者用户组 的标识, 或者得到所述用户设备对应的设备属性信息。  The identifier of the user equipment (such as the IMS I of the user equipment, the IMEI of the user equipment or the IMS I and IME I of the user equipment) and the user equipment may also be configured on the PGW, the SGW or the GGSN. Correspondence between the group identifiers to which the group identifiers belong, or the correspondence between the identifiers of the user equipments and the device attribute information corresponding to the user equipments. The PGW, the SGW, or the GGSN obtains the identifier of the user equipment, and obtains the identifier of the group or the user group to which the user equipment belongs according to the configuration information, or obtains the device attribute information corresponding to the user equipment.
步骤 202、 生成群组共享的 PCC规则或触发事件(Event Tr i gger ), 具体 包括如下的方法:  Step 202: Generate a PCC rule or a trigger event (Event Tr i gger ) shared by the group, and specifically include the following methods:
( 1 ), 当静态 PCC应用时, PGW或者、 SGW或者 GGSN根据步骤 201中的 描述获得所述用户设备的群组标识和用户设备的设备属性信息的至少一项。 PGW或者 SGW或者 GGSN根据所述用户设备的群组标识或者设备属性信息中的 至少一项制定 PCC规则或者触发事件。 如, 上述远程抄表的 M2M应用, PGW或 者 SGW或者 GGSN根据获得的用户设备的设备属性信息, 如低移动性, 时延不 敏感, 根据其上静态配置的 PCC规则或者触发事件, 制定相应的 PCC规则或 者触发事件。 PGW或者 SGW或者 GGSN根据所述用户设备的群组标识或者设备 属性信息中的至少一项制定 PCC规则或者触发事件的另外一种方法是 PGW或 者 SGW或则 GGSN根据所述用户设备的群组标识, 根据其上静态配置的 PCC规 则或者触发事件, 制定与所述用户设备的群组标识对应的 PCC规则或者触发 事件。 PGW或者 SGW或者 GGSN指示为所述用户设备制定的 PCC规则或者触发 事件的应用范围是所述用户设备所属的群组或者用户组。 具体方法可以是在 生成的 PCC规则或者触发事件中, 增加指示 PCC规则或者触发事件应用范围 的信元, 如, App ly Scope , 当设置 App ly Scope为群组范围时, 则生成的 PCC 规则或者触发事件应用于所述用户设备所述的群组或用户组。 另外一种方法 是, 生成的 PCC规则或者触发事件中包含用户设备所述的群组或者用户组的 标识, 则服务网关、 分组数据网络网关或网关 GPRS支持节点根据群组或者用 户组的标识将 PCC规则或者触发事件应用于所述用户设备所述的群组或用户 组。 (1), when the static PCC is applied, the PGW or the SGW or the GGSN obtains at least one of the group identifier of the user equipment and the device attribute information of the user equipment according to the description in step 201. The PGW or the SGW or the GGSN formulates a PCC rule or a trigger event according to at least one of a group identity or device attribute information of the user equipment. For example, the M2M application of the remote meter reading, the PGW or the SGW or the GGSN, according to the obtained device attribute information of the user equipment, such as low mobility, delay insensitive, according to the statically configured PCC rules or trigger events, formulate corresponding PCC rules or trigger events. Another method for the PGW or the SGW or the GGSN to formulate a PCC rule or a trigger event according to at least one of the group identifier or the device attribute information of the user equipment is a PGW or an SGW or a GGSN according to the group identifier of the user equipment. And formulating a PCC rule or a trigger event corresponding to the group identifier of the user equipment according to the statically configured PCC rule or the trigger event. The PGW or the SGW or the GGSN indicates that the application scope of the PCC rule or the trigger event that is set for the user equipment is a group or a user group to which the user equipment belongs. The specific method may be: adding, in the generated PCC rule or the trigger event, a cell indicating a PCC rule or a trigger application range, for example, App ly Scope, when the Apply Scope is set to a group range, the generated PCC A rule or triggering event is applied to the group or group of users described by the user equipment. In another method, the generated PCC rule or the trigger event includes the identifier of the group or the user group described by the user equipment, and the service gateway, the packet data network gateway, or the gateway GPRS support node according to the identifier of the group or the user group. A PCC rule or triggering event is applied to the group or group of users described by the user equipment.
( 2 )、 当动态 PCC规则应用时, PGW、 SGW或 GGSN根据步骤 201中的描述获得 所述用户设备的群组标识, 另外也可以是获得所述用户设备的设备属性信息。 PGW、 SGW或 GGSN向 PCRF发送 IP CAN会话建立指示消息, 该消息中可以携 带所述用户设备的群组标识或者所述用户设备的设备属性信息。 PCRF在获得 上述的用户设备的群组标识后, 可在向 SPR发送配置信息请求消息(Prof i l e Reques t ) 中携带所述用户设备的群组标识。 另外 PCRF还可以通过接收 SPR 返回的配置信息响应消息 (Prof i le Re s ponse ) 的方式获取上述的群组标识 或者设备属性信息, 即在上述的配置信息响应消息携带用户设备的群组标识 或者设备属性信息。 PCRF根据所述用户设备所属的群组标识或者设备属性信 息或者所述用户设备的业务签约数据中的至少一项制定 PCC规则或者触发事 件。如上述远程抄表的 M2M应用, PCRF根据获得的用户设备的设备属性信息, 如低移动性, 时延不敏感, 制定相应的 PCC规则或者触发事件。 PCRF根据所 述用户设备所属的群组标识或者设备属性信息或者所述用户设备的业务签约 数据中的至少一项制定 PCC规则或者触发事件另一种方法是 PCRF根据所述用 户设备的群组标识和设备属性信息至少一项, 根据其上预配置的 PCC规则或 者触发事件, 制定与所述用户设备的群组标识或设备属性信息对应的 PCC规 则或者触发事件。 PCRF可以在为所述用户设备制定的 PCC规则中指示所述 PCC 规则应用范围为用户设备所属的群组或用户组, 或者在所述 PCC规则中携带 所述用户设备所属的群组的群组标识, PGW、 SGW或 GGSN根据所述 PCC规则中 的应用范围指示或者所述 PCC规则中携带所述用户设备所属的群组的群组标 识将获得的 PCC规则应用于所述用户设备所属的群组或者用户组。当动态 PCC 规则应用时, 所述 PCRF 在所述 PCC 规则中可以不提供服务数据流模版 ( Service Da te Flow Templa te ), 即 PCRF根据所述用户设备的群组标识或 者设备属性信息中的至少一项制定应用范围为群组或者用户设备组的 PCC策 略, 从而不在所述 PCC规则中提供服务数据流模版。 或者 PCRF根据所述用户 设备的群组标识或者设备属性信息中的至少一项制定应用范围为群组或者用 户设备组的 PCC策略, 但是 PCRF还在所述 PCC规则中提供服务数据流模版。 动态 PCC规则应用时, PCRF在 PCC规则中生成的服务数据流模版的方法包括: a)、 当用户设备发起 P匪连接建立流程(如, At tach流程或者 PDN连接建立 流程), PGW 为上述用户设备分配或者 PGW 向 DHCP ( Dynamic Hos t Conf igura t ion Protoco l )请求为上述用户设备分配 IPv4地址或者 IPv6地 址。 PGW获知所述用户设备的群组标识, PGW根据所述用户设备的群组标识为 所述用户设备分配或者向 DHCP请求为所述用户设备分配群组或者用户组粒度 的 IP地址, 具体方法包括: PGW根据所述用户设备的群组标识分配或向 DHCP 请求为所述用户设备所属的群组或用户组下的用户设备分配群组或者用户组 粒度的 IPv6地址前缀(一个完整的 IPv6地址由两部分组成, 分别是 IPv6地 址前缀和 IPv6接口标识)。 所述 IPv6地址前缀是群组或者用户组粒度的, 即 当与所述用户设备(第一用户设备)属于同一个群组的第二用户设备针对相 同 APN发起 PDN连接建立流程, PGW为第二用户设备分配 IPv6地址前缀与 PGW 获得的为所述用户设备(第一用户设备)分配的 IPv6地址前缀相同(即, PGW 使用为第一用户设备分配的 IPv6 地址前缀作为 PGW为第二用户设备分配的 IPv6地址前缀)。 或者 PGW根据所述用户设备的群组标识分配或向 DHCP请求 为所述用户设备所属的群组或用户组下的用户设备分配一个公共的 IPv4 地 址。 所述公共 IPv4地址是群组或者用户组粒度的。 (2) When the dynamic PCC rule is applied, the PGW, the SGW, or the GGSN obtains the group identifier of the user equipment according to the description in step 201, and may also obtain the device attribute information of the user equipment. The PGW, the SGW, or the GGSN sends an IP CAN session establishment indication message to the PCRF, where the message may carry the group identifier of the user equipment or device attribute information of the user equipment. After obtaining the group identifier of the user equipment, the PCRF may carry the group identifier of the user equipment in a configuration information request message (Prof ile Reques t ) sent to the SPR. In addition, the PCRF may also obtain the foregoing group identifier or device attribute information by receiving a configuration information response message (Profed Response) returned by the SPR, that is, the configuration information response message carries the group identifier of the user equipment or Device attribute information. The PCRF formulates a PCC rule or a trigger event according to at least one of a group identifier or device attribute information to which the user equipment belongs or service subscription data of the user equipment. For the M2M application of the remote meter reading described above, the PCRF formulates corresponding PCC rules or trigger events according to the obtained device attribute information of the user equipment, such as low mobility and delay insensitivity. The PCRF formulates a PCC rule or a trigger event according to at least one of the group identifier or the device attribute information of the user equipment or the service subscription data of the user equipment. Another method is that the PCRF is based on the group identifier of the user equipment. And at least one item of the device attribute information, according to the pre-configured PCC rule or the trigger event, formulating a PCC rule or a trigger event corresponding to the group identifier or the device attribute information of the user equipment. The PCRF may indicate, in the PCC rule that is set up for the user equipment, that the PCC rule applies to a group or a user group to which the user equipment belongs, or carries a group of the group to which the user equipment belongs in the PCC rule. The PCC rule obtained by the PGW, the SGW, or the GGSN according to the application scope indication in the PCC rule or the group identifier of the group to which the user equipment belongs in the PCC rule is applied to the group to which the user equipment belongs. Group or user group. When dynamic PCC When the rule is applied, the PCRF may not provide a service data flow template (Service Da te Flow Templa te) in the PCC rule, that is, the PCRF is determined according to at least one of a group identifier or a device attribute information of the user equipment. The application scope is a PCC policy of a group or a user equipment group, so that the service data flow template is not provided in the PCC rule. Or the PCRF formulates a PCC policy whose application scope is a group or a user equipment group according to at least one of a group identifier or a device attribute information of the user equipment, but the PCRF further provides a service data flow template in the PCC rule. When the dynamic PCC rule is applied, the method for the service data flow template generated by the PCRF in the PCC rule includes: a), when the user equipment initiates a P匪 connection establishment process (for example, an At tach process or a PDN connection establishment process), and the PGW is the above user. The device assignment or the PGW requests the DHCP device to allocate an IPv4 address or an IPv6 address to the user equipment. The PGW learns the group identifier of the user equipment, and the PGW allocates an IP address to the user equipment according to the group identifier of the user equipment or allocates a group or user group granularity to the user equipment according to the DHCP request, and the specific method includes: The PGW allocates an IPv6 address prefix of a group or a user group granularity according to the group identity of the user equipment or the DHCP request to the user equipment of the group or the user group to which the user equipment belongs (a complete IPv6 address is The two components are the IPv6 address prefix and the IPv6 interface identifier. The IPv6 address prefix is a group or user group granularity, that is, when the second user equipment that belongs to the same group as the user equipment (the first user equipment) initiates a PDN connection establishment procedure for the same APN, the PGW is the second. The user equipment allocates an IPv6 address prefix to be the same as the IPv6 address prefix allocated by the PGW for the user equipment (the first user equipment) (ie, the PGW allocates the IPv6 address prefix allocated for the first user equipment as the PGW to the second user equipment. IPv6 address prefix). Or the PGW allocates a public IPv4 address to the user equipment in the group or the user group to which the user equipment belongs according to the group identifier of the user equipment. The public IPv4 address is a group or user group granularity.
b)、 如特征 a )所述, PGW获得的了所述用户设备的 IPv6前缀或者公共 IPv4 地址, PGW向 PCRF发送 IP CAN会话建立指示消息, 所述 IP CAN会话建立指 示消息中包含 PGW获得的所述用户设备的 IPv6前缀或者公共 IPv4地址。 按 照上述描述 PCRF为所述用户设备制定 PCC规则, PCRF根据获知的 IPv6前缀 或者公共 IPv4地址生成服务数据流模版 ( Service Date Flow Template )0 c)、 PCRF向 PGW发送 IP CAN会话建立确认消息, 消息中包含所述 PCC规则, 且所述 PCC规则中包含所述服务数据流模版 ( Service Date Flow Template )0 PGW为每个不同的用户设备生成包过滤器(Packet Fi l ter , 用于匹配 Service Data Flow与承载之间的关系) 的方法包括, 如特征 a )描述当所述用户设备 发起 P匪连接建立流程(如, At tach流程或者 PDN连接建立流程), PGW为所 述用户设备分配或者 PGW向 DHCP ( Dynamic Hos t Conf igurat ion Protocol ) 请求为所述用户设备分配 IPv4地址或者 IPv6地址。 b), as described in feature a), the PGW obtains an IPv6 prefix or a public IPv4 address of the user equipment, and the PGW sends an IP CAN session establishment indication message to the PCRF, where the IP CAN session establishment indication message includes the PGW obtained. The IPv6 prefix or the public IPv4 address of the user equipment. Press As described above for the user equipment to develop PCRF PCC rules, PCRF generates a service data flow template (Service Date Flow Template) 0 c ) according to the known public IPv4 address or IPv6 prefix, PCRF transmits setup confirmation message to the PGW IP CAN session message It contains the PCC rules and the PCC rule contains a service data flow template (service Date flow template) 0 PGW for each different user equipment generates a packet filter (packet Fi l ter, for matching service data The method of the relationship between the flow and the bearer includes, for example, the feature a) describing when the user equipment initiates a P匪 connection establishment procedure (eg, an At tach flow or a PDN connection establishment procedure), and the PGW allocates or PGW to the user equipment. Requesting an IPv4 address or an IPv6 address for the user equipment to the DHCP (Dynamic Hos t Conf igurat Protocol).
如果为用户设备分配的是 IPv6地址时, PGW为此群组或者用户组的每个不同 的用户设备分配不同的接口标识( PGW为每个不同的用户设备分配不同的接口 标识的方法具体不做限制, 如, PGW根据用户设备的 IMEI标识或者 IMSI标识 分配不同的接口标识 ) , PGW根据获得的 IPv6地址前缀和为所述用户设备分配 的接口标识生成完整的 IPv6地址, PGW 4艮据所述完整的 IPv6地址生成所述用 户设备的包过滤器(Packet Fi l ter )0 If the user equipment is assigned an IPv6 address, the PGW assigns different interface identifiers to each different user equipment of the group or the user group. The PGW allocates different interface identifiers for each different user equipment. Restricting, for example, the PGW assigns a different interface identifier according to the IMEI identifier or the IMSI identifier of the user equipment, and the PGW generates a complete IPv6 address according to the obtained IPv6 address prefix and the interface identifier assigned to the user equipment, and the PGW 4 full IPv6 address of the user device generates a packet filter (packet Fi l ter) 0
如果为用户设备分配的是 IPv4地址时, PGW为此群组或者用户组的每个不同 的用户设备分配不同的 IPv4 地址(PGW 为每个不同的用户设备分配不同的 IPv4地址的方法具体不做限制, 如 PGW根据所述用户设备的 IMEI标识或者 IMSI标识分配不同的 IPv4地址), PGW根据为每个不同的用户设备分配不同 的 IPv4地址生成所述用户设备的包过滤器(Packet Fi l ter )。 If the user equipment is assigned an IPv4 address, the PGW allocates different IPv4 addresses for each different user equipment of the group or the user group (the PGW assigns different IPv4 addresses to each different user equipment. Restricting, if the PGW allocates different IPv4 addresses according to the IMEI identifier or the IMSI identifier of the user equipment, the PGW generates a packet filter of the user equipment according to assigning different IPv4 addresses to each different user equipment (Packet Fi l ter ).
步骤 203、 根据用户设备的群组标识执行 PCC优化处理, 如 202步骤的描述, PGW或者 SGW或者 GGSN或者 PCRF生成群组或者用户组共享的 PCC规则或者触 发事件。 网络侧根据第二所述用户设备(与第一用户设备属于同一个群组) 的群组标识执行 PCC优化, 具体包括: Step 203: Perform PCC optimization processing according to the group identifier of the user equipment. As described in step 202, the PGW or the SGW or the GGSN or the PCRF generates a PCC rule or a trigger event shared by the group or the user group. The network side performs PCC optimization according to the group identifier of the second user equipment (which belongs to the same group as the first user equipment), and specifically includes:
( 1 )、 第二用户设备发起 PDN连接建立流程 (如 At tach流程或者 PDN连接建 立流程 ), PGW或者 SGW或者 GGSN或者 PCRF为所述第二用户设备生成 PCC规 则或者触发事件, PGW或者 SGW或者 GGSN执行 PCC优化的方法包括, PGW或 者 SGW或者 GGSN根据所述第二用户设备的群组标识, 具体方法包括, 当静态 PCC应用时, PGW或者 SGW或者 GGSN获知第二所述用户设备的群组标识, 如 果所述第二用户设备的群组标识与所述第一其他用户设备的群组标识相同, 则为所述第二用户设备分配已生成的所述第一用户设备所属群组的策略与计 费规则或者触发事件。 可选的, 为第一用户设备生成的 PCC规则或者触发事 件时, 进一步的可以包括根据第一用户设备的群组标识或者设备属性信息中 的至少一个, 以及第一用户设备的在 PDN连接建立请求中携带的 APN信息, 生成 PCC规则或者触发事件。 所述第二用户设备发起的接入请求(例如 P匪 连接请求或者附着请求) 时, PGW或者 SGW或者 GGSN进一步确定所述第二用 户设备发起的 P匪连接对应的 APN信息与第一其他用户设备发起的 PDN连接 对应的 APN信息相同, 则 PGW或者 SGW或者 GGSN为所述第二用户设备生成与 为第一其他用户设备生成的 PCC规则或者触发事件相同的 PCC规则或者触发 事件(即 PGW或者 SGW或者 GGSN使用获知的为所述用户设备所属的群组或者 用户组针对某个 APN生成的 PCC规则或者触发事件)。 当动态 PCC应用时, PGW 或者 SGW或者 GGSN获知第二用户设备的群组标识, 如果所述第二用户设备的 群组标识与所述第一其他用户设备的群组标识相同, 则为所述第二用户设备 分配已生成的所述第一用户设备所属群组的策略与计费规则或者触发事件。 可选的, 为第一用户设备生成的 PCC规则或者触发事件时, 进一步的可以包 括根据第一用户设备的群组标识或者设备属性信息中的至少一个, 以及第一 用户设备的在 P匪连接建立请求中携带的 APN信息, 生成 PCC规则或者触发 事件。 所述第二用户设备发起的接入请求(例如 P匪连接请求或者附着请求) 时, PGW或者 SGW或者 GGSN进一步确定所述第二用户设备发起的 P匪连接对 应的 APN信息与第一其他用户设备发起的 P匪连接对应的 APN信息相同, 则 PGW或者 SGW或者 GGSN为所述第二用户设备生成与获得的为第一其他用户设 备生成的 PCC规则或者触发事件相同的 PCC规则或者触发事件(即 PGW或者 SGW或者 GGSN使用获知的为所述用户设备所属的群组或者用户组针对某个 APN生成的 PCC规则或者触发事件), 而不向 PCRF发送 IP CAN会话建立指示 消息。 (1) The second user equipment initiates a PDN connection establishment process (such as an At tach process or a PDN connection establishment process), and the PGW or the SGW or the GGSN or the PCRF generates a PCC rule for the second user equipment. The method of performing the PCC optimization by the PGW or the SGW or the GGSN includes: the PGW or the SGW or the GGSN according to the group identifier of the second user equipment, and the specific method includes: when the static PCC is applied, the PGW or the SGW or the GGSN learns a group identifier of the second user equipment, if the group identifier of the second user equipment is the same as the group identifier of the first other user equipment, the second user equipment is allocated the generated The policy and charging rules or triggering events of the group to which the first user equipment belongs. Optionally, when the PCC rule or the triggering event is generated for the first user equipment, the method may further include: configuring at least one of the group identity or the device attribute information of the first user equipment, and establishing the PDN connection of the first user equipment The APN information carried in the request generates a PCC rule or a trigger event. When the second user equipment initiates an access request (for example, a P匪 connection request or an attach request), the PGW or the SGW or the GGSN further determines the APN information corresponding to the P匪 connection initiated by the second user equipment, and the first other user. If the APN information corresponding to the device-initiated PDN connection is the same, the PGW or the SGW or the GGSN generates the same PCC rule or trigger event (ie, PGW or the same as the PCC rule or the trigger event generated for the first other user equipment. The SGW or the GGSN uses the learned PCC rules or trigger events generated for a certain APN by the group or group of users to which the user equipment belongs. When the dynamic PCC is applied, the PGW or the SGW or the GGSN learns the group identifier of the second user equipment, and if the group identifier of the second user equipment is the same as the group identifier of the first other user equipment, The second user equipment allocates the generated policy and charging rule or trigger event of the group to which the first user equipment belongs. Optionally, when the PCC rule or the triggering event is generated for the first user equipment, the method may further include: at least one of the group identifier or the device attribute information of the first user equipment, and the P匪 connection of the first user equipment The APN information carried in the request is established, and a PCC rule or a trigger event is generated. When the second user equipment initiates an access request (for example, a P匪 connection request or an attach request), the PGW or the SGW or the GGSN further determines the APN information corresponding to the P匪 connection initiated by the second user equipment, and the first other user. If the APN information corresponding to the device-initiated P-connection is the same, the PGW or the SGW or the GGSN generates, for the second user equipment, a PCC rule or a trigger event that is the same as the obtained PCC rule or trigger event generated by the first other user equipment. PGW or The SGW or the GGSN does not use the learned PCC rule or trigger event generated for the APN by the group or group of users to which the user equipment belongs, and does not send an IP CAN session establishment indication message to the PCRF.
( 2 )、 所述用户设备发起 PDN去连接流程(如, De tach流程或 PDN去连接流 程), PGW或者 SGW或者 GGSN收到删除 PDN连接请求的消息(如, De 1 e t e Se s s i on Reques t或者 De l e te PDP Context Reques t消息 ), PGW或者 SGW或者 GGSN 确定是否存在其他用户设备对应的群组标识与所述用户设备的群组标识相 同, PGW还可以进一步根据是否存在其他用户设备对应的群组标识和其他用户 设备所建立的 P匪连接对应的 APN信息与所述用户设备的群组标识和所述用 户设备所删除的 PDN连接对应的 APN信息相同, 如果存在, 则 PGW或者 SGW 或者 GGSN不会删除所述 PCC规则或者触发事件,或者 PGW或者 SGW或者 GGSN 不向 PCRF发送 IP CAN会话终止指示消息。 如果不存在, 则 PGW或者 SGW或 者 GGSN将删除所述 PCC规则或者触发事件, 或者 PGW或者 SGW或者 GGSN向 PCRF发送 IP CAN会话终止指示消息。  (2) The user equipment initiates a PDN de-connection process (eg, a Detach process or a PDN de-connection process), and the PGW or the SGW or the GGSN receives a message for deleting a PDN connection request (eg, De 1 ete Se ssi on Reques t Or the PGW or the SGW or the GGSN determines whether the group identifier corresponding to the other user equipment is the same as the group identifier of the user equipment, and the PGW may further determine whether there is another user equipment corresponding to the The APN information corresponding to the P匪 connection established by the group identifier and the other user equipment is the same as the APN information corresponding to the group identifier of the user equipment and the PDN connection deleted by the user equipment. If yes, the PGW or SGW or The GGSN does not delete the PCC rule or trigger event, or the PGW or SGW or GGSN does not send an IP CAN Session Termination Indication message to the PCRF. If not, the PGW or SGW or GGSN will delete the PCC rule or trigger event, or the PGW or SGW or GGSN sends an IP CAN Session Termination Indication message to the PCRF.
( 3 )、 当动态 PCC应用时, PCRF针对某个群组或者用户组发起 IP CAN会话终 止流程, PCRF向 PGW发送 IP CAN会话终止指示消息, 消息中携带群组标识, 可选的, PCRF需要终止的 P匪标识, 如 APN信息。  (3) When the dynamic PCC is applied, the PCRF initiates an IP CAN session termination procedure for a group or a user group, and the PCRF sends an IP CAN session termination indication message to the PGW, where the message carries the group identifier, optionally, the PCRF needs The terminated P匪 identifier, such as the APN information.
根据步骤 202和 203的描述,网络侧生成群组共享的 PCC规则或触发事件, 且网络侧根据所述用户设备的群组标识执行 PCC优化, 此方案既解决解决了 网络策略控制效率低下、 策略维护和管理复杂等问题, 也减少了 GW与 PCRF 之间的信令交互, 达到了信令优化的效果。  According to the description of steps 202 and 203, the network side generates a PCC rule or a trigger event shared by the group, and the network side performs PCC optimization according to the group identifier of the user equipment, which solves the problem of inefficient network policy control and the strategy. Maintenance and management of complex issues, etc., also reduces the signaling interaction between GW and PCRF, achieving the effect of signaling optimization.
图 3 为本发明群组策略与计费规则处理方法第二具体实施例的流程示意 图, 本实施例是在附着请求 (At tach ) 流程中实现对群组策略与计费规则的 处理, 根据用户设备的群组标识或者设备属性信息中的至少一项获取 PCC规 则或者触发事件。 如图 3所示, 包括如下步骤:  3 is a schematic flowchart of a second embodiment of a method for processing a group policy and a charging rule according to the present invention. In this embodiment, a group policy and a charging rule are processed in an attach request (At tach) process, according to a user. At least one of the group identifier or the device attribute information of the device acquires a PCC rule or a trigger event. As shown in Figure 3, the following steps are included:
步骤 301 、 M2ME向固 E发送附着请求消息。 M2ME在附着请求消息中携带 M2ME身份标识信息,可选的, M2ME可以在附着请求消息中携带群组计费标识。 可选的, M2ME可以在附着请求消息中携带其设备属性信息 (MTC Fea ture ); 步骤 302、 执行鉴权与认证的流程; Step 301: The M2ME sends an attach request message to the solid E. M2ME carries in the attach request message The M2ME identity information is optional. The M2ME may carry the group charging identifier in the attach request message. Optionally, the M2ME may carry its device attribute information (MTC Feature) in the attach request message; Step 302: perform a process of authentication and authentication;
步骤 303、 固 E向 HSS或者 Group签约数据库发送更新位置区请求消息。 如果固 E在附着请求消息中获得了群组标识, 则固 E在所述更新位置区请求 消息中携带所述群组标识;  Step 303: The solid E sends an update location area request message to the HSS or the group subscription database. If the E is obtained in the attach request message, the E is carried in the update location area request message;
步骤 304、 HSS或者 Group签约数据库返回更新位置区确认消息。 HSS在 所述更新位置区确认消息中返回签约数据信息。 可选的, 所述更新位置区确 认消息中包含群组标识信息。 可选的, 所述更新位置区确认消息中包含所述 M2ME的设备属性信息;  Step 304, the HSS or the Group subscription database returns an update location area confirmation message. The HSS returns the subscription data information in the update location area confirmation message. Optionally, the update location area confirmation message includes group identification information. Optionally, the update location area confirmation message includes device attribute information of the M2ME.
步骤 305、 固 E向 SGW发送创建会话请求消息。 如果 MME获得了 M2ME的 群组标识或者设备属性信息, 则可以在所述创建会话请求消息中携带群组标 识信息或者设备属性信息;  Step 305: The solid E sends a create session request message to the SGW. If the MME obtains the group identity or the device attribute information of the M2ME, the MME may carry the group identification information or the device attribute information in the creation session request message.
步骤 306、 SGW向 PGW发送创建会话请求消息。 如果 SGW获得了 M2ME的 群组标识或者设备属性信息, 则可以在所述创建会话请求消息中携带群组标 识信息或者设备属性信息;  Step 306: The SGW sends a create session request message to the PGW. If the SGW obtains the group identity or the device attribute information of the M2ME, the group identification information or the device attribute information may be carried in the creation session request message;
如下的步骤 307到步骤 310为动态 PCC应用时执行的步骤, 在静态 PCC 应用时不执行。  The following steps 307 to 310 are performed for the dynamic PCC application and are not executed during the static PCC application.
步骤 307、 PGW向 PCRF发送 IP CAN会话建立指示消息。 如果 PGW获得了 M2ME的群组标识, 则可以在所述 IP CAN会话建立指示消息中携带所述群组标 识。 可选的, 如果在步骤 306中, PGW获得了所述 M2ME的设备属性信息, PGW 在所述 IP CAN会话建立指示消息中携带所述 M2ME的设备属性信息;  Step 307: The PGW sends an IP CAN session establishment indication message to the PCRF. If the PGW obtains the group identity of the M2ME, the group identity may be carried in the IP CAN session establishment indication message. Optionally, if the PGW obtains the device attribute information of the M2ME in step 306, the PGW carries the device attribute information of the M2ME in the IP CAN session establishment indication message;
步骤 308、 PCRF向 SPR或者 Group签约数据库发送配置信息请求消息。 如果 PCRF获得了 M2ME的群组标识, 则 PCRF在所述配置信息请求消息中携带 所述群组标识;  Step 308: The PCRF sends a configuration information request message to the SPR or the group subscription database. If the PCRF obtains the group identifier of the M2ME, the PCRF carries the group identifier in the configuration information request message;
步骤 309、 SPR或者 Group签约数据库返回配置信息响应消息。 SPR或者 Group签约数据库在配置信息响应消息中返回 M2ME的业务签约数据。可选的, 此消息中包含 M2ME群组标识, 或者 M2ME的设备属性信息; Step 309: The SPR or the group subscription database returns a configuration information response message. SPR or The Group subscription database returns the service subscription data of the M2ME in the configuration information response message. Optionally, the message includes an M2ME group identifier, or device attribute information of the M2ME.
步骤 31 0、 PCRF根据所述用户设备所属的群组标识或者设备属性信息或 者所述用户设备的业务签约数据中的至少一项制定 PCC规则或者触发事件并 向 PGW发送 IP CAN会话建立确认消息。具体方法如第一具体实施例的步骤 202 描述, 如, PCRF在为所述用户设备制定的 PCC规则中指示所述 PCC规则应用 范围为用户设备所属的群组或用户组, 或者在所述 PCC规则中携带所述用户 设备所属的群组的群组标识, PGW根据所述 PCC规则中的应用范围或者所述 PCC规则中携带所述用户设备所属的群组的群组标识将获得的 PCC规则应用于 所述用户设备所属的群组或者用户组。 所述 PCRF在所述 PCC规则中生成的服 务数据流模版 ( Serv i ce Da te F l ow Temp l a te ) 的方法如第一具体实施例的 步骤 202的特征(2 ) 中特征 a )、 b )、 c )描述。 本实施例不再赘述。 可选的, PCRF生成触发事件, 所述触发事件应用于群组或者用户组粒度, 如, 当 PGW 统计此群组或者用户组的用户设备所用数据流量达到某一个阔值, PGW将此事 件上艮给 PCRF;  Step 31: The PCRF formulates a PCC rule or a trigger event according to at least one of the group identifier or the device attribute information of the user equipment or the service subscription data of the user equipment, and sends an IP CAN session establishment confirmation message to the PGW. The specific method is as described in step 202 of the first embodiment. For example, the PCRF indicates, in the PCC rule that is specified for the user equipment, that the PCC rule application range is a group or a user group to which the user equipment belongs, or in the PCC. The rule carries the group identifier of the group to which the user equipment belongs, and the PGW obtains the PCC rule according to the application scope in the PCC rule or the group identifier of the group to which the user equipment belongs in the PCC rule. Applies to the group or user group to which the user equipment belongs. The method of the service data stream template generated by the PCRF in the PCC rule is characterized by a feature a), b in the feature (2) of step 202 of the first embodiment. ), c) description. This embodiment will not be described again. Optionally, the PCRF generates a trigger event, where the trigger event is applied to a group or a user group granularity, for example, when the PGW counts the data traffic used by the user equipment of the group or the user group to reach a certain threshold, the PGW sends the event.艮 give PCRF;
步骤 31 1、 PGW向 SGW发送创建会话响应消息, 消息中包含 PGW获得 PCC 规则或者触发事件。 当静态 PCC应用时, PGW根据所述用户设备的群组标识或 者设备属性信息中的至少一项制定 PCC规则或者触发事件。 具体的方法如第 一具体实施例中的步骤 202特征( 1 ) 的描述, 本实施例不再赘述。 PGW将为 所述用户设备制定的 PCC规则或者触发事件应用于所述用户设备所属的群组 或者用户组;  Step 31: The PGW sends a Create Session Response message to the SGW, where the message includes the PGW to obtain a PCC rule or a trigger event. When the static PCC is applied, the PGW formulates a PCC rule or a trigger event according to at least one of the group identifier or the device attribute information of the user equipment. The specific method is as described in the feature (1) of the step 202 in the first embodiment, and is not described in this embodiment. The PCGW rules or triggering events that are set by the PGW for the user equipment are applied to the group or user group to which the user equipment belongs;
步骤 312、 SGW向固 E发送创建会话响应消息;  Step 312: The SGW sends a session creation response message to the solid E.
步骤 31 3、 固 E向 M2ME发送附着接受消息。  Step 31 3. The solid E sends an attach accept message to the M2ME.
另外在当所述 M2ME发起附着流程, PGW或者 PCRF根据所述 M2ME的群组标识 执行 PCC优化。 具体方法如第一具体实施例中步骤 203的描述: PGW根据所述 M2ME的群组标识, 可选的, 还可以根据所述 M2ME发起的 P匪连接对应的 APN信 息确定是否使用获知的为所述 M2ME所属的群组或者用户组生成的 PCC规则或 者触发事件。 具体的方法如第一具体实施例的步骤 203的特征( 1 )描述, 本 实施例不再赘述。 In addition, when the M2ME initiates an attach procedure, the PGW or the PCRF performs PCC optimization according to the group identifier of the M2ME. The specific method is as described in step 203 in the first embodiment: the PGW is configured according to the group identifier of the M2ME, and optionally, according to the P2 connection initiated by the M2ME, the corresponding APN letter. It is determined whether to use the learned PCC rules or trigger events generated for the group or group of users to which the M2ME belongs. The specific method is described in the feature (1) of the step 203 of the first embodiment, and is not described in this embodiment.
本发明的另一实施例提供所述 M2ME发起 P匪去连接流程 (如 De tach流程或 者 PDN去连接流程), 如第一具体实施例中的步骤 203的特征(2 )描述, PGW收 到删除 PDN连接请求的消息 (De le te Ses s ion Reques t ), 具体可如图 4所示: 步骤 40 PGW收到删除 I P CAN会话请求消息,如 De 1 e t e Se s s i on Reque s t 消息。 PGW确定是否存在其他用户设备对应的群组标识与所述用户设备的群组 标识相同, 可选的, 进一步的, PGW根据是否存在其他用户设备对应的群组标 识和其他用户设备所建立的 P匪连接对应的 APN信息与所述用户设备的群组 标识和所述用户设备所删除的 P匪连接对应的 APN信息相同, 如果存在, 则 PGW不会删除所述 PCC规则或者触发事件, 或者 PGW不向 PCRF发送 IP CAN会 话终止指示消息。 如果不存在, 则 PGW将删除所述 PCC规则或者触发事件, 或者 PGW向 PCRF发送 IP CAN会话终止指示消息;  Another embodiment of the present invention provides the M2ME initiating a P-to-connection process (such as a Detach process or a PDN de-connection process), as described in feature (2) of step 203 in the first embodiment, and the PGW receives the deletion. The PDN connection request message (De le te Ses s ion Reques t ), as shown in FIG. 4: Step 40 The PGW receives the delete IP CAN session request message, such as a De 1 ete Se ssi on Reque st message. The PGW determines whether the group identifier corresponding to the other user equipment is the same as the group identifier of the user equipment, and optionally, the PGW establishes the P identifier corresponding to the other user equipment and the P established by the other user equipment. The APN information corresponding to the 匪 connection is the same as the APN information corresponding to the group identifier of the user equipment and the P 匪 connection deleted by the user equipment. If yes, the PGW does not delete the PCC rule or the trigger event, or the PGW. The IP CAN Session Termination Indication message is not sent to the PCRF. If not, the PGW will delete the PCC rule or trigger event, or the PGW sends an IP CAN session termination indication message to the PCRF;
步骤 402、 如果 PCRF收到终止 IP CAN会话指示消息。 可选的, 消息中携 带所述用户设备所属的群组的群组标识,可选的和所述用户设备所删除的 PDN 连接对应的 APN信息, PCRF根据所述用户设备所属的群组的群组标识, 可选 的, 进一步的, 和所述 APN信息, 确定针对此群组或者用户组, 可选的, 进 一步的, 针对此群组或者用户组和所述 APN信息, 是否存在其他的 PGW服务。 如果存在, 则 PCRF返回确认终止 IP CAN会话消息, 而不向 SPR发送取消签 约数据通知请求。 如果不存在, 则 PCRF返回确认终止 IP CAN会话消息, 且 向 SPR发送取消签约数据通知请求;  Step 402: If the PCRF receives the termination IP CAN session indication message. Optionally, the message carries the group identifier of the group to which the user equipment belongs, and the optional APN information corresponding to the PDN connection deleted by the user equipment, and the PCRF is based on the group of the group to which the user equipment belongs. Group identification, optional, further, and the APN information, determined for the group or user group, optionally, further, for the group or user group and the APN information, whether there is another PGW service. If so, the PCRF returns an acknowledgment to terminate the IP CAN session message without sending a cancel subscription data notification request to the SPR. If not, the PCRF returns an acknowledgment to terminate the IP CAN session message, and sends a cancel subscription data notification request to the SPR;
步骤 403、 PCRF向 PGW发送确认终止 IP CAN会话消息;  Step 403: The PCRF sends an acknowledgement to the PGW to terminate the IP CAN session message.
步骤 404、 PGW发送删除 IP CAN会话响应消息;  Step 404: The PGW sends a delete IP CAN session response message.
步骤 405、 根据步骤 402的描述, PCRF向 SPR发送取消签约数据通知请 求 步骤 406、 如果收到取消签约数据通知请求消息, SPR向 PCRF返回取消 签约数据通知响应; Step 405: According to the description in step 402, the PCRF sends a cancel subscription data notification request to the SPR. Step 406: If the cancel subscription data notification request message is received, the SPR returns a cancellation subscription data notification response to the PCRF.
步骤 407、 PGW向 0CS发送最终阔值上报。 可选的消息中携带所述用户设 备所属的群组的群组标识  Step 407: The PGW sends a final threshold report to the 0CS. The optional message carries the group identifier of the group to which the user equipment belongs.
步骤 408、 0CS返回阔值确认消息。  Steps 408 and 0CS return a threshold confirmation message.
图 5 为本发明群组策略与计费规则处理方法第三具体实施例的流程示意 图, 本实施例是在 PDN连接流程中实现对群组策略与计费规则的处理, 根据 用户设备的群组标识或者设备属性信息中的至少一项获取 PCC规则或者触发 事件。 如图 5所示, 包括如下步骤:  FIG. 5 is a schematic flowchart of a method for processing a group policy and a charging rule according to a third embodiment of the present invention. In this embodiment, a group policy and a charging rule are processed in a PDN connection process, according to a group of user equipments. At least one of the identification or device attribute information acquires a PCC rule or a trigger event. As shown in Figure 5, the following steps are included:
步骤 501、 M2ME向固 E发送 PDN连接建立请求消息。 消息中携带 APN等 信息;  Step 501: The M2ME sends a PDN connection establishment request message to the solid E. The message carries information such as APN;
步骤 502、 固 E向 SGW发送创建会话请求消息。 如果 MME获得了 M2ME的 群组标识或者设备属性信息, 则可以在所述创建会话请求消息中携带群组标 识信息或者设备属性信息;  Step 502: The solid E sends a create session request message to the SGW. If the MME obtains the group identity or the device attribute information of the M2ME, the MME may carry the group identification information or the device attribute information in the creation session request message.
步骤 503、 SGW向 PGW发送创建会话请求消息。 如果 SGW获得了 M2ME的 群组标识或者设备属性信息, 则可以在所述创建会话请求消息中携带群组标 识信息或者设备属性信息;  Step 503: The SGW sends a create session request message to the PGW. If the SGW obtains the group identity or the device attribute information of the M2ME, the group identification information or the device attribute information may be carried in the creation session request message;
如果是静态 PCC应用, 则下述的步骤 504到步骤 507被略过。  If it is a static PCC application, steps 504 through 507 described below are skipped.
步骤 504、 在动态 PCC应用时, PGW向 PCRF发送 IP CAN会话建立指示消 息。 如果 PGW获得了 M2ME的群组标识, 则可以在所述 IP CAN会话建立指示 消息中携带所述群组标识。可选的,如果在步骤 503中, PGW获得了所述 M2ME 的设备属性信息, PGW在所述 IP CAN会话建立指示消息中携带所述 M2ME的设 备属性信息;  Step 504: When the dynamic PCC is applied, the PGW sends an IP CAN session establishment indication message to the PCRF. If the PGW obtains the group identity of the M2ME, the group identity may be carried in the IP CAN session establishment indication message. Optionally, if the PGW obtains the device attribute information of the M2ME in step 503, the PGW carries the device attribute information of the M2ME in the IP CAN session establishment indication message;
步骤 505、 PCRF向 SPR或者 Group签约数据库发送配置信息请求消息。 如果 PCRF获得了 M2ME的群组标识, 则 PCRF在所述配置信息请求消息中携带 所述群组标识; 步骤 506、 SPR或者 Group签约数据库返回配置信息响应消息。 SPR或者 Group签约数据库在配置信息响应消息中返回 M2ME的业务签约数据。可选的, 此消息中包含 M2ME群组标识, 或者 M2ME的设备属性信息; Step 505: The PCRF sends a configuration information request message to the SPR or the group subscription database. If the PCRF obtains the group identifier of the M2ME, the PCRF carries the group identifier in the configuration information request message; Step 506: The SPR or the Group subscription database returns a configuration information response message. The SPR or the group subscription database returns the service subscription data of the M2ME in the configuration information response message. Optionally, the message includes an M2ME group identifier, or device attribute information of the M2ME.
步骤 507、 PCRF根据所述用户设备所属的群组标识或者设备属性信息或 者所述用户设备的业务签约数据中的至少一项制定 PCC规则或者触发事件并 向 PGW发送 IP CAN会话建立确认消息。具体方法可如第一具体实施例步骤 302 描述, 如, PCRF在为所述用户设备制定的 PCC规则中指示所述 PCC规则应用 范围为用户设备所属的群组或用户组, 或者在所述 PCC规则中携带所述用户 设备所属的群组的群组标识, PGW根据所述 PCC规则中的应用范围或者所述 PCC规则中携带所述用户设备所属的群组的群组标识将获得的 PCC规则应用于 所述用户设备所属的群组或者用户组。 所述 PCRF在所述 PCC规则中生成的服 务数据流模版 ( Serv i ce Da te F l ow Temp l a te ) 的方法如第一具体实施例中 步骤 202的特征(2 ) 中特征 a )、 b )、 c )描述。 本实施例不再赘述。 可选的, PCRF生成触发事件, 所述触发事件应用于群组或者用户组粒度, 如, 当 PGW 统计此群组或者用户组的用户设备所用数据流量达到某一个阔值, PGW将此事 件上艮给 PCRF;  Step 507: The PCRF formulates a PCC rule or a trigger event according to at least one of a group identifier or device attribute information of the user equipment or service subscription data of the user equipment, and sends an IP CAN session establishment confirmation message to the PGW. The specific method may be as described in step 302 of the first embodiment. For example, the PCRF indicates, in the PCC rule that is specified for the user equipment, that the PCC rule application range is a group or a user group to which the user equipment belongs, or in the PCC. The rule carries the group identifier of the group to which the user equipment belongs, and the PGW obtains the PCC rule according to the application scope in the PCC rule or the group identifier of the group to which the user equipment belongs in the PCC rule. Applies to the group or user group to which the user equipment belongs. The method of the service data stream template generated by the PCRF in the PCC rule is the feature a), b in the feature (2) of step 202 in the first embodiment. ), c) description. This embodiment will not be described again. Optionally, the PCRF generates a trigger event, where the trigger event is applied to a group or a user group granularity, for example, when the PGW counts the data traffic used by the user equipment of the group or the user group to reach a certain threshold, the PGW sends the event.艮 give PCRF;
步骤 508、 PGW向 SGW发送创建会话响应消息, 消息中包含 PGW获得 PCC 规则或者触发事件。 当静态 PCC应用时, PGW根据所述用户设备的群组标识或 者设备属性信息中的至少一项制定 PCC规则或者触发事件。 具体的方法如第 一具体实施例中的步骤 202特征( 1 ) 的描述, 本实施例不再赘述。 PGW将为 所述用户设备制定的 PCC规则或者触发事件应用于所述用户设备所属的群组 或者用户组;  Step 508: The PGW sends a create session response message to the SGW, where the message includes the PGW to obtain a PCC rule or a trigger event. When the static PCC is applied, the PGW formulates a PCC rule or a trigger event according to at least one of the group identifier or the device attribute information of the user equipment. The specific method is as described in the feature (1) of the step 202 in the first embodiment, and is not described in this embodiment. The PCGW rules or triggering events that are set by the PGW for the user equipment are applied to the group or user group to which the user equipment belongs;
步骤 509、 SGW向固 E发送创建会话响应消息;  Step 509: The SGW sends a session creation response message to the solid E.
步骤 51 0、 固 E向 eNodeB发送 E-RAB建立请求消息, 消息中携带发送给 M2ME的激活缺省承载请求消息;  Step 51: The E sends an E-RAB setup request message to the eNodeB, where the message carries an active default bearer request message sent to the M2ME.
步骤 51 1、 eNodeB向 M2ME发送 RRC连接重配置消息; 步骤 512、 M2ME向 eNodeB返回 RRC连接重配置完成消息; 步骤 51 3、 eNodeB向 MME发送 E-RAB建立响应消息; Step 51: The eNodeB sends an RRC connection reconfiguration message to the M2ME. Step 512: The M2ME returns an RRC connection reconfiguration complete message to the eNodeB. Step 51: The eNodeB sends an E-RAB setup response message to the MME.
步骤 514、 M2ME向 eNodeB发送直接传输消息, 消息中携带激活缺省承载 响应消息;  Step 514: The M2ME sends a direct transmission message to the eNodeB, where the message carries an active default bearer response message.
步骤 515、 eNodeB将激活缺省承载响应消息传递给 MME;  Step 515: The eNodeB delivers an activation default bearer response message to the MME.
步骤 516、 固 E向 SGW发送修改承载请求消息;  Step 516: The solid E sends a modify bearer request message to the SGW.
步骤 517、 SGW向固 E返回修改承载响应消息。  Step 517: The SGW returns a modify bearer response message to the solid E.
本发明实施例还提供了一种群组策略与计费规则处理装置, 图 6 为本发 明群组策略与计费规则处理装置实施例的结构示意图, 如图 6 所示, 包括获 取模块 1 1和规则生成模块 12 , 其中获取模块 1 1用于获取用户设备的群组标 识或者设备属性信息中的至少一项; 规则生成模块 12用于根据所述用户设备 的群组标识或者设备属性信息中的至少一项生成策略与计费规则或者触发事 件。  The embodiment of the present invention further provides a group policy and charging rule processing device. FIG. 6 is a schematic structural diagram of an embodiment of a group policy and charging rule processing device according to the present invention. As shown in FIG. 6, the acquiring module 1 1 is included. And a rule generating module 12, wherein the obtaining module 1 is configured to acquire at least one of a group identifier or a device attribute information of the user equipment; the rule generating module 12 is configured to use the group identifier or the device attribute information of the user equipment. At least one of the generated policy and charging rules or trigger events.
本发明实施例提供的群组策略与计费规则处理装置通过获取用户设备的 群组标识或者设备属性信息, 并根据上述获取的信息生成策略与计费规则或 者触发事件, 能够有效提高群组的用户设备或者具有相同的设备特征的用户 设备的策略控制效率, 并降低策略维护和管理的复杂度。  The group policy and the charging rule processing device provided by the embodiment of the present invention can obtain the group identifier or the device attribute information of the user equipment, and generate a policy and a charging rule or a trigger event according to the obtained information, thereby effectively improving the group. Policy control efficiency of user equipment or user equipment with the same device characteristics reduces the complexity of policy maintenance and management.
在静态 PCC应用时, 上述实施例中的获取模块包括第一获取单元, 第一 获取单元用于获取用户设备在接入请求消息中携带的群组标识或者设备属性 信息中的至少一项; 或用于获取归属用户服务器或群组签约数据库签约的用 户设备的群组标识或者设备属性信息中的至少一项; 或用于获取用户设备的 标识, 根据所述用户设备的标识从预先配置的用户设备信息中获取用户设备 的群组标识或者设备属性信息中的至少一项; 相应的规则生成模块包括第一 规则生成单元, 该第一规则生成单元用于根据获取的用户设备的群组标识或 者设备属性信息中的至少一项生成策略与计费规则或者触发事件, 并指示所 述策略与计费规则或者触发事件的应用范围为用户设备所属的群组或者用户 组。 In the static PCC application, the acquiring module in the foregoing embodiment includes a first acquiring unit, where the first acquiring unit is configured to acquire at least one of a group identifier or device attribute information carried by the user equipment in the access request message; or At least one of a group identifier or a device attribute information of the user equipment for obtaining a home subscriber server or a group subscription database subscription; or an identifier for acquiring the user equipment, from the pre-configured user according to the identifier of the user equipment Obtaining at least one of a group identifier or a device attribute information of the user equipment in the device information; the corresponding rule generating module includes a first rule generating unit, where the first rule generating unit is configured to use the acquired group identifier of the user equipment or At least one of the device attribute information generates a policy and a charging rule or a triggering event, and indicates that the application scope of the policy and the charging rule or the triggering event is a group or a user to which the user equipment belongs. Group.
本实施例中的群组策略与计费规则处理装置可以设置在服务网关、 分组 数据网络网关或者网关 GPRS支持节点中。  The group policy and charging rule processing apparatus in this embodiment may be disposed in a serving gateway, a packet data network gateway, or a gateway GPRS support node.
在动态 PCC应用时, 获取模块包括第二获取单元, 该第二获取单元用于 获取 IP CAN会话消息携带的群组标识或者设备属性信息中的至少一项; 或用 于根据所述用户设备的标识从业务签约数据库或者群组签约数据库中获取用 户设备的群组标识或者设备属性信息中的至少一项。 相应的规则生成模块包 括第二规则生成单元, 该单元用于根据获取的用户设备的群组标识或者设备 属性信息中的至少一项生成策略与计费规则或者触发事件, 并在所述策略与 计费规则或触发事件中指示其应用范围为用户设备所属的群组或用户组。  In the dynamic PCC application, the acquiring module includes a second obtaining unit, where the second obtaining unit is configured to acquire at least one of a group identifier or device attribute information carried in the IP CAN session message, or used according to the user equipment. Identifying at least one of a group identifier or device attribute information of the user equipment obtained from the service subscription database or the group subscription database. The corresponding rule generating module includes a second rule generating unit, configured to generate a policy and a charging rule or a trigger event according to at least one of a group identifier or a device attribute information of the acquired user equipment, and in the policy and In the charging rule or triggering event, the application scope is indicated as the group or user group to which the user equipment belongs.
另外上述的实施例中的装置还可以包括优化处理模块, 该模块用于当第 二用户设备的群组标识或者设备属性信息中至少一项与所述第一用户设备相 同时, 为所述第二用户设备分配已生成的所述第一用户设备所属群组的策略 与计费规则或者触发事件。  In addition, the apparatus in the foregoing embodiment may further include an optimization processing module, where the module is configured to: when at least one of the group identifier or the device attribute information of the second user equipment is the same as the first user equipment, The second user equipment allocates the generated policy and charging rule or trigger event of the group to which the first user equipment belongs.
本发明实施例还提供了一种通信***, 包括上述的群组策略与计费规则 处理装置。 且上述的组策略与计费规则处理装置设置于服务网关、 分组数据 网络网关、 网关 GPRS支持节点或策略与计费规则功能实体。  The embodiment of the invention further provides a communication system, comprising the group policy and charging rule processing device described above. And the group policy and charging rule processing device described above is disposed on the service gateway, the packet data network gateway, the gateway GPRS support node, or the policy and charging rule function entity.
本发明实施例提供的通信***包括群组策略与计费规则处理装置, 通过 获取用户设备的群组标识或者设备属性信息, 并根据上述获取的信息生成群 组策略与计费规则或者触发事件, 能够有效提高群组的用户设备或者具有相 同的设备特征的用户设备的策略控制效率, 并降低策略维护和管理的复杂度。  The communication system provided by the embodiment of the present invention includes a group policy and a charging rule processing device, which acquires a group identity or device attribute information of a user equipment, and generates a group policy and a charging rule or a trigger event according to the obtained information. It can effectively improve the policy control efficiency of the user equipment of the group or the user equipment with the same equipment characteristics, and reduce the complexity of policy maintenance and management.
本发明实施例提供的群组策略与计费规则处理方法、 装置和通信***, 通过获取用户设备的群组标识或者设备属性信息, 并根据上述获取的信息生 成群组策略与计费规则或者触发事件, 能够有效提高群组的用户设备或者具 有相同的设备特征的用户设备的策略控制效率, 并降低策略维护和管理的复 杂度。 并进一步的根据所述用户设备的群组标识执行 PCC优化, 能够减少了 GW与 PCRF之间的信令交互, 达到了信令优化的效果。 The group policy and the charging rule processing method, the device, and the communication system provided by the embodiment of the present invention obtain the group identity or the device attribute information of the user equipment, and generate a group policy and charging rule or trigger according to the obtained information. The event can effectively improve the policy control efficiency of the user equipment of the group or the user equipment with the same equipment feature, and reduce the complexity of policy maintenance and management. And further performing PCC optimization according to the group identifier of the user equipment, which can be reduced The signaling interaction between the GW and the PCRF achieves the effect of signaling optimization.
最后应说明的是: 以上实施例仅用以说明本发明的技术方案而非对其进 行限制, 尽管参照较佳实施例对本发明进行了详细的说明, 本领域的普通技 术人员应当理解: 其依然可以对本发明的技术方案进行修改或者等同替换, 而这些修改或者等同替换亦不能使修改后的技术方案脱离本发明技术方案的 ^"神和范围。  It should be noted that the above embodiments are only intended to illustrate the technical solutions of the present invention and are not to be construed as limiting the embodiments of the present invention. The technical solutions of the present invention may be modified or equivalently replaced, and the modified technical solutions may not deviate from the technical scope of the present invention.

Claims

权 利 要求 Rights request
1、 一种群组策略与计费规则处理方法, 其特征在于, 包括:  A method for processing a group policy and a charging rule, which is characterized by comprising:
获取用户设备的群组标识或者设备属性信息中的至少一项;  Obtaining at least one of a group identifier or device attribute information of the user equipment;
根据所述用户设备的群组标识或者设备属性信息中的至少一项生成策略 与计费规则或者触发事件。  Generating a policy and charging rule or a triggering event according to at least one of a group identity or device attribute information of the user equipment.
2、 根据权利要求 1所述的群组策略与计费规则处理方法, 其特征在于, 所述获取用户设备的群组标识或者设备属性信息中的至少一项包括:  The group policy and charging rule processing method according to claim 1, wherein the acquiring at least one of a group identifier or device attribute information of the user equipment includes:
服务网关、 分组数据网络网关或网关 GPRS支持节点获取用户设备在接入 请求消息中携带的群组标识或者设备属性信息中的至少一项; 或  The service gateway, the packet data network gateway, or the gateway GPRS support node acquires at least one of a group identifier or device attribute information carried by the user equipment in the access request message; or
服务网关、 分组数据网络网关或网关 GPRS支持节点获取归属用户服务器 或群组签约数据库或业务签约数据库签约的用户设备的群组标识或者设备属 性信息中的至少一项; 或  The service gateway, the packet data network gateway or the gateway GPRS support node acquires at least one of a group identifier or device attribute information of the user equipment subscribed to the home subscriber server or the group subscription database or the service subscription database; or
服务网关、分组数据网络网关或网关 GPRS支持节点获取用户设备的标识, 根据所述用户设备的标识从配置的用户设备信息中获取用户设备的群组标识 或者设备属性信息中的至少一项;  The service gateway, the packet data network gateway or the gateway GPRS support node acquires the identifier of the user equipment, and obtains at least one of the group identifier or the device attribute information of the user equipment from the configured user equipment information according to the identifier of the user equipment;
则所述根据用户设备的群组标识或者设备属性信息中的至少一项生成策 略与计费规则或者触发事件包括:  The generating the policy and charging rule or the triggering event according to the at least one of the group identifier or the device attribute information of the user equipment includes:
服务网关、 分组数据网络网关或网关 GPRS支持节点根据获取的用户设备 的群组标识或者设备属性信息中的至少一项生成策略与计费规则或者触发事 件, 并指示所述策略与计费规则或者触发事件的应用范围为所述用户设备所 属的群组或者用户组。  The service gateway, the packet data network gateway, or the gateway GPRS support node generates a policy and charging rule or a trigger event according to at least one of the obtained group identifier or device attribute information of the user equipment, and indicates the policy and charging rule or The application range of the triggering event is a group or a user group to which the user equipment belongs.
3、 根据权利要求 2所述的群组策略与计费规则处理方法, 其特征在于, 所述服务网关、 分组数据网络网关或网关 GPRS支持节点根据获取的用户设备 的群组标识或者设备属性信息中的至少一项生成策略与计费规则或者触发事 件包括:  The group policy and charging rule processing method according to claim 2, wherein the service gateway, the packet data network gateway or the gateway GPRS support node is configured according to the obtained group identifier or device attribute information of the user equipment. At least one of the generating policy and charging rules or triggering events includes:
服务网关、 分组数据网络网关或网关 GPRS支持节点根据获得的所述的用 户设备的设备属性信息制定相应的 PCC规则或者触发事件; 或 Service Gateway, Packet Data Network Gateway or Gateway GPRS Support Node according to the obtained usage The device attribute information of the user device is used to formulate a corresponding PCC rule or a trigger event; or
服务网关、 分组数据网络网关或网关 GPRS支持节点根据所述用户设备的 群组标识以及配置的 PCC规则或者触发事件, 获得与所述用户设备的群组标 识对应的 PCC规则或者触发事件。  The serving gateway, the packet data network gateway or the gateway GPRS support node obtains a PCC rule or a trigger event corresponding to the group identity of the user equipment according to the group identity of the user equipment and the configured PCC rule or trigger event.
4、 根据权利要求 2所述的群组策略与计费规则处理方法, 其特征在于, 所述指示策略与计费规则或者触发事件的应用范围为所述用户设备所属的群 组或者用户组包括:  The group policy and charging rule processing method according to claim 2, wherein the application range of the indication policy and the charging rule or the triggering event is a group or a user group to which the user equipment belongs :
在生成的 PCC规则或者触发事件中, 增加指示 PCC规则或者触发事件应 用范围的信元; 或  In the generated PCC rule or trigger event, add a cell indicating the PCC rule or triggering the application scope of the event; or
在生成的 PCC规则或者触发事件中包含用户设备所述的群组或者用户组 的标识。  The identifier of the group or user group described by the user equipment is included in the generated PCC rule or trigger event.
5、 根据权利要求 1所述的群组策略与计费规则处理方法, 其特征在于, 所述获取用户设备的群组标识或者设备属性信息中的至少一项包括:  The group policy and charging rule processing method according to claim 1, wherein the acquiring at least one of a group identifier or device attribute information of the user equipment includes:
策略与计费规则功能实体获取服务网关、 分组数据网络网关或网关 GPRS 支持节点在 IP CAN 会话消息携带的群组标识或者设备属性信息中的至少一 项; 或  The policy and charging rule function entity acquires at least one of a group identifier or a device attribute information carried by the serving gateway, the packet data network gateway or the gateway GPRS support node in the IP CAN session message; or
策略与计费规则功能实体根据所述用户设备的标识从业务签约数据库或者 群组签约数据库中获取用户设备的群组标识或者设备属性信息中的至少一项; 则所述根据用户设备的群组标识或者设备属性信息中的至少一项生成群 组策略与计费规则或者触发事件包括:  And the at least one of the group identifier or the device attribute information of the user equipment is obtained from the service subscription database or the group subscription database according to the identifier of the user equipment; Generating a group policy and charging rule or triggering event by at least one of the identifier or the device attribute information includes:
策略与计费规则功能实体根据获取的用户设备的群组标识或者设备属性 信息中的至少一项生成策略与计费规则或者触发事件, 并在所述策略与计费 规则或触发事件中指示其应用范围为用户设备所属的群组或用户组。  The policy and charging rule function entity generates a policy and charging rule or a trigger event according to at least one of the acquired group identifier or the device attribute information of the user equipment, and indicates the policy and the charging rule or the triggering event. The application scope is the group or user group to which the user equipment belongs.
6、 根据权利要求 5所述的群组策略与计费规则处理方法, 其特征在于, 所述策略与计费规则功能实体根据获取的用户设备的群组标识或者设备 属性信息中的至少一项生成策略与计费规则或者触发事件包括: 策略与计费规则功能实体根据获得的所述的用户设备的群组标识或者设 备属性信息中的至少一项制定相应的 PCC规则或者触发事件; 或 The group policy and charging rule processing method according to claim 5, wherein the policy and charging rule function entity is based on at least one of a group identifier or device attribute information of the acquired user equipment. Generating policy and charging rules or triggering events include: The policy and charging rule function entity formulates a corresponding PCC rule or a trigger event according to the obtained group identifier or device attribute information of the user equipment; or
策略与计费规则功能实体根据所述用户设备的群组标识或者设备属性信 息中的至少一项以及配置的 PCC规则或者触发事件, 制定与所述用户设备的群 组标识或者设备属性信息中的至少一项对应的 PCC规则或者触发事件。  The policy and charging rule function entity formulates the group identity or the device attribute information of the user equipment according to at least one of the group identity or the device attribute information of the user equipment and the configured PCC rule or the trigger event. At least one corresponding PCC rule or trigger event.
7、 根据权利要求 5所述的群组策略与计费规则处理方法, 其特征在于, 所述在策略与计费规则或触发事件中指示其应用范围为用户设备所属的群组 或用户组包括:  The group policy and charging rule processing method according to claim 5, wherein the policy or charging rule or the triggering event indicates that the application scope is a group or a user group to which the user equipment belongs. :
在生成的 PCC规则或者触发事件中, 增加指示 PCC规则或者触发事件应 用范围的信元; 或  In the generated PCC rule or trigger event, add a cell indicating the PCC rule or triggering the application scope of the event; or
在生成的 PCC规则或者触发事件中包含用户设备所述的群组或者用户组 的标识。  The identifier of the group or user group described by the user equipment is included in the generated PCC rule or trigger event.
8、 根据权利要求 5所述的群组策略与计费规则处理方法, 其特征在于, 所述根据获取的用户设备的群组标识或者设备属性信息中的至少一项生成策 略与计费规则或者触发事件包括:  The group policy and charging rule processing method according to claim 5, wherein the generating a policy and a charging rule according to at least one of a group identifier or a device attribute information of the acquired user equipment, or Trigger events include:
根据所述用户设备的群组标识为所述用户设备分配或者向 DHCP请求为所 述用户设备分配群组或用户设备组粒度的 IP地址。  Assigning to the user equipment according to the group identifier of the user equipment or requesting, by the DHCP, an IP address for assigning a group or user equipment group granularity to the user equipment.
9、 根据权利要求 8所述的群组策略与计费规则处理方法, 其特征在于, 所述根据用户设备的群组标识为所述用户设备分配或者向 DHCP请求为所述用 户设备分配群组或用户设备组粒度的 IP地址包括:  The group policy and charging rule processing method according to claim 8, wherein the grouping is performed according to a group identifier of the user equipment, or assigning a group to the user equipment according to a DHCP request. Or the IP address of the user equipment group granularity includes:
根据所述用户设备的群组标识分配或向 DHCP请求为所述用户设备所属的 群组或用户组下的用户设备分配群组或者用户组粒度的 IPv6地址前缀; 或 根据所述用户设备的群组标识分配或向 DHCP请求为所述用户设备所属的 群组或用户组下的用户设备分配一个公共的 IPv4地址。  Allocating an IPv6 address prefix of a group or a user group granularity according to a group identity of the user equipment or a DHCP request to a user equipment of a group or a user group to which the user equipment belongs; or according to the group of the user equipment The group identity assignment or the DHCP request allocates a common IPv4 address to the user equipment under the group or user group to which the user equipment belongs.
10、 根据权利要求 1所述的群组策略与计费规则处理方法, 所述用户设备 为第一用户设备, 其特征在于, 还包括: 当第二用户设备的群组标识或者设备 属性信息中至少一项与所述第一用户设备相同时, 为所述第二用户设备分配已 生成的所述第一用户设备所属群组的策略与计费规则或者触发事件。 The method for processing a group policy and a charging rule according to claim 1, wherein the user equipment is a first user equipment, and further comprising: a group identifier or a device of the second user equipment When at least one item of the attribute information is the same as the first user equipment, the second user equipment is allocated a policy and charging rule or a trigger event of the group to which the first user equipment belongs.
1 1、根据权利要求 1 0所述的群组策略与计费规则处理方法,其特征在于, 所述方法还包括:  The method for processing a group policy and a charging rule according to claim 10, wherein the method further comprises:
获取第一用户设备的在 PDN连接建立请求中携带的 APN信息;  Obtaining APN information carried in the PDN connection establishment request of the first user equipment;
则根据所述用户设备的群组标识或者设备属性信息中的至少一项生成策 略与计费规则或者触发事件包括: 根据第一用户设备的群组标识或者设备属 性信息中的至少一个,以及第一用户设备的在 PDN连接建立请求中携带的 APN 信息, 生成 PCC规则或者触发事件;  And generating, according to at least one of the group identifier or the device attribute information of the user equipment, a policy and a charging rule or a triggering event, including: at least one of a group identifier or a device attribute information of the first user equipment, and Generating a PCC rule or a trigger event by the APN information carried in the PDN connection establishment request of the user equipment;
则所述为所述第二用户设备分配已生成的所述第一用户设备所属群组的 策略与计费规则或者触发事件包括: 根据所述第二用户设备发起的 PDN连接 对应的 APN信息为所述第二用户设备分配已生成的所述第一用户设备所属群 组的策略与计费规则或者触发事件。  And the step of: assigning, by the second user equipment, the generated policy and the charging policy or the triggering event of the group to which the first user equipment belongs: the APN information corresponding to the PDN connection initiated by the second user equipment is The second user equipment allocates the generated policy and charging rule or trigger event of the group to which the first user equipment belongs.
12、 一种群组策略与计费规则处理装置, 其特征在于, 包括:  12. A group policy and charging rule processing device, comprising:
获取模块, 用于获取用户设备的群组标识或者设备属性信息中的至少一 项;  An obtaining module, configured to acquire at least one of a group identifier or device attribute information of the user equipment;
规则生成模块, 用于根据所述用户设备的群组标识或者设备属性信息中 的至少一项生成策略与计费规则或者触发事件。  And a rule generating module, configured to generate a policy and charging rule or a trigger event according to at least one of a group identifier or a device attribute information of the user equipment.
1 3、根据权利要求 12所述的群组策略与计费规则处理装置,其特征在于, 所述获取模块包括:  The group policy and charging rule processing device according to claim 12, wherein the acquiring module comprises:
第一获取单元, 用于获取用户设备在接入请求消息中携带的群组标识或 者设备属性信息中的至少一项; 或  a first acquiring unit, configured to acquire at least one of a group identifier or device attribute information carried by the user equipment in the access request message; or
用于获取归属用户服务器或群组签约数据库签约的用户设备的群组标识 或者设备属性信息中的至少一项; 或  At least one of a group identifier or device attribute information used to obtain a user equipment that is subscribed to the home subscriber server or the group subscription database; or
用于获取用户设备的标识, 根据所述用户设备的标识从预先配置的用户 设备信息中获取用户设备的群组标识或者设备属性信息中的至少一项; 所述规则生成模块包括: An identifier for obtaining a user equipment, from a pre-configured user according to the identifier of the user equipment Obtaining at least one of a group identifier or a device attribute information of the user equipment in the device information; the rule generating module includes:
第一规则生成单元, 用于根据获取的用户设备的群组标识或者设备属性 信息中的至少一项生成策略与计费规则或者触发事件, 并指示所述策略与计 费规则或者触发事件的应用范围为所述用户设备所属的群组或者用户组。  a first rule generating unit, configured to generate a policy and charging rule or a trigger event according to at least one of a group identifier or a device attribute information of the acquired user equipment, and indicate the application of the policy and the charging rule or the trigger event The range is the group or user group to which the user equipment belongs.
14、根据权利要求 12所述的群组策略与计费规则处理装置,其特征在于, 所述获取模块包括:  The group policy and charging rule processing device according to claim 12, wherein the obtaining module comprises:
第二获取单元, 用于获取 IP CAN会话消息携带的群组标识或者设备属性 信息中的至少一项; 或  a second acquiring unit, configured to acquire at least one of a group identifier or device attribute information carried in the IP CAN session message; or
用于根据所述用户设备的标识从业务签约数据库或者群组签约数据库中 获取用户设备的群组标识或者设备属性信息中的至少一项;  At least one of a group identifier or device attribute information for obtaining a user equipment from a service subscription database or a group subscription database according to the identifier of the user equipment;
所述规则生成模块包括:  The rule generation module includes:
第二规则生成单元, 用于根据获取的用户设备的群组标识或者设备属性 信息中的至少一项生成策略与计费规则或者触发事件, 并在所述策略与计费 规则或触发事件中指示其应用范围为用户设备所属的群组或用户组。  a second rule generating unit, configured to generate a policy and charging rule or a trigger event according to at least one of a group identifier or a device attribute information of the acquired user equipment, and indicate in the policy and charging rule or a trigger event The scope of application is the group or user group to which the user equipment belongs.
15、 根据权利要求 12所述的群组策略与计费规则处理装置, 所述用户设 备为第一用户设备, 其特征在于, 所述的群组策略与计费规则处理装置还包 括:  The group policy and charging rule processing apparatus according to claim 12, wherein the user equipment is a first user equipment, and the group policy and charging rule processing apparatus further includes:
优化处理模块, 用于当第二用户设备的群组标识或者设备属性信息中至 少一项与所述第一用户设备相同时, 为所述第二用户设备分配已生成的所述 第一用户设备所属群组的策略与计费规则或者触发事件。  And an optimization processing module, configured to: when the at least one of the group identifier or the device attribute information of the second user equipment is the same as the first user equipment, assign the generated first user equipment to the second user equipment Policy and charging rules or trigger events for the group.
16、 一种通信***, 其特征在于, 包括权利要求 12-15任一所述的群组 策略与计费规则处理装置。  A communication system, comprising the group policy and charging rule processing apparatus according to any one of claims 12-15.
17、 根据权利要求 16所述的通信***, 其特征在于, 所述群组策略与计 费规则处理装置设置于服务网关、 分组数据网络网关、 网关 GPRS支持节点或 策略与计费规则功能实体。  The communication system according to claim 16, wherein the group policy and the charging rule processing device are provided in a service gateway, a packet data network gateway, a gateway GPRS support node, or a policy and charging rule function entity.
PCT/CN2010/076617 2009-09-04 2010-09-03 Method, device and communication system for processing group policy and charging rules WO2011026440A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910091997.5 2009-09-04
CN2009100919975A CN102014343A (en) 2009-09-04 2009-09-04 Group policy and charging rule treatment method and device, and communication system

Publications (1)

Publication Number Publication Date
WO2011026440A1 true WO2011026440A1 (en) 2011-03-10

Family

ID=43648904

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/076617 WO2011026440A1 (en) 2009-09-04 2010-09-03 Method, device and communication system for processing group policy and charging rules

Country Status (2)

Country Link
CN (1) CN102014343A (en)
WO (1) WO2011026440A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019104358A3 (en) * 2017-11-27 2019-09-19 Cisco Technology, Inc. Establishing a group session in a mobile network for subscribers associated with a group

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102238512B (en) * 2010-04-29 2015-11-25 中兴通讯股份有限公司 The application of policies method of machine type communication MTC and tactful and charging execution entity
TWI501603B (en) 2011-12-19 2015-09-21 Ind Tech Res Inst Method for grouping mtc devices in mtc networks and communication method
CN103179616A (en) * 2011-12-20 2013-06-26 华为技术有限公司 Method, system and device for selecting policy and charging rule function modules
WO2014043917A1 (en) * 2012-09-24 2014-03-27 华为技术有限公司 Group control method, mobility management entity and user equipment
KR20140045215A (en) * 2012-10-08 2014-04-16 삼성전자주식회사 Method and apparatus for configuring connection based on group
CN105247900A (en) * 2013-10-15 2016-01-13 华为技术有限公司 Method for controlling group to access wireless network and related apparatus
CN104581612B (en) * 2013-10-28 2019-04-12 华为终端有限公司 Control method, subscribed database and the mobile management device of M2M equipment
CN104683956B (en) * 2013-11-27 2018-01-26 普天信息技术研究院有限公司 QoS control method and system
WO2016054777A1 (en) 2014-10-08 2016-04-14 华为技术有限公司 Background traffic downloading method, equipment and system
CN107580290B (en) 2016-06-30 2021-04-06 阿尔卡特朗讯公司 Method and equipment for realizing MTC group message transmission
CN113938845B (en) 2018-05-21 2023-07-18 华为技术有限公司 Context management method and device
CN111385790B (en) * 2018-12-27 2023-04-07 中国电信股份有限公司 User access control method, system and computer readable storage medium
CN113395670B (en) * 2020-03-12 2022-10-04 中国电信股份有限公司 Policy control method, device, system and computer readable storage medium
CN113556693B (en) * 2021-03-12 2022-09-16 中国电信股份有限公司 Internet of things policy control method, data network gateway, storage medium and electronic equipment

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070150936A1 (en) * 2005-11-30 2007-06-28 Oracle International Corporation Orchestration of policy engines and format technologies
CN101127609A (en) * 2006-08-14 2008-02-20 华为技术有限公司 A method for managing user policy, billing control and subscription information in evolved network
CN101345633A (en) * 2007-07-10 2009-01-14 华为技术有限公司 Applied policy control method and apparatus
CN101355489A (en) * 2007-07-23 2009-01-28 中兴通讯股份有限公司 User management method based on dynamic host configuration protocol prefix proxy

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070150936A1 (en) * 2005-11-30 2007-06-28 Oracle International Corporation Orchestration of policy engines and format technologies
CN101127609A (en) * 2006-08-14 2008-02-20 华为技术有限公司 A method for managing user policy, billing control and subscription information in evolved network
CN101345633A (en) * 2007-07-10 2009-01-14 华为技术有限公司 Applied policy control method and apparatus
CN101355489A (en) * 2007-07-23 2009-01-28 中兴通讯股份有限公司 User management method based on dynamic host configuration protocol prefix proxy

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019104358A3 (en) * 2017-11-27 2019-09-19 Cisco Technology, Inc. Establishing a group session in a mobile network for subscribers associated with a group
US10791431B2 (en) 2017-11-27 2020-09-29 Cisco Technology, Inc. Methods and apparatus for establishing a group session in a mobile network for subscribers associated with a group
GB2583270A (en) * 2017-11-27 2020-10-21 Cisco Tech Inc Establishing a group session in a mobile network for subscribers associated with a group
GB2583270B (en) * 2017-11-27 2022-04-06 Cisco Tech Inc Methods and Apparatus for establishing a group session in a mobile network for subscribers associated with a group
US11729586B2 (en) 2017-11-27 2023-08-15 Cisco Technology, Inc. Methods and apparatus for establishing a group session in a mobile network for subscribers associated with a group

Also Published As

Publication number Publication date
CN102014343A (en) 2011-04-13

Similar Documents

Publication Publication Date Title
WO2011026440A1 (en) Method, device and communication system for processing group policy and charging rules
US11330113B2 (en) Charging method and device involved in a protocol data unit (PDU) session
JP6164219B2 (en) Mobile communication system, control device, communication control method, and program
CN101977416B (en) A kind of overload controlling method of MTC device and system
KR102048882B1 (en) Method and system for selecting pcef and pcrf in a wireless communication system
EP2453609A1 (en) Method, device and communication system for group charging
US8369288B2 (en) Method and apparatus for bearer processing
GB2600892A (en) Establishing a group session in a mobile network for subscribers associated with a group
WO2011140884A1 (en) Method for machine type communication group selecting packet data network gateway, and mobile management network element
WO2011134329A1 (en) Method and system for transmitting small data packets
WO2012094957A1 (en) Method and system for performing mobility management on mtc terminal
CN109802839B9 (en) Charging method, device and system
WO2011098022A1 (en) Session management method, system and device based on machine to machine (m2m) application
WO2011047589A1 (en) Method and apparatus for establishing network connection, method and system for making policy and charging control (pcc) strategy
WO2014166294A1 (en) Proximity service server selection method and apparatus, and user registration method and apparatus
WO2011134336A1 (en) Machine type communication events report method, device and system
KR20140045215A (en) Method and apparatus for configuring connection based on group
WO2011020435A1 (en) Method and system for transmitting data packet at machine-to-machine (m2m) application server
EP3235173B1 (en) Policy and charging control for groups
WO2013135213A1 (en) Tdf session process method and pcrf
WO2016019559A1 (en) Apparatus, system and method for user equipment identification of shared network
CN102177757B (en) Method, device and system for implementing registration
KR20130127368A (en) A method and apparatus for group based polishing in mobile communication networks
WO2013159605A1 (en) Communication system, device, and method
WO2011134321A1 (en) Policy sending method and system for machine type communication

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

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

Country of ref document: EP

Kind code of ref document: A1