WO2012028044A1 - Procédé et système pour traiter une erreur ifom - Google Patents

Procédé et système pour traiter une erreur ifom Download PDF

Info

Publication number
WO2012028044A1
WO2012028044A1 PCT/CN2011/077638 CN2011077638W WO2012028044A1 WO 2012028044 A1 WO2012028044 A1 WO 2012028044A1 CN 2011077638 W CN2011077638 W CN 2011077638W WO 2012028044 A1 WO2012028044 A1 WO 2012028044A1
Authority
WO
WIPO (PCT)
Prior art keywords
flow
pcrf
message
ifom
information
Prior art date
Application number
PCT/CN2011/077638
Other languages
English (en)
Chinese (zh)
Inventor
周星月
周晓云
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012028044A1 publication Critical patent/WO2012028044A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels

Definitions

  • the present invention relates to an IP flow migration (IFOM) technology in the field of communications, and more particularly to a method and system for processing an IFOM error.
  • IFOM IP flow migration
  • FIG. 1 is an EPS network architecture diagram of a non-roaming scenario.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • HSS Home Subscriber Server
  • PCRF Policy and Charging Rules Function
  • the application function entity (AF, Application Function) provides access points for service applications.
  • the network resources used by these service applications require dynamic policy control.
  • the AF passes the relevant service information to the PCRF. If the service information is consistent with the policy of the PCRF, the PCRF accepts the negotiation; otherwise, the PCRF rejects the negotiation and simultaneously gives the business parameters acceptable to the PCRF in the feedback. The AF can then return these parameters to the user equipment (UE, User Equipment).
  • UE User Equipment
  • the interface between AF and PCRF is the Rx interface.
  • the PCRF is the core of Policy and Charging Control (PCC) and is responsible for policy decision making and charging 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.
  • PCRF The policy and charging rules are sent to the Policy and Charging Enforcement Function (PCEF).
  • PCEF Policy and Charging Enforcement Function
  • the basis for formulating the policy and charging rules by the PCRF includes: obtaining information related to the service from the AF; obtaining the subscription information with the user policy charging control from the SPR (Spread Profile Repository); and obtaining the information related to the bearer related network from the PCEF .
  • the PCEF is usually located in the gateway (GW, GateWay) and performs the policy and charging rules defined by the PCRF on the bearer plane.
  • the PCEF detects the service data flow according to the service data flow filter in the rule sent by the PCRF, and then executes the policy and charging rules formulated by the PCRF for these service data flows.
  • the PCEF performs QoS authorization according to the rules sent by the PCRF, and performs gate control according to the execution of the AF.
  • the charging rule sent by the PCRF the PCEF performs a corresponding service data flow charging operation, and the charging can be either online charging or offline charging. In the case of online charging, PCEF needs to perform credit management together with the Online Charging System (OCS).
  • OCS Online Charging System
  • PCEFs are generally located on the gateway of the network, such as GPRS Gateway Support Node (GGSN) in the General Packet Radio Service (GPRS, General Packet Radio Service), Intelligent Wireless Office i or Network (I-WLAN, Intelligent Packet Data Gateway (PDG) in Wireless Local Area Networks
  • GGSN GPRS Gateway Support Node
  • I-WLAN Intelligent Packet Data Gateway
  • PSG Intelligent Packet Data Gateway
  • BPCF broadband policy control architecture
  • PEF Policy Enforcement Point
  • BRAS Broadband Remote Access Server
  • BNG Broadband Network Gateway
  • AAA Authentication Authorization and Accounting
  • the IFOM (IP Flow Mobility) technology can implement the migration of IP service flows between different access systems.
  • the UE can modify the service flow routing path according to the network congestion status and policies to ensure communication quality and improve user experience.
  • the UE is connected to the same PDN through the 3GPP access system and the I-WLAN access system at the same time, and the service flow through the 3GPP network includes a voice IP stream, a traditional video stream, and a non-traditional video stream.
  • the service flow of the I-WLAN access system includes a network (Web) service flow and a File Transfer Protocol (FTP) flow.
  • Web network
  • FTP File Transfer Protocol
  • the UE initiates an IFOM process of migrating the Web stream from the I-WLAN to the 3GPP to ensure the Web application. Transmission quality. As shown in Figure 3, after a successful migration, the path of the Web stream is changed to be transmitted from the 3GPP network.
  • the UE and the network side move IPv6 through a double tunnel (DSMIPv6,
  • the signaling of the dual-Stack Mobile IPv6 is negotiated for the flow migration information.
  • the UE and the network side modify the corresponding flow migration routing rule information accordingly.
  • the network side may apply for the network bearer resources for the migrating flow to perform QoS guarantee. If there is a failure to apply for the resource, there is no corresponding solution for how to process the service flow that has been modified by the routing rule. If it is not processed, the QoS of the migrated service flow will not be guaranteed or even the service interruption, which will make the user experience worse.
  • the main purpose of the present invention is to provide a method and system for processing an IFOM error, in the process of solving the existing IFOM, in the case that the resource for the migrated stream fails, the traffic flow after the migration is caused. QoS is not guaranteed or even business interruption.
  • the technical solution of the present invention is achieved as follows:
  • the present invention provides a method for processing an IFOM error, the method comprising:
  • the policy and charging rule function entity PCRF
  • the flow migration information is notified to the home agent (HA) of the UE, triggering a processing operation for the failure.
  • the faulty flow migration information is: routing rule information of the flow or routing rule identifier of the flow.
  • the method further includes:
  • the HA sends an acknowledgement message to the PCRF, and notifies the UE of the faulty flow migration information by using the binding release indication message;
  • the UE sends a binding release message confirmation to the HA.
  • the method further includes: the UE sending a binding update message to the HA, and notifying the HA to re-select a routing path for the flow corresponding to the fault;
  • the HA sends an IP connection access network (IP-CAN) session modification request message to the PCRF, where the routing rule information that needs to be updated is included;
  • IP-CAN IP connection access network
  • the PCRF sends an IP-CAN session modification response message to the HA;
  • the HA sends a Binding Update Confirm message to the UE.
  • the rerouting path is rectified for the flow corresponding to the fault, which is specifically:
  • the flow corresponding to the fault is returned to the routing path before the flow migration, or a new routing path is selected for the flow corresponding to the fault, or a default path is selected for the flow corresponding to the fault.
  • the present invention also provides a processing system when the IFOM is in error, and the system includes: a network side, a PCRF, a UE, and a HA of the UE, where The UE and the network side, the routing rule negotiation for completing the flow migration in the IFOM process; the PCRF is configured to perform QoS resource management on the network side after the routing rule negotiation of the flow migration is completed on the UE and the network side In the case of a related fault, the faulty flow migration information is notified to the HA of the UE, and the processing operation for the fault is triggered.
  • the faulty flow migration information is: routing rule information of the flow or routing rule identifier of the flow.
  • the HA is further configured to: after the PCRF notifies the HA of the UE of the faulty flow migration information, the HA sends an acknowledgement message to the PCRF, and notifies the faulty flow migration information to the UE;
  • the UE is further configured to send a binding release message acknowledgement to the HA.
  • the UE is further configured to: send a binding update message to the HA, and notify the HA to re-select a routing path for the flow corresponding to the fault;
  • the HA is further used to send an IP-CAN session modification request message to the PCRF, where the routing rule information that needs to be updated is included;
  • the PCRF is further configured to send an IP-CAN session modification response message to the HA; the HA is further configured to send a binding update confirmation message to the UE.
  • the UE is further configured to notify the HA to roll back the flow corresponding to the fault to the routing path before the flow migration, or select a new routing path for the flow corresponding to the fault, or select a default path for the flow corresponding to the fault.
  • the IFOM error processing method and system provided by the present invention, after the routing rule negotiation of the flow migration is completed between the UE and the network side in the IFOM process, if the QoS resource management related fault occurs on the network side, the PCRF will be faulty.
  • the flow migration information is notified to the HA of the UE, triggering a processing operation for the failure.
  • the present invention in the process of solving the existing IFOM, if the resource application for the migrated flow fails, the QoS of the migrated service flow cannot be guaranteed or even the service is interrupted, and the continuity of the service is ensured. The quality of the user experience is guaranteed.
  • FIG. 1 is an EPS network architecture diagram of a non-roaming scenario in the prior art
  • FIG. 2 is a schematic diagram 1 of IP flow migration in the prior art
  • FIG. 3 is a schematic diagram 2 of IP flow migration in the prior art
  • FIG. 4 is a flowchart of a processing method when an IFOM error is performed according to the present invention.
  • FIG. 5 is a flowchart of a method for processing an IFOM error in a scenario according to Embodiment 1 of the present invention
  • FIG. 6 is a flowchart of a method for processing an IFOM error in a scenario according to Embodiment 2 of the present invention
  • the method for processing an IFOM error provided by the present invention mainly includes the following contents: After the routing rule negotiation (step 401) of the flow migration between the UE and the network side in the IFOM process, if the network The QoS resource management related fault occurs on the side, and the PCRF notifies the home agent (HA, Home Agent) of the faulty flow migration information, and triggers a processing operation for the fault (step 402).
  • the faulty flow migration information may be: a routing rule information of the flow or a routing rule ID of the flow.
  • the processing of the fault includes: re-selecting the routing path for the flow corresponding to the fault. Specifically, the flow corresponding to the fault may be returned to the routing path before the flow migration, or a new routing path may be selected for the flow corresponding to the fault. Or select the default path for the stream corresponding to the fault.
  • the processing method of the above IFOM error will be further elaborated below in conjunction with a specific embodiment.
  • the application scenario of the first embodiment of the present invention is: the UE is simultaneously connected to the 3GPP access network and the non-3GPP access network, and multiple binding relationships and multiple IP flow binding association registrations are established for the same home address (Home Address).
  • the UE sends a binding update message to the HA, and the service flow transmitted through the non-3GPP is migrated to the 3GPP network for transmission, and the PCRF applies for the QoS of the migrated service flow. 7
  • the S-GW and the P-GW in 3GPP use the S5 interface based on the Proxy Mobile IPv6 (Proxy Mobile IPv6) mobility management protocol.
  • the specific process mainly includes the following steps:
  • Step 501 The UE currently connects to the 3GPP and the non-3GPP access network at the same time, and establishes a binding association for the service flows that belong to the same PDN connection and through different access networks, and establishes multiple binding relationships and multiple IP flows. Registration.
  • Step 502 The UE sends a Binding Update message to the HA, where the message carries the home address, the binding identifier, and the flow binding information of the UE. After receiving the binding update message, the HA according to the binding identifier and the flow. The binding information is used to modify the routing rule information of the corresponding service flow, where the routing rule information includes the quintuple information of the IP file and the corresponding route of the IP address.
  • Step 503 The P-GW (HA) sends an IP-Connectivity Access Network (IP-CAN, IP-Connectivity Access Network) session modification request message to the PCRF, where the request message includes routing rule information to be updated.
  • IP-CAN IP-Connectivity Access Network
  • IP-Connectivity Access Network IP-Connectivity Access Network
  • P-GW (HA) is a function indicating that the P-GW includes HA, and P-GW and HA are combined.
  • Step 504 The PCRF sends an IP-CAN session modification response message to the P-GW.
  • Step 505 The HA returns a Binding Update Acknowledgement message to the UE to confirm the service flow binding operation of the UE, where the message includes a binding lifetime, a home address of the UE, and a binding identifier. , stream binding information.
  • Step 506 The PCRF sends a gateway control and a QoS providing message to the S-GW, where the message includes information such as a QoS rule and an event trigger.
  • Step 507 The S-GW sends an Update Bearer Request message to the MME, where the message includes a Process Transaction Id (PTI), an EPS bearer identifier, an EPS bearer QoS information, and a data flow template (TFT, Traffic Flow). Template ), Access Point Name - Aggregate Maximum Bit Rate (APN-AMBR).
  • eNB evolved NodeB
  • Step 509 The eNB fails to coordinate the allocation of the QoS-related bearer resource according to the information in the received session management request message.
  • Step 510 The eNB sends a bearer modification response message to the MME, to notify the MME that the EPS bearer QoS requested is not allocated.
  • Step 511 The MME sends an update bearer response message to the S-GW, to notify the EPS bearer that the QoS assignment fails.
  • Step 512 The S-GW sends a gateway control and QoS rule execution response message to the PCRF, and notifies that the corresponding QoS rule of the PCRF fails to be executed.
  • Step 513 The PCRF sends a PCC rule providing message to the P-GW (HA) to notify the PCC that the rule execution fails.
  • the message includes information to identify a service flow that cannot allocate the QoS resource, and the information may be a routing rule of the service flow.
  • the rule ) information can also be the routing rule ID (requires the HA to be saved and the routing rule ID consistent on the PCRF).
  • Step 514 the P-GW (HA) sends an acknowledgement message to the PCRF.
  • Step 515 The P-GW (HA) notifies the UE of the service flow information that fails the QoS resource application, and the UE may be notified by carrying the flow binding information in the binding release indication message.
  • Step 516 The UE sends a binding release message confirmation to the P-GW (HA).
  • Step 517 The UE sends a new binding update message to the P-GW (HA) to roll back the previous service flow to the original routing path.
  • the UE's manipulation depends on the UE's local policy implementation, and the UE may also select a new routing path or select a default route for the service flow.
  • Step 518 The P-GW (HA) sends an IP-CAN session modification request message to the PCRF, where the request message includes routing rule information to be updated.
  • step 519 the PCRF sends an IP-CAN session modification response message to the P-GW.
  • the application scenario of the second embodiment of the present invention is: the UE is simultaneously connected to the WLAN access system of the 3GPP and the BBF, and multiple binding relationships and multiple IP flow binding association registrations are established for the same home address; the UE sends the binding to the HA.
  • the update message is used to migrate the traffic flow transmitted by the 3GPP to the BBF network, and the BPCF fails to apply for the QoS bearer resource for the migrated service flow.
  • the specific process mainly includes the following steps:
  • Step 601 The UE is currently connected to the WLAN access system of the 3GPP and the BBF, and establishes a binding association for the service flows that belong to the same PDN connection and through different access networks, and establishes multiple binding relationships and multiple IP flows. Bind registration.
  • Step 602 The UE sends a Binding Update message to the HA, where the message carries the home address, the binding identifier, and the flow binding information of the UE. After receiving the binding update message, the HA binds according to the binding identifier and the flow. Determine the information and modify the routing rule information of the corresponding service flow.
  • Step 603 The P-GW (HA) sends an IP-CAN session modification request to the PCRF, where the request message includes routing rule information to be updated, and the like.
  • Step 604 The PCRF sends an IP-CAN session modification response message to the P-GW.
  • Step 605 The HA returns a binding update confirmation message to the UE, to confirm the service flow binding operation of the UE, where the message includes a binding lifetime, a home address, a binding identifier, and a flow binding information of the UE. .
  • Step 606 The PCRF sends an S9* session request message to the BPCF, where the message includes information such as a QoS rule and an event trigger.
  • Step 607 The BPCF fails to allocate the QoS-related bearer resource according to the information in the received session management request message in the BBF access system.
  • Step 608 The BPCF returns an S9* session response message to the PCRF, indicating that the QoS related resource application fails.
  • Step 609 The PCRF sends a PCC rule providing message to the P-GW (HA) to notify the PCC.
  • the rule fails to be executed.
  • the message contains information to identify the service flow that cannot allocate the QoS resource.
  • the information may be the routing rule information of the service flow, or the routing rule ID (requires the HA to be saved and consistent on the PCRF). Routing rule ID).
  • Step 610 The P-GW (HA) sends an acknowledgement message to the PCRF.
  • Step 611 The P-GW (HA) notifies the UE of the service flow information that fails the QoS resource application, and the UE may be notified by carrying the flow binding information in the binding release indication message.
  • Step 612 The UE sends a binding release message confirmation to the P-GW (HA).
  • Step 613 The UE sends a new binding update message to the P-GW (HA), and the previous service flow is returned to the original routing path.
  • the UE's manipulation depends on the UE's local policy implementation, and the UE may also select a new routing path or select a default route for the service flow.
  • Step 614 The P-GW (HA) sends an IP-CAN session modification request message to the PCRF, where the request message includes routing rule information to be updated.
  • Step 615 The PCRF sends an IP-CAN session modification response message to the P-GW.
  • Step 616 The P-GW (HA) sends a binding update confirmation message to the UE.
  • the application scenario of the third embodiment of the present invention is: the UE is simultaneously connected to the 3GPP access network and the non-3GPP access network, and multiple binding relationships and multiple IP flow binding association registrations are established for the same home address;
  • the binding update message is sent, and a new service flow routing rule (establishing a new service flow binding association) is transmitted in the 3GPP network, and the PCRF fails to apply for the QoS bearer resource for the new service flow.
  • the S5 interface based on the PMIPv6 mobility management protocol used by the S-GW and the P-GW in 3GPP. As shown in FIG.
  • Step 701 The UE currently connects to the 3GPP and the non-3GPP access network at the same time, and establishes a binding association for the service flows that belong to the same PDN connection and pass through different access networks. Multiple binding relationships and multiple IP flow binding registrations have been established.
  • Step 702 The UE sends a binding update (Binding Update) message to the HA, where the message carries the home address, the binding identifier, the flow binding information, and the like of the UE.
  • Binding Update a binding update (Binding Update) message to the HA, where the message carries the home address, the binding identifier, the flow binding information, and the like of the UE.
  • Add a new service flow routing rule according to the binding identifier and the flow binding information that is, establish a new service flow binding association.
  • Step 703 The P-GW (HA) sends an IP-CAN session modification request message to the PCRF, where the request message includes the routing rule information to be added.
  • Step 704 The PCRF sends an IP-CAN session modification response message to the P-GW.
  • Step 705 The HA returns a Binding Update Acknowledgement message to the UE to confirm the service flow binding operation of the UE, where the message includes a binding lifetime, a home address of the UE, and a binding identifier. , stream binding information.
  • Step 706 The PCRF sends a gateway control and a QoS providing message to the S-GW, where the message includes information such as a QoS rule and an event trigger.
  • Step 707 The S-GW sends an Update Bearer Request message to the MME, where the message includes a PTI, an EPS bearer identifier, an EPS bearer QoS information, a TFT, and an APN-AMBR.
  • Step 708 The MME sends a session management request (bearer modification request or session modification request) message to the eNB, and sends the PTI, the EPS bearer identifier, the EPS bearer QoS parameter, the TFT, and the APN-AMBR to the eNB for bearer modification.
  • a session management request (bearer modification request or session modification request) message
  • Step 709 The eNB fails to coordinate the allocation of the QoS-related bearer resource according to the information in the received session management request message.
  • Step 710 The eNB sends a bearer modification response message to the MME, to notify the MME that the EPS bearer QoS requested is not allocated.
  • Step 711 The MME sends an update bearer response message to the S-GW to notify the EPS bearer that the QoS assignment fails.
  • Step 712 The S-GW sends a gateway control and QoS rule execution response message to the PCRF, and notifies that the corresponding QoS rule of the PCRF fails to be executed.
  • Step 713 The PCRF sends a PCC rule providing message to the P-GW or the HA to notify the PCC.
  • the rule fails to be executed.
  • the message contains information to identify the service flow that cannot allocate the QoS resource.
  • the information may be the routing rule information of the service flow, or the routing rule ID (requires the HA to be saved and consistent on the PCRF). Routing rule ID).
  • Step 714 the P-GW (HA) sends an acknowledgement message to the PCRF.
  • Step 715 The P-GW (HA) notifies the UE of the service flow information that fails the QoS resource application, and the UE may be notified by carrying the flow binding information in the binding release indication message.
  • Step 716 The UE sends a binding release message confirmation to the P-GW (HA).
  • Step 717 The P-GW (HA) sends an IP-CAN session modification request message to the PCRF, where the request message includes routing rule information to be updated.
  • Step 718 The PCRF sends an IP-CAN session modification response message to the P-GW.
  • the present invention also provides a processing system for an IFOM error, including: a network side, a PCRF, a UE, and a UE HA.
  • the UE and the network side are used to negotiate the routing rules for the flow migration in the IFOM process.
  • the PCRF is used to notify the HA of the UE of the faulty flow migration information when the QoS resource management related fault occurs on the network side after the routing rule negotiation of the flow migration is performed on the UE and the network side, and triggers the processing of the fault.
  • the HA is further configured to: after the PCRF notifies the HA of the faulty flow migration information to the HA of the UE, the HA sends an acknowledgement message to the PCRF, and notifies the UE of the faulty flow migration information by using the binding release indication message;
  • the UE is further configured to send a binding release message acknowledgement to the HA.
  • the UE is further configured to: send a binding update message to the HA, and notify the HA to re-select the routing path for the flow corresponding to the fault;
  • the HA is further used to send an IP-CAN session modification request message to the PCRF, where the routing rule information that needs to be updated is included;
  • the PCRF is further configured to send an IP-CAN session modification response message to the HA;
  • the HA is also used to send a binding update confirmation message to the UE.
  • the UE is further configured to notify the HA to roll back the flow corresponding to the fault to the routing path before the flow migration, or select a new routing path for the flow corresponding to the fault, or select a default for the flow corresponding to the fault. path.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé et un système pour traiter une erreur de mobilité de flux IP (IFOM). Le procédé comprend les étapes suivantes : après qu'un équipement d'utilisateur (UE) et un côté réseau achèvent une négociation de règles d'acheminement sur une migration de flux, si une défaillance liée à la gestion de ressources de qualité de service (QoS) se produit sur le côté réseau, une fonction de règles de politique et de facturation (PCRF) informe un agent nominal (HA) de l'UE des informations sur la migration de flux qui a échoué, et déclenche une opération de traitement pour l'échec. L'invention résout le problème selon lequel dans un processus IFOM de l'art antérieur, lorsqu'une demande de ressources pour un flux migré échoue, la QoS du flux de service migré ne peut pas être garantie, ou même le service est interrompu. Par conséquent, la continuité de service est garantie, et la qualité de l'expérience d'utilisateur est garantie.
PCT/CN2011/077638 2010-08-30 2011-07-26 Procédé et système pour traiter une erreur ifom WO2012028044A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010269015.X 2010-08-30
CN201010269015.XA CN102387063B (zh) 2010-08-30 2010-08-30 一种ifom错误时的处理方法和系统

Publications (1)

Publication Number Publication Date
WO2012028044A1 true WO2012028044A1 (fr) 2012-03-08

Family

ID=45772142

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/077638 WO2012028044A1 (fr) 2010-08-30 2011-07-26 Procédé et système pour traiter une erreur ifom

Country Status (2)

Country Link
CN (1) CN102387063B (fr)
WO (1) WO2012028044A1 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103379569A (zh) * 2012-04-17 2013-10-30 中兴通讯股份有限公司 流迁移的触发方法及装置
CN105025544B (zh) 2014-04-18 2019-03-05 电信科学技术研究院 一种ip流路由规则的确定方法和设备
CN105282798A (zh) * 2014-07-24 2016-01-27 中兴通讯股份有限公司 一种关于流迁移触发的相关实现方法及设备
CN106162801A (zh) * 2015-03-27 2016-11-23 中兴通讯股份有限公司 实现缺省路由决策的方法、核心网网元、用户设备及系统
WO2023006061A1 (fr) * 2021-07-29 2023-02-02 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil de facturation

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101426252A (zh) * 2007-11-02 2009-05-06 华为技术有限公司 一种路径切换的处理方法、系统和装置
CN101459524A (zh) * 2008-03-18 2009-06-17 中兴通讯股份有限公司 一种下发策略计费控制规则的方法
CN101572915A (zh) * 2008-04-28 2009-11-04 华为技术有限公司 一种无线网络中实现切换的方法、装置及系统
WO2010022374A1 (fr) * 2008-08-22 2010-02-25 Qualcomm Incorporated Protocole internet mobile mandataire (pmip) dans un environnement de communication à plusieurs interfaces

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6138007A (en) * 1997-11-26 2000-10-24 Nortel Networks Corporation Methods and systems for late call forwarding when roaming from GSM system to IS41 system
CN101064648A (zh) * 2006-04-30 2007-10-31 华为技术有限公司 实现移动IPv6的系统及其用户连接建立方法
CN101369901B (zh) * 2007-08-15 2012-02-22 华为技术有限公司 一种关联策略和计费执行功能实体的方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101426252A (zh) * 2007-11-02 2009-05-06 华为技术有限公司 一种路径切换的处理方法、系统和装置
CN101459524A (zh) * 2008-03-18 2009-06-17 中兴通讯股份有限公司 一种下发策略计费控制规则的方法
CN101572915A (zh) * 2008-04-28 2009-11-04 华为技术有限公司 一种无线网络中实现切换的方法、装置及系统
WO2010022374A1 (fr) * 2008-08-22 2010-02-25 Qualcomm Incorporated Protocole internet mobile mandataire (pmip) dans un environnement de communication à plusieurs interfaces

Also Published As

Publication number Publication date
CN102387063B (zh) 2015-10-21
CN102387063A (zh) 2012-03-21

Similar Documents

Publication Publication Date Title
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
EP2339781B1 (fr) Procédé et système pour réaliser la commande de politique et de facturation sur la scène de multiples réseaux de données par paquets (pdn)
US8874715B2 (en) Charging method, system and reporting method for terminal accessing through multiple access networks
US9380446B2 (en) Policy and charging control method supporting IP flow mobility in roaming scenario
US9351325B2 (en) Policy control method and system for converged network
US9113436B2 (en) Method and system for information transmission
US8661145B2 (en) Method and system for transmitting a bearer control mode in roaming scenarios
US9565052B2 (en) Method and system for realizing application detection and control in IP-CAN session supporting dual stack
US20110131313A1 (en) Method for provisioning and installing event triggers
WO2011006317A1 (fr) Procédé et système permettant d'effacer des informations redondantes d'une fonction d’imputation et de règles domestique
WO2011124106A1 (fr) Procédé, système et dispositif de commande de politique et de facturation
CN102332985B (zh) 一种提供基于lipa承载的计费支持的方法及装置
US9854555B2 (en) Method and system for notifying access network location information
WO2011095025A1 (fr) Procédé et système de commande de politique pour accès local d'utilisateur mobile
WO2012028044A1 (fr) Procédé et système pour traiter une erreur ifom
US9485106B2 (en) Method for processing TDF session and PCRF
Ahmed et al. Multi access data network connectivity and IP flow mobility in Evolved Packet System (EPS)
WO2012129992A1 (fr) Procédé de traitement de connectivité de données sponsorisées, et fonction d'imputation et de règles
WO2011026409A1 (fr) Procédé, appareil et système de mise à jour de session
JP2015530765A (ja) 通信ネットワークにおける課金制御方法およびシステム
WO2013113263A1 (fr) Procédé et système d'identification de mode fonction de commande de détection d'application
WO2012146092A1 (fr) Procédé et système de contrôle de politique pour mesurer la mobilité d'un flux ip
CN102958117A (zh) 一种解决服务质量策略控制冲突的方法和系统
CN102932915B (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: 11821070

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

Country of ref document: EP

Kind code of ref document: A1