WO2011134317A1 - 机器类通信的策略应用方法及策略和计费执行实体 - Google Patents

机器类通信的策略应用方法及策略和计费执行实体 Download PDF

Info

Publication number
WO2011134317A1
WO2011134317A1 PCT/CN2011/071647 CN2011071647W WO2011134317A1 WO 2011134317 A1 WO2011134317 A1 WO 2011134317A1 CN 2011071647 W CN2011071647 W CN 2011071647W WO 2011134317 A1 WO2011134317 A1 WO 2011134317A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
policy
pcef
session
pcrf
Prior art date
Application number
PCT/CN2011/071647
Other languages
English (en)
French (fr)
Inventor
曲爱妍
支春霞
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US13/695,282 priority Critical patent/US8885568B2/en
Priority to EP11774308.8A priority patent/EP2566197A4/en
Publication of WO2011134317A1 publication Critical patent/WO2011134317A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Definitions

  • the present invention relates to communication or, in particular, to a policy application method and strategy for machine type communication (MTC). Billing execution entity. Background technique
  • the 3GPP wireless core network includes a General Packet Radio Service (GPRS) network, an Evolved Packet System (EPS) network, and a Universal Mobile Telecommunications System (UMTS).
  • GPRS General Packet Radio Service
  • EPS Evolved Packet System
  • UMTS Universal Mobile Telecommunications System
  • Figure 1 shows a schematic diagram of an emergency call for accessing an IP Multimedia Subsystem (IMS) by means of SAE and UMTS through a device-based communication MTC User Equipment (UE).
  • IMS IP Multimedia Subsystem
  • UE User Equipment
  • the solid line indicates signaling, and the dotted line indicates the user's IP channel.
  • the UE can also be called a mobile station (Mobile Station, referred to as MS).
  • MS mobile station
  • the MTC UE accesses the MTC through EPS or UMTS.
  • the main network elements involved in the MTC Server include: the network element of the EPS network part, the network element of the UMTS network part, and the MTC Server.
  • the MTC UE can also be called the MTC device.
  • the PCC Policy and Charging Control framework is implemented.
  • the PCC architecture is a functional framework that can be applied to multiple access technologies.
  • the PCC architecture can be applied to UMTS, GSM/GSM Data Enhanced Evolution (EDGE) radio access networks, Interworking wireless office i or network (I-WLAN) and EPS.
  • EDGE GSM/GSM Data Enhanced Evolution
  • I-WLAN Interworking wireless office i or network
  • EPS Interworking wireless office i or network
  • PCC mainly implements two functions of policy control and billing.
  • Figure 2 is a schematic diagram of the existing PCC component architecture. The following describes the logical functional entities and their interface functions in the PCC architecture shown in Figure 2. as shown in picture 2:
  • AF an access point used to provide business applications.
  • the network resources used by these business applications require dynamic policy control.
  • AF transmits related service information.
  • Policy Control and Charging Rules Functional Entity PCRF, Policy and Charging Rules
  • the PCRF accepts the negotiation; if not, the PCRF rejects the negotiation and gives the business parameters acceptable to the PCRF upon feedback.
  • the AF can then return these parameters to the user equipment (UE, User Equipment) caravan where the interface between AF and PCRF is the Rx interface.
  • UE User Equipment
  • the PCRF is the core of the PCC and is responsible for policy decision making and billing rules.
  • the PCRF provides network control rules based on service data flows, including traffic data flow detection, Gating Control, Quality of Service (QoS) control, and data flow based charging rules.
  • the PCRF sends its policy and charging rules to the Policy and Control Enforcement Function (PCEF).
  • PCEF Policy and Control Enforcement Function
  • the basis for the PCRF to formulate policies and charging rules includes: business-related information obtained from AF, user policy charging control related to policy control and charging obtained from a user subscription database (subscriber profile) Signing information, and information about the bearer-related network obtained from the PCEF through the Gx interface.
  • the PCEF is usually located in the gateway (GW, Gate- Way) and performs the policy and charging rules established by the PCRF on the carrier.
  • the PCEF detects the service data flow according to the service data flow filter in the rule sent by the PCRF, and then performs the policy and charging rule defined by the PCRF for the service data flow; when the bearer is established, the PCEF performs the rule according to the PCRF.
  • Resource allocation, and performing gating control according to the information provided by the AF at the same time, the PCEF triggers reporting the event occurring on the bearer network according to the event subscribed by the PCRF; according to the charging rule sent by the PCRF, the PCEF performs the corresponding service operation of the service data flow,
  • the billing can be either online charging or offline charging.
  • PCEF In the case of online charging, the PCEF needs to perform credit management together with the Online Charging System (OCS); when offline charging, the related calculation between the PCEF and the Offline Charging System (OFCS) Fee information.
  • OCS Online Charging System
  • OFCS Offline Charging System
  • the interface between the PCEF and the PCRF is a Gx interface
  • the interface between the PCEF and the OCS is a Gy interface
  • the interface between the PCEF and the OFCS is a Gz interface.
  • PCEFs are generally located on gateways of the network, such as the Packet Data Network Gateway (PDN-GW) of the EPS, the GPRS Gateway Support Node (GGSN) in the General Packet Radio Service (GPRS), and the Internet of the Internet ( I-WLAN, Interworking WLAN), such as Packet Data Gateway (PDG).
  • PDN-GW Packet Data Network Gateway
  • GGSN General Packet Radio Service
  • I-WLAN, Interworking WLAN such as Packet Data Gateway (PD
  • the Bearer Binding and Event Reporting Function is usually located in the Access Network Gateway. ⁇ mouth When the user equipment accesses the EPS through the E-UTRAN, the Serving Gateway S-GW and the P-GW use the Proxy Mobile Internet Protocol version 6 protocol, the S-GW There is a BBERF. When the user equipment accesses through the trusted non-3GPP access network, the BBERF also exists in the trusted non-3GPP access gateway.
  • the user subscription database (user database) stores user policy charging control subscription information related to policy control and charging.
  • the interface between the user database and the PCRF is the Sp interface.
  • OCS and PCEF jointly complete the control and management of user credit under online charging mode.
  • an MTC device accesses an MTC server.
  • an IP-CAN session must be established through EPS or UMTS.
  • the policy enforcement entity in the EPS or UMTS system establishes a Diameter session with the PCRF for each IP-CAN session.
  • the policy enforcement entity reports the access information of the MTC device to the PCRF, and the PCRF sends the policy to the policy enforcement entity.
  • MTC devices tend to be numerous and need to be online for a long time.
  • a primary object of the present invention is to provide a method and apparatus for applying a machine type communication MTC to at least solve the problem.
  • a policy application method for a machine type communication MTC including: establishing an Internet Protocol-Connected Access Network IP-CAN session process in an MTC device attached to a policy and charging execution entity PCEF
  • the PCEF locally obtains a group policy corresponding to the device group to which the MTC device belongs; the group policy applies to the IP-CAN session.
  • the PCEF locally acquires the group policy corresponding to the device group to which the MTC device belongs, the PCEF determines the group identifier of the group to which the MTC device belongs, and the PCEF searches for the group policy corresponding to the group identifier in the first corresponding relationship saved locally.
  • the first correspondence relationship is a correspondence between the group identifier and the group policy.
  • the determining, by the PCEF, the group identifier of the group to which the MTC device belongs includes: acquiring the group identifier carried by the IP-CAN session request message sent by the MTC device.
  • the determining, by the PCEF, the group identifier of the group to which the MTC device belongs includes: acquiring a user identifier of the MTC device carried in the IP-CAN session request message sent by the MTC device; searching for a group corresponding to the user identifier in the locally saved second correspondence relationship The identifier, wherein the second correspondence is a correspondence between the group label i and only the user label i.
  • the method further includes: the PCEF locally recording the correspondence between the group policy and the IP-CAN session.
  • the PCEF requests a group policy from the PCRF by establishing a Diameter session connection with the PCRF; the PCRF is based on the service information acquired from the application function entity AF, the user subscription information obtained from the user subscription database, and the user identifier obtained from the PCEF.
  • the group ID is used to formulate a group policy
  • the group policy is delivered to the PCEF through the Diameter session connection.
  • the PCEF acquires and saves the group policy
  • the Diameter session connection is disconnected.
  • the method further includes: the PCEF receiving the re-established group policy from the policy and charging rule function entity PCRF, where the re-established group policy and the device to which the MTC device belongs
  • the PCEF updates the original group policy corresponding to the device group to which the MTC device belongs by using the re-established group policy; and applies the updated group policy to all IP-CAN sessions corresponding to the device group to which the MTC device belongs.
  • the method further includes: the PCRF receiving the message from the application function entity AF, where the message carries the service information corresponding to the device group; and the PCRF acquires the device from the PCEF.
  • the corresponding IP-CAN session status of the group; the PCRF re-forms the group policy for the device group based on the service information and the IP-CAN session status, and delivers the group policy to the PCEF.
  • the method further includes: the PCRF receiving the updated subscription document request sent by the user subscription database SPR, where the updated subscription document request carries the updated information corresponding to the device group Contract document; PCRF obtained from PCEF The IP-CAN session status corresponding to the device group; the PCRF re-defines the group policy for the device group according to the updated subscription document and the IP-CAN session status, and delivers the group policy to the PCEF.
  • a policy and charging enforcement entity PCEF comprising: an obtaining module, configured to be locally located during an Internet Protocol-Connected Access Network IP-CAN session established by an MTC device attached to a PCEF
  • the set storage module obtains the group policy corresponding to the device group to which the MTC device belongs, and triggers the application module; the application module is set to apply the group policy to the IP-CAN session; and the storage module is set to save the device group attached to the PCEF.
  • an obtaining module configured to be locally located during an Internet Protocol-Connected Access Network IP-CAN session established by an MTC device attached to a PCEF
  • the set storage module obtains the group policy corresponding to the device group to which the MTC device belongs, and triggers the application module; the application module is set to apply the group policy to the IP-CAN session; and the storage module is set to save the device group attached to the PCEF.
  • Group policy configured to be locally located during an Internet Protocol-Connected Access Network IP-CAN session established by an MTC device attached to a PCEF
  • the PCEF further includes: a requesting module, configured to: when the PCEF does not locally obtain the group policy corresponding to the device group to which the MTC device belongs, request the group policy from the policy and charging rule function entity PCRF, and trigger
  • the saving module is configured to save the requested group policy to the storage module and trigger the application module; the application module is further configured to apply the requested group policy to the IP-CAN session.
  • the PCEF further includes: a receiving module, configured to receive a re-established group policy from the policy and charging rule function entity PCRF, and trigger an update module, where the re-established group policy and the device group to which the MTC device belongs Corresponding; the update module is configured to update the original group policy corresponding to the device group to which the MTC device belongs in the re-established group policy, and trigger the application module; the application module is further configured to apply the updated group policy to All IP-CAN sessions corresponding to the device group to which the MTC device belongs.
  • the PCEF locally saves the group policy of the device group attached to the PCEF.
  • the PCEF When the MTC device in a certain device group establishes an IP-CAN session, the PCEF locally obtains the group policy corresponding to the device group to which the device belongs. And applied to the corresponding IP-CAN session, in the process of establishing an IP-CAN session for each MTC device in the prior art, the PCRF needs to apply to the PCRF for the policy applied to the IP-CAN session, resulting in network resources.
  • the wasteful problem shortens the time for applying the MTC strategy, saves network resources, and improves network resource utilization.
  • FIG. 1 is a schematic diagram of an MTC device access system according to the related art
  • 2 is a schematic diagram of a PCC architecture according to the related art
  • FIG. 3 is a flowchart of a method for applying an MTC policy according to an embodiment of the present invention
  • FIG. 4 is a flowchart of a PCEF local acquisition group policy according to Embodiment 2 of the present invention
  • FIG. 1 is a schematic diagram of an MTC device access system according to the related art
  • 2 is a schematic diagram of a PCC architecture according to the related art
  • FIG. 3 is a flowchart of a method for applying an MTC policy according to an embodiment of the present invention
  • FIG. 4 is a flowchart of a PCEF local acquisition group policy according to Embodiment 2 of the present invention
  • FIG. 1 is a schematic diagram of an MTC device access system according to the related art
  • 2 is a schematic diagram of a PCC architecture according to the related art
  • FIG. 3 is a flowchart of
  • FIG. 5 is a flowchart of a PCEF request group policy according to Embodiment 3 of the present invention
  • FIG. 6 is a flowchart of a BBERF request group policy according to Embodiment 3 of the present invention
  • FIG. 7 is a fourth embodiment of the present invention.
  • FIG. 8 is a flowchart of a group policy application according to Embodiment 5 of the present invention
  • FIG. 9 is a flowchart of group policy update according to Embodiment 6 of the present invention
  • FIG. 10 is a group according to Embodiment 7 of the present invention
  • FIG. 11 is a block diagram of a first preferred PCEF structure according to an eighth embodiment of the present invention
  • Embodiment 13 is a block diagram of a first preferred PCEF structure according to an eighth embodiment of the present invention.
  • BEST MODE FOR CARRYING OUT THE INVENTION
  • the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.
  • Embodiment 1 This embodiment provides a policy application method for a machine type communication MTC, which may be, but is not limited to, applied to the PCC system shown in FIG. 2, and FIG. 3 is an application method of the MTC policy according to the embodiment of the present invention.
  • the method includes: Step S302, establishing an MTC device attached to a policy and charging execution entity PCEF
  • Step S304 Apply the group policy to the IP-CAN session.
  • the PCEF in the process of establishing an IP-CAN session bearer for each MTC device, the PCEF needs to apply to the PCRE for the corresponding policy of the device, and applies to the IP-CAN session requested by the device, but belongs to the same MTC device group.
  • Many MTC device policy rules are the same. For example, for the same service, all MTC devices in the group use the same QoS rules. Therefore, the root cause of the inefficiency of existing MTC policy applications is: For the same group
  • the PCRF sends the same policy rule multiple times.
  • the foregoing method provided in this embodiment saves the group policy of the MTC device group that is attached to the PCEF in the local area of the PCEF, and locally searches for and acquires the device group to which the MTC device belongs in the process of establishing the IP-CAN session of the MTC device.
  • the group policy is applied to the IP-CAN session that is requested to be established, so that the PCEF does not need to apply for the policy of the MTC device to the PCRF every time during the session of the MTC to establish an IP-CAN, thereby saving the application time of the policy. , which saves network resources and improves the utilization of network resources.
  • the PCEF may be, but is not limited to, configuring the group policy of the MTC device group locally by: (1) statically configuring the group policy, that is, the network device administrator manually configures each MTC device attached to the PCEF locally. Group policy.
  • Dynamic application/maintenance group policy that is, in the process of establishing an IP-CAN session by the first MTC device attached to an MTC device group of the PCEF, the PCEF requests the group policy of the device group from the PCRF. After receiving the group policy of the device group, it is saved locally on the PCEF. In the above manner, the PCEF implements the local saving of the group policy of the MTC device group attached to itself, so that the MTC device that belongs to the MTC device group after the IPC is not required to apply to the PCRF for each MTC device in the process of establishing the IP-CAN. Policy rules that simplify the existing MTC device policy application process.
  • the PCEF may also locally record the correspondence between the group policy of the MTC device group and the IP-CAN session.
  • the PCEF can apply the changed group policy to all corresponding ones according to the corresponding relationship.
  • the IP-CAN session ensures the normal application of the MTC device.
  • Embodiment 2 In the first embodiment, how the PCEF implements the local saving and maintenance of the group policy is described. In this embodiment, the PCEF obtains the group policy corresponding to the device group to which the MTC device belongs locally.
  • Step S402 The PCEF determines a group identifier of a group to which an MTC device requesting to establish an IP-CAN session belongs;
  • Step S404 PCEF is Find the group policy corresponding to the group ID in the mapping between the locally saved group ID and the group policy.
  • the PCEF may perform local search by identifying the group identifier to which the MTC device belongs, which may be, but is not limited to, during implementation. Identify the group ID in the following ways:
  • the MTC device carries the group identifier of the device group in the IP-CAN session establishment request message, and after receiving the P-CAN session establishment request message, the PCEF parses the group identifier.
  • the MTC device carries the user identifier or the device identifier in the IP-CAN session establishment request message, and the PCEF locally maintains the correspondence between the user identifier and the group identifier, or maintains the correspondence between the device identifier and the group identifier, and the PCEF receives the corresponding relationship.
  • the user identifier or the device identifier of the device is parsed, and the group identifier i corresponding to the parsed user label i or the device label i is searched for in the corresponding relationship.
  • the PCEF After the PCEF determines the group identifier, the PCEF searches for the group policy in the corresponding relationship between the locally saved group identifier and the group policy. Through the above process, the PCEF implements a local search of the group policy.
  • the search method provided in this embodiment replaces the technical solution that the PCEF requests the policy from the PCRF every time the MTC device establishes an IP-CAN session.
  • the PCEF local search not only does not need to occupy the network resources for communication between the PCEF and the PCRF, but also the search time is much lower than the message transmission, reception, processing and waiting time consumed by the existing request policy.
  • Embodiment 3 The first embodiment and the second embodiment respectively describe how the PCEF implements the local save group policy and the local search group policy.
  • the group policy of the device group needs to be added locally.
  • This embodiment provides a technical solution for solving this requirement.
  • the PCEF does not locally obtain the group policy corresponding to the device group to which the MTC device belongs, request the group policy from the PCRF, save it locally, and ⁇ A set of policies is applied to the IP-CAN session.
  • the request for group policy can be implemented by the following manner: FIG.
  • Step S502 The PCEF requests a group policy from the PCRF by establishing a Diabet session connection with the PCRF.
  • Step S504 The PCRF obtains the service information obtained from the application function entity AF from the user subscription database.
  • the user subscription information and the user ID or group ID obtained from the PCEF are used to formulate a group policy, and the group policy is delivered to the PCEF through a Diameter session connection.
  • the BBERF is used in the PCC system shown in FIG.
  • the BBERF also implements the local saving of the group policy and the local search of the group policy according to the method provided in the foregoing embodiment, which may be, but is not limited to, implementing the group policy by the following manner.
  • Figure 6 is a flowchart of a BBERF request group policy according to Embodiment 3 of the present invention.
  • Step S602 The BBERF requests a group policy from the PCRF by establishing a Diameter session connection with the PCRF;
  • Step S604 PCRF is based on Forming a group policy from the service information obtained by the application function entity AF, the user subscription information obtained from the user subscription database, and the user identifier or group identifier obtained from the PCEF, and delivering the group policy to the BBERF through the Diameter session connection;
  • Step S606 BBERF After saving the group policy, sending an IP-CAN session establishment request to the PCEF;
  • the PCEF requests the group policy from the PCRF.
  • step S610 the PCRF sends the group policy specified in the step S604 to the PCEF, so that the group policy saved by the BBERF is synchronized with the group policy saved by the PCRE.
  • the PCEF applies to the PCRF for the group policy of the MTC device group, thereby realizing the dynamic addition of the group policy locally. .
  • the Diameter session connection established for applying the group policy may be disconnected. In the prior art, the Diameter session connection established for applying for group policy needs to be maintained at all times.
  • the method of disconnecting the Diameter session connection does not need to always occupy the communication link between the PCEF and the PCRF, thereby further saving network resources.
  • Embodiment 4 the MTC Device 1 and the MTC Device 2 belonging to the same device group are respectively configured to establish an IP-CAN session.
  • the PCEF and the PCRF acquire a group policy.
  • the PCEF does not interact with the PCRF.
  • the group policy obtained by the MTC Device 1 directly binds the session of the MTC Device 2.
  • the IP-CAN session established by MTC Device 1 and MTC Device 2 does not use BBERF.
  • Step S701 In the process of requesting the establishment of the IP-CAN session 1 by the MTC Device 1, sending a request to the PCEF to establish an IP address - a CAN session message, in which the user identifier 1 of the MTC Device 1 or the group label K of the MTC Device 1 is carried in the message; in step S702, the PCEF sends an IP-CAN session establishment indication message to the PCRF, in the IP-CAN session establishment indication message. Carry the user ID 1 or group ID. This message establishes a Diameter session between PCEF and PCRF, denoted as Gx Session 1.
  • the group identifier is optional.
  • Step S703 The PCRF sends a subscription document request to the user database, where the subscription document request carries the user identifier 1 or the group identifier.
  • the group identification information is optional. If the group identifier is not carried in the request message, the user database is responsible for interpreting the group identifier corresponding to the MTC Device 1.
  • step S704 the user database returns the group subscription information of the MTC Device according to the group identifier or the user identifier 1;
  • step S705 PCRF Group policy is based on group signing information, access information, and network policies.
  • the PCRF sends the group policy to the PCEF through the IP-CAN session confirmation message, where the group policy includes the group policy PCC rule and the group policy QoS rule.
  • Step S706 the PCEF saves the correspondence between the group policy and the group identifier and the IP-CAN session; Step 4 Poly S707, PCEF execution strategy.
  • the gateway where the PCEF is located returns a response to the MTC Device 1 to establish an IP-CAN session message.
  • Step S708 in the process of requesting the establishment of the IP-CAN session 2 by the MTC Device2, sending a request to the PCEF to establish an IP-CAN session message, requesting to establish an IP-CAN session.
  • the message carries the user ID 2 or group ID of the MTC Device 2.
  • the MTC Device 1 and the MTC Device 2 belong to the same group. Therefore, the group identifier is the same.
  • the PCEF applies the group policy to the IP-CAN session 2, and updates the correspondence between the group identifier and the IP-CAN session.
  • the PCEF executes the policy.
  • the gateway where the PCEF is located returns a response to the MTC Device2 to establish an IP-CAN session message. In the above embodiment, the PCEF is only used when the first device in the group establishes an IP-CAN request.
  • the PCRF obtains the group policy.
  • the PCEF directly applies the group policy to the IP-CAN session and no longer requests the group policy from the PCRF.
  • the PCEF sends an IP-CAN session establishment request to the PCRF to carry the group identifier, or may not carry it. If not carried, the PCRF or user database needs to be able to interpret the group ID.
  • Embodiment 5 the MTC Device 1 and the MTC Device 2 of the same user group are in the process of establishing an IP-CAN session respectively.
  • the BBERF and the PCEF respectively interact with the PCRF to obtain the group policy QoS rules and groups. Policy PCC rules.
  • the BBERF and the PCEF do not interact with the PCRF.
  • FIG. 8 is a flowchart of a group policy application according to Embodiment 5 of the present invention. As shown in FIG. 8, the process includes: Step S801: Send a request to the BBERF during the request of the MTC Device 1 to establish an IP-CAN session 1. The message of the IP-CAN session is set up, and the message carries the user identifier of the MTC Device 1, the PDN identifier, or the group identifier of the user group to which the MTC Device 1 belongs.
  • Step S802 The BBERF sends a gateway control session establishment message to the PCRF.
  • the gateway control session establishment message carries a user identifier 1, a PDN identifier, or a group identifier.
  • the message establishes a Diameter session (gateway control session) between the BBERF and the PCRF, denoted as Gxx session 1; step S803, the PCRF sends a subscription document request to the user database, and the subscription document request carries the user identifier 1, the PDN identifier or The group identifier is determined.
  • the user database returns the group subscription information according to the user identifier 1 and the group identifier. Further, the user database may send the group user ID of the group to which the MTC Device 1 belongs to the PCRF. When the IP-CAN session is established by the subsequent Device in the information group, the PCRF may not interact with the user database.
  • Step S805 the PCRF signs the group according to the group. Information, access information, and network policy development group policy.
  • the PCRF sends the group policy to the BBERF.
  • the group policy here is a group policy QoS rule; step S806, the BBERF saves the group policy; step S807, the BBERF executes the group policy QoS rule.
  • the gateway where the BBERF is located sends a message requesting the establishment of the IP-CAN session 1 to the gateway where the PCEF is located, and the message carries the user identifier 1 or the group identifier of the MTC Device 1;
  • Step S 808 the PCEF sends an IP-CAN session establishment indication message to the PCRF, the message It carries the user ID 1 or group ID.
  • This message establishes a Diameter session between PCEF and PCRF, denoted as Gx session 1; Step S809, the PCRF associates Gxx Session 1 and Gx Session 1 according to the group identifier. Further, the policy executed in step S805 (except QoS rule 1) is sent to the PCEF; in step S810, the PCEF saves the group policy QoS rule and the group policy PCC rule; step S811, the PCEF executes the policy.
  • the gateway where the PCEF is located responds to the gateway where the BBERF is located to establish an IP-CAN session 1 message; Step S812, the gateway where the BBERF is located returns a response to establish an IP-CAN session 1 message; Step S813, in the process of requesting the establishment of the IP-CAN session 2 by the MTC Device2, The BBERF sends a message requesting to establish an IP-CAN session, and the message carries the user ID 2 or group identifier of the MTC Device 2.
  • the group label K ⁇ is the same; in step S814, the BBERF sends a gateway control session setup message to the PCEF, where the gateway control session setup message carries the user identifier 2 or the group identifier; 815: The PCEF does not perform a policy request to the PCRF, directly applies the locally saved group policy to the IP-CAN session 2, and updates the correspondence between the group identifier and the IP-CAN session. In step S816, the PCEF executes the policy.
  • the gateway where the PCEF is located responds to the gateway where the BBERF is located to establish an IP-CAN session 2 message, carrying the IP Address2; Step S817, the gateway where the BBERF is located returns a response to establish an IP-CAN session 2 message.
  • the PCEF obtains the group policy from the PCRF only when the first device in the group establishes the IP-CAN 7 load request. When other devices in the group establish the IP-CAN load, the PCEF directly applies the group policy to the IP- The CAN session no longer requests group policy from the PCRF.
  • Embodiment 6 This embodiment describes a tampering process of an IP-CAN session triggered by the service access of the MTC Device 1 and the MTC Device 2 after the IP-CAN session established in the fourth embodiment or the fifth embodiment. It is possible for the AF to provide the service group information to the PCRF, and the service group information can be applied to the group. All equipment. Therefore, the PCRF can match the service group information according to the IP address segment, the group identifier, or the user number segment. FIG.
  • Step S901 The AF provides a service group information to the PCRF, and the service group information matches the service flow according to the corresponding
  • the matching of the MTC device group may be defined as matching according to the IP address segment, the group identifier or the user number segment;
  • Step S902 the PCRF saves the service information provided by the AF, and sends a response message to the AF;
  • Step S903, the PCRF sends the packet to the PCEF.
  • Step S904 the PCEF returns the IP-CAN session response message of the device in the group to the PCRF, where the message carries the IP-CAN session status in the group;
  • the 7-time group policy is processed directly by the PCEF and is not reported to the PCRF. If the PCRF needs to formulate a group policy according to the IP-CAN session conditions in the group, it needs to request the PCEF for the IP-CAN session in the group. Steps S903 to S904 complete this function.
  • Step S905 the PCRF performs policy decision according to the service information, and formulates a group policy, including a group policy QoS rule and a group policy PCC rule.
  • Step S906 the PCRF sends a group policy QoS rule to the BBERF.
  • Step S907 the BBERF updates the local group policy. QoS rules, and perform resource reservation procedures for existing IP-CAN sessions in the group. The BBERF sends an acknowledgement message to the PCRF.
  • step S908 the PCRF sends a group policy PCC rule to the PCEF.
  • step S909 the PCEF updates the local group policy PCC rule, and performs a resource reservation process for the existing IP-CAN session in the group. The PCEF returns a confirmation message to the PCRF.
  • Embodiment 7 This embodiment describes the modification of the IP-CAN session triggered after the IP-CAN session established according to the first embodiment or the second embodiment and after the user accesses the service through the third embodiment.
  • FIG. 10 is a flowchart of group policy update according to Embodiment 7 of the present invention. As shown in FIG. 10, the process includes: In step S1001, the user database detects that the subscription data of the user group changes. In step S1002, the SRP sends a group subscription update request to the PCRF, where the message carries the changed subscription document.
  • Step S1003 the PCRF saves the updated subscription document data, and Sending a confirmation message to the user database;
  • Step S1004 the PCRF sends an intra-group device IP-CAN session request message to the PCEF, where the message carries the group identifier;
  • Step S1005 the PCEF returns the IP-CAN session response message of the device in the group to the PCRF, message The IP-CAN session is carried in the group; in step S1006, the PCRF makes a policy decision according to the updated subscription document. If it is hosted by default
  • the PCRF will re-define the QoS rules and PCC rules for the group policy.
  • the PCRF sends the group policy QoS rule to the BBERF.
  • the BBERF updates the local group policy QoS rules, and is respectively a group.
  • the existing IP-CAN session performs a resource reservation process.
  • the BBERF sends an acknowledgement message to the PCRF; in step S1009, the PCRF sends a group policy PCC rule to the PCEF; in step S1010, the PCEF updates the local group policy PCC rule, and respectively performs a resource reservation process for the existing IP-CAN session in the group. .
  • the PCEF returns a confirmation message to the PCRF.
  • Embodiment 8 This embodiment provides a policy and charging execution entity PCEF, which may be, but is not limited to, applied to the PCC system shown in FIG. 2, and FIG. 11 is a block diagram of a PCEF structure according to Embodiment 8 of the present invention.
  • the PCEF includes: an obtaining module 1002, an application module 1004, and a storage module 1006, wherein the obtaining module 1002 is configured to locally set the storage during the establishment of an Internet Protocol-Connected Access Network IP-CAN session by the MTC device attached to the PCEF.
  • the module 1006 obtains a group policy corresponding to the device group to which the MTC device belongs, and triggers the application module 1004.
  • the application module 1004 is configured to apply the group policy to the IP-CAN session.
  • the storage module 1006 is configured to save the device attached to the PCEF.
  • Group policy The PCEF provided in this embodiment saves the group policy of the MTC device group attached to the PCEF in the PCEF local state, and locally searches for and acquires the device group to which the MTC device belongs in the process of establishing the IP-CAN session of the MTC device.
  • the group policy is applied to the IP-CAN session that is requested to be established, so that the PCEF does not need to apply for the policy of the MTC device to the PCRF every time during the session of the MTC to establish an IP-CAN, thereby saving the application time of the policy. , which saves network resources and improves the utilization of network resources.
  • 12 is a block diagram of a first preferred PCEF structure according to Embodiment 8 of the present invention.
  • the PCEF may further include: a requesting module 1008, a saving module 1010, where the requesting module 1008 is set to be locally acquired in the PCEF.
  • the group policy is requested from the PCRF, and the saving module 1010 is triggered.
  • the saving module 1010 is configured to save the requested group policy to the storage module 1006, and trigger the application module. 1004;
  • the application module 1004 is also arranged to apply the requested group policy to the IP-CAN session.
  • the preferred PCEF applies to the PCRF for the group policy of the MTC device group, thereby realizing dynamic local addition.
  • the PCEF may further include: a receiving module 1012, an update module 1014, where the receiving module 1012 is configured to receive a re-recovery from the PCRF.
  • the group policy is set, and the update module 1014 is triggered, wherein the re-established group policy corresponds to the device group to which the MTC device belongs; the update module 1014 is configured to update the original MTC device in the storage module 1006 with the re-defined group policy.
  • the device group corresponds to the group policy, and triggers the application module 1004; in the preferred PCEF, the application module 1004 is further configured to apply the updated group policy to all IP-CAN sessions corresponding to the device group to which the MTC device belongs. .
  • the PCRF reassigns the group policy corresponding to a certain MTC device group, the above preferred
  • the PCEF can receive the updated group policy in real time, thereby realizing dynamic local addition. And maintenance group policy.
  • the technical solution provided by the embodiment of the present invention uses the PCEF to locally save the group policy of the device group attached to the PCEF.
  • the PCEF obtains the local Group policy corresponding to the device group to which the device belongs, and apply to the corresponding
  • the IP-CAN session solves the problem in the prior art that each MTC device establishes an IP-CAN session.
  • the PCRF needs to apply to the PCRF for the application of the IP-CAN session, resulting in wasted network resources, which shortens the time for applying the MTC policy, saves network resources, and improves network resource utilization.
  • the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.

Landscapes

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

Description

机器类通信的策略应用方法及策略和计费执行实体 技术领域 本发明涉及通信领 i或， 具体而言， 涉及一种机器类通信 ( Machine Type Communication, 简称为 MTC ) 的策略应用方法及策略和计费执行实体。 背景技术
3GPP无线核心网包括通用无线分组业务 ( General Packet Radio Service, 简称为 GPRS )网络、 演进的分组系统（ Evolved Packet System, 简称为 EPS ) 网络、 通用移动通信系统 （Universal Mobile Telecommunications System, 简 称为 UMTS )„ 图 1示出了机器类通信 MTC用户设备 ( User Equipment, 简称为 UE ) 通过 SAE和 UMTS接入 IP多媒体子系统（ IP Multimedia Subsystem, 简称为 IMS ) 的紧急呼叫的示意图， 在图 1中， 实线表示信令， 虚线表示用户的 IP 通道。 通过 UMTS接入时， UE又可称为移动台 （ Mobile Station, 简称为 MS )。 如图 1所示， MTC UE通过 EPS或 UMTS接入 MTC月艮务器（ MTC Server ) 所涉及的主要网元包括： EPS网络部分的网元、 UMTS网络部分的网元以及 MTC Server, 这种情况下， MTC UE也可称为 MTC设备。 自第三代合作伙伴计划阶段 7 ( 3GPP Release7 ) 标准体系以来， 策略和 计费功能由策略和计费控制（ PCC, Policy and Charging Control )框架来实现。 PCC架构是一个能够应用于多种接入技术的功能框架， 例如， PCC架构可以 应用于 UMTS , GSM/GSM数据增强演进 ( EDGE ) 无线接入网、 互通无线 局 i或网 （I-WLAN ) 以及 EPS。
PCC主要实现了策略控制和计费两大功能。 图 2为现有 PCC组成架构 示意图，以下对图 2所示的 PCC架构中的各个逻辑功能实体及其接口功能进 行描述。 如图 2所示：
AF, 用于提供业务应用的接入点， 这些业务应用所使用的网络资源需要 进行动态的策略控制。 在业务面进行参数协商时， AF将相关业务信息传递 给策略控制与计费规则功能实体 ( PCRF , Policy and Charging Rules
Function )。如果这些业务信息与 PCRF的策略相一致， 则 PCRF接受该协商； 如果不一致， PCRF拒绝该协商， 并在反馈时给出 PCRF可接受的业务参数。 随后， AF可将这些参数返回给用户设备（UE, User Equipment )„ 其中， AF 和 PCRF之间的接口是 Rx接口。
PCRF是 PCC的核心， 用于负责策略决策和计费规则的制定。 PCRF提 供基于业务数据流的网络控制规则， 这些网络控制包括业务数据流的检测、 门控 （ Gating Control )、 月艮务质量 （QoS , Quality of Service )控制以及基于 数据流的计费规则等。 PCRF将其制定的策略和计费规则发送给策略和计费 执行功能实体 ( PCEF, Policy and Control Enforcement Function )执行； 同时， PCRF还需要保证这些规则和用户的签约信息一致。 其中， PCRF制定策略和 计费规则的依据包括： 从 AF获得的与业务相关的信息、 从用户签约数据库 (用户数据库， Subscription Profile Repository ) 获得的与策略控制和计费相 关的用户策略计费控制签约信息、 以及通过 Gx接口从 PCEF获得的与承载 相关网络的信息。
PCEF通常位于网关（GW, Gate- Way ) 内， 在 载面执行 PCRF所制定 的策略和计费规则。 PCEF按照 PCRF所发送的规则中的业务数据流过滤器 对业务数据流进行检测， 进而对这些业务数据流执行 PCRF所制定的策略和 计费规则； 在承载建立时， PCEF按照 PCRF发送的规则进行资源分配， 并 根据 AF提供的信息进行门控控制； 同时， PCEF根据 PCRF订阅的事件触发 上报承载网络上发生的事件； 根据 PCRF发送的计费规则， PCEF执行相应 的业务数据流计费操作， 其中， 计费既可以是在线计费， 也可以是离线计费。 如果是在线计费， 则 PCEF需要和在线计费系统 （ OCS , Online Charging System ) 一起进行信用管理； 离线计费时， PCEF和离线计费系统 （ OFCS , Offline Charging System ) 之间交换相关的计费信息。 其中， PCEF与 PCRF 之间的接口是 Gx接口， PCEF与 OCS之间的接口是 Gy接口， PCEF与 OFCS 之间的接口是 Gz接口。 PCEF—般都位于网络的网关上， 如 EPS的分组数 据网络网关 （PDN-GW )、 通用无线分组业务 ( GPRS , General Packet Radio Service )中的 GPRS网关支持节点（ GGSN )以及互联无线网局域网（ I-WLAN, Interworking WLAN ) 中的分组数据网关 （ PDG, Packet Data Gateway ) 等。 载绑定和事件 4艮告功能实体 （ BBERF, Bearer Binding and Event Reporting Function )通常位于接入网网关 ( Access Network Gateway ) 内。 ^口 当用户设备通过 E-UTRAN接入 EPS、 服务网关 S-GW与 P-GW之间釆用代 理移动互联网十办议版本 6 ( ΡΜΙΡνό, Proxy Mobile Internet Protocol version 6 ) 协议时， S-GW中就存在 BBERF。 当用户设备通过可信任非 3GPP接入网接 入时， 可信任非 3GPP接入网关中也存在 BBERF。 用户签约数据库（用户数据库），存储有与策略控制和计费相关的用户策 略计费控制签约信息。 用户数据库和 PCRF之间的接口是 Sp接口。
OCS和 PCEF共同完成在线计费方式下用户信用的控制和管理。
OFCS与 PCEF共同完成离线计费方式下的计费操作。 现有技术中， MTC设备（ MTC Device, 即终端）接入 MTC服务器， 首 先必须先通过 EPS或 UMTS建立 IP-CAN会话。 为了实现对 IP-CAN会话的 策略和计费控制， EPS或 UMTS系统中的策略执行实体与 PCRF为每一个 IP-CAN会话建立 Diameter 会话。通过 Diameter会话，策略执行实体向 PCRF 上报 MTC设备的接入信息， PCRF向策略执行实体下发策略。 发明人发现： 在实际使用过程中， MTC设备往往数量众多， 且需长期在 线， 如果每个 MTC设备建立 IP-CAN会话的过程中， PCRF都需要向 PCRF 申请应用于该 IP-CAN会话的策略， 将占用大量网络资源， 从而降低了网络 资源的利用率， 导致网络资源的浪费。 发明内容 本发明的主要目的在于提供一种机器类通信 MTC的策略应用方法及装 置， 以至少解决问题。 才艮据本发明的一个方面， 提供了一种机器类通信 MTC的策略应用方法， 包括： 在附着到策略和计费执行实体 PCEF的 MTC设备建立因特网协议-连 接接入网 IP-CAN会话过程中， PCEF在本地获取与 MTC设备所属的设备组 对应的组策略； 夺组策略应用于 IP-CAN会话。 优选地， 上述 PCEF在本地获取与 MTC设备所属的设备组对应的组策 略包括： PCEF确定 MTC设备所属组的组标识； PCEF在本地保存的第一对 应关系中查找与组标识对应的组策略， 其中， 第一对应关系为组标识与组策 略的对应关系。 优选地， 上述 PCEF确定 MTC设备所属组的组标识包括： 获取 MTC设 备发送的 IP-CAN会话请求消息携带的组标识。 优选地， 上述 PCEF确定 MTC设备所属组的组标识包括： 获取 MTC设 备发送的 IP-CAN会话请求消息携带的 MTC设备的用户标识； 在本地保存 的第二对应关系中查找与用户标识对应的组标识， 其中第二对应关系为组标 i只与用户标 i只的对应关系。 优选地， 上述在将组策略应用于 IP-CAN会话的同时， 还包括： PCEF 在本地记录组策略与 IP-CAN会话的对应关系。 优选地， 如果 PCEF没有在本地获取到与 MTC设备所属的设备组对应 的组策略， 则向策略和计费规则功能实体 PCRF请求组策略， 保存在本地， 并^ 1组策略应用于 IP-CAN会话。 优选地，上述 PCEF通过建立与 PCRF之间的 Diameter会话连接向 PCRF 请求组策略； PCRF根据从应用功能实体 AF获取的业务信息、从用户签约数 据库获取的用户签约信息、 以及从 PCEF获取的用户标识或组标识制定组策 略， 并通过 Diameter会话连接向 PCEF下发组策略； 在 PCEF获取并保存组 策略之后， 断开 Diameter会话连接。 优选地， 在将组策略应用于 IP-CAN会话之后， 还包括： PCEF接收来 自于策略和计费规则功能实体 PCRF的重新制定的组策略， 其中， 重新制定 的组策略与 MTC设备所属的设备组对应； PCEF以重新制定的组策略更新原 有的与 MTC设备所属的设备组对应的组策略； 将更新后的组策略应用于与 MTC设备所属的设备组对应的所有 IP-CAN会话。 优选地， 在 PCEF接收来自于 PCRF的重新制定的组策略之前， 还包括： PCRF接收来自应用功能实体 AF的消息， 其中， 消息中携带有与设备组对应 的业务信息； PCRF从 PCEF获取与设备组对应的 IP-CAN会话情况； PCRF 根据业务信息和 IP-CAN会话情况为设备组重新制定组策略， 并下发给 PCEF。 优选地， 在 PCEF接收来自于 PCRF的重新制定的组策略之前， 还包括： PCRF接收用户签约数据库 SPR发送的更新签约文档请求， 其中， 更新签约 文档请求中携带有与设备组对应的更新后的签约文档； PCRF从 PCEF获取 与设备组对应的 IP-CAN会话情况； PCRF才艮据更新后的签约文档和 IP-CAN 会话情况为设备组重新制定组策略， 并下发给 PCEF。 根据本发明的另一方面， 提供一种策略和计费执行实体 PCEF , 包括： 获取模块， 设置为在附着到 PCEF的 MTC设备建立因特网协议-连接接入网 IP-CAN会话过程中，在本地设置的存储模块中获取与 MTC设备所属的设备 组对应的组策略，并触发应用模块；应用模块，设置为将组策略应用于 IP-CAN 会话； 存储模块， 设置为保存附着于 PCEF的设备组的组策略。 优选地， 上述 PCEF还包括： 请求模块， 设置为在 PCEF没有在本地获 取到与 MTC设备所属的设备组对应的组策略的情况下， 向策略和计费规则 功能实体 PCRF请求组策略， 并触发保存模块； 保存模块， 设置为将请求到 的组策略保存至存储模块， 并触发应用模块； 应用模块还设置为将请求到的 组策略应用于 IP-CAN会话。 优选地， 上述 PCEF还包括： 接收模块， 设置为接收来自于策略和计费 规则功能实体 PCRF的重新制定的组策略， 并触发更新模块， 其中， 重新制 定的组策略与 MTC设备所属的设备组对应； 更新模块， 设置为以重新制定 的组策略更新存储模块中原有的与 MTC设备所属的设备组对应的组策略， 并触发应用模块； 应用模块还设置为将更新后的组策略应用于与 MTC设备 所属的设备组对应的所有 IP-CAN会话。 通过本发明，釆用 PCEF本地保存附着到该 PCEF下的设备组的组策略， 某个设备组内的 MTC设备建立 IP-CAN会话时， PCEF在本地获取与该设备 所属设备组对应的组策略， 并应用于相应的 IP-CAN会话， 解决了现有技术 中每个 MTC设备建立 IP-CAN会话的过程中， PCRF都需要向 PCRF申请应 用于该 IP-CAN会话的策略， 导致的网络资源浪费的问题， 进而缩短了应用 MTC策略的时间， 节省了网络资源， 提高了网路资源利用率。 附图说明 此处所说明的附图用来提供对本发明的进一步理解， 构成本申请的一部 分， 本发明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的 不当限定。 在附图中： 图 1是根据相关技术的 MTC设备接入系统的示意图； 图 2是根据相关技术的 PCC架构示意图； 图 3是才艮据本发明实施例一 MTC策略应用方法的流程图； 图 4是才艮据本发明实施例二的 PCEF本地获取组策略的流程图； 图 5是才艮据本发明实施例三的 PCEF请求组策略的流程图； 图 6是根据本发明实施例三的 BBERF请求组策略的流程图； 图 7是才艮据本发明实施例四的组策略应用流程图； 图 8是根据本发明实施例五的组策略应用流程图； 图 9是根据本发明实施例六的组策略更新流程图； 图 10是根据本发明实施例七的组策略更新流程图； 图 11是才艮据本发明实施例八的 PCEF结构^ I图； 图 12是才艮据本发明实施例八的第一优选 PCEF结构框图； 图 13是才艮据本发明实施例八的第二优选 PCEF结构框图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是， 在 不冲突的情况下， 本申请中的实施例及实施例中的特征可以相互组合。 实施例一 本实施例提供了一种机器类通信 MTC的策略应用方法， 可以但不限于 应用于图 2所示的 PCC系统中， 图 3是才艮据本发明实施例一 MTC策略应用 方法的流程图， 该方法包括： 步骤 S302, 在附着到策略和计费执行实体 PCEF的 MTC设备建立
IP-CAN会话过程中， PCEF在本地获取与 MTC设备所属的设备组对应的组 策略； 步骤 S304 , 将组策略应用于 IP-CAN会话。 相关技术中， 每个 MTC设备建立 IP-CAN会话承载的过程中， PCEF需 要向 PCRE申请该设备对应的策略， 并应用于该设备请求建立的 IP-CAN会 话中，但是属于同一 MTC设备组的众多 MTC设备策略规则是相同的，例如， 针对同一种业务， 组内的所有 MTC设备釆用相同的 QoS规则。 因此， 导致现有的 MTC策略应用效率低下的根本原因是： 针对同一组
MTC设备， PCRF多次下发相同策略规则。 本实施例提供的上述方法， 将附着于 PCEF下的 MTC设备组的组策略 保存在 PCEF本地， 在 MTC设备建立 IP-CAN的会话过程中， 在本地查找并 获取该 MTC设备所属的设备组的组策略， 并将该组策略应用于请求建立的 IP-CAN会话， 从而使得 MTC建立 IP-CAN的会话过程中， PCEF无需每次 都向 PCRF申请该 MTC设备的策略， 从而节省了策略应用时间， 节省了网 路资源， 进而提高了网络资源的利用率。 在实施过程中， PCEF可以但不限于通过以下方式在本地配置 MTC设备 组的组策略： ( 1 )、 静态配置组策略， 即由网络设备管理人员在本地手动配置附着于 该 PCEF的各个 MTC设备组的组策略。
( 2 )、 动态申请 /维护组策略， 即在置附着于该 PCEF的某个 MTC设备 组的第一个 MTC设备建立 IP-CAN会话的过程中， PCEF向 PCRF请求该设 备组的组策略， 接收到该设备组的组策略之后， 保存在 PCEF本地。 通过上述方式， PCEF实现附着于自身的 MTC设备组的组策略的本地保 存，使得之后隶属于这些 MTC设备组的 MTC设备在建立 IP-CAN的过程中， PCEF无需为每个 MTC设备向 PCRF申请策略规则，从而简化了现有的 MTC 设备策略应用流程。 优选地， 在实施过程中， 执行上述步骤 S304的同时， PCEF还可以在本 地记录该 MTC设备组的组策略与 IP-CAN会话更的对应关系。 这样， 实现 了组策略与 IP-CAN会话对应关系的动态维护， 一旦某个 MTC设备组的组 策略发生变化时， PCEF可以才艮据上述对应关系， 将变化后的组策略应用在 所有对应的 IP-CAN会话上， 从而保证了 MTC设备的正常应用。 实施例二 在上述实施例一中介绍了 PCEF如何实现组策略的本地保存与维护， 在 本实施例中， 对 PCEF如何在本地获取与 MTC设备所属的设备组对应的组 策略进行详细介绍。 图 4是才艮据本发明实施例二的 PCEF本地获取组策略的流程图， 该流程 包括： 步骤 S402, PCEF确定请求建立 IP-CAN会话的 MTC设备所属组的组 标识； 步骤 S404 , PCEF在本地保存的组标识与组策略的对应关系中查找与组 标识对应的组策略。 为了使 PCEF能够在本地查找到当前请求建立 IP-CAN会话的 MTC设备 所属设备组的组策略， PCEF可以通过识别该 MTC设备所属的组标识来进行 本地查找， 在实施过程中， 可以但不限于通过以下方式识别组标识：
( 1 )、 MTC设备在 IP-CAN会话建立请求消息中携带所属设备组的组标 识， PCEF接收到 P-CAN会话建立请求消息后， 解析出该组标识。 ( 2 )、 MTC设备在 IP-CAN会话建立请求消息中携带用户标识或设备标 识， PCEF本地维护一个用户标识与组标识的对应关系， 或者维护一个设备 标识与组标识的对应关系， PCEF接收到 IP-CAN会话建立请求消息后， 解 析出该设备的用户标识或设备标识， 并在上述对应关系中查找与解析出的用 户标 i只或设备标 i只对应的组标 i只。 通过上述方式， PCEF确定组标识后， 在本地保存的组标识与组策略的 对应关系中查找组策略。 通过上述流程， PCEF实现了组策略的本地查找， 相对于现有技术而言， 本实施例提供的查找方法替代了每次 MTC设备建立 IP-CAN会话时， PCEF 向 PCRF请求策略的技术方案， PCEF的本地查找不仅不需要占用 PCEF与 PCRF之间进行通信的网络资源， 而且查找时间也大大低于现有的请求策略 所耗费的消息发送、 接收、 处理及等待时间。 实施例三 上述实施例一和实施例二分别介绍了 PCEF实现本地保存组策略和本地 查找组策略的实现方法。 针对某个 MTC设备组的 MTC设备， 如果 PCEF在 本地没有查找到该设备组的组策略， 则需要在本地增加该设备组的组策略， 本实施例提供了解决这一需求的技术方案。 在某个 MTC设备组的 MTC设备建立 IP-CAN会话的过程中，如果 PCEF 没有在本地获取到与 MTC设备所属的设备组对应的组策略， 则向 PCRF请 求组策略， 保存在本地， 并^ 1组策略应用于 IP-CAN会话。 在实施过程中， 如果图 2所示的 PCC系统中不使用 BBERF, 可以但不 限于通过以下方式实现组策略的请求： 图 5是才艮据本发明实施例三的 PCEF请求组策略的流程图，该流程包括： 步骤 S502, PCEF通过建立与 PCRF之间的认证 ( Diameter ) 会话连接 向 PCRF请求组策略； 步骤 S 504 , PCRF根据从应用功能实体 AF获取的业务信息、 从用户签 约数据库获取的用户签约信息、 以及从 PCEF获取的用户标识或组标识制定 组策略， 并通过 Diameter会话连接向 PCEF下发组策略。 在实施过程中， 如果图 2所示的 PCC系统中使用 BBERF, 则 BBERF 也如上述实施例提供的方法实现组策略的本地保存和组策略的本地查找， 可 以但不限于通过以下方式实现组策略的请求： 图 6是根据本发明实施例三的 BBERF请求组策略的流程图， 该流程包 括： 步骤 S602, BBERF通过建立与 PCRF之间的 Diameter会话连接向 PCRF 请求组策略； 步骤 S604 , PCRF根据从应用功能实体 AF获取的业务信息、 从用户签 约数据库获取的用户签约信息、 以及从 PCEF获取的用户标识或组标识制定 组策略， 并通过 Diameter会话连接向 BBERF下发组策略； 步骤 S606, BBERF保存组策略之后， 向 PCEF发送 IP-CAN会话建立 请求； 步骤 S608, PCEF向 PCRF请求组策略； 步骤 S610, PCRF将上述步骤 S604中制定的组策略下发给 PCEF, 从而 使得 BBERF保存的组策略与 PCRE保存的组策略同步。 通过本实施例提供的上述方案， 当某个 MTC设备组内的设备第一次建 立 IP-CAN会话时， PCEF向 PCRF申请该 MTC设备组的组策略， 从而实现 了组策略在本地动态添力。及维护组策略。 优选地， 在 PCEF申请并保存组策略之后， 可以断开为申请该组策略所 建立的 Diameter会话连接。 现有技术中， 为申请组策略所建立的 Diameter会话连接需要始终保持。 相对于现有技术， 上述在申请成功组策略后， 断开 Diameter会话连接的方式 无需始终占用 PCEF和 PCRF之间的通信链路， 从而进一步地节省了网络资 源。 实施例四 本实施例中描述了属于同一个设备组的 MTC Device 1和 MTC Device2 在分别建立 IP-CAN会话过程， MTC Device 1在建立会话过程中， PCEF与 PCRF交互获取组策略。 MTC Device2在建立会话过程中 PCEF不与 PCRF 交互， 直接用 MTC Device 1获取的组策略对 MTC Device2的会话进行绑定。 其中 MTC Device 1和 MTC Device2建立的 IP-CAN会话都不使用 BBERF。 图 7是根据本发明实施例四的组策略应用流程图，如图 7所示，该流程包括： 步骤 S701 ,在 MTC Device 1请求建立 IP-CAN会话 1的过程中，向 PCEF 发送请求建立 IP-CAN会话消息， 在消息中携带有 MTC Device 1的用户标识 1或 MTC Device 1的组标 K; 步骤 S702, PCEF向 PCRF发送 IP-CAN会话建立指示消息， 在 IP-CAN 会话建立指示消息中携带有用户标识 1或组标识。 该消息建立了 PCEF和 PCRF之间的 Diameter会话， 表示为 Gx会话 1。 其中组标识为可选， 若请求 消息中未携带 MTC Device 1的组标识， 则 PCRF负责解释出组标识信息。 PCRF可通过本地策略解释出 MTC Device 1对应的组标识； 步骤 S703 , PCRF向用户数据库发送签约文档请求， 在签约文档请求中 携带有用户标识 1或组标识。 其中， 组标识信息可选。 若在请求消息中未携 带组标识， 用户数据库负责解释出 MTC Device 1对应的组标识； 步骤 S704, 用户数据库才艮据组标识或用户标识 1返回 MTC Device的组 签约信息； 步骤 S705 , PCRF才艮据组签约信息、接入信息以及网络策略制定组策略。 PCRF将组策略通过 IP-CAN会话确认消息发送给 PCEF , 其中组策略包括组 策略 PCC规则和组策略 QoS规则； 步骤 S706, PCEF保存组策略及组标识与 IP-CAN会话的对应关系； 步 4聚 S707, PCEF执行策略。 PCEF所在网关向 MTC Device 1返回应答 建立 IP-CAN会话消息； 步骤 S708,在 MTC Device2请求建立 IP-CAN会话 2的过程中，向 PCEF 发送请求建立 IP-CAN会话消息，请求建立 IP-CAN会话 2, 在消息中携带有 MTC Device2的用户标识 2或组标识。 MTC Device 1和 MTC Device2属于同 一个组， 因此， 组标识是相同的； 步骤 S709, PCEF将组策略应用于 IP-CAN会话 2, 并更新组标识与 IP-CAN会话的对应关系； 步-骤 S710, PCEF执行策略。 PCEF所在网关向 MTC Device2返回应答 建立 IP-CAN会话消息。 上述实施例中， PCEF只在组内第一个设备建立 IP-CAN 载请求时从
PCRF获取到组策略， 当组内其他设备建立 IP-CAN 载时， PCEF直接将组 策略应用于 IP-CAN会话， 不再向 PCRF请求组策略。
PCEF向 PCRF获取组策略过程中，向 PCRF发送 IP-CAN会话建立请求 可携带组标识， 也可以不携带。 若没有携带， PCRF或用户数据库需能够解 释出组标识。 实施例五 本实施例中描述了同一个用户组的 MTC Device 1和 MTC Device2在分 别建立 IP-CAN会话过程中， MTC Device 1在建立会话过程中， BBERF、PCEF 分别与 PCRF交互获取组策略 QoS规则和组策略 PCC规则。 MTC Device2 在建立会话过程中 BBERF和 PCEF不再与 PCRF交互，直接用 MTC Device 1 获取的组策略 QoS规则和组策略 PCC规则对 MTC Device2的会话进行绑定。 其中 MTC Device 1和 MTC Device2建立的 IP-CAN会话都使用 BBERF。 图 8是才艮据本发明实施例五的组策略应用流程图， 如图 8所示， 该流程包括： 步骤 S801 ,在 MTC Device 1请求建立 IP-CAN会话 1的过程中，向 BBERF 发送请求建立 IP-CAN会话的消息， 在消息中携带有 MTC Device 1的用户标 识 1、 PDN标识， 或 MTC Device 1属于的用户组的组标识； 步骤 S802 , BBERF向 PCRF发送网关控制会话建立消息， 在网关控制 会话建立消息中携带有用户标识 1、 PDN标识或组标识。 该消息建立了 BBERF和 PCRF之间的 Diameter会话 (网关控制会话 ),表示为 Gxx会话 1 ; 步骤 S803 , PCRF向用户数据库发送签约文档请求， 在签约文档请求中 携带有用户标识 1、 PDN标识或组标识； 步骤 S804, 用户数据库才艮据用户标识 1及组标识， 返回组签约信息。 进 一步的用户数据库可能会将 MTC Device 1所属组的组用户标识全部下发给 PCRF, 通过此信息组内后续 Device建立 IP-CAN会话时， PCRF可不与用户 数据库交互； 步骤 S805 , PCRF根据组签约信息、接入信息以及网络策略制定组策略。
PCRF将组策略发送给 BBERF。 此处的组策略是组策略 QoS规则； 步骤 S806, BBERF保存组策略； 步骤 S807, BBERF执行组策略 QoS规则。 BBERF所在网关向 PCEF所 在网关发送请求建立 IP-CAN会话 1的消息， 消息中携带有 MTC Device 1的 用户标识 1或组标识； 步骤 S 808 , PCEF向 PCRF发送 IP-CAN会话建立指示消息， 消息中携 带有用户标识 1或组标识。 该消息建立了 PCEF和 PCRF之间的 Diameter会 话， 表示为 Gx会话 1 ; 步骤 S809, PCRF根据组标识将 Gxx会话 1和 Gx会话 1进行关联。 进 而将步骤 S805执行的策略 (除 QoS规则 1 )发送给 PCEF; 步骤 S810 , PCEF保存组策略 QoS规则及组策略 PCC规则； 步骤 S811 , PCEF执行策略。 PCEF所在网关向 BBERF所在网关应答建 立 IP-CAN会话 1消息； 步骤 S812, BBERF所在网关返回应答建立 IP-CAN会话 1消息； 步骤 S813 ,在 MTC Device2请求建立 IP-CAN会话 2的过程中，向 BBERF 发送请求建立 IP-CAN会话的消息， 在消息中携带有 MTC Device2的用户标 识 2或组标识。 由于 MTC Device 1和 MTC Device2属于同一组， 所以组标 K^目同； 步骤 S814 , BBERF向 PCEF发送网关控制会话建立消息， 在网关控制 会话建立消息中携带有用户标识 2或组标识； 步骤 S 815 , PCEF并不向 PCRF进行策略请求， 直接将本地保存的组策 略应用于 IP-CAN会话 2 , 并更新组标识与 IP-CAN会话的对应关系； 步骤 S816, PCEF执行策略。 PCEF所在网关向 BBERF所在网关应答建 立 IP-CAN会话 2消息， 携带 IP Address2; 步骤 S817, BBERF所在网关返回应答建立 IP-CAN会话 2消息。 上述实施例中， PCEF只在组内第一个设备建立 IP-CAN 7 载请求时从 PCRF获取到组策略， 当组内其他设备建立 IP-CAN 载时， PCEF直接将组 策略应用于 IP-CAN会话， 不再向 PCRF请求组策略。
PCEF向 PCRF获取组策略过程中，向 PCRF发送 IP-CAN会话建立请求 可携带组标识， 也可以不携带。 若没有携带， PCRF或用户数据库需能够解 释出组标识。 实施例六 本实施例描述的是基于实施例四或实施例五建立的 IP-CAN会话后， 由 于 MTC Device 1和 MTC Device2的业务访问，而触发的 IP-CAN会话的 4爹改 流程。 AF向 PCRF有可能提供的是业务组信息，该业务组信息可应用于组内 所有设备。 因此， PCRF可按照 IP地址段、 组标识或用户号码段对业务组信 息进行匹配。 图 9是根据本发明实施例六的组策略更新流程图，如图 9所示， 该流程包括： 步骤 S901 , AF向 PCRF提供一个业务组信息， 业务组信息中对业务流 的匹配按对应的 MTC设备组进行匹配， 可以定义为按照 IP地址段、 组标识 或用户号码段进行匹配； 步骤 S902 , PCRF保存 AF提供的业务信息， 并向 AF发送响应消息； 步骤 S903 , PCRF向 PCEF发送组内设备 IP-CAN会话请求消息， 消息 中携带组标识； 步骤 S904 , PCEF向 PCRF返回组内设备 IP-CAN会话响应消息， 消息 中携带组内的 IP-CAN会话情况； 注， 由组内设备建立 7 载时组策略直接由 PCEF处理， 并没有向 PCRF 报告。 若 PCRF需根据组内 IP-CAN会话情况制定组策略则需要向 PCEF请 求组内的 IP-CAN会话情况。 步骤 S903〜步骤 S904完成此功能。 步骤 S905 , PCRF根据业务信息等进行策略决策， 制定出组策略， 其中 包括组策略 QoS规则和组策略 PCC规则； 步骤 S906, PCRF向 BBERF发送组策略 QoS规则； 步骤 S907 , BBERF更新本地的组策略 QoS规则， 并分别为组内已有的 IP-CAN会话执行资源预留过程。 BBERF向 PCRF发送确认消息； 步骤 S908, PCRF向 PCEF发送组策略 PCC规则； 步骤 S909 , PCEF更新本地的组策略 PCC规则， 并分别为组内已有的 IP-CAN会话执行资源预留过程。 PCEF向 PCRF返回确认消息。 实施例七 本实施例描述的是基于实施例一或实施例二建立的 IP-CAN会话后并且 通过实施例三访问业务后由于用户组签约数据发生变化后 ,而触发的 IP-CAN 会话的修改流程。 图 10是根据本发明实施例七的组策略更新流程图， 如图 10所示， 该流程包括： 步骤 S 1001 , 用户数据库检测用户组的签约数据发生变化； 步骤 S 1002, SRP向 PCRF发送组签约更新请求， 消息中携带发生变化 的签约文档； 步骤 S 1003 , PCRF保存更新的签约文档数据， 并向用户数据库发送确 认消息； 步骤 S 1004, PCRF向 PCEF发送组内设备 IP-CAN会话请求消息， 消息 中携带组标识； 步骤 S 1005 , PCEF向 PCRF返回组内设备 IP-CAN会话响应消息， 消息 中携带组内的 IP-CAN会话情况； 步骤 S 1006, PCRF根据更新的签约文档进行策略决策。 若默认承载的
QoS发生了变化， 那么 PCRF将重新制定针对组策略的 QoS规则和 PCC规 则； 步骤 S 1007, PCRF向 BBERF发送组策略 QoS规则； 步骤 S 1008, BBERF更新本地的组策略 QoS规则， 并分别为组内已有 的 IP-CAN会话执行资源预留过程。 BBERF向 PCRF发送确认消息； 步骤 S 1009, PCRF向 PCEF发送组策略 PCC规则； 步骤 S 1010, PCEF更新本地的组策略 PCC规则， 并分别为组内已有的 IP-CAN会话执行资源预留过程。 PCEF向 PCRF返回确认消息。 实施例八 本实施例提供了一种策略和计费执行实体 PCEF, 可以但不限于应用于 图 2所示的 PCC系统中， 图 11是才艮据本发明实施例八的 PCEF结构框图， 该 PCEF包括： 获取模块 1002、 应用模块 1004以及存储模块 1006 , 其中， 获取模块 1002 , 设置为在附着到 PCEF的 MTC设备建立因特网协议-连接接 入网 IP-CAN会话过程中， 在本地设置的存储模块 1006中获取与 MTC设备 所属的设备组对应的组策略， 并触发应用模块 1004; 应用模块 1004 , 设置 为将组策略应用于 IP-CAN会话； 存储模块 1006 , 设置为保存附着于 PCEF 的设备组的组策略。 本实施例提供的上述 PCEF,将附着于 PCEF下的 MTC设备组的组策略 保存在 PCEF本地， 在 MTC设备建立 IP-CAN的会话过程中， 在本地查找并 获取该 MTC设备所属的设备组的组策略， 并将该组策略应用于请求建立的 IP-CAN会话， 从而使得 MTC建立 IP-CAN的会话过程中， PCEF无需每次 都向 PCRF申请该 MTC设备的策略， 从而节省了策略应用时间， 节省了网 路资源， 进而提高了网络资源的利用率。 图 12是才艮据本发明实施例八的第一优选 PCEF结构框图， 优选地， 该 PCEF还可以包括： 请求模块 1008、 保存模块 1010 , 其中， 请求模块 1008 , 设置为在 PCEF没有在本地获取到与 MTC设备所属的设备组对应的组策略 的情况下， 向 PCRF请求组策略， 并触发保存模块 1010; 保存模块 1010 , 设 置为将请求到的组策略保存至存储模块 1006 , 并触发应用模块 1004; 在这 种优选的 PCEF中，应用模块 1004还设置为将请求到的组策略应用于 IP-CAN 会话。 当某个 MTC设备组内的设备第一次建立 IP-CAN会话时上述优选 PCEF 向 PCRF申请该 MTC设备组的组策略， 从而实现了在本地动态添力。及维护 组策略。 图 13是才艮据本发明实施例八的第二优选 PCEF结构框图， 优选地， 该 PCEF还可以包括： 接收模块 1012、 更新模块 1014 , 其中， 接收模块 1012 , 设置为接收来自于 PCRF的重新制定的组策略，并触发更新模块 1014 ,其中， 重新制定的组策略与 MTC设备所属的设备组对应； 更新模块 1014 , 设置为 以重新制定的组策略更新存储模块 1006中原有的与 MTC设备所属的设备组 对应的组策略，并触发应用模块 1004;在这种优选的 PCEF中，应用模块 1004 还设置为将更新后的组策略应用于与 MTC设备所属的设备组对应的所有 IP-CAN会话。 当 PCRF重新指定对应于某个 MTC设备组的组策略后， 上述优选的
PCEF可以实时地接收更新后的组策略， 从而实现了在本地动态添力。及维护 组策略。 综上， 本发明实施例提供的技术方案， 釆用 PCEF本地保存附着到该 PCEF下的设备组的组策略，某个设备组内的 MTC设备建立 IP-CAN会话时， PCEF在本地获取与该设备所属设备组对应的组策略， 并应用于相应的
IP-CAN会话，解决了现有技术中每个 MTC设备建立 IP-CAN会话的过程中， PCRF都需要向 PCRF申请应用于该 IP-CAN会话的策略， 导致的网络资源 浪费的问题， 进而缩短了应用 MTC策略的时间， 节省了网络资源， 提高了 网路资源利用率。 显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布 在多个计算装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程 序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 并 且在某些情况下， 可以以不同于此处的顺序执行所示出或描述的步骤， 或者 将它们分别制作成各个集成电路模块， 或者将它们中的多个模块或步骤制作 成单个集成电路模块来实现。 这样， 本发明不限制于任何特定的硬件和软件 结合。 以上仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本领域 的技术人员来说， 本发明可以有各种更改和变化。 凡在本发明的 ^"神和原则 之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护范围 之内。

Claims

权 利 要 求 书
1. 一种机器类通信 MTC的策略应用方法， 包括：
在附着到策略和计费执行实体 PCEF的 MTC设备建立因特网协议 -连接接入网 IP-CAN会话过程中，所述 PCEF在本地获取与所述 MTC 设备所属的设备组对应的组策略；
将所述组策略应用于所述 IP-CAN会话。
2. 根据权利要求 1所述的方法，其中，所述 PCEF在本地获取与所述 MTC 设备所属的设备组对应的组策略包括：
所述 PCEF确定所述 MTC设备所属组的组标识；
所述 PCEF在本地保存的第一对应关系中查找与所述组标识对应 的所述组策略， 其中， 所述第一对应关系为组标识与组策略的对应关 系。
3. 根据权利要求 2所述的方法， 其中， 所述 PCEF确定所述 MTC设备所 属组的组标识包括：获取所述 MTC设备发送的 IP-CAN会话请求消息 携带的所述组标识。
4. 根据权利要求 2所述的方法， 其中， 所述 PCEF确定所述 MTC设备所 属组的组标识包括：
获取所述 MTC设备发送的 IP-CAN会话请求消息携带的所述 MTC设备的用户标识；
在本地保存的第二对应关系中查找与所述用户标识对应的所述组 标识， 其中所述第二对应关系为组标识与用户标识的对应关系。
5. 根据权利要求 1所述的方法， 其中， 在将所述组策略应用于所述
IP-CAN会话的同时， 还包括： 所述 PCEF在本地记录所述组策略与所 述 IP-CAN会话的对应关系。
6. 居权利要求 1所述的方法， 其中， 如果所述 PCEF没有在本地获取 到与所述 MTC设备所属的设备组对应的组策略，则向策略和计费规则 功能实体 PCRF请求所述组策略， 保存在本地， 并将所述组策略应用 于所述 IP-CAN会话。
7. 根据权利要求 6所述的方法， 其中，
所述 PCEF通过建立与所述 PCRF之间的 Diameter会话连接向所 述 PCRF请求所述组策略；
所述 PCRF根据从应用功能实体 AF获取的业务信息、 从用户签 约数据库获取的用户签约信息、 以及从所述 PCEF获取的用户标识或 组标识制定所述组策略， 并通过所述 Diameter会话连接向所述 PCEF 下发所述组策略；
在所述 PCEF获取并保存所述组策略之后， 断开所述 Diameter会 话连接。
8. 根据权利要求 1至 7任一项所述的方法， 其中， 在将所述组策略应用 于所述 IP-CAN会话之后， 还包括：
所述 PCEF接收来自于策略和计费规则功能实体 PCRF的重新制 定的组策略， 其中， 所述重新制定的组策略与所述 MTC设备所属的设 备组对应；
所述 PCEF以所述重新制定的组策略更新原有的与所述 MTC设备 所属的设备组对应的组策略；
将更新后的组策略应用于与所述 MTC设备所属的设备组对应的 所有 IP-CAN会话。
9. 根据权利要求 8所述的方法，其中，在所述 PCEF接收来自于所述 PCRF 的重新制定的组策略之前， 还包括：
所述 PCRF接收来自应用功能实体 AF的消息， 其中， 所述消息 中携带有与所述设备组对应的业务信息； 所述 PCRF从所述 PCEF获取与所述设备组对应的 IP-CAN会话 情况；
所述 PCRF根据所述业务信息和所述 IP-CAN会话情况为所述设 备组重新制定组策略， 并下发给所述 PCEF。
10. 根据权利要求 8所述的方法，其中，在所述 PCEF接收来自于所述 PCRF 的重新制定的组策略之前， 还包括：
所述 PCRF接收用户签约数据库 SPR发送的更新签约文档请求， 其中， 所述更新签约文档请求中携带有与所述设备组对应的更新后的 签约文档；
所述 PCRF从所述 PCEF获取与所述设备组对应的 IP-CAN会话 情况；
所述 PCRF 居所述更新后的签约文档和所述 IP-CAN会话情况 为所述设备组重新制定组策略， 并下发给所述 PCEF。
11. 一种策略和计费执行实体 PCEF, 包括：
获取模块，设置为在附着到所述 PCEF的 MTC设备建立因特网协 议 -连接接入网 IP-CAN会话过程中， 在本地设置的存储模块中获取与 所述 MTC设备所属的设备组对应的组策略， 并触发应用模块；
所述应用模块， 设置为将所述组策略应用于所述 IP-CAN会话； 所述存储模块， 设置为保存附着于所述 PCEF的设备组的组策略。
12. 根据权利要求 11所述的 PCEF, 其中， 还包括：
请求模块，设置为在所述 PCEF没有在本地获取到与所述 MTC设 备所属的设备组对应的组策略的情况下， 向策略和计费规则功能实体 PCRF请求所述组策略， 并触发保存模块；
所述保存模块， 设置为将所述请求到的组策略保存至所述存储模 块， 并触发所述应用模块；
所述应用模块还设置为将请求到的组策略应用于所述 IP-CAN会 话。
13. 根据权利要求 11或 12所述的 PCEF, 其中， 还包括：
接收模块， 设置为接收来自于策略和计费规则功能实体 PCRF的 重新制定的组策略， 并触发更新模块， 其中， 所述重新制定的组策略 与所述 MTC设备所属的设备组对应； 所述更新模块， 设置为以所述重新制定的组策略更新所述存储模 块中原有的与所述 MTC设备所属的设备组对应的组策略，并触发所述 应用模块；
所述应用模块还设置为将更新后的组策略应用于与所述 MTC设 备所属的设备组对应的所有 IP-CAN会话。
PCT/CN2011/071647 2010-04-29 2011-03-09 机器类通信的策略应用方法及策略和计费执行实体 WO2011134317A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US13/695,282 US8885568B2 (en) 2010-04-29 2011-03-09 Policy application method for machine type communication, and policy and charging enforcement function
EP11774308.8A EP2566197A4 (en) 2010-04-29 2011-03-09 GUIDANCE APPLICATION METHOD FOR MACHINE COMMUNICATION AND GUIDANCE AND CHARGE GAINING FUNCTION

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010173622.6 2010-04-29
CN201010173622.6A CN102238512B (zh) 2010-04-29 2010-04-29 机器类通信mtc的策略应用方法及策略和计费执行实体

Publications (1)

Publication Number Publication Date
WO2011134317A1 true WO2011134317A1 (zh) 2011-11-03

Family

ID=44860838

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/071647 WO2011134317A1 (zh) 2010-04-29 2011-03-09 机器类通信的策略应用方法及策略和计费执行实体

Country Status (4)

Country Link
US (1) US8885568B2 (zh)
EP (1) EP2566197A4 (zh)
CN (1) CN102238512B (zh)
WO (1) WO2011134317A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130196623A1 (en) * 2012-01-27 2013-08-01 Openet Telecom Ltd. System and Method For Enabling Interactions Between a Policy Decision Point and a Charging System
WO2014000142A1 (en) * 2012-06-25 2014-01-03 Telefonaktiebolaget L M Ericsson (Publ) Policy control for a machine-to-machine group
WO2014053197A1 (en) * 2012-10-02 2014-04-10 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatuses for policy and charging control of machine-to-machine type communications
EP2909996A1 (en) * 2012-10-22 2015-08-26 Nokia Solutions and Networks Oy Methods, apparatuses, system, related computer program product for routing and processing policy requests related to group subscription

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011025876A1 (en) * 2009-08-27 2011-03-03 Interdigital Patent Holdings, Inc. Method and apparatus for solving limited addressing space in machine-to-machine (m2m) environments
EP2837156B1 (en) * 2012-04-09 2018-08-22 Telefonaktiebolaget LM Ericsson (publ) Method, apparatus and computer readable medium for providing quality of service functionality supporting a plurality of different data streams in a single ims session for machine-to-machine mtm device communications
CN103533525B (zh) * 2012-07-02 2016-12-07 华为终端有限公司 策略控制和计费相关的规则传输的方法、设备和系统
WO2014040284A1 (zh) * 2012-09-17 2014-03-20 华为终端有限公司 机器类型通信会话处理方法和装置
WO2014059599A1 (zh) * 2012-10-16 2014-04-24 华为终端有限公司 计费处理方法、装置和系统
US10334416B2 (en) * 2013-03-15 2019-06-25 Alcatel Lucent Control of group triggers for MTC services
US9609144B2 (en) * 2013-05-03 2017-03-28 Qualcomm Incorporated Method for policy control and charging for D2D services
WO2014180949A1 (en) * 2013-05-08 2014-11-13 Nec Europe Ltd. A method for operating a network and an according network
WO2014183282A1 (zh) * 2013-05-15 2014-11-20 华为技术有限公司 群组计费方法、网关设备、计费设备以及通信系统
EP2991400A4 (en) * 2013-05-30 2016-05-18 Huawei Tech Co Ltd DATA TRANSFER CONTROL METHOD AND DEVICE BASED ON A WIRELESS COMMUNICATION NETWORK
CN103686648A (zh) * 2013-12-17 2014-03-26 中国联合网络通信集团有限公司 一种策略计费控制规则信息的请求方法、装置及系统
CN105323705B (zh) * 2014-07-14 2019-06-18 中兴通讯股份有限公司 更新机器类型通信设备组激活信息的方法、装置及系统
WO2016096013A1 (en) * 2014-12-18 2016-06-23 Nokia Solutions And Networks Oy Policy and charging control for groups
US11153106B2 (en) * 2015-02-09 2021-10-19 Telefonaktiebolaget Lm Ericsson (Publ) System for improved traffic handling in a network
KR102458443B1 (ko) * 2016-02-23 2022-10-25 삼성전자주식회사 무선통신 시스템에서 무선자원의 사용을 과금하는 방법 및 장치
US10778589B2 (en) * 2016-06-30 2020-09-15 Parallel Wireless, Inc. Intelligent RAN flow management and distributed policy enforcement
EP3958646A3 (en) * 2016-12-13 2022-06-22 Microsoft Technology Licensing, LLC Machine-to-machine network optimization and online charging
CN109246656B (zh) * 2017-06-01 2022-01-18 诺基亚通信公司 用于设备到设备通信的方法、网络设备及计算机可读介质
US11082881B2 (en) * 2018-04-05 2021-08-03 At&T Intellectual Property I, L.P. Dynamic quality of service setting system
CN113938845B (zh) * 2018-05-21 2023-07-18 华为技术有限公司 上下文管理方法及装置
CN110913507B (zh) 2018-09-18 2023-04-18 华为技术有限公司 通信方法和装置
WO2023283791A1 (zh) * 2021-07-12 2023-01-19 北京小米移动软件有限公司 策略处理方法及装置、通信设备及存储介质
CN116156667A (zh) * 2021-11-23 2023-05-23 维沃移动通信有限公司 物联网设备的会话建立方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060212924A1 (en) * 2005-03-16 2006-09-21 Michael Xie Inheritance based network management
CN101291233A (zh) * 2007-04-20 2008-10-22 华为技术有限公司 一种实现事件检测的方法及系统
CN101355438A (zh) * 2007-07-25 2009-01-28 华为技术有限公司 策略计费控制的实现方法、设备及系统

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101453339B (zh) * 2006-11-20 2011-11-30 华为技术有限公司 一种网络融合策略计费控制架构的系统及处理方法
US8086216B2 (en) * 2007-01-31 2011-12-27 Alcatel Lucent Mobility aware policy and charging control in a wireless communication network
CN101272256B (zh) * 2007-03-23 2011-07-06 华为技术有限公司 业务处理方法和系统、策略控制和计费规则功能实体
WO2009006630A1 (en) * 2007-07-05 2009-01-08 Starent Networks, Corp System and method for reducing latency in call setup and teardown
CN100546258C (zh) * 2007-07-24 2009-09-30 华为技术有限公司 实现策略与计费控制的方法、装置和系统
WO2009033382A1 (fr) * 2007-09-13 2009-03-19 Huawei Technologies Co., Ltd. Procédé et dispositif d'élément de réseau destinés à acquérir l'information de contrôle des règles d'une session d'accès ip
EP2234422B1 (en) * 2007-12-27 2015-08-12 ZTE Corporation Method for selecting policy and charging rules function
CA2712480C (en) * 2008-03-20 2015-06-16 Redknee Inc. Metering of telecommunication services
US8640188B2 (en) * 2010-01-04 2014-01-28 Tekelec, Inc. Methods, systems, and computer readable media for providing group policy configuration in a communications network using a fake user
CN102160452B (zh) * 2008-06-05 2015-02-04 凯敏公司 用于在网络中提供移动性管理的方法及系统
US8813168B2 (en) * 2008-06-05 2014-08-19 Tekelec, Inc. Methods, systems, and computer readable media for providing nested policy configuration in a communications network
CN101577935B (zh) * 2008-07-17 2011-09-21 中兴通讯股份有限公司 一种事件触发器的下发和安装方法
WO2010060457A1 (en) * 2008-11-03 2010-06-03 Nokia Siemens Networks Oy Charging control providing correction of charging control information
WO2010086013A1 (en) * 2009-01-27 2010-08-05 Telefonaktiebolaget Lm Ericsson (Publ) Group session management for policy control
WO2010136070A1 (en) * 2009-05-29 2010-12-02 Telefonaktiebolaget Lm Ericsson (Publ) Policy and charging control method, network entities, communication system and computer program therefor
CN102014343A (zh) * 2009-09-04 2011-04-13 华为技术有限公司 群组策略与计费规则处理方法、装置以及通信系统
WO2011026523A1 (en) * 2009-09-04 2011-03-10 Telefonaktiebolaget Lm Ericsson (Publ) Policy and/or charging control for a communication session
US8787174B2 (en) * 2009-12-31 2014-07-22 Tekelec, Inc. Methods, systems, and computer readable media for condition-triggered policies
US9184924B2 (en) * 2010-02-16 2015-11-10 Telefonaktiebolaget L M Ericsson (Publ) Nodes for communicating credit related information
US8605583B2 (en) * 2010-02-18 2013-12-10 Alcatel Lucent PCC/QOS rule creation
CN102238510B (zh) * 2010-04-26 2014-09-10 中兴通讯股份有限公司 机器类通信的策略下发方法及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060212924A1 (en) * 2005-03-16 2006-09-21 Michael Xie Inheritance based network management
CN101291233A (zh) * 2007-04-20 2008-10-22 华为技术有限公司 一种实现事件检测的方法及系统
CN101355438A (zh) * 2007-07-25 2009-01-28 华为技术有限公司 策略计费控制的实现方法、设备及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2566197A4 *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130196623A1 (en) * 2012-01-27 2013-08-01 Openet Telecom Ltd. System and Method For Enabling Interactions Between a Policy Decision Point and a Charging System
US9173081B2 (en) * 2012-01-27 2015-10-27 Openet Telecom Ltd. System and method for enabling interactions between a policy decision point and a charging system
WO2014000142A1 (en) * 2012-06-25 2014-01-03 Telefonaktiebolaget L M Ericsson (Publ) Policy control for a machine-to-machine group
CN104662935A (zh) * 2012-06-25 2015-05-27 爱立信(中国)通信有限公司 机器对机器群的策略控制
US20150341851A1 (en) * 2012-06-25 2015-11-26 Telefonaktiebolaget L M Ericsson (Publ) Policy control for a machine-to-machine group
EP2865208A4 (en) * 2012-06-25 2016-02-24 Ericsson Telefon Ab L M GUIDANCE CONTROL FOR A MACHINE TO MACHINE GROUP
US9615319B2 (en) 2012-06-25 2017-04-04 Telefonaktiebolaget L M Ericsson (Publ) Policy control for a machine-to-machine group
CN104662935B (zh) * 2012-06-25 2018-07-10 爱立信(中国)通信有限公司 机器对机器群的策略控制
WO2014053197A1 (en) * 2012-10-02 2014-04-10 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatuses for policy and charging control of machine-to-machine type communications
US9319867B2 (en) 2012-10-02 2016-04-19 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatuses for policy and charging control of machine-to-machine type communications
EP2909996A1 (en) * 2012-10-22 2015-08-26 Nokia Solutions and Networks Oy Methods, apparatuses, system, related computer program product for routing and processing policy requests related to group subscription

Also Published As

Publication number Publication date
EP2566197A1 (en) 2013-03-06
EP2566197A4 (en) 2016-04-20
CN102238512B (zh) 2015-11-25
US8885568B2 (en) 2014-11-11
US20130044646A1 (en) 2013-02-21
CN102238512A (zh) 2011-11-09

Similar Documents

Publication Publication Date Title
WO2011134317A1 (zh) 机器类通信的策略应用方法及策略和计费执行实体
US9137652B2 (en) Method for implementing policy and charging control in a roaming scene
US8799440B2 (en) Policy and charging control method and system for multi-PDN connections of single APN
US8131831B1 (en) Centralized policy management framework for telecommunication networks
US8874715B2 (en) Charging method, system and reporting method for terminal accessing through multiple access networks
CN102186162B (zh) 一种终端可达状态的获取方法和设备
US8661145B2 (en) Method and system for transmitting a bearer control mode in roaming scenarios
CN102131172B (zh) 业务处理方法及系统
US20110320544A1 (en) Diameter session audits
WO2011063688A1 (zh) 策略和计费规则功能实体的选择方法及系统
WO2010135931A1 (zh) 一种实现制定业务计费策略的方法及系统
CN106304195B (zh) 第三方应用的策略控制方法、scef和pcrf
US20130297812A1 (en) Method and system for realizing application detection and control in ip-can session supporting dual stack
CN102332985B (zh) 一种提供基于lipa承载的计费支持的方法及装置
WO2015055063A1 (zh) 应用接入控制方法及应用功能实体装置
CN101420338B (zh) Pcc架构中的信息查询方法、装置及系统
CN102111740B (zh) 一种支持多接入的策略计费控制方法和系统
WO2011098155A1 (en) Method and apparatus for use with ip connectivity access network
CN101583152B (zh) 一种信息传递方法、装置和系统
US9485106B2 (en) Method for processing TDF session and PCRF
WO2016062026A1 (zh) 一种策略和计费规则功能的选择方法及装置
WO2015188555A1 (zh) 策略控制和计费的方法、装置及设备
CN102238510B (zh) 机器类通信的策略下发方法及系统
WO2009149775A1 (en) Improved credit authorization in a core network
US20150036550A1 (en) Method and system for identifying application detection and control function mode

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 13695282

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2011774308

Country of ref document: EP