WO2009117932A1 - 策略控制的方法和装置 - Google Patents
策略控制的方法和装置 Download PDFInfo
- Publication number
- WO2009117932A1 WO2009117932A1 PCT/CN2009/070922 CN2009070922W WO2009117932A1 WO 2009117932 A1 WO2009117932 A1 WO 2009117932A1 CN 2009070922 W CN2009070922 W CN 2009070922W WO 2009117932 A1 WO2009117932 A1 WO 2009117932A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- session
- policy control
- range
- information
- function
- Prior art date
Links
Classifications
-
- 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0894—Policy-based network configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
Definitions
- the present invention relates to the field of communications, and in particular, to a method and apparatus for policy control.
- Figure 1 shows the User Equipment (User Equipment) in the 3GPP (3rd Generation Partnership Project) SAE (System Architecutre Evolution) system through the non-3 gpp network.
- SAE System Architecutre Evolution
- the s2c interface is connected to the policy control architecture of the EPC (Evolved Packet Core).
- EPC Evolved Packet Core
- PDN Packet Data Network
- IP network If a PDN is assigned to a UE, the UE can access the PDN.
- the Policy Control and Charging Rules Function determines the corresponding policy according to the restriction of the user access network, the operator policy, the user subscription data, and the service information currently being performed by the user.
- the policy is provided to the PCEF (Policy and Charging Enforcement Function) and the BBERF (Bearer Binding and Event Reporting Function). These policies are implemented by the PCEF and the BBERF.
- the policy includes the detection rules of the service data flow (the completion of a certain service, such as a voice IP flow set), whether it is gated, the QoS corresponding to the service data flow, and the flow-based charging rule;
- PGW PDN GateWay, PDN Gateway
- PDN Packet Data
- Network, packet data network) access gateway
- the PCEF performs the PCRF delivery or the specified policy, specifically, the detection, accounting, and QOS control of the service data flow.
- the PCRF sends the policy to the PCEF through the Gx interface in the figure, and the PCEF can be located on the PGW.
- BBERF located in the non-3gpp network, is responsible for the service data stream delivered by the PCRF and
- the QoS policy is bound to the corresponding IP-CAN bearer in the non-3gpp network, and has the function of carrying event reporting.
- the PCRF sends the policy information such as the subscription of the QOS policy and the bearer event to the BBERF through the Gxa interface in the figure;
- the UE, the interface between the UE and the PGW is the s2c interface, and the user packet between the UE and the PDN is transmitted through the DSMIPv6 tunnel on the s2c interface and the SGi interface between the PGW and the PDN.
- HoA Home of Address
- CoA Care of Address
- IP-Connected Network IP-Connected Access Network
- IP-CAN IP-Connected Access Network
- IP-CAN bearer IP-CAN bearer
- IP-CAN bearer IP transmission path with clear rate, delay and bit error rate.
- IP-CAN bearer is the channel from UE to non-3gpp network
- IP-CAN session which refers to the connection relationship between the UE and the PDN identifier (APN (Access Point Name)).
- the connection relationship is based on the IP address of the UE and the identifier of the UE. Identification. As long as the UE is assigned the IP address (HoA) of this PDN and can access this PDN, the Bay ij IP-CAN exists.
- An IP-CAN session can contain one or more IP-CAN bearers.
- the CoA is obtained, and the corresponding Gxa session is established between the BBERF and the PCRF.
- the session carries information about the IP CAN Session corresponding to the CoA.
- the UE establishes a DSMIPv6 tunnel between the CoA and the PGW, and the UE obtains the HoA, and the service data flow of the HoA is carried by the tunnel.
- the PCEF initiates the establishment of the IP CAN Session corresponding to the HoA and its corresponding Gx session to the PCRF.
- the PCRF generates policy control related information of the IP CAN Session corresponding to the HoA, for example, The AMBR (Aggregate Maximum Bit Rate), the event reporting subscription, and the like, and the uplink AMBR and the event reporting subscription can be sent to the BBERF through the Gxa session.
- the uplink AMBR is applicable to the uplink non-GBR service data flow in the IP CAN Session range, and the event reporting subscription is applicable to the entire IP CAN Session range.
- the BBERF cannot obtain the IP CAN Sessum range corresponding to the HoA from the information about the IP CAN session corresponding to the CoA carried on the Gxa session, and the prior art does not specify that the policy control related information is transmitted when the Gxa session is delivered. Applicable IP CAN Session range method. Therefore, under the prior art, BBERF cannot obtain the scope of application of these policy control related information, and cannot apply these policies to control related information to control user services and network resources.
- the embodiment of the invention provides a method and a device for controlling a policy, so that the BBERF can obtain the application scope of the policy control related information, and then apply the policies to control the related information to control the user service and the network resource.
- the embodiment of the invention discloses a method for applying policy control, which includes:
- the bearer binding and event reporting function receives the policy control related information of the IP CAN Session and the indication information of the IP CAN Session range;
- the bearer binding and event reporting function applies the policy control related information of the IP CAN Session within the IP CAN Session specified by the indication information of the IP CAN Session range.
- the embodiment of the invention further provides a device for controlling a policy, comprising:
- the receiving unit receives the tunnel encapsulation header information of the service data flow of the IP CAN Session reported by the policy and the charging execution function;
- the sending unit sends the policy control related information of the IP CAN session and the indication information of the IP CAN Sessum range to the bearer binding and event reporting function.
- An embodiment of the present invention further provides an apparatus for applying policy control, including:
- the policy control information of the session and the indication information of the range of the IP CAN Session Instructing the execution unit to apply the policy control related information of the IP CAN Session according to the indication information of the range of the IP CAN Session.
- the embodiment of the present invention sends the policy control related information of the IP CAN Sessum and the indication information of the IP CAN Session range to the BBERF according to the tunnel encapsulation header information of the service data flow of the IP CAN Session reported by the PCEF.
- the BBERF can obtain the application scope of the policy control related information, and then apply the policies to control the related information to control the user service and the network resource, thereby ensuring the user's service experience and improving the network resource utilization.
- FIG. 1 is a schematic diagram of a policy control architecture of a UE in an existing 3GPP SAE accessing an EPC through a non-3gpp network through an s2c interface;
- FIG. 2 is a schematic flow chart of a method for specifying a policy control related information application scope according to an embodiment of the present invention
- FIG. 3 is a schematic flow chart of a method for specifying a policy control related information application scope according to Embodiment 2 of the present invention
- FIG. 4 is a schematic flow chart of a method for specifying a policy control related information application scope according to Embodiment 3 of the present invention.
- FIG. 5 is a schematic flow chart of a method for specifying a policy control related information application scope according to Embodiment 4 of the present invention.
- FIG. 6 is a schematic diagram showing the structure of an apparatus for specifying a policy control related information application scope according to Embodiment 5 of the present invention.
- FIG. 7 is a schematic diagram showing the structure of an apparatus for controlling a related application range of an application policy according to Embodiment 6 of the present invention.
- FIG. 2 is a schematic flowchart of a method for specifying a policy control related information application scope according to Embodiment 1 of the present invention.
- Step S201 The PCEF reports the tunnel encapsulation header information of the service data flow of the IP CAN Session. Give PCRF.
- the tunnel encapsulation header of the service data flow of the IP CAN session reported by the PCEF to the PCRF can be in multiple formats.
- the GRE encapsulation format is adopted, and the tunnel encapsulation header includes an IP header and a GRE header, and the UE with the tunnel in the IP header is included.
- the end address (set to the UE's CoA), the PGW end address (set to the PGW address), the upper layer protocol type (set to GRE (47)), etc.
- the GRE header contains information such as the GRE-Key.
- Step S202 The PCRF sends the policy control related information of the IP CAN session and the indication information of the IP CAN Session range to the BBERF.
- the PCRF may send a combination of one field or multiple fields of the tunnel encapsulation header described in step S201 to the BBERF as the indication information of the IP CAN Session range.
- the PCRF may The GRE-Key is sent to the BBERF as the indication information of the IP CAN Session range, or the combination of the GRE-Key, the CoA, the tunnel PGW end address, and the upper layer protocol type (GRE) is used as the IP CAN.
- the indication of the session range is sent to BBERF.
- the PCRF may also send the indication information of the corresponding IP CAN Session range to the BBERF according to the combination of one field or multiple fields of the tunnel encapsulation header in the step S201, for example, the tunnel encapsulation header in the GRE encapsulation format, PCRF
- the identifier of the GRE-Key may be generated and sent to the BBERF as the indication information of the corresponding IP CAN Session range.
- the PCRF may send the indication information of the IP CAN Session range by using the RAR command of the Diameter, and the indication information of the IP CAN Session range may be represented by a Diameter AVP, and the GRE encapsulation format is taken as an example.
- -Key is used as the indication information of the IP CAN Session range, and the AVP and message examples are as follows:
- the policy control related information of the IP CAN session sent to the BBERF by the PCRF may be an event report subscription, an uplink AMBR, or the like.
- the information may also be sent by using the RAR command of the Diameter, but is not limited to the same RAR command.
- Step S203 The BBERF applies the policy control related information of the IP CAN Session to the IP CAN Session specified by the indication information of the IP CAN Session range.
- the BBERF applies the event reporting subscription to the IP CAN Session range specified by the indication information of the IP CAN Session range, and the BBERF detects and reports the corresponding event in the IP CAN Session range.
- the BJF BBERF applies the uplink AMBR to the uplink non-GBR service data flow in the IP CAN Session range specified by the indication information of the IP CAN Session range, and the g ⁇ BBERF uses the uplink AMBR to the IP CAN Session range.
- the indication information is limited by the total bandwidth of one or more uplink non-GBR service data streams in the specified IP CAN Session range.
- FIG. 3 is a schematic flowchart of a method for specifying a policy control related information application scope according to Embodiment 2 of the present invention.
- Step S301 The UE is attached to the non-3gpp network, the non-3gpp network allocates the CoA to the UE, and the corresponding Gxa session is established between the BBERF and the PCRF.
- Step S302 The UE is triggered to establish an IP CAN Session to a PDN.
- Step S303 The UE and the PGW interact with each other. In this process, the IP CAN Session is allocated, and the GRE tunnel encapsulation header of the service data stream is generated for the IP CAN Session.
- Step S305 The PCRF generates two service data flows SDF1 and SDF2 of the IP CAN Session and corresponding policies, wherein only SDF1 is an uplink non-GBR service data flow. At the same time, the PCRF obtains the AMBR of the IP CAN Session (including the uplink and downlink AMBR).
- Step S306 The PCRF sends the tunnel encapsulation header, the SDF1 and its corresponding policy, the SDF2 and its corresponding policy, and the uplink AMBR to the BBERF.
- the GRE-Key included in the tunnel encapsulation header is used to indicate the uplink AMBR.
- the PCRF uses the Diameter RAR message to deliver the information and uses the Gxa session established in step 1 to carry the message.
- Step S307 The BBERF applies the uplink AMBR to the SDF1 in the IP CAN Session range, that is, the BBERF detects all the SDFs in the IP CAN Session range by using the GRE-Key in the tunnel encapsulation header, and uses the uplink AMBR pair to all of them.
- the total bandwidth of the non-GBR uplink SDF, SDF1 is limited.
- Step S308 The PCRF is triggered to generate a new service data flow SDF3 of the IP CAN Session and a corresponding policy, and SDF3 is an uplink non-GBR service data flow.
- Step S309 The PCRF sends the tunnel encapsulation header, the SDF3 and the corresponding policy to the BBERF, where the GRE-Key included in the tunnel encapsulation header is used to indicate the IP CAN Session range applicable to the uplink AMBR, and the PCRF uses the Diameter.
- the RAR message is sent to deliver the information and the Gxa session established in step 1 is used to carry the message.
- Step S310 The BBERF applies the uplink AMBR to the IP CAN Session range, that is, the BBERF detects all the SDFs in the IP CAN Session range by using the GRE-Key in the tunnel encapsulation header, and uses all the non-GBRs in the uplink AMBR pair.
- the total bandwidth of the upstream SDF, SDF1 and SDF3, is limited.
- the method of the second embodiment implements:
- the PCEF initiates an IP CAN Session and its corresponding Gx session to the PCRF, and carries The tunnel encapsulation header of the GRE encapsulation format of the service data stream of the IP CAN Session
- the PCRF uses the GRE-Key in the tunnel encapsulation header as the indication information of the IP CAN Session range
- the GRE-Key and the uplink AMBR of the IP CAN Session are Sended to BBERF
- BBERF applies the uplink AMBR to the upstream non-GBR service data stream in the corresponding IP CAN Session range.
- FIG. 4 is a schematic flowchart of a method for specifying a policy application related information in the third embodiment of the present invention.
- Step S401 The UE is attached to the non-3gpp network, the non-3gpp network allocates the CoA to the UE, and the corresponding Gxa session is established between the BBERF and the PCRF.
- Step S402 The UE is triggered to establish an IP CAN Session to a PDN.
- Step S403 The UE and the PGW interact with each other.
- the IP CAN Session is allocated ⁇ , and the GRE tunnel encapsulation header of the service data stream is generated for the IP CAN Session.
- Step S404 The PCEF initiates establishment of an IP CAN Session and its corresponding Gx session to the PCRF, and carries the tunnel encapsulation header and the HoA in the request.
- Step S405 The PCRF generates the service data flow SDF1 of the IP CAN Session and the corresponding policy, and the SDF1 is the uplink GBR service data flow. At the same time, the PCRF obtains the AMBR of the IP CAN Session (including the uplink and downlink AMBR).
- Step S406 The PCRF sends the tunnel encapsulation header, the SDF1 and the corresponding policy to the BBERF, where the tunnel encapsulation header includes the GRE-Key, the CoA, the tunnel PGW end address, and the upper layer protocol type (GRE).
- GRE upper layer protocol type
- the combination is used to indicate the IP CAN Session range applicable to the uplink AMBR, and the PCRF uses the Diameter RAR message to deliver the information, and uses the established Gxa session in the first step to carry the message.
- Step S407 The PCRF is triggered to generate a new service data flow SDF2 of the IP CAN Session and a corresponding policy, and SDF2 is an uplink non-GBR service data flow.
- Step S408 The PCRF sends the tunnel encapsulation header, the SDF2 and its corresponding policy, and the uplink AMBR to the BBERF, where the tunnel encapsulation header includes a GRE-Key, a CoA, a tunnel PGW end address, and an upper layer protocol type (GRE).
- GRE upper layer protocol type
- a combination of four is used to indicate the uplink AMBR
- the PCRF uses the Diameter RAR message to deliver the information and uses the Gxa session established in step 1 to carry the message.
- Step S409 The BBERF applies the uplink AMBR to the SDF2 in the IP CAN Session range, and the ⁇ BBERF detects all the SDFs in the IP CAN Session range by using a combination of the GRE-Key and the like in the tunnel encapsulation header. , using the uplink AMBR to limit the total bandwidth of all non-GBR uplink SDFs, ie, SDF2.
- the method of the third embodiment implements: When the UE establishes an IP CAN Session to a PDN, the PCEF initiates an IP CAN Session and its corresponding Gx session to the PCRF, and carries the GRE encapsulation format of the service data flow of the IP CAN Session.
- the tunnel encapsulation header, the combination of the GRE-Key, the CoA, the tunnel PGW end address, and the upper layer protocol type (GRE) in the tunnel encapsulation header is used as the indication information of the IP CAN Session range, and the indication information is sequentially
- the uplink AMBR of the IP CAN Session is sent to the BBERF, and the BBERF applies the uplink AMBR to the uplink non-GBR service data stream in the corresponding IP CAN Session range.
- FIG. 5 is a schematic flowchart showing a method for specifying a policy control related information application scope according to Embodiment 4 of the present invention.
- Step S501 The UE is attached to the non-3gpp network, the non-3gpp network allocates the CoA to the UE, and the corresponding Gxa session is established between the BBERF and the PCRF.
- Step S502 The UE is triggered to establish an IP CAN Session to a PDN.
- Step S503 The UE and the PGW interact with each other.
- the IP CAN Session is allocated ⁇ , and the GRE tunnel encapsulation header of the service data stream is generated for the IP CAN Session.
- Step S504 The PCEF initiates establishment of an IP CAN Session and its corresponding Gx session to the PCRF, and carries the tunnel encapsulation header and the HoA in the request.
- Step S505 The PCRF generates two service data flows SDF1 and SDF2 of the IP CAN Session and respective corresponding policies, and generates the IP CAN Session range of the IP CAN Session according to the GRE-Key in the tunnel encapsulation header. Instructions.
- Step S506 The PCRF sends the tunnel encapsulation header, the SDF1 and the SDF2, and the corresponding policies and the indication of the IP CAN Session range to the BBERF, and the PCRF uses the Diameter RAR.
- the message is sent to the message and the message is carried using the Gxa session established in step 1.
- Step S507 The PCRF is triggered to update the SDF2 policy, and the event reporting subscription of the IP CAN Session is generated.
- Step S508 The PCRF sends the updated SDF2 policy, the IP CAN Session range indication, and the IP CAN Session event report subscription to the BBERF, and the PCRF uses the Diameter RAR message to deliver the information, and is established in the first step.
- the Gxa session to host the message.
- Step S509 The BBERF applies the event reporting subscription to the IP CAN Session range indicated by the indication of the IP CAN Session range, that is, the tunnel encapsulation header corresponding to the indication of the IP CAN Session range by the BBERF (from step 6)
- the information in the obtained) detects all SDFs in the range of the IP CAN Session, and detects and reports the related events of all the SDFs, namely SDF1 and SDF2.
- the method of the fourth embodiment implements:
- the PCEF initiates an IP CAN Session and its corresponding Gx session to the PCRF, and carries the GRE encapsulation format of the service data stream of the IP CAN Session.
- the tunnel encapsulation header the PCRF generates the indication information of the IP CAN Session range of the IP CAN Session according to the GRE-Key in the tunnel encapsulation header, and sends the indication information and the event reporting subscription of the IP CAN Session to the BBERF.
- the BBERF applies the event escalation subscription to the corresponding IP CAN Session range.
- FIG. 6 is a schematic structural diagram of an apparatus for specifying a policy control related information application scope according to Embodiment 5 of the present invention.
- An apparatus for specifying a policy to control a range of application of related information which is specifically
- PCRF including:
- the receiving unit receives the tunnel encapsulation header information of the service data flow of the IP CAN Session reported by the policy and the charging execution function;
- the sending unit sends the policy control related information of the IP CAN session and the indication information of the IP CAN Sessum range to the bearer binding and event reporting function.
- the tunnel encapsulation header information of the service data flow of the IP CAN session includes the following fields: a UE end address, a PGW end address, an upper layer protocol type, and a GRE-Key of the tunnel.
- the sending unit includes:
- the first unit sends a combination of one or more fields in the tunnel encapsulation header information to the bearer binding and event reporting function as the indication information of the IP CAN Sessum range.
- the sending unit includes:
- the second unit is configured to send the indication information of the IP CAN Sessum range to the bearer binding and event reporting function according to the one of the tunnel encapsulation header information or the combination of the one or more fields.
- the sending unit further includes:
- the third unit sends the policy control related information of the IP CAN session and the indication information of the IP CAN Session range to the bearer binding and event reporting function by using the RAR command of the Diameter protocol, where the indication of the IP CAN Session range is Information is indicated by Diameter AVP.
- FIG. 7 is a schematic structural diagram of an apparatus for applying a policy to control related information in the sixth embodiment of the present invention.
- An apparatus for controlling the application scope of the related information by using a policy which is specifically a BBERF in this embodiment, and includes:
- the policy of the session controls related information and the indication information of the range of the IP CAN Session.
- the instruction execution unit applies the policy control information of the IP CAN Session according to the indication information of the range of the IP CAN Session.
- the indication execution unit includes: a first executing unit, detecting and reporting an event in a range of the IP CAN session.
- the indication execution unit includes: a second execution unit, using the uplink aggregate maximum bit rate to one of a range of the IP CAN Session or The total bandwidth of multiple upstream non-GBR service data streams is limited.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Description
策略控制的方法和装置 技术领域
本发明涉及通信领域, 特别是涉及一种策略控制的方法和装置。
背景技术
如图 1所示, 图 1给出了 3GPP ( Third Generation Partnership Project, 第三代合作项目) SAE ( System Architecutre Evolution, 系统架构演进) 中 UE (User Equipment, 用户设备) 通过 non-3 gpp网络以 s2c接口接入 EPC (Evolved Packet Core, 演进的分组核心) 的策略控制架构, 其中各个功能 实体作用如下描述:
PDN (Packet Data Network, 包数据网络) , 一般是一个 IP网络, 如果 给一个 UE分配了这个 PDN的 IP地址, 贝 l」 UE可以访问这个 PDN;
PCRF (Policy Control and Charging Rules Function, 策略控制和计费规 则功能) , 该功能实体根据用户接入网络的限制, 运营商策略, 用户签约数 据以及用户当前正在进行的业务信息等决定对应的策略, 并将该策略提供给 PCEF (Policy and Charging Enforcement Function, 策略和计费执行功能) 和 BBERF (Bearer Binding and Event Reporting Function, 承载绑定与事件上报 功能) , 由 PCEF和 BBERF执行这些策略。 策略包括业务数据流 (完成某 一业务, 比如语音的 IP流集合) 的检测规则, 是否门控, 业务数据流对应 的 QoS和基于流的计费规则等;
PGW (PDN GateWay, PDN网关) , 为 EPC接入 PDN (Packet Data
Network, 分组数据网络) 的接入网关;
PCEF, 执行 PCRF下发或者指定的策略, 具体来说就是执行业务数据 流的检测、 计费、 QOS控制等, PCRF通过图中的 Gx接口将策略下发给 PCEF, PCEF可位于 PGW上;
BBERF, 位于 non-3gpp网络中, 负责将 PCRF下发的业务数据流及其
QoS策略绑定到 non-3gpp网络中相应的 IP-CAN bearer, 并具备承载事件上 报功能。 PCRF将 QOS策略和承载事件上报的订阅等策略信息通过图中的 Gxa接口下发给 BBERF;
UE, UE与 PGW之间的接口为 s2c接口, UE与 PDN之间的用户报文 通过 s2c接口上的 DSMIPv6隧道和 PGW与 PDN之间的 SGi接口传输。
以下阐述几个术语:
HoA ( Home of Address, 家乡地址) , 即给 UE分配的 PDN的 IP地址; CoA (Care of Address,转发地址) , 在图 1中为 non-3gpp网络为 UE分 配的 IP地址;
IP-CAN (IP Connectivity Access Network, IP连续性接入网络) , 当用 户在接入网络内漫游 (位置改变时) 仍能保存 IP业务连续性 (即不中断业 务) , 具有这样性质的接入网络称为 IP-CAN, 比如 GPRS网络, non-3gpp 网络等;
IP-CAN bearer (IP-CAN承载) , 具有明确速率, 延迟和误比特率的 IP 传输路径, 对于图 1来说 IP-CAN bearer即 UE到 non-3gpp网络的通道;
IP-CAN session ( IP-CAN会话) , 指的是 UE和 PDN标识 (APN (Access Point Name, 接入点名称) ) 之间的连接关系, 该连接关系通过 UE的 IP地址和 UE的标识来识别。 只要 UE被分配了这个 PDN的 IP地址 (HoA) 并且能访问这个 PDN, 贝 ij IP-CAN存在。 IP-CAN会话可以包含一 到多个 IP-CAN承载。
UE附着到 non-3gpp网络时获得 CoA, 同时 BBERF与 PCRF之间建立 对应的 Gxa会话,该会话承载 CoA对应的 IP CAN Session的相关信息。
UE使用 CoA与 PGW间建立 DSMIPv6隧道, 同时 UE获得 HoA, HoA 的业务数据流由该隧道承载。 同时 PCEF向 PCRF发起建立 HoA对应的 IP CAN Session及其对应的 Gx会话。
PCRF生成 HoA对应的 IP CAN Session的策略控制相关信息, 例如上
行 AMBR (Aggregate Maximum Bit Rate, 聚合最大比特率) 、 事件上报订 阅等,上行 AMBR和事件上报订阅可以通过 Gxa会话下发给 BBERF。 上行 AMBR适用于 IP CAN Session范围内的上行 non-GBR业务数据流, 事件上 报订阅则适用于整个 IP CAN Session范围。 而 BBERF无法从 Gxa会话上承 载的 CoA对应的 IP CAN Session的相关信息得到所述 HoA对应的 IP CAN Sessum范围, 现有技术也没有给出在 Gxa会话上传递所述策略控制相关信 息时指明其适用的 IP CAN Session范围的方法。 因此, 现有技术下 BBERF 无法获得这些策略控制相关信息的适用范围, 无法应用这些策略控制相关信 息对用户业务和网络资源进行控制。
发明内容
本发明实施例提供一种策略控制的方法和装置, 使得 BBERF可以获得 策略控制相关信息的应用范围, 从而应用这些策略控制相关信息对用户业务 和网络资源进行控制。
本发明实施例公开一种应用策略控制的方法, 包括:
承载绑定与事件上报功能接收 IP CAN Session的策略控制相关信息和所 述 IP CAN Session范围的指示信息;
承载绑定与事件上报功能在所述 IP CAN Session范围的指示信息指定的 IP CAN Session范围内应用所述 IP CAN Session的策略控制相关信息。
本发明实施例还提供一种策略控制的装置, 包括:
接收单元, 接收策略和计费执行功能上报的 IP CAN Session的业务数据 流的隧道封装头信息;
下发单元, 将所述 IP CAN Session的策略控制相关信息和所述 IP CAN Sessum范围的指示信息下发给承载绑定与事件上报功能。
本发明实施例还提供一种应用策略控制的装置, 包括:
指示接收单元, 接收所述策略控制和计费规则功能下发的所述 IP CAN
Session的策略控制相关信息和所述 IP CAN Session的范围的指示信息;
指示执行单元, 根据所述 IP CAN Session的范围的指示信息应用所述 IP CAN Session的策略控制相关信息。
本发明实施例通过 PCRF根据接收的 PCEF上报的 IP CAN Session的业 务数据流的隧道封装头信息, 下发所述 IP CAN Sessum的策略控制相关信息 和所述 IP CAN Session范围的指示信息给 BBERF, 使得 BBERF可以获得策 略控制相关信息的应用范围, 从而应用这些策略控制相关信息对用户业务和 网络资源进行控制, 从而保证了用户的业务体验, 提高了网络资源利用率。 附图说明
图 1是现有 3GPP SAE中 UE通过 non-3gpp网络以 s2c接口接入 EPC 的策略控制架构图;
图 2是本发明实施例一指定策略控制相关信息应用范围的方法流程示 意图;
图 3 是本发明实施例二指定策略控制相关信息应用范围的方法流程示 意图;
图 4是本发明实施例三指定策略控制相关信息应用范围的方法流程示 意图;
图 5是本发明实施例四指定策略控制相关信息应用范围的方法流程示 意图;
图 6是本发明实施例五指定策略控制相关信息应用范围的装置结构示 意图;
图 7是本发明实施例六应用策略控制相关信息应用范围的装置结构示 意图。
具体实施方式
如图 2所示, 图 2给出了本发明实施例一指定策略控制相关信息应用范 围的方法流程示意图。
歩骤 S201: PCEF上报 IP CAN Session的业务数据流的隧道封装头信息
给 PCRF。
PCEF上报给 PCRF的 IP CAN Session的业务数据流的隧道封装头可以 采用多种格式, 本实施例采用 GRE封装格式, 则隧道封装头包含有 IP头和 GRE头, IP头中包含有隧道的 UE端地址 (设为 UE的 CoA) 、 PGW端地 址 (设为 PGW的地址) 、 上层协议类型 (设为 GRE (47) ) 等信息, GRE 头中包含有 GRE-Key等信息。
歩骤 S202: PCRF将所述 IP CAN Session的策略控制相关信息和所述 IP CAN Session范围的指示信息下发给 BBERF。
PCRF可以将歩骤 S201 中所述的隧道封装头的一个字段或者多个字段 的组合作为所述 IP CAN Session范围的指示信息下发给 BBERF, 例如对于 GRE封装格式的隧道封装头, PCRF可以将其中的 GRE-Key作为所述 IP CAN Session范围的指示信息下发给 BBERF , 或者将其中的 GRE-Key、 CoA、 隧道 PGW端地址、 上层协议类型 (GRE) 四者的组合作为所述 IP CAN Session范围的指示信息下发给 BBERF。
PCRF还可以根据歩骤 S201 中所述隧道封装头的一个字段或者多个字 段的组合生成对应的所述 IP CAN Session范围的指示信息下发给 BBERF, 例如对于 GRE封装格式的隧道封装头, PCRF可以生成所述 GRE-Key的标 识作为对应的所述 IP CAN Session范围的指示信息下发给 BBERF。
具体实现上, PCRF可以通过 Diameter的 RAR命令下发所述 IP CAN Session范围的指示信息, 而所述 IP CAN Session范围的指示信息可以用 Diameter AVP来表示, 以 GRE封装格式为例, 如果以 GRE-Key作为所述 IP CAN Session范围的指示信息, 则 AVP和消息示例如下:
隧道封装头:
Tunnel-Header: := < AVP Header: XXXX >
. . .
[ GRE-Key ]
<RA-Request>:: = < Diameter Header: 258, REQ, PXY >
< Session-Id > [Tunnel-Header]
*[ AVP]
PCRF下发给 BBERF的 IP CAN Session的策略控制相关信息可以是事 件上报订阅、 上行 AMBR等, 这些信息也可以使用 Diameter的 RAR命令 下发, 但不限于使用同一条 RAR命令下发。
歩骤 S203: BBERF在所述 IP CAN Session范围的指示信息指定的 IP CAN Session上应用所述 IP CAN Session的策略控制相关信息。
对于事件上报订阅, BBERF 将事件上报订阅应用于所述 IP CAN Session范围的指示信息指定的 IP CAN Session范围, g卩 BBERF对所述 IP CAN Session范围内的相应事件进行检测和上报。
对于上行 AMBR , 贝 lj BBERF将上行 AMBR应用于所述 IP CAN Session范围的指示信息指定的 IP CAN Session范围中的上行 non-GBR业务 数据流, g卩 BBERF使用上行 AMBR对所述 IP CAN Session范围的指示信 息指定的 IP CAN Session范围中的一个或者多个上行 non-GBR业务数据流 的总带宽进行限制。
如图 3所示, 图 3给出了本发明实施例二指定策略控制相关信息应用范 围的方法流程示意图。
歩骤 S301 : UE附着到 non-3gpp 网络上, non-3gpp 网络为 UE分配 CoA, BBERF与 PCRF之间建立对应的 Gxa会话。
歩骤 S302: UE被触发建立到某个 PDN的 IP CAN Session。
歩骤 S303: UE和 PGW之间进行交互, 在这个过程中, 为 IP CAN Session 分配好 ΗοΑ, 为 IP CAN Session生成其业务数据流的 GRE隧道封装头。
歩骤 S304: PCEF向 PCRF发起建立 IP CAN Session及其对应的 Gx会 话, 并在请求中携带所述隧道封装头和 HoA。
歩骤 S305 : PCRF生成 IP CAN Session的两个业务数据流 SDF1 和 SDF2以及各自对应的策略, 其中仅 SDF1为上行 non-GBR业务数据流。 同 时 PCRF获得 IP CAN Session的 AMBR (包含上行和下行 AMBR) 。
歩骤 S306: PCRF将所述隧道封装头、 SDF1 及其对应的策略、 SDF2 及其对应的策略、 上行 AMBR下发给 BBERF , 所述隧道封装头包含的 GRE-Key用来指示所述上行 AMBR适用的 IP CAN Session范围, PCRF使 用 Diameter RAR消息来下发这些信息, 并使用歩骤 1中建立好的 Gxa会话 来承载该消息。
歩骤 S307: BBERF将上行 AMBR应用于所述 IP CAN Session范围中 的 SDF1 , 即 BBERF使用隧道封装头中的 GRE-Key检测到该 IP CAN Session范围内的所有 SDF, 使用上行 AMBR对其中的所有 non-GBR上行 SDF即 SDF1的总带宽进行限制。
歩骤 S308: PCRF被触发生成 IP CAN Session的新业务数据流 SDF3以 及对应的策略, SDF3为上行 non-GBR业务数据流。
歩骤 S309 : PCRF将所述隧道封装头、 SDF3及其对应的策略下发给 BBERF, 所述隧道封装头包含的 GRE-Key用来指示所述上行 AMBR适用 的 IP CAN Session范围, PCRF使用 Diameter RAR消息来下发这些信息, 并使用歩骤 1中建立好的 Gxa会话来承载该消息。
歩骤 S310: BBERF将上行 AMBR应用于所述 IP CAN Session范围, 即 BBERF使用隧道封装头中的 GRE-Key检测到该 IP CAN Session范围内 的所有 SDF, 使用上行 AMBR对其中的所有 non-GBR上行 SDF即 SDF1和 SDF3的总带宽进行限制。
实施例二的方法实现了: 当 UE建立到某个 PDN的 IP CAN Session 时, PCEF向 PCRF发起建立 IP CAN Session及其对应的 Gx会话, 并携带
IP CAN Session的业务数据流的 GRE封装格式的隧道封装头, PCRF以隧道 封装头中的 GRE-Key作为所述 IP CAN Session范围的指示信息, 将 GRE- Key和该 IP CAN Session的上行 AMBR下发给 BBERF, BBERF将上行 AMBR应用于对应的 IP CAN Session范围中的上行 non-GBR业务数据流。
如图 4所示, 图 4给出了本发明实施例三指定策略控制相关信息应用范 围的方法流程示意图。
歩骤 S401 : UE附着到 non-3gpp 网络上, non-3gpp 网络为 UE分配 CoA, BBERF与 PCRF之间建立对应的 Gxa会话。
歩骤 S402: UE被触发建立到某个 PDN的 IP CAN Session。
歩骤 S403: UE和 PGW之间进行交互, 在这个过程中, 为 IP CAN Session 分配好 ΗοΑ, 为 IP CAN Session生成其业务数据流的 GRE隧道封装头。
歩骤 S404: PCEF向 PCRF发起建立 IP CAN Session及其对应的 Gx会 话, 并在请求中携带所述隧道封装头和 HoA。
歩骤 S405: PCRF生成 IP CAN Session的业务数据流 SDF1和对应的策 略, SDF1 为上行 GBR业务数据流。 同时 PCRF获得 IP CAN Session的 AMBR (包含上行和下行 AMBR) 。
歩骤 S406 : PCRF将所述隧道封装头、 SDF1 及其对应的策略下发给 BBERF, 所述隧道封装头包含的 GRE-Key、 CoA、 隧道 PGW端地址、 上层 协议类型 (GRE) 四者的组合用来指示所述上行 AMBR适用的 IP CAN Session范围, PCRF使用 Diameter RAR消息来下发这些信息, 并使用歩骤 1中建立好的 Gxa会话来承载该消息。
歩骤 S407: PCRF被触发生成 IP CAN Session的新业务数据流 SDF2以 及对应的策略, SDF2为上行 non-GBR业务数据流。
歩骤 S408 : PCRF将所述隧道封装头、 SDF2及其对应的策略、 上行 AMBR下发给 BBERF , 所述隧道封装头包含的 GRE-Key、 CoA、 隧道 PGW端地址、 上层协议类型 (GRE) 四者的组合用来指示所述上行 AMBR
适用的 IP CAN Session范围, PCRF使用 Diameter RAR消息来下发这些信 息, 并使用歩骤 1中建立好的 Gxa会话来承载该消息。
歩骤 S409: BBERF将上行 AMBR应用于所述 IP CAN Session范围中 的 SDF2,g卩 BBERF使用隧道封装头中的所述 GRE-Key等四者的组合检测到 该 IP CAN Session范围内的所有 SDF, 使用上行 AMBR对其中的所有 non- GBR上行 SDF即 SDF2的总带宽进行限制。
实施例三的方法实现了: 当 UE建立到某个 PDN的 IP CAN Session 时, PCEF向 PCRF发起建立 IP CAN Session及其对应的 Gx会话, 并携带 IP CAN Session的业务数据流的 GRE封装格式的隧道封装头, PCRF以隧道 封装头中的 GRE-Key、 CoA、 隧道 PGW端地址、 上层协议类型 (GRE) 四 者的组合作为所述 IP CAN Session范围的指示信息, 并先后将该指示信息和 该 IP CAN Session的上行 AMBR下发给 BBERF, BBERF将上行 AMBR应 用于对应的 IP CAN Session范围中的上行 non-GBR业务数据流。
如图 5所示, 图 5给出了本发明实施例四指定策略控制相关信息应用范 围的方法流程示意图。
歩骤 S501 : UE附着到 non-3gpp 网络上, non-3gpp 网络为 UE分配 CoA, BBERF与 PCRF之间建立对应的 Gxa会话。
歩骤 S502: UE被触发建立到某个 PDN的 IP CAN Session。
歩骤 S503: UE和 PGW之间进行交互, 在这个过程中, 为 IP CAN Session 分配好 ΗοΑ, 为 IP CAN Session生成其业务数据流的 GRE隧道封装头。
歩骤 S504: PCEF向 PCRF发起建立 IP CAN Session及其对应的 Gx会 话, 并在请求中携带所述隧道封装头和 HoA。
歩骤 S505: PCRF生成该 IP CAN Session的两个业务数据流 SDF1和 SDF2 以及各自对应的策略, 并根据所述隧道封装头中的 GRE-Key生成该 IP CAN Session的所述 IP CAN Session范围的指示信息。
歩骤 S506: PCRF将所述隧道封装头、 SDF1和 SDF2以及各自对应的策 略、 所述 IP CAN Session范围的指示下发给 BBERF, PCRF使用 Diameter RAR
消息来下发这些信息, 并使用歩骤 1中建立好的 Gxa会话来承载该消息。
歩骤 S507: PCRF被触发更新 SDF2的策略, 同时生成 IP CAN Session 的事件上报订阅。
歩骤 S508: PCRF将更新的 SDF2的策略、 IP CAN Session范围的指示、 IP CAN Session的事件上报订阅下发给 BBERF, PCRF使用 Diameter RAR消 息来下发这些信息, 并使用歩骤 1中建立好的 Gxa会话来承载该消息。
歩骤 S509: BBERF将所述事件上报订阅应用于所述 IP CAN Session范 围的指示指示的 IP CAN Session范围, 即 BBERF根据所述 IP CAN Session 范围的指示所对应的隧道封装头 (从歩骤 6得到) 中的信息检测到该 IP CAN Session范围内的所有 SDF, 对其中的所有 SDF即 SDF1和 SDF2的相 关事件进行检测和上报。
实施例四的方法实现了: 当 UE建立到某个 PDN的 IP CAN Session 时, PCEF向 PCRF发起建立 IP CAN Session及其对应的 Gx会话, 并携带 IP CAN Session的业务数据流的 GRE封装格式的隧道封装头, PCRF根据隧 道封装头中的 GRE-Key生成该 IP CAN Session的所述 IP CAN Session范围 的指示信息, 并先后将该指示信息和该 IP CAN Session的事件上报订阅下发 给 BBERF, BBERF将该事件上报订阅应用于对应的 IP CAN Session范围。
如图 6所示, 图 6给出了本发明实施例五指定策略控制相关信息应用范 围的装置结构示意图。
一种指定策略控制相关信息应用范围的的装置, 在本实施例中具体为
PCRF, 包括:
接收单元, 接收策略和计费执行功能上报的 IP CAN Session的业务数据 流的隧道封装头信息;
下发单元, 将所述 IP CAN Session的策略控制相关信息和所述 IP CAN Sessum范围的指示信息下发给承载绑定与事件上报功能。
其中, IP CAN Session的业务数据流的隧道封装头信息包括以下字段: 所述隧道的 UE端地址、 PGW端地址、 上层协议类型、 GRE-Key。
可选的, 下发单元包括:
第一单元, 将所述隧道封装头信息中的一个字段或一个以上字段的组合 作为所述 IP CAN Sessum范围的指示信息下发给承载绑定与事件上报功能。
可选的, 下发单元包括:
第二单元, 根据所述隧道封装头信息中的一个字段或一个以上字段的组 合生成所述 IP CAN Sessum范围的指示信息下发给承载绑定与事件上报功能。
可选的, 下发单元还包括:
第三单元, 通过 Diameter协议的 RAR命令将所述 IP CAN Session的策 略控制相关信息和所述 IP CAN Session范围的指示信息下发给承载绑定与事 件上报功能, 所述 IP CAN Session范围的指示信息用 Diameter AVP表示。
如图 7所示, 图 7给出了本发明实施例六应用策略控制相关信息应用范 围的装置结构示意图。
一种应用策略控制相关信息应用范围的装置, 本实施例中具体为 BBERF, 包括:
指示接收单元, 接收所述策略控制和计费规则功能下发的所述 IP CAN
Session的策略控制相关信息和所述 IP CAN Session的范围的指示信息; 指示执行单元, 根据所述 IP CAN Session的范围的指示信息应用所述 IP CAN Session的策略控制相关信息。
可选的, 当所述策略控制相关信息为事件上报订阅, 所述指示执行单元包 括: 第一执行单元, 对所述 IP CAN Session的范围内的事件进行检测和上报。
可选的, 当所述策略控制相关信息为上行聚合最大比特率, 所述指示执 行单元包括: 第二执行单元, 使用所述上行聚合最大比特率对所述 IP CAN Session的范围内的一个或多个上行 non-GBR业务数据流的总带宽进行限制。
显然, 本领域的技术人员可以对本发明进行各种改动和变型而不脱离本 发明的精神和范围。 这样, 倘若本发明的这些修改和变型属于本发明权利要 求及其等同技术的范围之内, 则本发明也意图包含这些改动和变型在内。
Claims
1、 一种应用策略控制的方法, 其特征在于, 所述方法包括:
承载绑定与事件上报功能接收 IP CAN Session的策略控制相关信息和所 述 IP CAN Session的范围的指示信息;
所述承载绑定与事件上报功能根据所述 IP CAN Session的范围的指示信 息应用所述 IP CAN Session的策略控制相关信息。
2、 如权利要求 1所述的方法, 其特征在于, 所述方法还包括: 策略控制和计费规则功能接收策略和计费执行功能上报的所述 IP CAN
Session的业务数据流的隧道封装头信息;
所述策略控制和计费规则功能根据所述 IP CAN Session的业务数据流的 隧道封装头信息将所述 IP CAN Session的范围的指示信息下发给所述承载绑 定与事件上报功能。
3、 如权利要求 2所述的方法, 其特征在于, 所述策略控制和计费规则 功能根据所述 IP CAN Session的业务数据流的隧道封装头信息将所述 IP CAN Session的范围的指示信息下发给所述承载绑定与事件上报功能包括: 所述策略控制和计费规则功能将所述隧道封装头信息中的一个字段或一 个以上字段的组合作为所述 IP CAN Session的范围的指示信息下发给所述承 载绑定与事件上报功能。
4、 如权利要求 2所述的方法, 其特征在于, 所述策略控制和计费规则 功能根据所述 IP CAN Session的业务数据流的隧道封装头信息将所述 IP
CAN Session的范围的指示信息下发给所述承载绑定与事件上报功能包括: 所述策略控制和计费规则功能根据所述隧道封装头信息中的一个字段或 一个以上字段的组合生成所述 IP CAN Session的范围的指示信息下发给所述 承载绑定与事件上报功能。
5、 如权利要求 2所述的方法, 其特征在于, 所述策略控制和计费规则 功能根据所述 IP CAN Session的业务数据流的隧道封装头信息将所述 IP CAN Session的范围的指示信息下发给所述承载绑定与事件上报功能包括:
所述策略控制和计费规则功能通过 Diameter协议的 RAR命令将所述 IP CAN Session的策略控制相关信息和所述 IP CAN Session的范围的指示信息 下发给所述承载绑定与事件上报功能, 所述 IP CAN Session的范围的指示信 息用 Diameter AVP表示。
6、 如权利要求 1所述的方法, 其特征在于,
所述策略控制相关信息为事件上报订阅;
所述承载绑定与事件上报功能根据所述 IP CAN Session的范围的指示信 息应用所述 IP CAN Session的策略控制相关信息为: 所述承载绑定与事件上 报功能对所述 IP CAN Session的范围内的事件进行检测和上报。
7、 如权利要求 1所述的方法, 其特征在于,
所述策略控制相关信息为上行聚合最大比特率;
所述承载绑定与事件上报功能根据所述 IP CAN Session的范围的指示信 息应用所述 IP CAN Session的策略控制相关信息为: 所述承载绑定与事件上 报功能使用所述上行聚合最大比特率对所述 IP CAN Session的范围内的一个 或多个上行 non-GBR业务数据流的总带宽进行限制。
8、 一种策略控制的装置, 其特征在于, 所述装置包括:
接收单元, 用于接收策略和计费执行功能上报的 IP CAN Session的业务 数据流的隧道封装头信息;
下发单元, 用于将所述 IP CAN Session的策略控制相关信息和所述 IP CAN Sessum范围的指示信息下发给承载绑定与事件上报功能。
9、 如权利要求 8所述的装置, 其特征在于, 所述 IP CAN Session的业 务数据流的隧道封装头是 GRE封装格式的隧道封装头, 包括以下字段: 所述隧道的 UE端地址、 所述隧道的 PGW端地址、 所述 GRE封装格式 的隧道封装头中的上层协议类型、 所述隧道的 GRE-Key。
10、 如权利要求 9所述的装置, 其特征在于, 所述下发单元包括: 第一单元, 用于将所述隧道封装头信息中的一个字段或一个以上字段的组 合作为所述 IP CAN Session范围的指示信息下发给承载绑定与事件上报功能。
11、 如权利要求 9所述的装置, 其特征在于, 所述下发单元包括: 第二单元, 用于根据所述隧道封装头信息中的一个字段或一个以上字段 的组合生成所述 IP CAN Session范围的指示信息下发给承载绑定与事件上报 功能。
12、 如权利要求 8所述的装置, 其特征在于, 所述下发单元包括: 第三单元, 用于通过 Diameter协议的 RAR命令将所述 IP CAN Session的 策略控制相关信息和所述 IP CAN Session范围的指示信息下发给承载绑定与 事件上报功能, 所述 IP CAN Session范围的指示信息用 Diameter AVP表示。
13、 如权利要求 8所述的装置, 其特征在于,
所述装置为策略控制和计费规则功能。
14、 一种应用策略控制的装置, 其特征在于, 包括:
指示接收单元, 用于接收所述策略控制和计费规则功能下发的所述 IP CAN Session的策略控制相关信息和所述 IP CAN Session的范围的指示信息; 指示执行单元, 用于根据所述 IP CAN Session的范围的指示信息应用所 述 IP CAN Session的策略控制相关信息。
15、 如权利要求 14所述的装置, 其特征在于,
所述装置为承载绑定与事件上报功能接收。
16、 如权利要求 14所述的装置, 其特征在于,
所述策略控制相关信息为事件上报订阅;
所述指示执行单元包括: 第一执行单元, 用于对所述 IP CAN Session的 范围内的事件进行检测和上报。
17、 如权利要求 14所述的装置, 其特征在于,
所述策略控制相关信息为上行聚合最大比特率;
所述指示执行单元包括: 第二执行单元, 用于使用所述上行聚合最大比 特率对所述 IP CAN Session的范围内的一个或多个上行 non-GBR业务数据 流的总带宽进行限制。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200810066196.9 | 2008-03-26 | ||
CN200810066196A CN101547133A (zh) | 2008-03-26 | 2008-03-26 | 策略控制的方法和装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2009117932A1 true WO2009117932A1 (zh) | 2009-10-01 |
Family
ID=41112960
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2009/070922 WO2009117932A1 (zh) | 2008-03-26 | 2009-03-20 | 策略控制的方法和装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN101547133A (zh) |
WO (1) | WO2009117932A1 (zh) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102137370B (zh) * | 2010-01-25 | 2015-10-21 | 中兴通讯股份有限公司 | 一种实现对用户进行统一计费的方法和装置 |
CN102215469B (zh) * | 2010-04-09 | 2015-01-28 | 中兴通讯股份有限公司 | 一种基于网络负荷的策略计费控制方法和系统 |
CN102075898B (zh) | 2010-12-21 | 2014-02-26 | 华为技术有限公司 | 业务控制方法、装置及系统 |
US9231774B2 (en) * | 2012-09-27 | 2016-01-05 | Alcatel Lucent | Congestion control for radio access networks (RAN) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1770915A1 (en) * | 2005-09-29 | 2007-04-04 | Matsushita Electric Industrial Co., Ltd. | Policy control in the evolved system architecture |
WO2007138407A2 (en) * | 2006-06-01 | 2007-12-06 | Nokia Corporation | Inter-access handover with access specific policy control functions |
CN101141821A (zh) * | 2007-09-30 | 2008-03-12 | 中兴通讯股份有限公司 | 一种无线通信网络的策略和计费执行功能节点定位方法 |
CN101141412A (zh) * | 2007-10-12 | 2008-03-12 | 中兴通讯股份有限公司 | 一种为用户终端建立专有承载的方法 |
-
2008
- 2008-03-26 CN CN200810066196A patent/CN101547133A/zh active Pending
-
2009
- 2009-03-20 WO PCT/CN2009/070922 patent/WO2009117932A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1770915A1 (en) * | 2005-09-29 | 2007-04-04 | Matsushita Electric Industrial Co., Ltd. | Policy control in the evolved system architecture |
WO2007138407A2 (en) * | 2006-06-01 | 2007-12-06 | Nokia Corporation | Inter-access handover with access specific policy control functions |
CN101141821A (zh) * | 2007-09-30 | 2008-03-12 | 中兴通讯股份有限公司 | 一种无线通信网络的策略和计费执行功能节点定位方法 |
CN101141412A (zh) * | 2007-10-12 | 2008-03-12 | 中兴通讯股份有限公司 | 一种为用户终端建立专有承载的方法 |
Also Published As
Publication number | Publication date |
---|---|
CN101547133A (zh) | 2009-09-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN101841797B (zh) | 一种终端通过多接入网接入的计费方法和系统及上报方法 | |
EP2339781B1 (en) | Method and system for realizing the policy and charging control in the multiple packet data networks (pdn) scene | |
EP2443865B1 (en) | Establishing a communication session | |
US9191960B2 (en) | Methods and apparatus for mitigating service interruption | |
US9602417B2 (en) | Multiple bearer support upon congestion situations | |
WO2011063722A1 (zh) | 一种实现用量监测控制的方法及系统 | |
WO2007109982A1 (fr) | Procédé et appareil de commande de porteuses de flux de données de services | |
WO2011060698A1 (zh) | 一种实现用量监测控制的方法及系统 | |
WO2012058998A1 (zh) | 漫游场景下支持ip流迁移的策略计费控制方法和系统 | |
WO2008128470A1 (fr) | Procédé, système et entité de réalisation de détection d'événement | |
WO2012103770A1 (zh) | 一种支持流检测功能的用量监控方法及系统 | |
WO2013104234A1 (zh) | 一种融合网络中策略控制方法及系统 | |
EP3116284A1 (en) | Method and device for managing charging session | |
WO2011124106A1 (zh) | 一种策略计费控制方法、系统和装置 | |
WO2011029289A1 (zh) | 漫游场景下承载控制模式的发送方法和系统 | |
WO2011085614A1 (zh) | 在全业务融合网络中控制资源的方法和系统 | |
WO2012097676A1 (zh) | 支持双栈的ip-can会话实现应用检测和控制的方法及系统 | |
WO2011140895A1 (zh) | 签约业务合并场景下对qos参数进行处理的方法及设备 | |
WO2014032289A1 (zh) | 带宽控制方法、装置及系统 | |
WO2011095025A1 (zh) | 一种对移动用户本地接入的策略控制方法和系统 | |
WO2013060170A1 (zh) | 一种提供基于lipa承载的计费支持的方法及装置 | |
WO2011120222A1 (zh) | 优先级业务激活、去激活方法、装置和系统 | |
WO2014094488A1 (zh) | 漫游本地业务的计费策略方法及装置 | |
WO2009117932A1 (zh) | 策略控制的方法和装置 | |
WO2011088702A1 (zh) | 在全业务融合网络中控制资源的方法和系统 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09724862 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: 09724862 Country of ref document: EP Kind code of ref document: A1 |