WO2011026440A1 - Procédé, dispositif et système de communication permettant de gérer des politiques et des règles de taxation de groupe - Google Patents

Procédé, dispositif et système de communication permettant de gérer des politiques et des règles de taxation de groupe 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
English (en)
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/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/62—Arrangements 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/64—On-line charging system [OCS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/765—Linked or grouped accounts, e.g. of users or devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/765—Linked or grouped accounts, e.g. of users or devices
    • H04M15/7652—Linked or grouped accounts, e.g. of users or devices shared by users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/77—Administration or customization aspects; Counter-checking correct charges involving multiple accounts per user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/70—Administration or customization aspects; Counter-checking correct charges
    • H04M15/77—Administration or customization aspects; Counter-checking correct charges involving multiple accounts per user
    • H04M15/771—Administration or customization aspects; Counter-checking correct charges involving multiple accounts per user per terminal or location, e.g. mobile device with multiple directory numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing

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

La présente invention se rapporte à un procédé, à un dispositif et à un système de communication permettant de gérer des politiques et des règles de taxation de groupe. Le procédé de gestion de politiques et de règles de taxation de groupe consiste : à obtenir au moins un de l'identifiant de groupe ou des informations d'attributs d'équipement d'un équipement d'utilisateur; à générer des politiques et des règles de taxation ou un événement déclencheur en accord avec au moins un de l'identifiant de groupe ou des informations d'attributs d'équipement de l'équipement d'utilisateur. Le dispositif comprend : un module d'obtention pour obtenir au moins un de l'identifiant de groupe ou des informations d'attributs d'équipement de l'équipement d'utilisateur; un module de génération de règles pour générer les politiques et les règles de taxation ou l'événement déclencheur en accord avec au moins un de l'identifiant de groupe ou des informations d'attributs d'équipement de l'équipement d'utilisateur. La présente invention se rapporte également au système de communication comprenant le dispositif susmentionné. Avec le procédé, le dispositif et le système de communication selon l'invention, l'efficacité du contrôle des politiques peut être améliorée, et la complexité de la maintenance et de la gestion des politiques est réduite.
PCT/CN2010/076617 2009-09-04 2010-09-03 Procédé, dispositif et système de communication permettant de gérer des politiques et des règles de taxation de groupe WO2011026440A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910091997.5 2009-09-04
CN2009100919975A CN102014343A (zh) 2009-09-04 2009-09-04 群组策略与计费规则处理方法、装置以及通信系统

Publications (1)

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

Family

ID=43648904

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/076617 WO2011026440A1 (fr) 2009-09-04 2010-09-03 Procédé, dispositif et système de communication permettant de gérer des politiques et des règles de taxation de groupe

Country Status (2)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019104358A3 (fr) * 2017-11-27 2019-09-19 Cisco Technology, Inc. Procédés et appareil d'établissement d'une session de groupe pour des abonnés associés à un groupe, dans un réseau mobile

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102238512B (zh) * 2010-04-29 2015-11-25 中兴通讯股份有限公司 机器类通信mtc的策略应用方法及策略和计费执行实体
TWI501603B (zh) * 2011-12-19 2015-09-21 Ind Tech Res Inst 在機器類型通信網路中對機器類型通信裝置分組之方法以及通信方法
CN103179616A (zh) * 2011-12-20 2013-06-26 华为技术有限公司 策略与计费规则功能模块选择方法及系统、设备
CN103828405B (zh) * 2012-09-24 2018-06-19 华为技术有限公司 群组控制方法、移动性管理实体和用户设备
KR20140045215A (ko) 2012-10-08 2014-04-16 삼성전자주식회사 그룹 기반 연결 설정 방법 및 장치
WO2015054823A1 (fr) * 2013-10-15 2015-04-23 华为技术有限公司 Procédé de contrôle d'accès d'un groupe à un réseau sans fil, et appareil correspondant
CN104581612B (zh) * 2013-10-28 2019-04-12 华为终端有限公司 M2m设备的控制方法、签约数据库及移动管理设备
CN104683956B (zh) * 2013-11-27 2018-01-26 普天信息技术研究院有限公司 QoS控制方法和系统
WO2016054777A1 (fr) 2014-10-08 2016-04-14 华为技术有限公司 Procédé, équipement et système de téléchargement de trafic d'arrière-plan
CN107580290B (zh) * 2016-06-30 2021-04-06 阿尔卡特朗讯公司 一种用于实现mtc 组消息传送的方法与设备
CN113938845B (zh) * 2018-05-21 2023-07-18 华为技术有限公司 上下文管理方法及装置
CN111385790B (zh) * 2018-12-27 2023-04-07 中国电信股份有限公司 用户访问控制方法、系统和计算机可读存储介质
CN113395670B (zh) * 2020-03-12 2022-10-04 中国电信股份有限公司 策略的控制方法、装置、系统和计算机可读存储介质
CN113556693B (zh) * 2021-03-12 2022-09-16 中国电信股份有限公司 物联网策略控制方法、数据网网关、存储介质及电子设备

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 (zh) * 2006-08-14 2008-02-20 华为技术有限公司 一种在演进网络中管理用户策略计费控制签约信息的方法
CN101345633A (zh) * 2007-07-10 2009-01-14 华为技术有限公司 一种应用的策略控制方法及装置
CN101355489A (zh) * 2007-07-23 2009-01-28 中兴通讯股份有限公司 基于动态主机配置协议前缀代理的用户管理方法

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 (zh) * 2006-08-14 2008-02-20 华为技术有限公司 一种在演进网络中管理用户策略计费控制签约信息的方法
CN101345633A (zh) * 2007-07-10 2009-01-14 华为技术有限公司 一种应用的策略控制方法及装置
CN101355489A (zh) * 2007-07-23 2009-01-28 中兴通讯股份有限公司 基于动态主机配置协议前缀代理的用户管理方法

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019104358A3 (fr) * 2017-11-27 2019-09-19 Cisco Technology, Inc. Procédés et appareil d'établissement d'une session de groupe pour des abonnés associés à un groupe, dans un réseau mobile
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 (zh) 2011-04-13

Similar Documents

Publication Publication Date Title
WO2011026440A1 (fr) Procédé, dispositif et système de communication permettant de gérer des politiques et des règles de taxation de groupe
EP3634016B1 (fr) Procédés et dispositifs de facturation
JP6164219B2 (ja) 移動通信システム、制御装置、通信制御方法、及びプログラム
CN101977416B (zh) 一种mtc设备的过载控制方法和系统
KR102048882B1 (ko) 무선 통신 시스템에서 ｐｃｅｆ 및 ｐｃｒｆ를 선택하는 방법 및 시스템
EP2453609A1 (fr) Procédé, dispositif et système de communication destinés à facturer de groupe
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 (fr) Procédé destiné à un groupe de communication de type machine sélectionnant une passerelle de réseau de données par paquets, et élément de réseau de gestion de mobilité
WO2011134329A1 (fr) Procédé et système pour transmettre des paquets de données de petite taille
WO2012094957A1 (fr) Procédé et système pour effecteur une gestion de mobilité sur un terminal mtc
CN109802839B9 (zh) 一种计费方法、装置及系统
WO2011098022A1 (fr) Procédé, système et dispositif de gestion de session basés sur une application de machine à machine (m2m)
WO2011047589A1 (fr) Procédé et appareil d'établissement de connexion au réseau, procédé et système d'élaboration de stratégie de commande de politique et de facturation (pcc)
WO2014166294A1 (fr) Méthode et appareil de sélection de serveur de service de proximité, et méthode et appareil d'inscription d'utilisateur
KR20140045215A (ko) 그룹 기반 연결 설정 방법 및 장치
WO2011020435A1 (fr) Procédé et système permettant de transmettre des paquets de données au niveau d'un serveur d'application de machine à machine (m2m)
EP3235173B1 (fr) Commande de politique et de facturation pour des groupes
WO2013135213A1 (fr) Procédé de traitement de session tdf et pcrf
WO2016019559A1 (fr) Appareil, système, et procédé d'identification d'équipement d'utilisateur de réseau partagé
CN102177757B (zh) 一种实现注册的方法、装置和系统
KR20130127368A (ko) 이동통신망에서의 그룹 기반 폴리싱 방법 및 장치
WO2013159605A1 (fr) Système, dispositif et procédé de communication
WO2011134321A1 (fr) Procédé et système d'envoi de politique pour communication de type machine
WO2013075337A1 (fr) Procédé de gestion de filtres basé sur une interface gx, et pgw et pcrf correspondantes

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