CN102014343A - Group policy and charging rule treatment method and device, and communication system - Google Patents

Abstract

Embodiments of the present invention provide a group policy and charging rule processing method, device, and communication system, wherein the group policy and charging rule processing method includes: acquiring at least one of the group identifier or device attribute information of the user equipment item; generating a policy and charging rule or a trigger event according to at least one item of the user equipment group identifier or equipment attribute information. The device includes: an acquisition module, configured to acquire at least one item of the group ID or device attribute information of the user equipment; a rule generation module, configured to generate Policy and charging rules or trigger events. The embodiment of the present invention also provides a communication system including the above device. The method, device and system provided by the embodiments of the present invention can control the efficiency of policies and reduce the complexity of policy maintenance and management.

Description

Group policy and charging rule processing method, device and communication system

technical field

The embodiments of the present invention relate to the technical field of communication, and in particular, to a group policy and charging rule processing method, device and communication system.

Background technique

The policy charging control (Policy Charging Control, hereinafter referred to as: PCC) mechanism of the prior art stipulates that when the user conducts business, it is necessary to establish an independent policy control mechanism for each business service data flow of all users. The establishment process includes the following steps. First, after the gateway receives the IP-CAN session establishment request message initiated by the user equipment (assigning an IP address visible to the network PDN network), it sends a message including UE identification, IP address and APN information to the PCRF. The IP CAN session establishment message notifies the PCRF of the establishment of the IP CAN session. If the PCRF needs information about the user's subscription, it sends a profile request message to the SPR, and the SPR returns a response message of the user's subscription information, including the service currently signed by the user. , charging mode and other information; 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 business data flow according to the rule, and executes Corresponding QoS and charging rules, then GW sends IP CAN session establishment response message to UE.

In the process of implementing the present invention, the inventors found that: for machine type communication (Machine Type Communication, hereinafter referred to as: MTC) applications, that is, network communication between one or more network elements or devices without the need for participation, It can also be called machine-to-machine (M2M) applications, such as traffic control and management, factory control and remote meter reading applications. Operators group MTC devices into groups according to the characteristics of the above-mentioned M2M applications. . For example, for the application of remote meter reading, the operator will form a group of meter devices in a certain area, and the MTC devices in the above group all have the same M2M device attribute information, such as low mobility, insensitive to delay, etc. After the above-mentioned MTC devices are connected to the network, according to the current PCC processing mechanism, the network side needs to execute and issue corresponding PCC rules for each service establishment initiated by each MTC device. However, due to the large number of MTC devices, If the existing PCC processing mechanism is used, it will definitely cause a lot of overhead to the performance of the network. In addition, some M2M devices are simple to apply, and for MTC devices belonging to the same group, they have the same M2M device attribute information, that is, their service types are consistent, such as the above-mentioned remote meter reading service, for the above-mentioned group The MTC devices in the group can share the same PCC control policy. If the existing PCC processing mechanism is used, there are disadvantages of low policy control efficiency and complicated policy maintenance.

Contents of the invention

The purpose of the embodiments of the present invention is to provide a group policy and charging rule processing method, device and communication system, so as to improve policy control efficiency.

To achieve the above purpose, an embodiment of the present invention provides a group policy and charging rule processing method, including:

Acquiring at least one item of the group identifier or device attribute information of the user equipment;

A policy and charging rule or a trigger event is generated according to at least one item of the user equipment group identifier or equipment attribute information.

The embodiment of the present invention also provides a group policy and charging rule processing device, including:

An acquisition module, configured to acquire at least one item of the user equipment group identifier or equipment attribute information;

A rule generating module, configured to generate policy and charging rules or trigger events according to at least one item of the user equipment group identifier or equipment attribute information.

An embodiment of the present invention also provides a communication system, including the above-mentioned apparatus for processing group policy and charging rules.

The group policy and charging rule processing method, device, and communication system provided by the embodiments of the present invention obtain the group ID or device attribute information of user equipment, and generate group policy and charging rules or trigger The event can effectively improve the policy control efficiency of user equipments in a group or user equipments with the same equipment characteristics, and reduce the complexity of policy maintenance and management.

Description of drawings

FIG. 1 is a schematic flow diagram of Embodiment 1 of the group policy and charging rule processing method of the present invention;

FIG. 2 is a schematic flowchart of a first specific embodiment of a group policy and charging rule processing method according to the present invention;

FIG. 3 is a schematic flowchart of a second specific embodiment of the group policy and charging rule processing method of the present invention;

Fig. 4 is a schematic flow chart of PCC optimization processing in the embodiment described in Fig. 3;

FIG. 5 is a schematic flowchart of a third specific embodiment of the group policy and charging rule processing method of the present invention;

FIG. 6 is a schematic structural diagram of an embodiment of an apparatus for processing group policies and charging rules according to the present invention.

Detailed ways

The technical solutions of the present invention will be described in further detail below with reference to the accompanying drawings and embodiments.

An embodiment of the present invention provides a group policy and charging rule processing method. FIG. 1 is a schematic flowchart of Embodiment 1 of the group policy and charging rule processing method of the present invention. As shown in FIG. 1 , it includes the following steps:

Step 101. Obtain at least one of the group ID or device attribute information of the user equipment; that is, the group ID or the device attribute information of the user equipment is acquired in this step, or both of the above two items are acquired simultaneously.

For a user group or a group user, the group identifier of the user equipment is a user group identifier (also can be described as a user group user identifier) or a group identifier (also can be described as a group user identifier), or other indicators indicating that the user equipment The identification of the group or user group to which the user equipment belongs, for example, by APN (Access Point Name) to identify the group or user group to which the user equipment belongs, then the APN is the identification of the group or user group to which the user equipment belongs. In this embodiment, the group identification No restrictions. The group or user group may be a user equipment group or an M2M industry user (MTC User) or an M2M application subscriber (MTC Subscriber) or other groups composed of multiple devices, which is not limited in this embodiment.

Wherein, the device attribute information is attribute information shared by user devices with the same characteristics, and is different device characteristic information obtained according to different applications of different industry users (MTC User) or M2M application subscribers (MTC Subscriber). It can be called as Machine Feature or Machine Type or Service Class. For example, if the user equipment in the remote meter reading system has the characteristics of low mobility and insensitivity to time delay, etc., its device attribute information is low mobility and insensitive to time delay; The name of the information does limit.

Step 102: Generate a policy and charging rule or a trigger event according to at least one item of the user equipment group identifier or equipment attribute information.

Wherein, the scope of application of the policy and charging rule or trigger event is the group or user group to which the user equipment belongs. That is, the policy and charging rule or the triggering event is also applied to other users in the group or user group to which the user equipment belongs subsequently.

The trigger event in this embodiment is a PCEF or BBERF event reporting behavior rule, and its scope of application is for the group to which the user equipment belongs or all user equipment under the user group. For example, when the triggering event is a change in the location of a user equipment in the group, the PCEF or BBERF needs to report the location change event of the user equipment to the policy and charging rule functional entity after being informed.

In this embodiment, by obtaining the group identifier or device attribute information of the user equipment, and generating group policies and charging rules or trigger events based on the information obtained above, it is possible to effectively improve the user equipment in the group or have the same equipment characteristics. Policy control efficiency of user equipment, and reduce the complexity of policy maintenance and management.

Can be divided into dynamic PCC application and static PCC application two kinds of situations in the above-mentioned embodiment of the present invention:

1. For performing static PCC application, at least one of the group identification or equipment attribute information (MTC Feature) to obtain the user equipment includes: the serving gateway, the packet data network gateway or the gateway GPRS support node obtains the access request message of the user equipment (For example, Attach Request (Attach Request), Location Area Update Request (Routeing Area Update Request or Tracking Area Update Request), PDN Connection Establishment Request (PDN Connectivity Establishment Request), Activate PDP Context Request (Active PDP Context Request), Create PDP At least one of the group identifier or device attribute information carried in the context request (Create PDP Context Request) or create session request (Create Session Request); At least one of the group identifier or equipment attribute information of the user equipment subscribed to the group subscription database; or the above-mentioned network element can obtain the identifier of the user equipment through the existing process, and obtain the identifier of the user equipment according to the identifier of the user equipment from the pre-configured At least one item of the user equipment group identifier or equipment attribute information is obtained from the user equipment information.

Generating policy and charging rules or triggering events according to at least one of the group identifier or device attribute information of the user equipment includes: the serving gateway, the packet data network gateway or the gateway GPRS support node according to the obtained user equipment group identifier or device At least one item of attribute information generates a policy and charging rule or a trigger event, and indicates that the scope of application of the policy and charging rule or trigger event is the group or user group described by the user equipment. Specifically can include:

a) the specific service gateway, packet data network gateway or gateway GPRS support node can generate policy and charging rules or trigger events as follows: a method is that the service gateway, packet data network gateway or gateway GPRS support node according to the obtained According to the device attribute information of the user equipment, such as low mobility and delay insensitivity, corresponding PCC rules or trigger events are formulated according to the statically configured PCC rules or trigger events. Another method is that the serving gateway, the packet data network gateway or the gateway GPRS support node formulate the group identification information related to the user equipment group according to the PCC rules statically configured on it or the trigger event according to the obtained user equipment group identification information. Corresponding PCC rules or trigger events.

b) Indicate that the application scope of the policy and charging rule or trigger event is the group or user group described by the user equipment. The specific method may be: in the generated PCC rule or trigger event, add the indicated PCC rule or trigger event The information element of the event application scope, such as 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. Another method is that the generated PCC rule or the trigger event includes the group or user group identifier described by the user equipment, then the serving gateway, packet data network gateway or gateway GPRS support node will The PCC rule or trigger event is applied to the group or user group described by the user equipment.

2. For dynamic PCC applications, obtaining at least one of the group identifier or device attribute information of the user equipment includes: one way is that the policy and charging rule functional entity obtains the serving gateway, packet data network gateway or gateway GPRS support node At least one of the group identification or device attribute information carried in the IP CAN session message (such as Indication IPCAN Session Establishment); another way is to select from the service subscription database or the group subscription database according to the identification of the user equipment Acquiring at least one of the group identifier or device attribute information of the user equipment, that is, the policy and charging control function entity sends a configuration request message (such as Profile Request) to the service subscription database (SPR) or the group subscription database, The configuration request message carries the user equipment identifier, and the service subscription database or the group subscription database obtains at least one of the user equipment group identifier or device attribute information according to the user equipment identifier, and sends the configuration response message ( Profile Response) is returned to the policy and charging control functional entity.

Generating a group policy and charging rule or a trigger event according to at least one of the group identifier or device attribute information of the user equipment includes: the policy and charging rule functional entity according to the obtained user equipment group identifier or device attribute information At least one of them generates a policy and charging rule or a trigger event, and indicates in the policy and charging rule or trigger event that its scope of application is the group or user group to which the user equipment belongs. Specifically can include:

a) The method for the policy and charging rule functional entity to generate policy and charging rules or trigger events may be as follows. One method is that the policy and charging rule functional entity obtains the user equipment group ID and device attribute information At least one item, such as low mobility and insensitivity to delay, formulate corresponding PCC rules or trigger events. Another method is that the policy and charging rule functional entity formulates a group ID with the user equipment according to at least one item of the user equipment group identifier and equipment attribute information, and according to the pre-configured PCC rules or trigger events thereon. The PCC rule or trigger event corresponding to the group identifier or device attribute information.

In addition: the process of generating policy and charging rules or triggering events includes: assigning or requesting DHCP for the user equipment according to the group identifier of the user equipment to assign an IP with group or user equipment group granularity to the user equipment address. The above-mentioned steps may specifically be: assigning or requesting DHCP for the group to which the user equipment belongs or the user equipment under the user group according to the group identifier of the user equipment to assign a group or user group granularity IPv6 address prefix; or according to The group identifier allocation of the user equipment or request to DHCP to allocate a public IPv4 address to the group to which the user equipment belongs or to the user equipment under the user group.

b) Indicate that the application scope of the policy and charging rule or trigger event is the group or user group described by the user equipment. The specific method may be: in the generated PCC rule or trigger event, add the indicated PCC rule or trigger event The information element of the event application scope, such as 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. Another method is that the generated PCC rule or the trigger event includes the group or user group identifier described by the user equipment, then the serving gateway, packet data network gateway or gateway GPRS support node will The PCC rule or trigger event is applied to the group or user group described by the user equipment.

Another embodiment of the present invention may further include: a step of performing optimization processing of policies and charging rules according to group identifiers of user equipments. Since the application scope of the policy and charging rule or the triggering event is the group or user group to which the user equipment belongs, the policy and charging rule or trigger event. When another new user equipment requests access (for example, initiates an attach process or a PDN connection establishment process), and at least one of the group identifier or device attribute information of the new user equipment is the same as the user equipment in step 101, The above steps may specifically assign the generated policy and charging rules or trigger events of the group to which the user equipment belongs in step 101 (ie, the policy and charging rules or trigger events in step 102 ) to the new user equipment. For the specific method, refer to the description of the method for the PGW, SGW or GGSN to perform PCC optimization in step 203 of the first specific embodiment regarding the second user equipment initiating the PDN connection establishment process.

Another embodiment of the present invention may further include: terminating the group policy and charging rule or trigger event 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 disconnection process (for example, initiates a detachment process or a PDN disconnection process), the packet data network gateway or GPRS support node or the policy and charging control function entity The group identifier determines whether there are other user equipments under the group to keep connected, if there is, the policy and charging rules or trigger events of the group generated for the group to which the user equipment belongs are kept, otherwise, it is terminated for all The policy and charging rules or trigger events of the group generated by the group to which the user equipment belongs. The specific method can refer to the description of the processing steps performed by the PGW, SGW or GGSN when the user equipment initiates the PDN connection establishment process in step 203 of the first specific embodiment.

Another embodiment of the present invention may further include: assigning the user equipment to the generated policy and charging rule or trigger event of the group to which the user equipment belongs may specifically be the APN corresponding to the PDN connection initiated by the user equipment The information assigns the generated policy and charging rules or trigger events of the group to which the user equipment belongs to the user equipment. For the specific method, refer to the description of the method for the PGW, SGW or GGSN to perform PCC optimization in step 203 of the first specific embodiment regarding the second user equipment initiating the PDN connection establishment process.

Another embodiment of the present invention may further include: the above-mentioned policy and charging rules or trigger events for terminating the group generated for the group to which the user equipment belongs according to the group identifier of the user equipment may specifically be based on the PDN initiated by the user equipment. The APN information corresponding to the connection terminates the group policy and charging rule or trigger event generated for the group to which the user equipment belongs. The specific method can refer to the description of the processing steps performed by the PGW, SGW or GGSN when the user equipment initiates the PDN connection establishment process in step 203 of the first specific embodiment.

Fig. 2 is a schematic flowchart of a first specific embodiment of the group policy and charging rule processing method of the present invention, as shown in Fig. 2 , including the following steps:

Step 201. Acquire at least one item of group identifiers or device attribute information of user equipment. PGW or SGW or GGSN or PCRF can learn the group identity of the user equipment as follows: MME or SGSN 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.) The group identifier is carried. Optionally, the MME or the SGSN carries the device attribute information (MTCFeature) of the user equipment in the message. The method for the MME or SGSN to obtain the identity or device attribute information of the user equipment includes that the user equipment carries the group identity of the user equipment in an access request message (for example, Attach Request or TAU Request or PDN Connectivity Establishment Request or Active PDP Context Request) Or device attribute information. Alternatively, the HSS or the Group subscription database provides the group identifier or device attribute information of the user equipment to the MME or SGSN, for example, after receiving the Update Location Request message sent by the MME, the user equipment identifier carried in the message is sent to the MME The returned Update Location Ack message carries the group identifier or device attribute information of the user equipment.

Or when dynamic PCC is applied, the specific method for the PCRF to obtain at least one item of the user equipment's group identifier or equipment attribute information (Machine Feature) includes that the PCRF sends a configuration information request message (Profile Request) to the SPR, and the message carries the user equipment The identity of the device, the SPR returns a configuration information response message (Profile Response), according to the identity of the user equipment carried in the message, the configuration information response message carries at least one item. After the PCRF obtains at least one item of the group identifier of the user equipment and the equipment attribute information of the user equipment, the PCRF may additionally provide the group identifier of the user equipment or the equipment attribute information of the user equipment to the PGW or SGW (such as in Acknowledge IP CAN Session Establishment or Acknowledge IP CANSession Modification or Policy and Charging Rules Provision and other messages). Another method for the PCRF to obtain at least one item of the group identifier of the user equipment and the equipment attribute information of the user equipment may be that the PCRF receives an IPCAN session message (such as Indication of IP CAN Session Establishment) sent by the PGW or the GGSN or the SGW, so The IP CAN session message carries the group identifier of the user equipment or the equipment attribute information of the user equipment.

The identity of the user equipment (such as the IMSI of the user equipment, the IMEI of the user equipment, or the IMSI and IMEI of the user equipment) and the group to which the user equipment belongs may also be configured on the PGW, SGW or GGSN The corresponding relationship between group identifiers, or the corresponding relationship between the identifier of the user equipment and the corresponding equipment attribute information of the user equipment. The PGW, SGW or GGSN obtains the identifier of the user equipment, and according to the configuration information thereon, obtains the identifier of the group or user group to which the user equipment belongs, or obtains the device attribute information corresponding to the user equipment.

Step 202, generate group shared PCC rules or trigger events (Event Trigger), specifically include the following methods:

(1) When the static PCC is applied, the PGW or the SGW or the GGSN obtains at least one item 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 triggers an event according to at least one item of the user equipment group identifier or equipment attribute information. For example, in the above-mentioned M2M application of remote meter reading, the PGW or SGW or GGSN formulates a corresponding PCC rules or trigger events. Another method for the PGW or SGW or GGSN to formulate PCC rules or trigger events based on at least one item of the user equipment group ID or device attribute information is that the PGW or SGW or the GGSN base the user equipment group ID on , formulating a PCC rule or trigger event corresponding to the group identifier of the user equipment according to the statically configured PCC rule or trigger event. The PGW or the SGW or the GGSN indicates that the application scope of the PCC rule or trigger event formulated for the user equipment is the group or user group to which the user equipment belongs. The specific method can be to add an information element indicating the application scope of the PCC rule or trigger event in the generated PCC rule or trigger event, such as Apply Scope. When the Apply Scope is set to the group scope, the generated PCC rule or trigger event Applied to the group or user group described in the user equipment. Another method is that the generated PCC rule or the trigger event includes the group or user group identifier described by the user equipment, then the serving gateway, packet data network gateway or gateway GPRS support node will The PCC rule or trigger event is applied to the group or user group described by the user equipment.

(2) When the dynamic PCC rule is applied, the PGW, SGW or 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, SGW or GGSN sends an IP CAN session establishment instruction message to the PCRF, and the message may carry the group identifier of the user equipment or the device attribute information of the user equipment. After obtaining the above-mentioned group identifier of the user equipment, the PCRF may send the configuration information request message (Profile Request) to the SPR to carry the group identifier of the user equipment. In addition, the PCRF can also obtain the above-mentioned group identifier or device attribute information by receiving the configuration information response message (Profile Response) returned by the SPR, that is, the above-mentioned configuration information response message carries the group identifier or device attribute information of the user equipment. The PCRF formulates a PCC rule or a trigger event according to at least one of the group identifier or equipment attribute information to which the user equipment belongs, or the service subscription data of the user equipment. For example, in the above-mentioned M2M application of remote meter reading, the PCRF formulates corresponding PCC rules or triggers events according to the obtained equipment attribute information of the user equipment, such as low mobility and insensitive delay. The PCRF formulates PCC rules or triggers events according to at least one of the group ID to which the user equipment belongs, or equipment attribute information, or the service subscription data of the user equipment. Another method is that the PCRF uses the group ID of the user equipment and at least one item of device attribute information, formulate a PCC rule or trigger event corresponding to the group identifier or device attribute information of the user equipment according to the preconfigured PCC rule or trigger event. The PCRF may indicate in the PCC rule formulated for the user equipment that the application scope of the PCC rule is the group or user group to which the user equipment belongs, or carry the group of the group to which the user equipment belongs in the PCC rule ID, the PGW, SGW or GGSN applies the obtained PCC rule to the group to which the user equipment belongs according to the application scope indication in the PCC rule or the group identifier carrying the group to which the user equipment belongs in the PCC rule group or user group. When a dynamic PCC rule is applied, the PCRF may not provide a service data flow template (Service Date Flow Template) in the PCC rule, that is, the PCRF according to at least one of the group identifier or device attribute information of the user equipment Formulate a PCC policy whose application scope is a group or a user equipment group, so that no service data flow template is provided in the PCC rule. Or the PCRF formulates a PCC policy with an application scope of a group or a user equipment group according to at least one item of the user equipment group identifier or equipment attribute information, but the PCRF also provides a service data flow template in the PCC rule. When a dynamic PCC rule is applied, the method of the service data flow template generated by PCRF in the PCC rule includes:

a) When the user equipment initiates a PDN connection establishment process (for example, the Attach process or the PDN connection establishment process), the PGW allocates or the PGW requests DHCP (Dynamic Host Configuration Protocol) to assign an IPv4 address or an IPv6 address for the above user equipment . The PGW learns the group identifier of the user equipment, and the PGW allocates or requests DHCP for the user equipment according to the group identifier of the user equipment to assign an IP address of a group or user group granularity to the user equipment, and the specific methods include : The PGW assigns or requests to DHCP according to the group identifier of the user equipment to assign a group or user group granular IPv6 address prefix for the group to which the user equipment belongs or user equipment under the user group (a complete IPv6 address consists of It consists of two parts, namely IPv6 address prefix and IPv6 interface identifier). The IPv6 address prefix is group or user group granular, that is, when the second user equipment belonging to the same group as the user equipment (first user equipment) initiates a PDN connection establishment procedure for the same APN, the PGW is the second The IPv6 address prefix allocated by the user equipment is the same as the IPv6 address prefix allocated by the PGW for the user equipment (first user equipment) (that is, the PGW uses the IPv6 address prefix allocated for the first user equipment as the PGW for the second user equipment. IPv6 address prefix). Or the PGW allocates or requests the DHCP to allocate a public IPv4 address to the group to which the user equipment belongs or to the user equipment under the user group according to the group identifier of the user equipment. The public IPv4 address is group or user group granular.

b), as described in feature a), the PGW has obtained the IPv6 prefix or public IPv4 address of the user equipment, and the PGW sends an IP CAN session establishment instruction message to the PCRF, and the IP CAN session establishment instruction message includes the IP CAN session establishment instruction message obtained by the PGW The IPv6 prefix or public IPv4 address of the user equipment. According to the above description, the PCRF formulates PCC rules for the user equipment, and the PCRF generates a service data flow template (Service Date Flow Template) according to the learned IPv6 prefix or public IPv4 address.

c), the PCRF sends an IP CAN session establishment confirmation message to the PGW, the message includes the PCC rule, and the PCC rule includes the service data flow template (Service Date Flow Template). The method for the PGW to generate a packet filter (Packet Filter, used to match the relationship between the Service Data Flow and the bearer) for each different user equipment includes, as feature a) describes when the user equipment initiates a PDN connection establishment process (such as , Attach process or PDN connection establishment process), the PGW allocates for the user equipment or the PGW requests DHCP (Dynamic Host Configuration Protocol) to allocate an IPv4 address or an IPv6 address for the user equipment.

If the user equipment is assigned an IPv6 address, the PGW assigns a different interface identifier to each different user equipment of this group or user group (the method for the PGW to assign a different interface identifier to each different user equipment is not specifically described. For example, the PGW assigns different interface identifiers according to the IMEI identifier or IMSI identifier of the user equipment), 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 generates a complete IPv6 address based on the complete The IPv6 address generates a packet filter (Packet Filter) of the user equipment.

If the user equipment is allocated an IPv4 address, the PGW allocates a different IPv4 address to each different user equipment of this group or user group (the method for the PGW to allocate a different IPv4 address to each different user equipment is not specifically described. Restrictions, such as PGW allocates different IPv4 addresses according to the IMEI identifier or IMSI identifier of the user equipment), the PGW generates the packet filter (Packet Filter) of the user equipment according to distributing different IPv4 addresses for each different user equipment.

Step 203: Execute PCC optimization processing according to the group identifier of the user equipment. As described in step 202, the PGW or SGW or GGSN or PCRF generates PCC rules or trigger events shared by the group or user group. The network side performs PCC optimization according to the group identifier of the second user equipment (belonging to the same group as the first user equipment), specifically including:

(1), the second user equipment initiates a PDN connection establishment process (such as an Attach process or a PDN connection establishment process), and the PGW or SGW or GGSN or PCRF generates a PCC rule or a trigger event for the second user equipment, and the PGW or SGW or GGSN The method for performing PCC optimization includes, PGW or SGW or GGSN according to the group identifier of the second user equipment, the specific method includes, when static PCC is applied, the PGW or SGW or GGSN obtains the 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, assigning the generated policy of the group to which the first user equipment belongs to the second user equipment and Billing rules or trigger events. Optionally, when generating a PCC rule or triggering an event for the first user equipment, it may further include at least one of the group identifier or device attribute information of the first user equipment, and the PDN connection establishment of the first user equipment. The APN information carried in the request generates PCC rules or triggers events. When the second user equipment initiates an access request (such as a PDN connection request or an attach request), the PGW or SGW or GGSN further determines that the APN information corresponding to the PDN connection initiated by the second user equipment is the same as that initiated by the first other user equipment. The APN information corresponding to the PDN connection of the corresponding PDN connection is the same, then the PGW or SGW or GGSN generates the same PCC rule or trigger event as the PCC rule or trigger event generated for the first other user equipment for the second user equipment (that is, the PGW or SGW or The GGSN uses the learned PCC rule or trigger event generated for a certain APN for the group or user group to which the user equipment belongs). When dynamic PCC is applied, the PGW or SGW or 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, then the The second user equipment distributes the generated policy and charging rules or trigger events of the group to which the first user equipment belongs. Optionally, when generating a PCC rule or triggering an event for the first user equipment, it may further include at least one of the group identifier or device attribute information of the first user equipment, and the PDN connection establishment of the first user equipment. The APN information carried in the request generates PCC rules or triggers events. When the second user equipment initiates an access request (such as a PDN connection request or an attach request), the PGW or SGW or GGSN further determines that the APN information corresponding to the PDN connection initiated by the second user equipment is the same as that initiated by the first other user equipment. The APN information corresponding to the PDN connection of the corresponding PDN connection is the same, then the PGW or SGW or GGSN generates for the second user equipment the same PCC rule or trigger event as the obtained PCC rule or trigger event generated for the first other user equipment (that is, the PGW or The SGW or the GGSN uses the known PCC rule or trigger event generated for a certain APN for the group or user group to which the user equipment belongs, and does not send the IP CAN session establishment indication message to the PCRF.

(2), the user equipment initiates a PDN connection process (such as a Detach process or a PDN connection process), and the PGW or SGW or GGSN receives a message deleting a PDN connection request (such as a Delete Session Request or Delete PDP Context Request message ), the PGW or SGW or GGSN determines whether there is a group ID corresponding to other user equipment that is the same as the group ID of the user equipment, and the PGW may further base on whether there is a group ID corresponding to other user equipment and the The APN information corresponding to the PDN connection of the user equipment is the same as the group identifier of the user equipment and the APN information corresponding to the PDN connection deleted by the user equipment. If it exists, the PGW or SGW or GGSN will 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 it does not exist, the PGW or SGW or GGSN will delete the PCC rule or trigger event, or the PGW or SGW or GGSN will send an IP CAN session termination indication message to the PCRF.

(3) When dynamic PCC is applied, PCRF initiates an IP CAN session termination process for a certain group or user group, and PCRF sends an IP CAN session termination instruction message to PGW, and the message carries a group identifier. Optionally, PCRF needs Terminated PDN identifier, such as APN information.

According to the description of steps 202 and 203, the network side generates group-shared PCC rules or trigger events, and the network side performs PCC optimization according to the group identifier of the user equipment. This solution not only solves the problem of low network policy control efficiency, policy Issues such as maintenance and management complexity also reduce the signaling interaction between the GW and the PCRF, achieving the effect of signaling optimization.

Fig. 3 is a schematic flowchart of the second specific embodiment of the group policy and charging rule processing method of the present invention. At least one of the group identifier or device attribute information obtains a PCC rule or a trigger event. As shown in Figure 3, it includes the following steps:

Step 301, the M2ME sends an attach request message to the MME. The M2ME carries the M2ME identity information in the attach request message. Optionally, the M2ME may carry the group charging identifier in the attach request message. Optionally, the M2ME may carry its device attribute information (MTCFeature) in the attach request message;

Step 302, execute the flow of authentication and authentication;

Step 303, the MME sends a location area update request message to the HSS or the Group subscription database. If the MME obtains the group identifier in the attach request message, the MME carries the group identifier in the update location area request message;

Step 304, the HSS or the Group subscription database returns a location area update confirmation message. The HSS returns 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 the device attribute information of the M2ME;

Step 305, the MME sends a session creation request message to the SGW. If the MME has obtained the group identifier or device attribute information of the M2ME, the group identifier information or device attribute information may be carried in the session creation request message;

Step 306, the SGW sends a session creation request message to the PGW. If the SGW has obtained the group identifier or device attribute information of the M2ME, the group identifier information or device attribute information may be carried in the session creation request message;

The following steps 307 to 310 are steps executed when dynamic PCC is applied, and are not executed when static PCC is applied.

Step 307, the PGW sends an IP CAN session establishment indication message to the PCRF. If the PGW has obtained the group identifier of the M2ME, the group identifier may be carried in the IP CAN session establishment indication message. Optionally, if in step 306, the PGW obtains the device attribute information of the M2ME, the PGW carries the device attribute information of the M2ME in the IP CAN session establishment instruction message;

Step 308, the PCRF sends a configuration information request message to the SPR or the Group subscription database. If the PCRF has obtained 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. The SPR or the Group subscription database returns the service subscription data of the M2ME in the configuration information response message. Optionally, this message includes the M2ME group identifier, or M2ME device attribute information;

Step 310, PCRF formulates PCC rules or triggers events according to at least one of the group identifier or device attribute information to which the user equipment belongs 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 specific embodiment. For example, the PCRF indicates in the PCC rule formulated for the user equipment that the scope of application of the PCC rule is the group or 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 will obtain the PCC rule according to the application scope of the PCC rule or the PCC rule carrying the group identifier of the group to which the user equipment belongs Applied to the group or user group to which the user equipment belongs. The method of the service data flow template (Service Date Flow Template) generated by the PCRF in the PCC rule is as described in feature a), b) and c) in feature (2) of step 202 of the first specific embodiment. This embodiment will not be described in detail. Optionally, the PCRF generates a trigger event, and the trigger event is applied to a group or user group granularity. For example, when the PGW counts the data traffic used by the user equipment of this group or user group reaching a certain threshold, the PGW reports this event to PCRF;

Step 311 , the PGW sends a session creation response message to the SGW, and the message includes the PCC rule or trigger event obtained by the PGW. When the static PCC is applied, the PGW formulates a PCC rule or triggers an event according to at least one item of the user equipment group identifier or equipment attribute information. The specific method is as described in the feature (1) of step 202 in the first specific embodiment, and will not be repeated in this embodiment. The PGW applies the PCC rule or trigger event formulated for the user equipment to the group or user group to which the user equipment belongs;

Step 312, the SGW sends a session creation response message to the MME;

Step 313, the MME sends an attach accept message to the M2ME.

In addition, when the M2ME initiates an attach procedure, the PGW or PCRF performs PCC optimization according to the group identifier of the M2ME. The specific method is as described in step 203 in the first specific embodiment: the PGW determines whether to use the group identifier of the M2ME, and optionally, the APN information corresponding to the PDN connection initiated by the M2ME. The PCC rule or trigger event generated by the group or user group to which the M2ME belongs. The specific method is as described in feature (1) of step 203 in the first specific embodiment, and will not be repeated in this embodiment.

Another embodiment of the present invention provides that the M2ME initiates a PDN disconnection process (such as a Detach process or a PDN disconnection process), as described in the feature (2) of step 203 in the first specific embodiment, and the PGW receives the deletion of the PDN connection The requested message (Delete Session Request), as shown in Figure 4:

Step 401, the PGW receives a delete IP CAN session request message, such as a Delete Session Request message. The PGW determines whether there is a group identifier corresponding to other user equipment that is the same as the group identifier of the user equipment. Optionally, further, the PGW determines whether there is a group identifier corresponding to other user equipment and the PDN established by other user equipment. The APN information corresponding to the connection is the same as the group identifier of the user equipment and the APN information corresponding to the PDN connection deleted by the user equipment. If it exists, the PGW will not delete the PCC rule or trigger event, or the PGW will not send The PCRF sends an IP CAN session termination indication message. If it does not exist, 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 IP CAN session termination instruction message. Optionally, the message carries the group identifier of the group to which the user equipment belongs, and optionally the APN information corresponding to the PDN connection deleted by the user equipment, and the PCRF according to the group ID of the group to which the user equipment belongs Group identification, optionally, further, and the APN information, determine whether there are other PGWs for this group or user group, optionally, further, for this group or user group and the APN information Serve. If it exists, the PCRF returns a message confirming the termination of the IP CAN session without sending a request to cancel the subscription data notification to the SPR. If it does not exist, the PCRF returns a message to confirm the termination of the IP CAN session, and sends a request to cancel the subscription data notification to the SPR;

Step 403, PCRF sends to PGW a confirmation termination IP CAN session message;

Step 404, PGW sends delete IP CAN session response message;

Step 405, according to the description of step 402, the PCRF sends a subscription cancellation data notification request to the SPR;

Step 406, if receiving the cancellation subscription data notification request message, the SPR returns the cancellation subscription data notification response to the PCRF;

Step 407, the PGW sends a final threshold report to the OCS. The optional message carries the group identifier of the group to which the user equipment belongs;

Step 408, the OCS returns a threshold confirmation message.

Fig. 5 is a schematic flowchart of the third specific embodiment of the group policy and charging rule processing method of the present invention. At least one item of identification or device attribute information acquires PCC rules or triggers events. As shown in Figure 5, it includes the following steps:

Step 501, the M2ME sends a PDN connection establishment request message to the MME. The message carries information such as APN;

Step 502, the MME sends a session creation request message to the SGW. If the MME has obtained the group identifier or device attribute information of the M2ME, the group identifier information or device attribute information may be carried in the session creation request message;

Step 503, the SGW sends a session creation request message to the PGW. If the SGW has obtained the group identifier or device attribute information of the M2ME, the group identifier information or device attribute information may be carried in the session creation request message;

If it is a static PCC application, the following steps 504 to 507 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 has obtained the group identifier of the M2ME, the group identifier may be carried in the IP CAN session establishment instruction message. Optionally, if in step 503, the PGW obtains the device attribute information of the M2ME, the PGW carries the device attribute information of the M2ME in the IP CAN session establishment instruction message;

Step 505, the PCRF sends a configuration information request message to the SPR or the Group subscription database. If the PCRF has obtained 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, this message includes the M2ME group identifier, or M2ME device attribute information;

Step 507: PCRF formulates PCC rules or triggers events according to at least one of the group identifier or device attribute information to which the user equipment belongs or the service subscription data of the user equipment, and sends an IP CAN session establishment confirmation message to the PGW. The specific method can be as described in step 302 of the first specific embodiment. For example, the PCRF indicates in the PCC rule formulated for the user equipment that the scope of application of the PCC rule is the group or 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 will obtain the PCC rule according to the application scope of the PCC rule or the PCC rule carrying the group identifier of the group to which the user equipment belongs Applied to the group or user group to which the user equipment belongs. The method of the service data flow template (Service Date Flow Template) generated by the PCRF in the PCC rule is as described in the features a), b), and c) in the feature (2) of step 202 in the first specific embodiment. This embodiment will not be described in detail. Optionally, the PCRF generates a trigger event, and the trigger event is applied to a group or user group granularity. For example, when the PGW counts the data traffic used by the user equipment of this group or user group reaching a certain threshold, the PGW reports this event to PCRF;

In step 508, the PGW sends a session creation response message to the SGW, and the message includes the PCC rule obtained by the PGW or a trigger event. When the static PCC is applied, the PGW formulates a PCC rule or triggers an event according to at least one item of the user equipment group identifier or equipment attribute information. The specific method is as described in the feature (1) of step 202 in the first specific embodiment, and will not be repeated in this embodiment. The PGW applies the PCC rule or trigger event formulated for the user equipment to the group or user group to which the user equipment belongs;

Step 509, the SGW sends a session creation response message to the MME;

Step 510, the MME sends an E-RAB establishment request message to the eNodeB, and the message carries the activation default bearer request message sent to the M2ME;

Step 511, 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 513, the eNodeB sends an E-RAB establishment response message to the MME;

Step 514, the M2ME sends a direct transfer message to the eNodeB, and the message carries an activation default bearer response message;

Step 515, the eNodeB transmits the activation default bearer response message to the MME;

Step 516, the MME sends a modify bearer request message to the SGW;

Step 517, the SGW returns a modify bearer response message to the MME.

The embodiment of the present invention also provides a group policy and charging rule processing device. FIG. 6 is a schematic structural diagram of an embodiment of the group policy and charging rule processing device of the present invention. As shown in FIG. 6 , it includes an acquisition module 11 and A rule generation module 12, wherein the acquisition module 11 is used to obtain at least one of the group identification or device attribute information of the user equipment; One generates policy and accounting rules or triggers events.

The group policy and charging rule processing device provided by the embodiment of the present invention can effectively improve the group policy by acquiring the group identifier or device attribute information of the user equipment, and generating a policy and charging rule or a trigger event based on the information obtained above. The policy control efficiency of the user equipment or the user equipment with the same equipment characteristics, and reduces the complexity of policy maintenance and management.

When the static PCC is applied, the obtaining module in the above embodiment includes a first obtaining unit, and the first obtaining unit is configured to obtain at least one of the group identifier or device attribute information carried by the user equipment in the access request message; or It is used to obtain at least one of the group identification or equipment attribute information of the user equipment subscribed by the home user server or the group subscription database; or used to obtain the identification of the user equipment, and from the pre-configured user equipment Obtain at least one of the group identifier or device attribute information of the user equipment from the equipment information; the corresponding rule generation module includes a first rule generation unit, which is used to obtain the group identifier or At least one item of device attribute information generates a policy and charging rule or a trigger event, and indicates that the scope of application of the policy and charging rule or trigger event is the group or user group to which the user equipment belongs.

The device for processing group policies and charging rules in this embodiment may be set in a service gateway, a packet data network gateway or a gateway GPRS support node.

When dynamic PCC is applied, the obtaining module includes a second obtaining unit, which is used to obtain at least one of the group identification or device attribute information carried by the IP CAN session message; or for according to the user equipment The identification acquires at least one of the group identification or equipment attribute information of the user equipment from the service subscription database or the group subscription database. The corresponding rule generation module includes a second rule generation unit, which is configured to generate policy and charging rules or trigger events according to at least one of the acquired group identifier or device attribute information of the user equipment, and in the policy and The application scope indicated in the charging rule or trigger event is the group or user group to which the user equipment belongs.

In addition, the apparatus in the above-mentioned embodiment may further include an optimization processing module, which is configured to, when at least one item of the group identifier or equipment attribute information of the second user equipment is the same as that of the first user equipment, optimize the processing module for the second user equipment. The second user equipment assigns the generated policy and charging rules or trigger events of the group to which the first user equipment belongs.

An embodiment of the present invention also provides a communication system, including the above-mentioned apparatus for processing group policy and charging rules. And the above-mentioned group policy and charging rule processing device is set in the service gateway, packet data network gateway, gateway GPRS support node or policy and charging rule functional entity.

The communication system provided by the embodiment of the present invention includes a group policy and charging rule processing device, by obtaining the group identifier or device attribute information of the user equipment, and generating a group policy and charging rule or a trigger event according to the obtained information, It can effectively improve the policy control efficiency of user equipments in a group or user equipments with the same equipment characteristics, and reduce the complexity of policy maintenance and management.

The group policy and charging rule processing method, device, and communication system provided by the embodiments of the present invention obtain the group ID or device attribute information of user equipment, and generate group policy and charging rules or trigger The event can effectively improve the policy control efficiency of user equipments in a group or user equipments with the same equipment characteristics, and reduce the complexity of policy maintenance and management. Furthermore, PCC optimization is performed according to the group identifier of the user equipment, which can reduce the signaling interaction between the GW and the PCRF, and achieve the effect of signaling optimization.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit them. Although the present invention has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that: it still Modifications or equivalent replacements can be made to the technical solutions of the present invention, and these modifications or equivalent replacements cannot make the modified technical solutions deviate from the spirit and scope of the technical solutions of the present invention.

Claims (17)

1. A method for processing group policies and charging rules, comprising: Acquiring at least one item of the group identifier or device attribute information of the user equipment; A policy and charging rule or a trigger event is generated according to at least one item of the user equipment group identifier or equipment attribute information. 2. The group policy and charging rule processing method according to claim 1, wherein said obtaining at least one of the group ID or device attribute information of the user equipment comprises: The serving gateway, the packet data network gateway or the gateway GPRS support node acquires at least one of the group identifier or device attribute information carried by the user equipment in the access request message; or The serving gateway, the packet data network gateway or the gateway GPRS support node acquires at least one of the group identifier or device attribute information of the user equipment subscribed to by the home user server or the group subscription database; or The serving gateway, the packet data network gateway or the gateway GPRS support node obtains the identifier of the user equipment, and obtains at least one of the group identifier or device attribute information of the user equipment from the pre-configured user equipment information according to the identifier of the user equipment; Then the generating policy and charging rules or triggering events according to at least one of the group identifier or device attribute information of the user equipment includes: The serving 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 acquired group identifier or device attribute information of the user equipment, and indicates that the policy and charging rule or The scope of application of the trigger event is the group or user group to which the user equipment belongs. 3. The group policy and charging rule processing method according to claim 2, wherein the serving gateway, packet data network gateway or gateway GPRS support node is based on the group identification or device attribute information of the user equipment obtained At least one of generating policy and accounting rules or triggering events includes: The serving gateway, packet data network gateway or gateway GPRS support node formulates corresponding PCC rules or trigger events according to the obtained device attribute information of the user equipment; or The serving gateway, packet data network gateway or gateway GPRS support node obtains the PCC rule or trigger event corresponding to the group ID of the user equipment according to the group ID of the user equipment and the statically configured PCC rule or trigger event. 4. The method for processing group policies and charging rules according to claim 2, wherein the scope of application of the indication policy and charging rules or the triggering event is that the group or user group to which the user equipment belongs includes : In the generated PCC rule or trigger event, add an information element indicating the application scope of the PCC rule or trigger event; or The identifier of the group or user group described by the user equipment is included in the generated PCC rule or trigger event. 5. The method for processing group policies and charging rules according to claim 1, wherein said acquiring at least one of the group ID or device attribute information of the user equipment comprises: The policy and charging rule functional entity obtains at least one of the group identifier or device attribute information carried by the serving gateway, packet data network gateway or gateway GPRS support node in the IP CAN session message; or The policy and charging rule function entity obtains at least one of the group identifier or device attribute information of the user equipment from the service subscription database or the group subscription database according to the identifier of the user equipment; Then the generating group policy and charging rules or triggering events according to at least one of the group identifier or device attribute information of the user equipment 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 obtained user equipment group identifier or device attribute information, and indicates its The scope of application is the group or user group to which the user equipment belongs. 6. The group policy and charging rule processing method according to claim 5, characterized in that: The policy and charging rule functional entity generating a policy and charging rule or triggering an event according to at least one of the obtained user equipment group ID or device attribute information includes: The policy and charging rule functional entity formulates corresponding PCC rules or trigger events according to at least one of the obtained user equipment group identifiers or equipment attribute information; or The policy and charging rule functional entity formulates the group ID or device attribute information of the user equipment according to at least one item of the user equipment group ID or device attribute information and a preconfigured PCC rule or trigger event. At least one of the corresponding PCC rules or trigger events. 7. The group policy and charging rule processing method according to claim 5, characterized in that, the application range indicated in the policy and charging rule or the trigger event is the group or user group to which the user equipment belongs includes : In the generated PCC rule or trigger event, add an information element indicating the application scope of the PCC rule or trigger event; or The identifier of the group or user group described by the user equipment is included in the generated PCC rule or trigger event. 8. The method for processing group policy and charging rules according to claim 5, characterized in that, said generating policy and charging rules or Trigger events include: Allocating the user equipment according to the group identifier of the user equipment or requesting DHCP to allocate an IP address at a group or user equipment group granularity for the user equipment. 9. The method for processing group policies and charging rules according to claim 8, characterized in that, according to the group identifier of the user equipment, the user equipment is assigned or requests DHCP to assign a group to the user equipment. Or the IP address at the user equipment group granularity includes: Allocating or requesting DHCP for the group to which the user equipment belongs or the user equipment under the user group according to the group identifier of the user equipment to allocate a group or user group granular IPv6 address prefix; or Allocating or requesting DHCP for the group to which the user equipment belongs or allocating a public IPv4 address for the user equipment under the user group according to the group identifier of the user equipment. 10. The method for processing group policies and charging rules according to claim 1, wherein the user equipment is the first user equipment, further comprising: when the group identifier or device attribute information of the second user equipment When at least one item is the same as the first user equipment, assign the generated policy and charging rules or trigger events of the group to which the first user equipment belongs to the second user equipment. 11. The group policy and charging rule processing method according to claim 10, characterized in that the method further comprises: Obtain the APN information carried in the PDN connection establishment request of the first user equipment; Then generating a policy and charging rule or a trigger event according to at least one of the group identifier or device attribute information of the user equipment includes: according to at least one of the group identifier or device attribute information of the first user equipment, and the second The APN information carried in the PDN connection establishment request of the user equipment generates a PCC rule or triggers an event; Then, assigning the generated policy and charging rules or triggering events of the group to which the first user equipment belongs to the second user equipment includes: according to the APN information corresponding to the PDN connection initiated by the second user equipment is The second user equipment assigns the generated policy and charging rules or trigger events of the group to which the first user equipment belongs. 12. A device for processing group policies and charging rules, comprising: An acquisition module, configured to acquire at least one item of the user equipment group identifier or equipment attribute information; A rule generating module, configured to generate policy and charging rules or trigger events according to at least one item of the user equipment group identifier or equipment attribute information. 13. The device for processing group policies and charging rules according to claim 12, wherein the acquiring module comprises: A first obtaining unit, configured to obtain at least one of the group identifier or device attribute information carried by the user equipment in the access request message; or Used to obtain at least one of the group identifier or device attribute information of the user equipment subscribed by the home user server or the group subscription database; or Obtaining the identifier of the user equipment, acquiring at least one of the group identifier or device attribute information of the user equipment from pre-configured user equipment information according to the identifier of the user equipment; The rule generation module includes: A first rule generation unit, configured to generate a policy and charging rule or a trigger event according to at least one of the acquired group identifier or device attribute information of the user equipment, and indicate the application of the policy and charging rule or the trigger event The scope is the group or user group to which the user equipment belongs. 14. The device for processing group policies and charging rules according to claim 12, wherein the acquiring module comprises: The second obtaining unit is used to obtain at least one of the group identification or device attribute information carried by the IP CAN session message; or Obtaining at least one of the group identifier or device attribute information of the user equipment from the service subscription database or the group subscription database according to the identifier of the user equipment; The rule generation module includes: The second rule generating unit is configured to generate a policy and charging rule or a trigger event according to at least one of the acquired group identifier or device attribute information of the user equipment, and indicate in the policy and charging rule or trigger event Its scope of application is the group or user group to which the user equipment belongs. 15. The device for processing group policies and charging rules according to claim 12, wherein the user equipment is a first user equipment, wherein the device for processing group policies and charging rules further comprises: An optimization processing module, configured to assign the generated first user equipment to the second user equipment when at least one item of group identifier or equipment attribute information of the second user equipment is the same as that of the first user equipment The policy and charging rules or trigger events of the group to which it belongs. 16. A communication system, comprising the group policy and charging rule processing device according to any one of claims 12-15. 17. The communication system according to claim 16, wherein the group policy and charging rule processing device is set in a serving gateway, a packet data network gateway, a gateway GPRS support node or a policy and charging rule functional entity.

Images