WO2012058998A1 - 漫游场景下支持ip流迁移的策略计费控制方法和系统 - Google Patents

漫游场景下支持ip流迁移的策略计费控制方法和系统 Download PDF

Info

Publication number
WO2012058998A1
WO2012058998A1 PCT/CN2011/080730 CN2011080730W WO2012058998A1 WO 2012058998 A1 WO2012058998 A1 WO 2012058998A1 CN 2011080730 W CN2011080730 W CN 2011080730W WO 2012058998 A1 WO2012058998 A1 WO 2012058998A1
Authority
WO
WIPO (PCT)
Prior art keywords
pcrf
rule
flow
flow migration
routing rule
Prior art date
Application number
PCT/CN2011/080730
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/882,591 priority Critical patent/US9380446B2/en
Priority to EP11837524.5A priority patent/EP2624607A4/en
Publication of WO2012058998A1 publication Critical patent/WO2012058998A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8038—Roaming or handoff
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/14—Mobility data transfer between corresponding nodes

Definitions

  • the present invention relates to the field of communications, and in particular to a policy charging control method and system for supporting IP flow migration in a roaming scenario. Background technique
  • an EPS is an access network and an evolved packet core network (Evolved Packet Core, referred to as EPC).
  • EPC evolved packet core network
  • the access network may be an Evolved Universal Terrestrial Radio Access Network (E-UTRAN)
  • EPC includes: a Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network Gateway (P-GW), Home Subscriber Server (HSS), and 3rd Generation Partnership Project ( The 3rd Generation Partnership Project (referred to as 3GPP) Authentication, Authorization, Accounting (AAA) server, Policy and Charging Rules Function (PCRF) and other supporting nodes.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • HSS Home Subscriber Server
  • 3GPP 3rd Generation Partnership Project
  • AAA Policy and Charging Rules Function
  • the MME is responsible for control planes such as mobility management, non-access stratum signaling processing, and user context management;
  • the S-GW is an access gateway device connected to the E-UTRAN, and is responsible for the E-UTRAN and P. - GW forwards data and caches paging waiting data;
  • P-GW is a 3rd Generation Partnership Project (3GPP) Evolved Packet System and Packet Data Network (Packet Data Network, referred to as PDN) border gateway, responsible for user terminal access to PDN, forwarding data between EPS and PDN, etc.;
  • PCRF is a policy and charging rule function entity, through receiving interface Rx and carrier network protocol (Internet Protocol, referred to as IP
  • IP Internet Protocol
  • EPS also supports user equipment (User Equipment, referred to as UE) by dividing E-UTRAN.
  • UE User Equipment
  • Access of other non-3GPP systems where the non-3GPP system implements access through the S2a/b/c interface, and the P-GW acts as a data anchor for access of the 3GPP system and access of the non-3GPP system.
  • non-3GPP systems are classified into a trusted non-3GPP IP access network and an untrusted non-3GPP IP access network.
  • the trusted non-3GPP IP access network can be directly connected to the P-GW through the S2a interface; the untrusted non-3GPP IP access network needs to be connected to the P-GW through an Evolved Packet Data Gateway (ePDG).
  • ePDG Evolved Packet Data Gateway
  • S2b The interface between the ePDG and the P-GW is S2b.
  • S2c is the interface between the UE and the P-GW, and provides control by using the Moblie IPv6 Support for Dual Stack Hosts and Routers (DSMIPv6) protocol of the dual-stack mobile network protocol version 6 (Internet Protocol Vision, abbreviated as IPv6). Mobility management.
  • DSMIPv6 Moblie IPv6 Support for Dual Stack Hosts and Routers
  • IPv6 Internet Protocol Vision
  • the EPS system supports IP Flow Mobility.
  • 2 is a schematic diagram of accessing IP flow migration in the prior art.
  • the UE passes through coverage of non-3GPP access (such as wireless local area network WLAN) and 3GPP access (such as E-UTRAN).
  • the non-3GPP IP access network and the 3GPP access network access the PDN through the same P-GW.
  • the UE is attached to the EPC through multiple access networks.
  • the P-GW allocates an IP address to the UE, and there is a PDN connection between the UE and the PDN (also called an IP connection access network IP-CAN session).
  • IP flow migration can select an applicable access network transmission service according to the characteristics of the service, and multiple access networks can share the network load and avoid network congestion.
  • the non-3GPP access network is a WLAN
  • the Hypertext Transfer Protocol (Http) and File Transfer Protocol (Ftp) service data streams can pass through the WLAN, and the IP phone (voice)
  • the service data stream of over IP (referred to as VoIP) can be sent to the UE through 3GPP.
  • FIG. 3 is a flowchart of a method for establishing a PDN connection after a UE first establishes a PDN connection through a 3GPP access network, and then establishes a PDN connection through non-3GPP access, and simultaneously uses two accesses to use the PDN connection.
  • Dynamic Policy and Charging Control (PCC) is deployed in the network.
  • the UE uses the DSMIPv6 protocol.
  • the method includes the following steps 301 to 316:
  • Step 301 The UE accesses the EPC through the 3GPP access network, where the S-GW and the P-GW pass a General Packet Radio Service Tunneling Protocol (GTP) or a proxy mobile IPv6 (Proxy Mobile). IPv6, referred to as PMIPv6)
  • GTP General Packet Radio Service Tunneling Protocol
  • PMIPv6 proxy mobile IPv6
  • the protocol establishes a tunnel, and possibly existing services are transmitted on the tunnel;
  • Step 302 The UE discovers the non-3GPP access network and decides to initiate multiple access. If the non-3GPP access network is trusted, the UE performs access authentication and authorization in the trusted non-3GPP access network, and the UE performs layer 3 attachment and obtains the local IP address IP Address1 as the care-of address (Care of Address, referred to as CoA). If the non-3GPP access network is untrustworthy, the UE will establish an IPSec tunnel with the ePDG. During the tunnel establishment process, the ePDG allocates an IP address IP Address1 to the UE as a CoA.
  • CoA care-of address
  • Step 303 The bearer binding and event reporting function (BBERF) in the trusted non-3GPP access network or the ePDG sends a gateway control session establishment message to the PCRF, establishes a request to establish a gateway control session, and carries the user identifier and the IP Address1;
  • BBERF bearer binding and event reporting function
  • Step 304 The PCRF returns a confirmation message to the BBERF.
  • Step 305 The UE finds the P-GW selected during the 3GPP access by using a mobile IPv6 (Mobile IPv6, MIPv6 for short) self-boot process.
  • a security association is established between the UE and the PDN.
  • the UE initiates a secure association by using Internet Key Exchange 2 (abbreviated as ⁇ 2).
  • the Extensible Authentication Protocol (EAP) is used for authentication on top of IKEv2.
  • the P-GW interacts with the AAA to complete the EAP authentication.
  • the P-GW returns the IP address 2 assigned by the P-GW when the UE accesses the 3GPP, and the UE uses the IP address as the Home of Address (referred to as ⁇ ) when the DSMIPv6 is bound.
  • the P-GW performs the function of a Home Agent (HA);
  • HA Home Agent
  • Step 306 The UE sends a DSMIPv6 binding update message to the P-GW/HA, where the binding update message carries a (HoA, CoA, BID (Binging Identification), FID (Flow Identification)).
  • HoA, CoA, BID, FID is a correspondence.
  • the value of the HoA in the binding update message is IP Address2, and the value of the CoA is IP Address1, indicating that the corresponding BID is a binding through non-3GPP access, and the FID uniquely identifies a certain data flow of the user accessing the service. Bind to a connection through non-3GPP access.
  • the value of the HoA in the binding update message is IP Address2, and the value of the CoA is IP Address2, indicating that the corresponding BID is a binding through the 3GPP access, and the service data flow identified by the FID is bound to the connection through the 3GPP access. on. If a new flow binding is added, the corresponding relationship also includes a routing filter (ie, an IP quintuple) for identifying a service data flow.
  • a routing filter ie, an IP quintuple
  • the correspondence between the FID and the Routing Filters is established by the message, and the modification of the service data stream can be represented by the FID.
  • the UE reports the default routing rule, that is, Routing Filters is a wildcard filter.
  • the UE may also request to migrate the service data stream (SDF) transmitted through the 3GPP access to the non-SDF
  • Step 307 After receiving the binding update message, the P-GW/HA performs multiple registration flow binding according to the parameters HoA, CoA, BID, FID and Routing Filters carried in the message. That is, the P-GW maintains both the GTP/PMIPv6 tunnel with the S-GW and the DSMIPv6 tunnel with the UE, and binds the traffic data stream to the 3GPP access or the non-3GPP access.
  • the PCEF located at the P-GW sends an IP-CAN session modification request indication to the PCRF, and the PCEF will send an event trigger routing rule modification (ROUTING_RULE_CHANGE) and IP flow migration routing rule information to the PCRF (for new and/or migrated in the flow)
  • the IP flow migration routing rule information is to install and/or modify the IP flow migration routing rule
  • the IP flow migration routing rule is the correspondence between the service data flow and the access, and is identified by the correspondence between the Routing Filters and the Routing Address.
  • the value of the Routing Address is IP Address 1, it indicates that it is through non-3GPP access, and when the value of the Routing Address is IP Address2, it is indicated as access through 3GPP.
  • This message includes the default IP flow migration routing rules, ie Routing Filters are wildcards.
  • the PCEF will provide the PCRF with the IP flow migration routing rule corresponding to the service data flow, to notify the PCRF that the routing of the service data flow occurs. migrate.
  • Routing Filters is the IP quintuple of the service data flow, and the Routing Address value is IP Address 1;
  • Step 308 the PCRF installs and/or modifies the IP flow migration routing rule. If the service data flow corresponding to the IP flow migration routing rule is migrated (that is, migrated from 3GPP access to non-3GPP access), the PCRF updates the PCC rule correspondingly and returns it to the PCEF.
  • the IP flow migration routing rule that is newly installed in the PCRF may cause the service data flow corresponding to the IP flow migration routing rule to be migrated from the default route to the route specified by the IP flow migration routing rule.
  • the IP flow migration routing rule modified by the PCRF may cause the service data flow corresponding to the IP flow migration routing rule to be migrated from the source routing path to the new routing path. In this flow, service data for migrating from transmitting 3GPP access to non-3GPP access
  • the flow PCC rules are updated and returned to the PCEF;
  • Step 309 The P-GW/HA returns a binding acknowledgement message to the UE, where the message carries the HoA, the CoA, the BID, and the FID to confirm that the UE is successfully registered, that is, the flow binding is successful, or the multiple registration is flow binding and the flow migration is successful.
  • Step 310 if a service data flow is migrated from 3GPP access to non-3GPP access, then
  • the PCRF will formulate QoS rules according to the PCC rules updated by the service data flow, and provide the QoS rules to the trusted non-3GPP access network or the BBERF in the ePDG;
  • Step 311 The non-3GPP access network performs a specific process for resource allocation or modification.
  • Step 312 The BBERF returns an acknowledgement message to the PCRF.
  • Step 313 If a service data flow is migrated from the 3GPP access to the non-3GPP access, and if a ⁇ tunnel is established between the S-GW and the P-GW, the PCRF deletes the QoS rule corresponding to the service data flow.
  • the PCRF provides the QoS rule to be deleted to the BBERF in the S-GW through the gateway control session established by the UE during the 3GPP access;
  • Step 314 The BBERF in the S-GW deletes the QoS rule, performs a bearer modification or release process of the 3GPP, and releases the resource of the migrated service data flow.
  • Step 315 the BBERF returns an acknowledgement message to the PCRF.
  • the P-GW will initiate a 3GPP bearer modification or release process after the step 308 to release the resources of the migrated service data stream. Steps 313-315 will not be performed.
  • Step 316 The UE completes the multi-registration flow binding and the possible flow migration.
  • a DSMIPv6 tunnel exists between the UE and the P-GW/HA, and a GTP/PMIPv6 tunnel exists between the S-GW and the P-GW.
  • the UE or the network can determine which access the service data is transmitted according to the policy.
  • FIG. 4 is a flowchart of the prior art that the UE first establishes a PDN connection through a non-3GPP access network access and then establishes a PDN connection through the 3GPP access, and simultaneously uses the two accesses to use the PDN connection. Dynamic PCC is deployed in the network.
  • the UE uses the DSMIPv6 protocol.
  • the method includes the following steps 401 to 413: Step 401: The UE accesses the EPC through the DSMIPv6 protocol through the non-3GPP access network. , UE and A DSMIPv6 tunnel is established between the P-GW and the HA, and the existing service is transmitted on the tunnel.
  • the address allocated by the non-3GPP access network to the UE is IP Address 1 as the CoA, and the IP address assigned by the P-GW to the UE is the IP address. Address2 as HoA;
  • Step 402 The UE discovers the 3GPP access network and decides to initiate multiple access.
  • the UE establishes a PDN connection to the same PDN through the attached procedure of the 3GPP.
  • the P-GW allocates an IP address to the UE as an IP Address2 to ensure that the same PDN connection is established through different accesses.
  • Step 403 The UE sends a DSMIPv6 binding update message to the P-GW/HA, where the binding update message carries (HoA, CoA, BID, FID).
  • (HoA, CoA, BID, FID) is a correspondence.
  • the message is IP Address 2 and the CoA value is IP Address 1 , indicating that the corresponding BID is a binding through non-3GPP access, and a certain data flow of the user ID access service uniquely identified by the FID is bound to the non-3GPP.
  • the message is IP Address2 and the CoA value is IP Address2, indicating that the corresponding BID is a binding through 3GPP access, and the service data flow identified by the FID is bound to the connection through 3GPP access.
  • the corresponding relationship also includes Routing Filters.
  • the correspondence between the FID and the Routing Filters is established by the message, and the modification of the service data stream can be expressed by the FID.
  • the UE may report the default routing rule, that is, Routing Filters is a wildcard filter.
  • the UE may also request to migrate the service data flow SDF transmitted through the non-3GPP access to the 3GPP access network;
  • Step 404 After receiving the binding update message, the P-GW/HA performs multiple registration flow binding according to the carried parameters HoA, CoA, BID, FID, and Routing Filters. That is, the P-GW simultaneously maintains the GTP/PMIPv6 tunnel with the S-GW and the DSMIPv6 tunnel with the UE, and binds the service data stream to the 3GPP access or the non-3GPP access.
  • the PCEF located at the P-GW sends an IP-CAN session modification request indication to the PCRF, and the PCEF will send an event trigger ROUTING_RULE_CHANGE and IP flow migration routing rule information to the PCRF (for new and/or migrated IP in the flow)
  • the IP flow migration routing rule information is to install and/or modify the IP flow migration routing rule
  • the IP flow migration routing rule is the correspondence between the service data flow and the access, and the correspondence between the Routing Filters and the Routing Address is identified.
  • IP Address 1 indicates that it is through non-3GPP access
  • IP Address2 when the value of the Routing Address2
  • the message may include the default IP flow migration routing rule, ie Routing Filters are wildcards. If the UE migrates a certain service data flow from the non-3GPP access to the 3GPP access, the PCEF will provide the PCRF with the IP flow migration routing rule corresponding to the service data flow, to notify the PCRF that the routing of the service data flow occurs. migrate.
  • the Routing Filters are the IP quintuple of the service data flow, and the Routing Address takes the value of IP Address2; Step 405, the PCRF installs and/or modifies the IP flow migration routing rule.
  • the PCRF updates the corresponding PCC rule and returns it to the PCEF.
  • the IP flow migration routing rule that is newly installed in the PCRF may cause the service data flow corresponding to the IP flow migration routing rule to be migrated from the default route to the route specified by the IP flow migration routing rule.
  • the IP flow migration routing rule modified by the PCRF may cause the service data flow corresponding to the IP flow migration routing rule to be migrated from the source routing path to the new routing path.
  • the PCC rules of the service data flow that is migrated from the non-3GPP access to the 3GPP access are updated and returned to the PCEF;
  • Step 406 The P-GW/HA returns a binding acknowledgement message to the UE, where the message carries the HoA, the CoA, the BID, and the FID to confirm that the UE has multiple registrations, that is, the flow binding is successful, or the multiple registration is flow binding and the flow migration succeeds;
  • Step 407 If a service data flow is migrated from a non-3GPP access to a 3GPP access, and if a PMIPv6 tunnel is established between the S-GW and the P-GW, the PCRF is determined according to the PCC rule updated by the service data flow. QoS rules and provide the QoS rules to the BBERF in the S-GW;
  • Step 408 The BBERF installs a QoS rule, and the S-GW initiates execution of a 3GPP bearer modification or establishment process for resource allocation or modification;
  • Step 409 The BBERF returns a confirmation message to the PCRF.
  • the P-GW will initiate a 3GPP bearer modification or establishment process after the step 405 to allocate the resources of the migrated service data stream. Steps 407-409 will not be performed.
  • Step 410 If a service data flow is migrated from a non-3GPP access to a 3GPP access, the PCRF deletes the QoS rule corresponding to the service data flow in the non-3GPP access network or the ePDG.
  • the PCRF passes the gateway control session established by the UE during non-3GPP access to the non-3GPP access network or The BBERF in the ePDG provides QoS rules that need to be deleted;
  • Step 411 The BBERF deletes the QoS rule, and initiates a specific resource modification or release process that is not a 3GPP;
  • Step 412 The BBERF returns an acknowledgement message to the PCRF.
  • Step 413 The UE completes the multi-registration flow binding and the flow migration, and the DSMIPv6 tunnel exists between the UE and the P-GW/HA, and the GTP/PMIPv6 tunnel exists between the S-GW and the P-GW.
  • the UE or the network can decide which access the service data is transmitted through according to the policy.
  • FIG. 5 is a flow chart of performing data flow migration between two access networks after the UE implements multi-registration flow binding through the process of FIG. 3 or FIG. 4 in the prior art. Dynamic PCC is deployed in the network. As shown in FIG. 5, the method includes the following steps 501 to 511:
  • Step 501 The UE simultaneously connects to the 3GPP access and the non-3GPP access through the process of FIG. 3 or FIG. 4, and performs multiple registration flow binding.
  • Step 502 The UE sends a DSMIPv6 binding update message to the P-GW/HA, where the binding update message carries (HoA, BID, FID).
  • the UE may request to migrate the traffic data stream SDF (represented by FID) transmitted in the non-3GPP access to the 3GPP access network (indicated by BID) or vice versa (ie modify the routing rule).
  • the UE may also request to delete the routing rule or add a new routing rule. If a new routing rule is added, the message also includes Routing Filters;
  • Step 503 After receiving the binding update message, the P-GW/HA performs flow binding update according to the carried parameters HoA, BID, and FID, including flow migration, adding or deleting, and the like.
  • the PCEF located at the P-GW sends an IP-CAN session modification request indication to the PCRF, and the PCEF will send an event trigger ROUTING_RULE_CHANGE and IP flow migration routing rule information to the PCRF, including installing, modifying, and/or deleting the IP flow migration route. rule.
  • IP Address1 is used to indicate that the currently transmitted access network is non-3GPP
  • IP Address2 indicates that the currently transmitted access network is 3GPP.
  • Step 504 the PCRF installs, modifies, and/or deletes the IP flow migration routing rule.
  • the PCRF updates the PCC rules according to the IP flow migration routing rules. For the IPF migration routing rule that is newly installed in the PCRF, the service data flow corresponding to the IP flow migration routing rule may be migrated from the default route to the default route. The IP flow migrates the route specified by the routing rule.
  • the IP flow migration routing rule modified by the PCRF may cause the service data flow corresponding to the IP flow migration routing rule to be migrated from the source routing path to the new routing path.
  • the IP flow migration routing rule deleted by the PCRF may cause the service data flow corresponding to the IP flow migration routing rule to be migrated from the source routing path to the path of the default routing rule.
  • Step 505 The P-GW/HA returns a binding acknowledgement message to the UE, where the message carries HoA, BID, and FID to confirm that the UE routing rule is updated successfully.
  • Step 506 If a PMIPv6 tunnel is established between the S-GW and the P-GW, the PCRF installs or deletes the QoS rule on the BBERF in the S-GW according to the rule reported by the PCEF. If migrating from non-3GPP to 3GPP, the QoS rule is installed, otherwise, the QoS rule is deleted; Step 507, BBERF installs or deletes the QoS rule, and the S-GW initiates the 3GPP bearer establishment, modification or deletion process for resource allocation and modification. Or release;
  • Step 508 The BBERF returns an acknowledgement message to the PCRF.
  • Steps 506-508 will not be performed.
  • Step 509 The PCRF will install or delete the QoS rule on the BBERF in the trusted non-3GPP access network or ePDG according to the rules reported by the PCEF. If migrating from 3GPP to non-3GPP, the QoS rule is installed, otherwise, the QoS rule is deleted;
  • Step 510 The BBERF installs or deletes the QoS rule, and initiates a specific resource allocation, modification, or release process of the non-3GPP;
  • Step 511 the BBERF returns an acknowledgement message to the PCRF.
  • the PCEF provides a routing rule indicating the service data transmission path to the PCRF.
  • the PCRF determines the access network currently transmitted by the service data flow according to the routing rule, and allocates resources for the service data flow in the current access network. If the service data flow has been migrated, the resources allocated by the service data flow are also released in the source access network.
  • the IP flow migration routing rule includes the following four parts:
  • Rule ID Used to uniquely identify a routing rule in an IP-CAN session
  • Route Filter Used to identify the service data stream
  • Priority Used to identify the priority of the routing rule.
  • Routing address The access network used to identify the current service data stream transmission, as shown in Figure 3, 4, and 5, IP Address 1 and IP Address 2
  • IP flow migration routing rules include three operations: installation, modification, and deletion.
  • the installation and modification operations need to carry the content of the IP flow migration rule, including the rule identifier, and at least one of the route filter, priority, and routing address.
  • the policy control method for IP flow migration in a non-roaming scenario is supported.
  • a roaming scenario there is no complete solution for how to support IP flow migration.
  • the policy charging control method for IP flow migration under the roaming scenario of Visited Access (referred to as VA, also referred to as Local Breaking Local Breakout) (see Figure 6)
  • VA Visited Access
  • Figure 6 how to optimize the strategy Billing control is a problem to be solved.
  • the technical problem to be solved by the present invention is to provide a policy charging control method and system for supporting IP flow migration in a roaming scenario.
  • the present invention provides a policy charging control method for supporting IP flow migration in a roaming scenario, including:
  • IP-PCRF Visited local policy and charging rule function
  • PCEF policy and charging execution function
  • H-PCRF home location policy and charging rule function
  • IP-CAN_CHANGE IP-CAN type modification
  • AN-GW_CHANGE access gateway modification
  • the IP flow migration routing rule information includes one or more of the following IP flow migration rules: Install, modify, or delete an IP flow migration routing rule.
  • the above method may also have the following features.
  • the V-PCRF After receiving the IP flow migration routing rule information, the V-PCRF performs one or more of the following operations: installing, modifying, or deleting the IP flow migration routing rule carried in the IP flow migration routing rule information.
  • the above method may further have the following features, the method further comprising: After the IP-connected access network (IP-CAN) session is established, the H-PCRF receives the IP flow migration routing rule information, and installs the IP flow migration carried in the IP flow migration routing rule information. Routing rules.
  • IP-CAN IP-connected access network
  • the above method may also have the following features.
  • the V-PCRF reports the IP flow migration routing rule information to the H-PCRF, it also reports that a routing rule modification (ROUTING_RULE_CHANGE) event is triggered to the H-PCRF.
  • ROUTING_RULE_CHANGE routing rule modification
  • the above method may further have the following features, the method further comprising:
  • the H-PCRF After the IP-CAN session modification process, the H-PCRF performs the following one or more operations after receiving the IP flow migration routing rule information: installing, modifying, or deleting the IP flow migration routing rule information IP flow migration routing rules.
  • the above method may further have the following features, the method further comprising:
  • the V-PCRF delivers the updated PCC rule to the PCEF.
  • the foregoing method may further have the following features, the method further comprising: sending the QoS rule to a specified bearer binding and event reporting function (BBERF) according to the IP flow migration routing rule.
  • BBERF bearer binding and event reporting function
  • the above method may further have the following features, the method further comprising:
  • the V-PCRF deletes the QoS rule corresponding to the service data flow from the BBERF that flows before the service data flow migrates.
  • the above method may further have the following features, the method further comprising: if the H-PCRF is not subscribed to the IP-CAN_CHANGE event trigger or the AN-GW_CHANGE event trigger, the V-PCRF Handle IP flow migration locally.
  • the foregoing method may further have the following feature: the V-PCRF processes the IP flow in the local area. Move includes:
  • the V-PCRF formulates a QoS rule according to the PCC rule corresponding to the IP flow migration routing rule, and according to the IP flow migration routing rule, The QoS rule is sent to the specified BBERF.
  • the V-PCRF processing the IP flow migration locally includes:
  • the V-PCRF deletes the QoS rule corresponding to the service data flow from the BBERF that flows before the service data flow migrates.
  • the present invention further provides a policy charging control system for supporting IP flow migration in a roaming scenario, including: a visited local policy and a charging rule function (V-PCRF) and a home location policy and a charging rule function (H-PCRF). among them:
  • V-PCRF visited local policy and a charging rule function
  • H-PCRF home location policy and a charging rule function
  • the V-PCRF is set to: when receiving the IP flow migration routing rule information reported by the policy and charging execution function (PCEF), if the H-PCRF subscribes to an IP-CAN type modification (IP-CAN_CHANGE) event trigger or The access gateway modification (AN_GW_CHANGE) event is triggered, and the IP flow migration routing rule information is reported to the H-PCRF, where the IP flow migration routing rule information includes one or more of the following IP flow migration rules: installation, modification Or delete the IP flow migration routing rule.
  • PCEF policy and charging execution function
  • the system may further have the following features, the V-PCRF is further configured to: after receiving the IP flow migration routing rule information, perform one or more of the following operations: installing, modifying, or deleting the IP flow Migrate the IP flow migration routing rules carried in the routing rule information.
  • the H-PCRF is further configured to: after receiving the IP flow migration routing rule information in the IP connection access network (IP-CAN) session establishment process, the installation office The IP flow migration routing rule carried in the IP flow migration routing rule information.
  • IP-CAN IP connection access network
  • the system may further have the following feature: the V-PCRF is further configured to report the routing rule modification (ROUTING_RULE_CHANGE) when the IP flow migration routing rule information is reported to the H-PCRF during the IP-CAN session modification process. The event is triggered to the H-PCRF.
  • the routing rule modification ROUTING_RULE_CHANGE
  • the H-PCRF is further configured to: after receiving the IP flow migration routing rule information in the IP-CAN session modification process, perform the following One or more operations: Install, modify, or delete the IP flow migration routing rules carried in the IP flow migration routing rule information.
  • the foregoing system may further have the following feature: the H-PCRF is further configured to: after installing or modifying an IP flow migration routing rule, if the service data flow corresponding to the IP flow migration routing rule is migrated, updating the PCC a rule, sending an updated PCC rule to the V-PCRF;
  • the V-PCRF is further configured to: deliver the updated PCC rule to the PCEF.
  • the system may further have the following feature, the V-PCRF is further configured to: formulate a QoS rule according to the updated PCC rule, and send the QoS rule to the specified BBERF according to the IP flow migration routing rule. .
  • the foregoing system may further have the following feature: the V-PCRF is further configured to: delete a QoS rule corresponding to the service data flow from a BBERF that flows before the service data flow migrates.
  • the above system may further have the following feature, the V-PCRF is further configured to: if the H-PCRF is not subscribed to the IP-CAN_CHANGE event trigger or the AN-GW_CHANGE event is triggered, locally Handle IP flow migration.
  • the foregoing system may further have the following feature: the V-PCRF local processing IP flow migration includes: if the service data flow corresponding to the IP flow migration routing rule is migrated, the V-PCRF is according to the IP flow
  • the PCC rule corresponding to the migration routing rule formulates a QoS rule, and sends the QoS rule to the specified BBERF according to the IP flow migration routing rule.
  • the foregoing system may further have the following feature: the V-PCRF processing the IP flow migration locally includes: deleting the QoS rule corresponding to the service data flow from the BBERF flowing before the service data flow migration.
  • the present invention also provides a visited location policy and a charging rule function (V-PCRF), where the V-PCRF is set to: when receiving the IP flow migration routing rule information reported by the policy and charging execution function (PCEF),
  • the attribution policy and charging rule function (H-PCRF) is subscribed to the IP-CAN type modification (IP-CAN_CHANGE) event trigger or the access gateway modification (AN_GW_CHANGE) event triggering, and reporting the IP flow migration routing rule information to the
  • the H-PCRF includes the following one or more IP flow migration rules in the IP flow migration routing rule information: installing, modifying, or deleting an IP flow migration routing rule.
  • the V-PCRF is further configured to: after receiving the IP flow migration routing rule information, perform one or more of the following operations: installing, modifying, or deleting the IP carried in the IP flow migration routing rule information Flow migration routing rules.
  • the V-PCRF is further configured to: when the IP flow migration routing rule information is reported to the H-PCRF in the IP-CAN session modification process, the reporting routing rule modification (ROUTING RULE CHANGE) event is triggered to the H-PCRF.
  • the reporting routing rule modification ROUTING RULE CHANGE
  • the V-PCRF is further configured to: send an updated PCC rule to the PCEF; the updated PCC rule is: after the H-PCRF installs or modifies an IP flow migration routing rule, The service data flow corresponding to the IP flow migration routing rule is migrated, and is updated by the H-PCRF to update the PCC rule; and the updated PCC rule is sent by the H-PCRF to the V-PCRF.
  • the V-PCRF is further configured to: formulate a QoS rule according to the updated PCC rule, and send the QoS rule to the designated BBERF according to the IP flow migration routing rule.
  • the V-PCRF is further configured to: delete a QoS rule corresponding to the service data flow from a BBERF that flows before the service data flow migrates.
  • the V-PCRF is further configured to: if the H-PCRF is not subscribed to the IP-CAN_CHANGE event trigger or the AN-GW_CHANGE event trigger, locally process IP flow migration.
  • the V-PCRF local processing IP flow migration includes: if the service data flow corresponding to the IP flow migration routing rule is migrated, the V-PCRF is determined according to the PCC rule corresponding to the IP flow migration routing rule. a QoS rule, and the QoS rule is sent to the designated BBERF according to the IP flow migration routing rule.
  • the visited network can perform IP flow migration locally;
  • H-PCRF supports IP flow migration
  • H-PCRF does not subscribe to IP-CAN-CHANGE or AN-GW-CHANGE
  • V-PCRF does not need to interact with H-PCRF, compared to any time.
  • the scheme that needs to interact with the H-PCRF can save the signaling overhead between the V-PCRF and the H-PCRF.
  • FIG. 1 is a schematic diagram of a system architecture of an EPS according to the related art
  • FIG. 2 is a schematic diagram of access of an IP flow migration according to the related art
  • FIG. 3 is a flowchart 1 of establishing an IP flow migration connection in a non-roaming scenario according to the related art
  • FIG. 4 is a flowchart 2 of establishing an IP flow migration connection in a non-roaming scenario according to the related art
  • Figure 7 is a flow chart of the first embodiment of the present invention.
  • Figure 8 is a flow chart of the second embodiment of the present invention.
  • Figure 9 is a flow chart of Embodiment 3 of the present invention.
  • Figure 10 is a flow chart of Embodiment 4 of the present invention. Preferred embodiment of the invention
  • the present invention is proposed for policy charging control that supports IP flow migration in a local grooming roaming scenario.
  • the present invention provides a policy charging control method for supporting IP flow migration in a roaming scenario, including: the visited local policy and the charging rule function (V-PCRF) receive the IP flow migration reported by the policy and charging execution function (PCEF) When routing rule information, where:
  • H-PCRF Home Policy and Charging Rules Function
  • IP-CAN_CHANGE Event Trigger or Access Gateway Modification (AN_GW_CHANGE) Event Triggering, the V-PCRF reporting the IP flow migration routing rule information to the H-PCRF;
  • the V-PCRF processes the IP stream migration locally;
  • the IP flow migration routing rule information includes one or more of the following IP flow migration rules: installing, modifying, or deleting an IP flow migration routing rule.
  • the V-PCRF After the V-PCRF receives the IP flow migration routing rule information, the V-PCRF performs one or more operations as follows: installing, modifying, or deleting the IP flow migration routing rule carried in the IP flow migration routing rule information. .
  • IP-CAN IP connection access network
  • the H-PCRF After receiving the IP flow migration routing rule information, the H-PCRF installs the IP flow migration routing rule carried in the IP flow migration routing rule information.
  • the reporting route modification (ROUTING_RULE_CHANGE) event is triggered to the H-PCRF;
  • the H-PCRF After receiving the IP flow migration routing rule information, the H-PCRF performs one or more of the following operations: installing, modifying, or deleting the IP flow migration routing rule carried in the IP flow migration routing rule information;
  • the H-PCRF modifies, or deletes the IP flow migration routing rule, if the service data flow corresponding to the IP flow migration routing rule is migrated, the PCC rule is updated, and the updated PCC rule is delivered to the V -PCRF;
  • the V-PCRF delivers the updated PCC rule to the PCEF
  • the V-PCRF formulates a QoS rule according to the updated PCC rule, and sends the QoS rule to the specified BBERF according to the IP flow migration routing rule;
  • the V-PCRF deletes the QoS rule corresponding to the service data flow from the BBERF that flows before the service data flow migrates. Further, the locally processing the IP stream migration by the V-PCRF includes:
  • the V-PCRF formulates a QoS rule according to the PCC rule corresponding to the IP flow migration routing rule, and according to the IP flow migration routing rule, QoS rules are sent to the specified BBERF;
  • the V-PCRF deletes the QoS rule corresponding to the service data flow from the BBERF that flows before the service data flow migrates.
  • FIG. 7 is a flow diagram of an example first UE attaching through a non-3GPP access network according to an embodiment of the present invention, where the UE uses the DSMIPv6 protocol when trusted non-3GPP access.
  • Step 701 The UE discovers a non-3GPP access network and initiates attaching. If the non-3GPP access network is trusted, the UE performs access authentication and authorization in the trusted non-3GPP access network, and the UE performs layer 3 attachment and obtains the local IP address IP Address1 as the CoA. If the non-3GPP access network is untrustable, the UE will establish an IPSec tunnel with the ePDG and perform tunnel authentication. During the tunnel establishment process, the ePDG allocates an IP address IP Address1 to the UE as a CoA.
  • Step 702 The BBERF located in the trusted non-3GPP access network or the ePDG sends a gateway control session establishment message to the V-PCRF, requesting to establish a gateway control session, where the message carries the user identifier and the IP Address1;
  • Step 703 The V-PCRF determines that the user is a roaming user according to the user identifier, and determines that the user does not have a corresponding S9 session, and the V-PCRF initiates an S9 session to the H-PCRF, carrying the user identifier and the IP Address1;
  • Step 704 If the H-PCRF does not have the user-related subscription data, the H-PCRF needs to interact with the Subscriber Profile Repository (SPR) to obtain the subscription data of the user.
  • the H-PCRF formulates policies based on contract data, network policies, and the like. Since there is no PDN identification information at this time, the policy formulated by H-PCRF does not target a PDN.
  • the policies developed by H-PCRF may include QoS rules and event triggers.
  • the H-PCRF returns an acknowledgement message for establishing an S9 session to the V-PCRF, which may carry QoS rules and event triggers;
  • Step 705 The V-PCRF returns a confirmation message for establishing a gateway control session to the BBERF, possibly Carry QoS rules and event triggers;
  • Step 706 The UE finds the P-GW selected when the 3GPP accesses through the self-starting process of the mobile IPv6.
  • a security association is established between the UE and the PDN.
  • the UE uses IKEv2 to initiate the establishment of a security association.
  • EAP is used for authentication on top of IKEv2.
  • the P-GW interacts with the AAA to complete the EAP authentication. And in the process, the P-GW returns the IP address IP Address2 allocated by the P-GW when the UE accesses the 3GPP, and the UE uses the IP Address2 as the HoA when the DSMIPv6 is bound. At this time, the P-GW performs the function of the HA;
  • Step 707 The UE sends a DSMIPv6 binding update message to the P-GW/HA, where the binding update message carries a (HoA, CoA, BID, FID, Routing Filters) routing rule.
  • the corresponding relationship includes a default routing rule, that is, the route filter is a wildcard filter, the HoA value is IP Address2, and the CoA value is IP Address 1;
  • Step 708 After receiving the binding update message, the P-GW/HA performs multiple registration flow binding according to the carried (HoA, CoA, BID, FID, Routing Filters).
  • the PCEF located in the P-GW sends an IP-CAN session establishment indication to the V-PCRF, and the PCEF sends an IP flow migration routing rule information to the V-PCRF.
  • the IP flow migration routing rule information includes installing an IP flow migration routing rule.
  • the IP flow migration routing rule information includes a default routing rule. These routing rules include the correspondence between (IP Address 1 and Routing Filters) (because there are currently only non-3GPP-access networks);
  • Step 709 The V-PCRF installs the IP flow migration routing rules carried in the IP flow migration routing rule information.
  • the V-PCRF determines whether the IP flow migration routing rule information needs to be reported to the H-PCRF according to the event trigger subscribed by the H-PCRF. If the H-PCRF is subscribed to the IP-CAN type modification event trigger or the access gateway modification event is triggered, the V-PCRF needs to report the IP flow migration routing rule information to the H-PCRF; otherwise, the V-PCRF does not report the IP flow migration to the H-PCRF. Routing rule information, performing local processing of the visited place;
  • the IP-CAN type modification is indicated by IP-CAN_CHANGE, and the access gateway modification is represented by AN-GW_CHANGE, if the value of the event trigger sent in step 704 includes IP-CAN_CHANE or AN- GW-CHANGE (When the H-PCRF is subscribed to the IP-CAN-CHANGE or AN-GW-CHANGE event), the V-PCRF needs to report the IP flow migration routing rule information to the H-PCRF; otherwise, the V-PCRF does not go to the H-PCRF.
  • the PCRF reports the IP flow migration routing rule information, and performs local processing of the visited place.
  • the IP-CAN class is used. Types include 3GPP-EPS and Non-3GPP-EPS, and the access gateway includes a trusted non-3GPP access gateway, S-GW, ePDG.
  • Step 710 The V-PCRF sends an S9 session modification message to the H-PCRF, and requests to establish an S9 Subsession (sub-session), where the Subsession carries information such as the IP Address2 and the corresponding PDN identifier. If it is determined in step 709 that the IP flow migration routing rule information needs to be reported, the V-PCRF includes the IP flow migration routing rule information in the Subsession, and sends the information to the H-PCRF. Otherwise, the V-PCRF does not send the IP flow migration routing rule information to the H. -PCRF;
  • Step 711 The H-PCRF installs an IP flow migration routing rule carried in the IP flow migration routing rule information.
  • the H-PCRF formulates a PCC rule according to the user subscription data and the network policy, and sends the PCC rule to the V-PCRF through the Subsession;
  • Step 712 the V-PCRF returns an acknowledgement message to the PCEF, and carries the PCC rule.
  • Step 713 The P-GW/HA returns a binding acknowledgement message to the UE, where the message carries HoA, CoA, BID, and FID to confirm that the UE is successfully registered and the flow binding is successful.
  • Step 714 The V-PCRF formulates a QoS rule according to the PCC rule sent in step 711, and provides the QoS rule to the trusted non-3GPP access network or the BBERF in the ePDG.
  • Step 715 The BBERF installs a QoS rule, and initiates a process specific to the non-3GPP access network to perform resource allocation.
  • Step 716 The BBERF returns an acknowledgement message to the V-PCRF.
  • Step 717 The UE completes the multi-registration flow binding, and a DSMIPv6 tunnel exists between the UE and the P-GW/HA.
  • FIG. 8 is a flowchart of implementing the PDN connection after the UE first establishes a PDN connection through the 3GPP access network, and then establishes the same PDN connection through non-3GPP access, and simultaneously uses the two accesses to use the PDN connection in the embodiment of the present invention.
  • Dynamic PCC is deployed in the network.
  • the UE uses the DSMIPv6 protocol.
  • Step 801 The UE accesses the EPC through the 3GPP access network, where the S-GW and the P-GW establish a tunnel through the GTP or the PMIPv6 protocol, and the existing service is transmitted on the tunnel.
  • the UE discovers the non-3GPP access network and decides to initiate multiple access. If the non-3GPP access network is trusted, the UE performs access authentication and authorization in the trusted non-3GPP access network, and the UE performs layer 3 attachment and obtains the local IP address IP Address1 as the CoA. If the non-3GPP access network is untrusted, the UE will establish an IPSec tunnel with the ePDG. During the tunnel establishment process, the ePDG allocates an IP address IP Address1 to the UE as a CoA.
  • Step 803 The BBERF located in the trusted non-3GPP access network or the ePDG sends a gateway control session establishment message to the V-PCRF, requesting to establish a gateway control session, carrying the user identifier and the IP Address1;
  • Step 804 The V-PCRF associates the gateway control session with the S9 session established by the user according to the user identifier, and the V-PCRF sends an S9 session modification to the H-PCRF, carrying the IP Address1; Step 805, because there is no PDN identifier at this time. Information, so the strategy developed by H-PCRF does not target a PDN.
  • the policies developed by H-PCRF may include QoS rules.
  • the H-PCRF returns an acknowledgment message to the V-PCRF to modify the S9 session, which may carry QoS rules.
  • Step 806 The V-PCRF returns an acknowledgement message to the BBERF.
  • Step 807 the UE finds the selected time in the 3GPP access by using the mobile IPv6 self-starting process.
  • P-GW A security association is established between the UE and the PDN.
  • the UE uses IKEv2 to initiate the establishment of a security association.
  • EAP is used for authentication on top of IKEv2.
  • the P-GW interacts with the AAA to complete the EAP authentication. And in the process, the P-GW returns the IP address IP Address2 allocated by the P-GW when the UE accesses the 3GPP, and the UE uses the IP address as the HoA when the DSMIPv6 is bound. At this time, the P-GW performs the function of the HA;
  • Step 808 The UE sends a DSMIPv6 binding update message to the P-GW/HA, where the binding update message carries (HoA, CoA, BID, FID).
  • (HoA, CoA, BID, FID) is a correspondence.
  • the message is IP Address2 and the CoA value is IP Address1, indicating that the corresponding BID is a binding through non-3GPP access, and a certain data flow of the user ID service uniquely identified by the FID is bound to access through non-3GPP.
  • the message is IP Address2 and the CoA value is IP Address2, indicating that the corresponding BID is a binding through the 3GPP access, and the service data flow identified by the FID is bound to the connection through the 3GPP access.
  • the corresponding relationship includes a routing filter (ie, an IP quintuple) to identify a service data flow.
  • a routing filter ie, an IP quintuple
  • the correspondence between the FID and the Routing Filters is established.
  • the modification of the business data stream in the future can be represented by an FID.
  • the UE reports the default routing rule, that is, Routing Filters is a wildcard filter.
  • the UE may also request to migrate the service data stream SDF transmitted through the 3GPP access to the non-3GPP access network;
  • Step 809 After receiving the binding update message, the P-GW/HA performs multiple registration flow binding according to the carried parameters HoA, CoA, BID, FID, and Routing Filters. That is, the P-GW simultaneously maintains the GTP/PMIPv6 tunnel with the S-GW and the DSMIPv6 tunnel with the UE, and binds the service data stream to the 3GPP access or the non-3GPP access.
  • the PCEF located at the P-GW sends an IP-CAN session modification indication to the V-PCRF, and the PCEF will send an event trigger ROUTING_RULE_CHANGE and IP flow migration routing rule information to the V-PCRF (for IP flow migration routing in the flow)
  • the rule information includes the installation and/or modification of the IP flow migration routing rule, and the IP flow migration routing rule, that is, the correspondence between the service data flow and the access, and the correspondence between the Routing Filters and the Routing Address is determined.
  • the Routing Address value is IP Address 1, Indicated as access through non-3GPP, and when the value of the Routing Address is IP Address2, it is indicated as being accessed through 3GPP.
  • This message includes the default IP flow migration routing rules, ie Routing Filters are wildcards.
  • the PCEF will provide the V-PCRF with the IP flow migration routing rule corresponding to the service data flow to notify the V-PCRF of the service data flow.
  • the migration of the route occurs.
  • Routing Filters is the IP quintuple of the service data flow, and the Routing Address takes the value of IP Address 1;
  • Step 810 The V-PCRF installs or modifies an IP flow migration routing rule carried in the IP flow migration routing rule information.
  • the V-PCRF determines whether the IP flow migration routing rule information needs to be reported to the H-PCRF according to the event trigger subscribed by the H-PCRF.
  • V-PCRF needs to be H -
  • the PCRF reports the IP flow migration routing rule information and ROUTING_RULE_CHANGE; otherwise, the V-PCRF does not migrate the routing rule information and ROUTING_RULE_CHANGE to the 4 IP flows on the H-PCRF, and performs local processing of the visited place;
  • Step 811 If it is determined in step 810 that the V-PCRF needs to report the IP flow migration routing rule information and the ROUTING_RULE_CHANGE to the H-PCRF, the V-PCRF includes the IP migration routing rule information in the Subsession corresponding to the IP-CAN session.
  • Step 812 if the V-PCRF reports the IP flow migration routing rule information and the ROUTING_RULE_CHANGE to the H-PCRF, then the H-PCRF installs and/or modifies the IP flow migration route. IP flow migration routing rules carried in the rule information. If the service data flow corresponding to the IP flow migration routing rule is migrated, the H-PCRF updates the corresponding PCC rule and returns it to the V-PCRF;
  • Step 813 The V-PCRF returns an acknowledgement message to the PCEF. If the V-PCRF reports the IP flow migration routing rule information and the ROUTING_RULE_CHANGE to the H-PCRF, the V-PCRF returns an updated PCC rule to the PCEF.
  • Step 814 The P-GW/HA returns a binding acknowledgement message to the UE, where the message carries the HoA, CoA, BID, and FID to confirm that the UE has multiple registrations, that is, the flow binding is successful or the multiple registration is flow binding and the flow migration succeeds;
  • Step 815 If the V-PCRF does not migrate the routing rule information and the ROUTING_RULE_CHANGE to the H-PCRF, the V-PCRF performs local processing, and if the service data flow corresponding to the IP flow migration routing rule is migrated, Then, the V-PCRF formulates QoS rules according to the PCC rules corresponding to the IP flow migration routing rules (these PCC rules are issued by the H-PCRF when the 3GPP accesses). If the V-PCRF reports the IP flow migration routing rule information and the ROUTING_RULE_CHANGE to the H-PCRF, the V-PCRF determines the QoS rule according to the newly issued PCC rule of the H-PCRF. The V-PCRF provides the QoS rule to a trusted non-3GPP access network or a BBERF in the ePDG;
  • Step 816 The BBERF installs a QoS rule, and initiates a process specific to the non-3GPP access network for resource allocation or modification;
  • Step 817 the BBERF returns an acknowledgement message to the V-PCRF.
  • Step 818 If the UE migrates a certain service data flow from the 3GPP access to the non-3GPP access, and if the PMIPv6 tunnel is established between the S-GW and the P-GW, the V-PCRF deletes the corresponding service data flow. QoS rules.
  • the V-PCRF provides the QoS rule to be deleted to the BBERF in the S-GW through the gateway control session established by the UE during 3GPP access;
  • Step 819 The BBERF deletes the QoS rule, performs a bearer modification or release process of the 3GPP, and releases the resource of the migrated service data flow.
  • Step 820 The BBERF returns an acknowledgement message to the V-PCRF.
  • the P-GW will initiate a 3GPP bearer modification or release process after the step 813 to release the resources of the migrated service data stream. Steps 818-820 will not be performed.
  • Step 821 The UE completes the multi-registration flow binding and the possible flow migration.
  • a DSMIPv6 tunnel exists between the UE and the P-GW/HA, and a GTP/PMIPv6 tunnel exists between the S-GW and the P-GW.
  • the UE or the network can determine which access the service data is transmitted according to the policy.
  • FIG. 9 is a flowchart of a process in which a UE establishes a PDN connection through a non-3GPP access network and then establishes a PDN connection through 3GPP access according to the present invention, and simultaneously uses two PDNs to connect using the PDN. Dynamic PCC is deployed in the network. When the trusted non-3GPP access is used in the figure, the UE uses the DSMIPv6 protocol.
  • Step 901 The UE accesses the EPC through the DSMIPv6 protocol through the non-3GPP access network, and the DSMIPv6 tunnel is established between the UE and the P-GW/HA, and the existing service is transmitted on the tunnel, where the non-3GPP access network allocates the UE.
  • the address is IP Address 1 as the CoA, and the IP address assigned by the P-GW to the UE is IP Address 2 as the HoA;
  • Step 902 The UE discovers the 3GPP access network and decides to initiate multiple access.
  • the UE establishes a PDN connection to the same PDN through the attached procedure of the 3GPP.
  • the P-GW allocates an IP address to the UE as an IP Address2 to ensure that the same PDN connection is established through different accesses.
  • Step 903 The UE sends a DSMIPv6 binding update message to the P-GW/HA, where the binding update message carries (HoA, CoA, BID, FID).
  • (HoA, CoA, BID, FID) is a correspondence.
  • the message is IP Address 2 and the CoA value is IP Address 1 , indicating that the corresponding BID is a binding through non-3GPP access, and a certain data flow of the user ID access service uniquely identified by the FID is bound to the non-3GPP.
  • the message passes the value of IP address2 of HoA, and the value of CoA is IP Address2, indicating that the corresponding BID is a one accessed through 3GPP.
  • the service data flow identified by the FID is bound to the connection through the 3GPP access. If a new stream binding is added, the corresponding relationship also includes Routing Filters. The corresponding relationship is established by the message FID and the Routing Filters, and the modification of the service data stream can be represented by the FID. In this message, the UE may report the default routing rule, that is, Routing Filters is a wildcard filter. The UE may also request to migrate the service data stream SDF transmitted through the non-3GPP access to the 3GPP access network;
  • Step 904 After receiving the binding update message, the P-GW/HA performs multiple registration flow binding according to the carried parameters HoA, CoA, BID, FID, and Routing Filters. That is, the P-GW simultaneously maintains the GTP/PMIPv6 tunnel with the S-GW and the DSMIPv6 tunnel with the UE, and binds the service data stream to the 3GPP access or the non-3GPP access.
  • the PCEF located at the P-GW sends an IP-CAN session modification indication to the V-PCRF, and the PCEF will send an event trigger ROUTING_RULE_CHANGE and IP flow migration routing rule information to the V-PCRF (for the flow, IP flow migration routing)
  • the rule information is to install and/or modify the IP flow migration routing rule.
  • the IP flow migration routing rule is the correspondence between the service data flow and the access.
  • the correspondence between the Routing Filters and the Routing Address is determined by the relationship between the routing address and the Routing Address.
  • This message may include the default IP flow migration routing rules, ie Routing Filters are wildcards. If the UE migrates a certain service data flow from the non-3GPP access to the 3GPP access, the PCEF will provide the V-PCRF with the IP flow migration routing rule corresponding to the service data flow to notify the V-PCRF of the service data flow. The migration of the route occurs.
  • Routing Filters is the IP quintuple of the service data flow, and the Routing Address takes the value of IP Address2;
  • Step 905 The V-PCRF installs and/or modifies an IP flow migration routing rule.
  • the V-PCRF determines whether the IP flow migration routing rule information needs to be reported to the H-PCRF according to the event trigger subscribed by the H-PCRF. If the value of the event trigger in the subscription includes IP-CAN_CHANGE or AN-GW_CHANGE (that is, the H-PCRF subscribes to the IP-CAN-CHANE or AN-GW-CHANGE event trigger), the V-PCRF needs to be H.
  • Step 906 If it is determined in step 905 that the V-PCRF needs to report the IP flow migration routing rule information and the ROUTING_RULE_CHANGE to the H-PCRF, the V-PCRF includes the IP flow migration routing rule in the Subsession corresponding to the IP-CAN session.
  • Routing rule information and ROUTING_RULE_CHANGE are included in the Subsession and sent to the H-PCRF;
  • Step 907 If the V-PCRF reports the IP flow routing rule information and ROUTING_RULE_CHANGE to the H-PCRF, the H-PCRF installs and/or modifies the IP flow migration routing rule. If the service data flow corresponding to the IP flow migration routing rule is migrated, the H-PCRF updates the corresponding PCC rule according to the IP flow migration routing rule and returns it to the V-PCRF;
  • Step 908 The V-PCRF returns an acknowledgement message to the PCEF. If the V-PCRF reports the IP flow migration routing rule information and the ROUTING_RULE_CHANGE to the H-PCRF, the V-PCRF returns an updated PCC rule to the PCEF.
  • Step 909 The P-GW/HA returns a binding acknowledgement message to the UE, where the message carries HoA, CoA,
  • the BID and the FID are used to confirm that the UE's multiple registration, that is, the flow binding is successful or the multiple registration is flow binding and the flow migration succeeds;
  • Step 910 If the V-PCRF does not report the IP flow migration routing rule information and the ROUTING_RULE_CHANGE to the H-PCRF, the V-PCRF performs local processing. If the service data flow corresponding to the IP flow migration routing rule is migrated, The V-PCRF formulates QoS rules according to the PCC rules corresponding to the IP flow migration routing rules (these PCC rules are delivered by the H-PCRF when the non-3GPP is accessed); if the V-PCRF reports the IP flow migration route to the H-PCRF Rule information and ROUTING_RULE_CHANGE, the V-PCRF formulates QoS rules based on the newly issued PCC rules of the H-PCRF. The V-PCRF provides the QoS rule to the BBERF in the S-GW;
  • Step 911 The BBERF installs a QoS rule, and the S-GW initiates execution of a 3GPP bearer modification or establishment process for resource allocation or modification;
  • Step 912 The BBERF returns an acknowledgement message to the V-PCRF.
  • the P-GW will be after step 908. Initiating a 3GPP bearer modification or establishment process, and allocating resources of the migrated service data flow. Steps 910-912 will not be performed.
  • Step 913 If a service data flow is migrated from the non-3GPP access to the 3GPP access, the V-PCRF deletes the QoS rule corresponding to the service data flow in the non-3GPP access network or the ePDG.
  • the V-PCRF provides the QoS rule to be deleted to the BBERF in the non-3GPP access network or the ePDG through the gateway control session established by the UE during non-3GPP access;
  • Step 914 the BBERF deletes the QoS rule, and initiates a specific resource modification or release process that is not a 3GPP;
  • Step 915 the BBERF returns an acknowledgement message to the V-PCRF
  • Step 916 The UE completes the multi-registration flow binding and the flow migration, and the DSMIPv6 tunnel exists between the UE and the P-GW/HA, and the GTP/PMIPv6 tunnel exists between the S-GW and the P-GW.
  • the UE or the network can decide which access the service data is transmitted through according to the policy.
  • FIG. 10 is a flowchart of implementing data flow migration, adding a service data flow, or deleting a service data flow between two access networks after the UE implements multiple registration flow binding by using the process of FIG. 8 or FIG. 9 according to the present invention.
  • Dynamic PCC is deployed in the network.
  • Step 1001 The UE simultaneously connects to the 3GPP access and the non-3GPP access through the process of FIG. 8 or FIG. 9, and performs multiple registration flow binding.
  • Step 1002 The UE sends a DSMIPv6 binding update message to the P-GW/HA, where the binding update message carries (HoA, BID, FID).
  • the UE may request to transmit through the non-3GPP access.
  • the service data stream SDF (represented by FID) is migrated to the 3GPP access network (represented by BID) or vice versa (ie, the routing rule is modified).
  • the UE may also request to delete the routing rule or add a routing rule.
  • the message also includes Routing Filters;
  • Step 1003 After receiving the binding update message, the P-GW/HA, according to the carried parameter HoA,
  • BID and FID perform flow binding updates, including stream migration, add or delete, and so on.
  • the PCEF located at the P-GW sends an IP-CAN session modification indication to the V-PCRF, and the PCEF will send an event trigger ROUTING_RULE_CHANGE and IP flow migration routing rule information to the V-PCRF, including installation, modification, and Delete the IP flow migration routing rule.
  • IP Address1 is used to indicate that the currently transmitted access network is non-3GPP
  • IP Address2 indicates that the currently transmitted access network is 3GPP.
  • Step 1004 The V-PCRF installs, modifies, and/or deletes the IP flow migration routing rule.
  • the V-PCRF determines whether the IP flow migration routing rule information needs to be reported to the H-PCRF according to the event trigger subscribed by the H-PCRF. If the value of the event trigger in the subscription includes IP-CAN_CHANGE or AN-GW_CHANGE (that is, the H-PCRF subscribes to the IP-CAN-CHANE or AN-GW-CHANGE event trigger), the V-PCRF needs to be H.
  • the PCRF reports the IP flow migration routing rule information and the ROUTING_RULE_CHANGE; otherwise, the V-PCRF does not report the IP flow migration routing rule information and the ROUTING_RULE_CHANGE to the H-PCRF, and performs local processing of the visited place;
  • Step 1005 If it is determined in step S1004 that the V-PCRF needs to migrate the routing rule information to the H-PCRF and the ROUTING_RULE_CHANGE, the V-PCRF includes the IP flow migration in the Subsession corresponding to the IP-CAN session.
  • the routing rule information and ROUTING_RULE_CHANGE are sent to the H-PCRF (ie, the ROUTING_RULE_CHANGE event is triggered to the H-PCRF to trigger and install, modify, and/or delete the IP flow migration routing rule); otherwise the V-PCRF will not IP flow migration routing rule information and ROUTING_RULE_CHANGE are included in the Subsession and sent to the H-PCRF;
  • Step 1006 If the V-PCRF reports the IP flow migration routing rule information and ROUTING_RULE_CHANGE to the H-PCRF, the H-PCRF installs, modifies, and/or deletes the IP flow migration routing rule. If the service data flow corresponding to the IP flow migration routing rule is migrated, the H-PCRF updates the corresponding PCC rule and returns it to the V-PCRF.
  • Step 1007 The V-PCRF returns an acknowledgement message to the PCEF. If the V-PCRF reports the IP flow migration routing rule information and the ROUTING_RULE_CHANGE to the H-PCRF, the confirmation message returned by the V-PCRF to the PCEF includes the updated PCC rule. ;
  • Step 1008 The P-GW/HA returns a binding acknowledgement message to the UE, where the message carries the HoA, BID, and FID to confirm that the UE routing rule is updated successfully, that is, the flow migration is successful.
  • Step 1009 If a PMIPv6 tunnel is established between the S-GW and the P-GW, the V-PCRF installs or deletes the QoS rule on the BBERF in the S-GW according to the routing rule reported by the PCEF. If it is migrated from non-3GPP to 3GPP, the QoS rule is installed, otherwise, the QoS rule is deleted. If the V-PCRF does not report the routing rule and ROUTING_RULE_CHANGE to the H-PCRF, the V-PCRF performs local processing. If the service data flow corresponding to the IP flow migration routing rule is migrated and the QoS rule needs to be installed, then The PCC rules corresponding to the IP flow migration routing rules formulate QoS rules.
  • the PCC rule is a PCC rule that is locally saved by the V-PCRF.
  • the PCC rule is previously issued by the H-PCRF, and may be delivered by the H-PCRF when the non-3GPP is accessed, or when the 3GPP is accessed. - issued by the PCRF, or, in other processes, issued by the H-PCRF. If the V-PCRF reports the IP flow migration routing rule information and the ROUTING_RULE_CHANGE to the H-PCRF, the V-PCRF formulates the QoS rule according to the newly-issued PCC rule of the H-PCRF, and the V-PCRF goes to the S-GW. BBERF provides this QoS rule. If the QoS rule needs to be deleted, the V-PCRF requests the BBERF to delete the QoS rule corresponding to the service data flow migrated from the 3GPP access;
  • Step 1010 The BBERF installs or deletes the QoS rule, and the S-GW initiates the 3GPP bearer establishment, modification, or deletion process to allocate, modify, or release the resource;
  • Step 1011 The BBERF returns an acknowledgement message to the V-PCRF.
  • Steps 1009-1011 will not be performed.
  • Step 1012 The V-PCRF installs or deletes the QoS rule on the BBERF in the trusted non-3GPP access network or the ePDG according to the IP flow migration routing rule information reported by the PCEF. If migrating from 3GPP to non-3GPP, the QoS rules are installed, otherwise the QoS rules are deleted. If the V-PCRF does not report the IP flow migration routing rule information and ROUTING_RULE_CHANGE to the H-PCRF, the V-PCRF performs local processing, if the service data flow corresponding to the IP flow migration routing rule is migrated, and QoS needs to be installed. The rule determines the QoS rule according to the PCC rule corresponding to the IP flow migration routing rule.
  • the PCC rule is a PCC rule saved locally by the V-PCRF.
  • the PCC rule is sent by the H-PCRF before the H-PCRF, or when the 3GPP accesses the H-PCRF. - issued by PCRF, or issued by H-PCRF in other processes. If the V-PCRF migrates the routing rule information and the ROUTING_RULE_CHANGE to the H-PCRF, the V-PCRF formulates the QoS rule according to the newly issued PCC rule of the H-PCRF, and the V-PCRF is trusted.
  • the BBERF in the 3GPP access network or ePDG provides this QoS rule. If the QoS rule needs to be deleted, the V-PCRF requests the BBERF to be deleted from the non-3GPP.
  • Step 1013 The BBERF installs or deletes the QoS rule, and initiates a specific resource allocation, modification, or release process of the non-3GPP;
  • step 1014 the BBERF returns an acknowledgement message to the V-PCRF.
  • the present invention further provides a policy charging control system for supporting IP flow migration in a roaming scenario, including: a visited local policy and a charging rule function (V-PCRF) and a home location policy and a charging rule function (H-PCRF). among them:
  • V-PCRF visited local policy and a charging rule function
  • H-PCRF home location policy and a charging rule function
  • the V-PCRF is configured to: when receiving the IP flow migration routing rule information reported by the Policy and Charging Enforcement Function (PCEF), if the H-PCRF subscribes to an IP-CAN type modification (IP-CAN_CHANGE) event trigger or The access gateway modification (AN_GW_CHANGE) event is triggered, and the IP flow migration routing rule information is reported to the H-PCRF, where the IP flow migration routing rule information includes one or more of the following IP flow migration rules: installation, modification Or delete the IP flow migration routing rule.
  • PCEF Policy and Charging Enforcement Function
  • the V-PCRF is further configured to: after receiving the IP flow migration routing rule information, perform one or more of the following operations: installing, modifying, or deleting the IP flow carried in the IP flow migration routing rule information Migrate routing rules.
  • the H-PCRF is further configured to carry the IP flow migration routing rule information in the IP connection migration network (IP-CAN) session establishment process, and after the IP flow migration routing rule information is received, IP flow migration routing rules.
  • IP-CAN IP connection migration network
  • the V-PCRF is further configured to: when the IP flow migration routing rule information is reported to the H-PCRF in the IP-CAN session modification process, the ROUTING RULE CHANGE event is triggered to the H - PCRF.
  • the H-PCRF is further configured to: after receiving the IP flow migration routing rule information in the IP-CAN session modification process, perform one or more of the following operations: installing, modifying, or deleting the IP flow Migrate the IP flow migration routing rules carried in the routing rule information.
  • the H-PCRF is further configured to: after the IP flow migration routing rule is installed, modified, or deleted, if the service data flow corresponding to the IP flow migration routing rule is migrated, the PCC rule is updated, Delivering updated PCC rules to the V-PCRF;
  • the V-PCRF is further configured to send the updated PCC rule to the PCEF.
  • the V-PCRF is further configured to: formulate a QoS rule according to the updated PCC rule, and send the QoS rule to the specified BBERF according to the IP flow migration routing rule.
  • the V-PCRF is further configured to delete a QoS rule corresponding to the service data flow from a BBERF that flows before the service data flow migrates.
  • the V-PCRF is further configured to: if the H-PCRF is not subscribed to the IP-CAN_CHANGE event trigger or the AN-GW_CHANGE event trigger, locally process IP flow migration.
  • the V-PCRF local processing IP flow migration includes: if the service data flow corresponding to the IP flow migration routing rule is migrated, the V-PCRF determines the QoS according to the PCC rule corresponding to the IP flow migration routing rule. Rules, and transmitting the QoS rules to the specified BBERF according to the IP flow migration routing rule.
  • the locally processing the IP stream migration by the V-PCRF further includes: deleting the QoS rule corresponding to the service data flow from the BBERF that flows before the service data flow migrates.
  • 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, or they may be separately fabricated into individual integrated circuit modules, or they may be Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any particular combination of hardware and software.
  • the visited network can perform IP flow migration locally;
  • H-PCRF supports IP flow migration
  • V-PCRF does not need to interact with H-PCRF, and it needs to be compared with H- at any time.
  • the PCRF interaction scheme can save the signaling overhead between the V-PCRF and the H-PCRF.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种漫游场景下支持IP流迁移的策略计费控制方法，包括：拜访地策略和计费规则功能（V-PCRF）接收到策略和计费执行功能（PCEF）上报的IP流迁移路由规则信息时，如果归属地策略和计费规则功能（H-PCRF）订阅了IP-CAN类型修改（IP-CAN_CHANGE）事件触发或接入网关修改（AN_GW_CHANGE）事件触发，所述V-PCRF上报所述IP流迁移路由规则信息至所述H-PCRF。采用本方案，拜访网络可以本地执行IP流迁移，或者，相比任何时候都需要与H-PCRF交互的方案，可以节省V-PCRF与H-PCRF之间的信令开销。

Description

漫游场景下支持 IP流迁移的策略计费控制方法和系统
技术领域
本发明涉及通信领域， 具体而言， 涉及一种漫游场景下支持 IP流迁移的 策略计费控制方法和系统。 背景技术
图 1是根据相关技术的演进的分组系统（ Evolved Packet System, 简称为 EPS ) 的系统架构示意图， 如图 1 所示， EPS 由接入网和演进的分组核心网 ( Evolved Packet Core, 简称为 EPC )组成， 其中， 接入网可以是演进的通用 陆地无线接入网 （ Evolved Universal Terrestrial Radio Access Network , 简称为 E-UTRAN )等， EPC包括： 移动管理实体（ Mobility Management Entity, 简 称为 MME ) 、 服务网关（ Serving Gateway, 简称为 S-GW ) 、 分组数据网络 网关（ Packet Data Network Gateway,简称为 P-GW )、归属用户服务器（ Home Subscriber Server , 简称为 HSS ) 、 第三代合作伙伴计划 （3rd Generation Partnership Project,简称为 3GPP )鉴权授权计费（ Authentication、 Authorization、 Accounting, 简称为 AAA )服务器、策略和计费规则功能（ Policy and Charging Rules Function , 简称为 PCRF )及其它支撑节点。
其中， MME负责移动性管理、非接入层信令的处理和用户上下文的管理 等控制面的相关工作； S-GW是与 E-UTRAN相连的接入网关设备， 负责在 E-UTRAN和 P-GW之间转发数据， 并对寻呼等待数据进行緩存； P-GW是第 三代合作伙伴计划（ 3rd Generation Partnership Project, 简称为 3GPP )演进分 组系统与分组数据网络（ Packet Data Network, 简称为 PDN ) 的边界网关， 负责用户终端到 PDN的接入、 在 EPS与 PDN间转发数据等； PCRF是策略 和计费规则功能实体，通过接收接口 Rx和运营商网络协议（ Internet Protocol , 简称为 IP )业务网络相连， 获取业务信息， 此外， 它通过 Gx/Gxa/Gxc接口与 网络中的网关设备相连， 负责发起 IP承载的建立， 保证业务数据的服务质量 ( Quality of Service , 简称为 QoS ) , 并进行计费控制。
EPS也支持用户设备 ( User Equipment, 简称为 UE )通过除 E-UTRAN 以外的其它非 3GPP系统的接入， 其中， 非 3GPP系统通过 S2a/b/c接口实现 接入， P-GW作为 3GPP系统的接入与非 3GPP系统的接入的数据锚点。 在 EPS的系统架构中， 非 3GPP系统被分为可信任非 3GPP IP接入网和不可信 任非 3GPP IP接入网。可信任非 3GPP IP接入网可直接通过 S2a接口与 P-GW 连接； 不可信任非 3GPP IP接入网需要经过演进的分组数据网关 （Evolved Packet Data Gateway, 简称为 ePDG )与 P-GW相连， ePDG与 P-GW间的接 口为 S2b。 S2c是 UE和 P-GW之间的接口， 釆用双栈的移动网络协议版本 6 ( Internet Protocol Vision, 简称为 IPv6 ) ( Moblie IPv6 Support for Dual Stack Hosts and Routers, 简称为 DSMIPv6 )协议提供控制和移动性管理。
EPS系统支持 IP流迁移（ IP Flow Mobility )。 图 2是现有技术中的 IP流 迁移的接入示意图， 如图 2所示， UE 同时在非 3GPP接入（如无线局域网 WLAN )和 3GPP接入 (如 E-UTRAN)的覆盖下 ,通过非 3GPP IP接入网和 3GPP 接入网通过同一个 P-GW接入到 PDN。 在这种场景下， UE通过多个接入网 附着到 EPC, P-GW为 UE分配一个 IP地址， UE和 PDN之间存在一个 PDN 连接 (也称 IP连接接入网 IP-CAN会话)。 由于不同的业务适用于釆用不同的 网络传输， IP流迁移可以根据业务的特性选择适用的接入网传输业务， 并且， 多个接入网可以分担网络负荷，避免网络拥堵。如果非 3GPP接入网是 WLAN 时， 超文本传输协议（ Hypertext Transfer Protocol, 简称为 Http )和文件传输 协议（ File Transfer Protocol , 简称为 Ftp ) 的业务数据流就可以通过 WLAN , 而 IP电话（ Voice over IP, 简称为 VoIP ) 的业务数据流就可以通过 3GPP发 送给 UE。
图 3是现有技术中实现 UE先通过 3GPP接入网接入建立 PDN连接后又 通过非 3GPP接入建立同一个 PDN连接， 并同时使用两个接入使用该 PDN 连接的流程。 网络中部署了动态策略和计费控制 PCC ( Policy and Charging Control )。 图中通过可信任非 3GPP接入时， UE釆用 DSMIPv6协议， 如图 3 所示， 该方法包括以下步骤 301至步骤 316:
步骤 301 , UE通过 3GPP接入网接入 EPC, 其中， S-GW和 P-GW之间 通过通用分组无线业务隧道协议 ( General Packet Radio Service Tunnelling Protocol, 简称为 GTP )或代理移动 IPv6 ( Proxy Mobile IPv6, 简称为 PMIPv6 ) 协议建立隧道， 且可能已有业务在该隧道上传输；
步骤 302, UE发现非 3GPP接入网并决定发起多接入。 若非 3GPP接入 网是可信任的， 那么 UE在可信任非 3GPP接入网中执行接入认证和授权， UE执行层 3 附着并获得本地 IP地址 IP Addressl 作为转交地址（Care of Address,简称为 CoA )。若非 3GPP接入网是不可信任的，那么 UE将与 ePDG 建立 IPSec隧道， 在隧道建立过程， ePDG为 UE分配 IP地址 IP Addressl并 作为 CoA;
步骤 303 ,位于可信任非 3GPP接入网或 ePDG中承载绑定及事件报告功 能 ( BBERF ) 向 PCRF发送网关控制会话建立消息， 建立请求建立网关控制 会话， 携带用户标识和 IP Addressl ;
步骤 304 , PCRF向 BBERF返回确认消息；
步骤 305, UE通过移动 IPv6 ( Mobile IPv6, 简称为 MIPv6 )的自启动过 程找到在 3GPP接入时选择的 P-GW。 UE和 PDN之间建立安全联盟。 UE釆 用网络密钥交换 2 ( Internet Key Exchange2 , 简称为 ΙΚΕν2 )发起建立安全联 盟。扩展认证协议（ Extensible Authentication Protocol, 简称为 EAP )在 IKEv2 之上用于认证。 P-GW与 AAA交互以完成 EAP认证。并且在该过程中， P-GW 返回 UE在 3GPP接入时 P-GW分配的 IP地址 IP Address2, UE将该 IP地址 作为 DSMIPv6绑定时的家乡地址（ Home of Address , 简称为 ΗοΑ ) 。 此时， P-GW执行的是家乡代理（Home Agent, 简称为 HA ) 的功能；
步骤 306 , UE向 P-GW/HA发送 DSMIPv6绑定更新消息， 该绑定更新消 息中携带有（ HoA, CoA, BID ( Banding Identification,绑定标识）， FID ( Flow Identification, 流标识） ） 。 （HoA, CoA, BID, FID )是一个对应关系。
其中， 该绑定更新消息中通过 HoA取值为 IP Address2, CoA取值为 IP Addressl ,表明对应的 BID是通过非 3GPP接入的一个绑定， FID唯一标识的 用户访问业务的某个数据流绑定到通过非 3GPP接入的连接上。
该绑定更新消息中通过 HoA取值为 IP Address2 , CoA取值为 IP Address2,表明对应的 BID是通过 3GPP接入的一个绑定， FID标识的业务数 据流绑定到通过 3GPP接入的连接上。 若是新增的一个流绑定， 那么对应关系中还包括路由过滤器 Routing Filters (即 IP五元组）用来标识一个业务数据流。 通过该消息 FID和 Routing Filters建立了对应关系， 在以后对该业务数据流的修改可以用 FID来表示。 在该消息中 UE上报默认的路由规则，即 Routing Filters是一个通配符过滤器。
UE也可以请求将经过 3GPP接入中传输的业务数据流（ SDF ) 迁移到非
3GPP接人网中；
步骤 307, P-GW/HA接收到绑定更新消息之后， 根据该消息中携带的参 数 HoA, CoA, BID, FID以及 Routing Filters执行多注册流绑定。 即， P-GW 同时保持与 S-GW的 GTP/PMIPv6隧道和与 UE的 DSMIPv6隧道， 并将业务 数据流绑定到 3GPP接入或非 3GPP接入上。位于 P-GW的 PCEF向 PCRF发 送 IP-CAN会话修改请求指示， PCEF将向 PCRF发送事件触发器路由规则修 改（ ROUTING_RULE_CHANGE )和 IP流迁移路由规则信息（对于该流程中 的新增和 /或迁移 IP流的情况， IP流迁移路由规则信息为安装和 /或修改 IP流 迁移路由规则， IP 流迁移路由规则为业务数据流与接入的对应关系， 通过 Routing Filters与 Routing Address对应关系进行标识 , Routing Address取值为 IP Address 1时，表示为通过非 3GPP接入， Routing Address取值为 IP Address2 时，表示为通过 3GPP接入）。该消息包括默认的 IP流迁移路由规则，即 Routing Filters是通配符。
若 UE将某个业务数据流从 3GPP接入中迁移到非 3GPP接入中，则 PCEF 将向 PCRF提供该业务数据流对应的 IP流迁移路由规则， 以通知 PCRF该业 务数据流的路由发生的迁移。 该路由规则中， Routing Filters为该业务数据流 的 IP五元组， Routing Address取值为 IP Address 1；
步骤 308, PCRF安装和 /或修改 IP流迁移路由规则。 若 IP流迁移路由规 则对应的业务数据流发生了迁移 （即从 3GPP接入迁移到了非 3GPP接入） ， PCRF对应地更新 PCC规则 , 并返回给 PCEF。 对于 PCRF新安装的 IP流迁 移路由规则， 可能会导致 IP流迁移路由规则对应的业务数据流从默认路由迁 移到 IP流迁移路由规则指定的路由上。对于 PCRF修改的 IP流迁移路由规则， 可能会导致 IP流迁移路由规则对应的业务数据流从源路由路径迁移到新的路 由路径上。本流程中，针对从传输 3GPP接入迁移到非 3GPP接入的业务数据 流的 PCC规则进行更新后返回给 PCEF;
步骤 309 , P-GW/HA向 UE返回绑定确认消息， 消息中携带 HoA, CoA, BID和 FID以确认 UE的多注册即流绑定成功 , 或多注册即流绑定以及流迁 移成功；
步骤 310, 若某个业务数据流从 3GPP接入迁移到了非 3GPP接入， 那么
PCRF将根据该业务数据流更新的 PCC规则制定 QoS规则， 并向可信任非 3GPP接入网或 ePDG中的 BBERF提供该 QoS规则；
步骤 311 , 非 3GPP接入网执行特定的流程进行资源分配或修改； 步骤 312, BBERF向 PCRF返回确认消息；
步骤 313 , 若某个业务数据流从 3GPP接入迁移到了非 3GPP接入， 并且 若 S-GW和 P-GW之间建立的是 ΡΜΙΡνό隧道， 那么 PCRF将删除该业务数 据流对应的 QoS规则。 PCRF通过 UE在 3GPP接入时建立的网关控制会话向 S-GW中的 BBERF提供需要删除的 QoS规则；
步骤 314, S-GW中的 BBERF删除 QoS规则， 执行 3GPP的承载修改或 释放流程， 释放迁移走的业务数据流的资源；
步骤 315, BBERF向 PCRF返回确认消息；
若 S-GW和 P-GW之间建立的是 GTP隧道，那么 P-GW将在步骤 308后， 发起 3GPP的承载修改或释放流程， 释放迁移走的业务数据流的资源。 步骤 313-315将不执行。
步骤 316, UE完成了多注册流绑定以及可能的流迁移， UE和 P-GW/HA 之间存在 DSMIPv6隧道， S-GW与 P-GW之间存在 GTP/PMIPv6隧道。 UE 或网络可以根据策略决定业务数据通过哪个接入进行传输。
图 4是现有技术中实现 UE先通过非 3GPP接入网接入建立 PDN连接后 又通过 3GPP接入建立同一个 PDN连接， 并同时使用两个接入使用该 PDN 连接的流程。 网络中部署了动态 PCC。 图中通过可信任非 3GPP接入时， UE 釆用 DSMIPv6协议， 如图 4所示， 该方法包括以下步骤 401至步骤 413: 步骤 401 , UE通过非 3GPP接入网釆用 DSMIPv6协议接入 EPC, UE与 P-GW/HA之间建立 DSMIPv6隧道，并已有业务在该隧道上传输，其中非 3GPP 接入网为 UE分配的地址为 IP Address 1作为 CoA, P-GW为 UE分配的 IP地 址为 IP Address2作为 HoA;
步骤 402, UE发现 3GPP接入网并决定发起多接入。 UE通过 3GPP的附 着流程建立到同一个 PDN的 PDN连接，在建立过程中， P-GW为 UE分配 IP 地址为 IP Address2 , 以保证通过不同接入建立了同一个 PDN连接；
步骤 403 , UE向 P-GW/HA发送 DSMIPv6绑定更新消息， 该绑定更新消 息中携带有 （HoA, CoA, BID, FID ) 。 （HoA, CoA, BID, FID )是一个 对应关系。 该消息通过 HoA取值 IP Address2 , CoA取值 IP Address 1 , 表明 对应的 BID是通过非 3GPP接入的一个绑定， FID唯一标识的用户访问业务 的某个数据流绑定到通过非 3GPP接入的连接上。 该消息通过 HoA取值 IP Address2 , CoA取值 IP Address2 , 表明对应的 BID是通过 3GPP接入的一个 绑定， FID标识的业务数据流绑定到通过 3GPP接入的连接上。若是新增的一 个流绑定，那么对应关系中还包括 Routing Filters。通过该消息 FID和 Routing Filters建立了对应关系， 在以后对该业务数据流的修改时可以用 FID来表示。 在该消息中 UE可能上报默认的路由规则， 即 Routing Filters是一个通配符过 滤器。 UE也可以请求将经过非 3GPP接入中传输的业务数据流 SDF迁移到 3GPP接人网中；
步骤 404, P-GW/HA接收到绑定更新消息之后，根据所携带的参数 HoA, CoA, BID, FID以及 Routing Filters执行多注册流绑定。 即， P-GW同时保持 与 S-GW的 GTP/PMIPv6隧道和与 UE的 DSMIPv6隧道， 并将业务数据流绑 定到 3GPP接入或非 3GPP接入上。位于 P-GW的 PCEF向 PCRF发送 IP-CAN 会话修 改请 求 指 示 ， PCEF 将 向 PCRF 发送事件触发 器 ROUTING— RULE— CHANGE和 IP流迁移路由规则信息 （对于该流程中的新 增和 /或迁移 IP流的情况， IP流迁移路由规则信息为安装和 /或修改 IP流迁移 路由规则， IP流迁移路由规则即业务数据流与接入的对应关系， 通过 Routing Filters与 Routing Address对应关系标识 , Routing Address取值为 IP Address 1 时， 表示为通过非 3GPP接入， Routing Address取值为 IP Address2时， 表示 为通过 3GPP接入 )。 该消息可能包括默认的 IP流迁移路由规则， 即 Routing Filters是通配符。 若 UE将某个业务数据流从非 3GPP接入中迁移到 3GPP接 入中， 则 PCEF将向 PCRF提供该业务数据流对应的 IP流迁移路由规则， 以 通知 PCRF该业务数据流的路由发生的迁移。该 IP流迁移路由规则中， Routing Filters为该业务数据流的 IP五元组， Routing Address取值为 IP Address2； 步骤 405, PCRF安装和 /或修改 IP流迁移路由规则。 若 IP流迁移路由规 则对应的业务数据流发生了迁移 （即从非 3GPP接入迁移到了 3GPP接入） ， PCRF更新对应的 PCC规则 , 并返回给 PCEF。 对于 PCRF新安装的 IP流迁 移路由规则， 可能会导致 IP流迁移路由规则对应的业务数据流从默认路由迁 移到 IP流迁移路由规则指定的路由上。对于 PCRF修改的 IP流迁移路由规则， 可能会导致 IP流迁移路由规则对应的业务数据流从源路由路径迁移到新的路 由路径上。 此流程中， 将从非 3GPP接入迁移到 3GPP接入的业务数据流的 PCC规则进行更新后返回给 PCEF;
步骤 406 , P-GW/HA向 UE返回绑定确认消息， 消息中携带 HoA, CoA, BID和 FID以确认 UE的多注册即流绑定成功或多注册即流绑定以及流迁移 成功；
步骤 407, 若某个业务数据流从非 3GPP接入迁移到了 3GPP接入， 并且 若 S-GW和 P-GW之间建立的是 PMIPv6隧道， 那么 PCRF将根据该业务数 据流更新的 PCC规则制定 QoS规则，并向 S-GW中的 BBERF提供该 QoS规 则；
步骤 408, BBERF安装 QoS规则， S-GW发起执行 3GPP的承载修改或 建立流程进行资源分配或修改；
步骤 409 , BBERF向 PCRF返回确认消息；
若 S-GW和 P-GW之间建立的是 GTP隧道，那么 P-GW将在步骤 405后， 发起 3GPP的承载修改或建立流程， 分配迁移入的业务数据流的资源。 步骤 407-409将不执行。
步骤 410, 若某个业务数据流从非 3GPP接入迁移到了 3GPP接入， 那么 PCRF将删除在非 3GPP接入网或 ePDG中该业务数据流对应的 QoS规则。 PCRF通过 UE在非 3GPP接入时建立的网关控制会话向非 3GPP接入网或 ePDG中的 BBERF提供需要删除的 QoS规则；
步骤 411 , BBERF删除 QoS规则， 并发起执行非 3GPP的特定的资源修 改或释放流程；
步骤 412 , BBERF向 PCRF返回确认消息；
步骤 413 , UE完成了多注册流绑定以及流迁移， UE和 P-GW/HA之间存 在 DSMIPv6隧道， S-GW与 P-GW之间存在 GTP/PMIPv6隧道。 UE或网络 可以根据策略决定业务数据通过哪个接入进行传输。
图 5是现有技术中实现 UE通过图 3或图 4的流程实现多注册流绑定后， 在两个接入网之间进行数据流迁移的流程图。 网络中部署了动态 PCC。 如图 5所示， 该方法包括以下步骤 501至步骤 511 :
步骤 501 , UE通过图 3或图 4的流程同时连接到 3GPP接入和非 3GPP 接入， 并进行了多注册流绑定。
步骤 502 , UE向 P-GW/HA发送 DSMIPv6绑定更新消息， 该绑定更新 消息中携带有（ HoA, BID , FID )。在该消息中， UE可以请求将经过非 3GPP 接入中传输的业务数据流 SDF (用 FID表示)迁移到 3GPP接入网中 （用 BID 表示）或反之 (即修改路由规则 )。 UE也可以请求删除路由规则或增加一个 新的路由规则。 若是新增路由规则， 则消息中还包括 Routing Filters;
步骤 503 , P-GW/HA接收到绑定更新消息之后，根据所携带的参数 HoA, BID和 FID执行流绑定更新 ,包括流迁移 ,新增或删除等。位于 P-GW的 PCEF 向 PCRF发送 IP-CAN会话修改请求指示， PCEF将向 PCRF发送事件触发器 ROUTING— RULE— CHANGE和 IP流迁移路由规则信息， 包括安装、 修改和 / 或删除 IP流迁移路由规则。 路由规则中用 IP Addressl表示当前传输的接入 网为非 3GPP,用 IP Address2表示当前传输的接入网为 3GPP。用 Routing Filters 来表示业务数据流；
步骤 504, PCRF安装、 修改和 /或删除 IP流迁移路由规则。 PCRF根据 IP流迁移路由规则对 PCC规则进行更新。 对于 PCRF新安装的 IP流迁移路 由规则， 可能会导致 IP流迁移路由规则对应的业务数据流从默认路由迁移到 IP流迁移路由规则指定的路由上。 对于 PCRF修改的 IP流迁移路由规则 , 可 能会导致 IP流迁移路由规则对应的业务数据流从源路由路径迁移到新的路由 路径上。对于 PCRF删除的 IP流迁移路由规则，可能会导致 IP流迁移路由规 则对应的业务数据流从源路由路径迁移到默认路由规则的路径上；
步骤 505, P-GW/HA向 UE返回绑定确认消息， 消息中携带 HoA, BID 和 FID以确认 UE路由规则更新成功；
步骤 506 , 若 S-GW和 P-GW之间建立的是 PMIPv6隧道， 那么 PCRF将 根据 PCEF上报的规则在 S-GW中的 BBERF上安装或删除 QoS规则。 如果 是从非 3GPP迁移入 3GPP, 则安装 QoS规则， 反之， 则删除 QoS规则； 步骤 507, BBERF安装或删除 QoS规则， S-GW发起执行 3GPP的承载 建立、 修改或删除流程进行资源分配、 修改或释放；
步骤 508 , BBERF向 PCRF返回确认消息；
若 S-GW和 P-GW之间建立的是 GTP隧道，那么 P-GW将在步骤 504后， 发起 3GPP的承载建立、 修改或删除流程。 步骤 506-508将不执行。
步骤 509, PCRF将根据 PCEF上报的规则在可信任非 3GPP接入网或 ePDG中的 BBERF上安装或删除 QoS规则。如果是从 3GPP迁移入非 3GPP, 则安装 QoS规则， 反之， 则删除 QoS规则；
步骤 510, BBERF安装或删除 QoS规则， 并发起执行非 3GPP的特定的 资源分配、 修改或释放流程；
步骤 511 , BBERF向 PCRF返回确认消息。
从上述流程分析可以看出， 在执行 IP流程的策略计费控制时。 由 PCEF 向 PCRF提供表示业务数据流传输路径的路由规则， PCRF根据路由规则确定 业务数据流当前传输的接入网，并在当前的接入网中为业务数据流分配资源。 若业务数据流发生了迁移， 那么还会在源接入网中释放业务数据流分配的资 源。
在现有技术中， IP流迁移路由规则包括如下 4部分内容：
规则标识： 用来在一个 IP-CAN会话中唯一标识一个路由规则； 路由过滤器： 用来标识业务数据流； 优先级： 用来标识该路由规则的优先级；
路由地址： 用来标识当前业务数据流传输的接入网， 如图 3、 4、 5中的 IP Address 1和 IP Address2„
IP流迁移路由规则包含安装、 修改和删除 3种操作。 安装和修改操作， 需要携带 IP流迁移规则的内容， 需包括规则标识， 还需包括路由过滤器、 优 先级、 路由地址中的至少一个。 删除操作时， 携带规则标识即可。
现有技术中， 对非漫游场景中 IP流迁移的策略控制方法提供了支持， 而 对于漫游场景下， 如何支持 IP流迁移的策略控制并没有完整的解决方案。 特 别是针对拜访地接入（Visited Access, 简称为 VA, 也称为本地疏导 Local Breakout )漫游场景（如图 6所示）下的支持 IP流迁移的策略计费控制方法， 如何更优化的策略计费控制是个待解决的问题。 发明内容
本发明要解决的技术问题是提供一种漫游场景下支持 IP流迁移的策略计 费控制方法和系统。
为了解决上述问题， 本发明提供了一种漫游场景下支持 IP流迁移的策略 计费控制方法， 包括：
拜访地策略和计费规则功能 （V-PCRF )接收到策略和计费执行功能 ( PCEF )上报的 IP 流迁移路由规则信息时， 如果归属地策略和计费规则功 能 ( H-PCRF )订阅了 IP-CAN类型修改（ IP-CAN_CHANGE )事件触发或接 入网关修改（ AN— GW— CHANGE )事件触发， 所述 V-PCRF上报所述 IP流迁 移路由规则信息至所述 H-PCRF, 所述 IP流迁移路由规则信息中包括如下一 种或多种 IP流迁移规则： 安装、 修改或删除 IP流迁移路由规则。
优选地， 上述方法还可具有以下特点，
所述 V-PCRF接收到所述 IP流迁移路由规则信息后， 执行如下一种或多 种操作： 安装、 修改或删除所述 IP流迁移路由规则信息中携带的 IP流迁移 路由规则。
优选地， 上述方法还可具有以下特点， 所述方法还包括： 在 IP连接接入网 （ IP - CAN )会话建立过程中 , 所述 H-PCRF接收到所 述 IP流迁移路由规则信息后， 安装所述 IP流迁移路由规则信息中携带的所 述 IP流迁移路由规则。
优选地， 上述方法还可具有以下特点，
在 IP-CAN会话修改过程中， 所述 V-PCRF上报 IP流迁移路由规则信息 至所述 H-PCRF时， 还上报路由规则修改 （ ROUTING_RULE_CHANGE )事 件触发至所述 H-PCRF。
优选地， 上述方法还可具有以下特点， 所述方法还包括：
在 IP - CAN会话修改过程中， 所述 H-PCRF接收到所述 IP流迁移路由 规则信息后， 执行如下一种或多种操作： 安装、 修改或删除所述 IP流迁移路 由规则信息中携带的 IP流迁移路由规则。
优选地， 上述方法还可具有以下特点， 所述方法还包括：
所述 H-PCRF安装、修改或删除 IP流迁移路由规则后，若所述 IP流迁移 路由规则对应的业务数据流发生了迁移， 则更新策略和计费控制 （PCC )规 则， 下发更新后的 PCC规则至所述 V-PCRF;
所述 V-PCRF下发所述更新后的 PCC规则至所述 PCEF。
优选地， 上述方法还可具有以下特点， 所述方法还包括： 根据所述 IP流迁移路由规则将所述 QoS规则发送至指定的承载绑定及事件报 告功能（BBERF ) 。
优选地， 上述方法还可具有以下特点， 所述方法还包括：
所述 V-PCRF从所述业务数据流迁移前流经的 BBERF中删除所述业务数 据流对应的 QoS规则。
优选地，上述方法还可具有以下特点，所述方法还包括，如果所述 H-PCRF 未订阅所述 IP-CAN— CHANGE事件触发或所述 AN— GW— CHANGE事件触发， 所述 V-PCRF在本地处理 IP流迁移。
优选地， 上述方法还可具有以下特点， 所述 V-PCRF在本地处理 IP流迁 移包括：
若所述 IP流迁移路由规则对应的业务数据流发生了迁移， 所述 V-PCRF 根据所述 IP流迁移路由规则对应的 PCC规则制定 QoS规则， 并根据所述 IP 流迁移路由规则将所述 QoS规则发送至指定的 BBERF。
优选地， 上述方法还可具有以下特点， 所述 V-PCRF在本地处理 IP流迁 移还包括：
所述 V-PCRF从所述业务数据流迁移前流经的 BBERF中删除所述业务数 据流对应的 QoS规则。
本发明还提供一种漫游场景下支持 IP流迁移的策略计费控制系统，包括： 拜访地策略和计费规则功能 （V-PCRF ) 和归属地策略和计费规则功能 ( H-PCRF ) , 其中：
所述 V-PCRF设置为： 接收到策略和计费执行功能（PCEF )上报的 IP 流迁移路由规则信息时， 如果所述 H-PCRF 订阅了 IP-CAN 类型修改 ( IP-CAN_CHANGE )事件触发或接入网关修改（ AN_GW_CHANGE )事件 触发， 上报所述 IP流迁移路由规则信息至所述 H-PCRF, 所述 IP流迁移路由 规则信息中包括如下一种或多种 IP流迁移规则： 安装、 修改或删除 IP流迁 移路由规则。
优选地， 上述系统还可具有以下特点， 所述 V-PCRF还设置为： 接收到 所述 IP流迁移路由规则信息后， 执行如下一种或多种操作： 安装、 修改或删 除所述 IP流迁移路由规则信息中携带的 IP流迁移路由规则。
优选地， 上述系统还可具有以下特点， 所述 H-PCRF还设置为： 在 IP连 接接入网 （IP - CAN )会话建立过程中， 接收到所述 IP流迁移路由规则信息 后， 安装所述 IP流迁移路由规则信息中携带的 IP流迁移路由规则。
优选地，上述系统还可具有以下特点，所述 V-PCRF还设置为：在 IP-CAN 会话修改过程中， 上报 IP流迁移路由规则信息至所述 H-PCRF时， 上报路由 规则修改 ( ROUTING_RULE_CHANGE )事件触发至所述 H-PCRF。
优选地， 上述系统还可具有以下特点， 所述 H-PCRF还设置为： 在 IP - CAN会话修改过程中， 接收到所述 IP流迁移路由规则信息后， 执行如下一 种或多种操作： 安装、 修改或删除所述 IP 流迁移路由规则信息中携带的 IP 流迁移路由规则。
优选地， 上述系统还可具有以下特点， 所述 H-PCRF还设置为： 安装或 修改 IP流迁移路由规则后， 若所述 IP流迁移路由规则对应的业务数据流发 生了迁移， 则更新 PCC规则， 下发更新后的 PCC规则至所述 V-PCRF;
所述 V-PCRF还设置为： 下发所述更新后的 PCC规则至所述 PCEF。 优选地， 上述系统还可具有以下特点， 所述 V-PCRF还设置为： 根据所 述更新后的 PCC规则制定 QoS规则，根据所述 IP流迁移路由规则将所述 QoS 规则发送至指定的 BBERF。
优选地， 上述系统还可具有以下特点， 所述 V-PCRF还设置为： 从所述 业务数据流迁移前流经的 BBERF中删除所述业务数据流对应的 QoS规则。
优选地， 上述系统还可具有以下特点， 所述 V-PCRF还设置为： 如果所 述 H-PCRF 未订 阅 所 述 IP-CAN— CHANGE 事 件 触 发或 所 述 AN— GW— CHANGE事件触发， 在本地处理 IP流迁移。
优选地， 上述系统还可具有以下特点， 所述 V-PCRF本地处理 IP流迁移 包括：若所述 IP流迁移路由规则对应的业务数据流发生了迁移，所述 V-PCRF 根据所述 IP流迁移路由规则对应的 PCC规则制定 QoS规则， 并根据所述 IP 流迁移路由规则将所述 QoS规则发送至指定的 BBERF。
优选地， 上述系统还可具有以下特点， 所述 V-PCRF在本地处理 IP流迁 移还包括：从所述业务数据流迁移前流经的 BBERF中删除所述业务数据流对 应的 QoS规则。
本发明还提供一种拜访地策略和计费规则功能（ V-PCRF ) ,所述 V-PCRF 设置为： 接收到策略和计费执行功能（PCEF )上报的 IP 流迁移路由规则信 息时， 如果归属地策略和计费规则功能（H-PCRF )订阅了 IP-CAN类型修改 ( IP-CAN_CHANGE )事件触发或接入网关修改（ AN_GW_CHANGE )事件 触发， 上报所述 IP流迁移路由规则信息至所述 H-PCRF, 所述 IP流迁移路由 规则信息中包括如下一种或多种 IP流迁移规则： 安装、 修改或删除 IP流迁 移路由规则。 优选地，所述 V-PCRF还设置为：接收到所述 IP流迁移路由规则信息后， 执行如下一种或多种操作： 安装、 修改或删除所述 IP流迁移路由规则信息中 携带的 IP流迁移路由规则。
优选地， 所述 V-PCRF还设置为： 在 IP-CAN会话修改过程中， 上报 IP 流迁移路由规则信息至所述 H-PCRF 时， 上报路由规则修改 ( ROUTING RULE CHANGE )事件触发至所述 H-PCRF。
优选地， 所述 V-PCRF还设置为： 下发更新后的 PCC规则至所述 PCEF; 所述更新的 PCC规则是， 在所述 H-PCRF安装或修改 IP流迁移路由规 则后， 若所述 IP 流迁移路由规则对应的业务数据流发生了迁移， 由所述 H-PCRF更新 PCC规则得到； 并由所述 H-PCRF下发更新后的 PCC规则至所 述 V-PCRF。
优选地， 所述 V-PCRF还设置为： 根据所述更新后的 PCC规则制定 QoS 规则， 根据所述 IP流迁移路由规则将所述 QoS规则发送至指定的 BBERF。
优选地，所述 V-PCRF还设置为：从所述业务数据流迁移前流经的 BBERF 中删除所述业务数据流对应的 QoS规则。
优选地， 所述 V-PCRF 还设置为： 如果所述 H-PCRF 未订阅所述 IP-CAN— CHANGE事件触发或所述 AN— GW— CHANGE事件触发， 在本地处 理 IP流迁移。
优选地， 所述 V-PCRF本地处理 IP流迁移包括： 若所述 IP流迁移路由 规则对应的业务数据流发生了迁移， 所述 V-PCRF根据所述 IP流迁移路由规 则对应的 PCC规则制定 QoS规则，并根据所述 IP流迁移路由规则将所述 QoS 规则发送至指定的 BBERF。
通过本发明实施例可以实现如下有益效果：
1)H-PCRF不支持 IP流迁移时 ,如果 H-PCRF没有订阅 IP-CAN— CHANGE 或 AN— GW— CHANGE , 那么拜访网络可以本地执行 IP流迁移；
2)H-PCRF支持 IP流迁移时， 如果 H-PCRF没有订阅 IP-CAN— CHANGE 或 AN— GW— CHANGE, V-PCRF就不需要与 H-PCRF交互， 相比任何时候都 需要与 H-PCRF交互的方案， 可以节省 V-PCRF与 H-PCRF之间的信令开销。 附图概述
此处所说明的附图用来提供对本发明的进一步理解， 构成本申请的一部 分， 本发明的示意性实施例及其说明用于解释本发明， 并不构成对本发明的 不当限定。 在附图中：
图 1是根据相关技术的 EPS的系统架构示意图；
图 2是根据相关技术的 IP流迁移的接入示意图；
图 3是根据相关技术的非漫游场景下建立 IP流迁移连接的流程图一； 图 4是根据相关技术的非漫游场景下建立 IP流迁移连接的流程图二； 图 5是根据相关技术的非漫游场景下实现 IP流迁移的流程图；
图 6是现有技术中拜访地接入场景下的 PCC架构；
图 7是本发明的实施例一的流程图；
图 8是本发明的实施例二的流程图；
图 9是本发明的实施例三的流程图；
图 10本发明的实施例四的流程图。 本发明的较佳实施方式
下文中将结合附图对本发明的实施例进行详细说明。 需要说明的是， 在 不冲突的情况下， 本申请中的实施例及实施例中的特征可以相互任意组合。
对在本地疏导漫游场景下支持 IP流程迁移的策略计费控制提出本发明。 本发明提供一种漫游场景下支持 IP流迁移的策略计费控制方法， 包括： 拜访地策略和计费规则功能 （V-PCRF )接收到策略和计费执行功能 ( PCEF )上报的 IP流迁移路由规则信息时， 其中：
如果归属地策略和计费规则功能 （H-PCRF )订阅了 IP-CAN类型修改
( IP-CAN_CHANGE )事件触发或接入网关修改（ AN_GW_CHANGE )事件 触发， 所述 V-PCRF上报所述 IP流迁移路由规则信息至所述 H-PCRF;
如果所述 H-PCRF 未订阅所述 IP-CAN— CHANGE 事件触发或所述 AN— GW— CHANGE事件触发， 所述 V-PCRF在本地处理 IP流迁移；
所述 IP流迁移路由规则信息中包括如下一种或多种 IP流迁移规则： 安 装、 修改或删除 IP流迁移路由规则。
进一步地， 所述 V-PCRF接收到所述 IP流迁移路由规则信息后， 执行如 下一种或多种操作： 安装、 修改或删除所述 IP流迁移路由规则信息中携带的 IP流迁移路由规则。
进一步地， 上报 IP流迁移路由规则信息分两种情况：
1 )在 IP连接接入网 （ IP - CAN )会话建立过程中
所述 H-PCRF接收到所述 IP流迁移路由规则信息后，安装所述 IP流迁移 路由规则信息中携带的所述 IP流迁移路由规则。
2 )在 IP-CAN会话修改过程中
所述 V-PCRF上报 IP流迁移路由规则信息至所述 H-PCRF时， 还上报路 由规则修改 ( ROUTING_RULE_CHANGE )事件触发至所述 H-PCRF;
所述 H-PCRF接收到所述 IP流迁移路由规则信息后， 执行如下一种或多 种操作： 安装、 修改或删除所述 IP流迁移路由规则信息中携带的 IP流迁移 路由规则；
所述 H-PCRF安装、修改或删除 IP流迁移路由规则后，若所述 IP流迁移 路由规则对应的业务数据流发生了迁移，则更新 PCC规则，下发更新后的 PCC 规则至所述 V-PCRF;
所述 V-PCRF下发所述更新后的 PCC规则至所述 PCEF;
所述 V-PCRF根据所述更新后的 PCC规则制定 QoS规则， 根据所述 IP 流迁移路由规则将所述 QoS规则发送至指定的 BBERF;
所述 V-PCRF从所述业务数据流迁移前流经的 BBERF中删除所述业务数 据流对应的 QoS规则。 进一步地， 所述 V-PCRF在本地处理 IP流迁移包括：
若所述 IP流迁移路由规则对应的业务数据流发生了迁移， 所述 V-PCRF 根据所述 IP流迁移路由规则对应的 PCC规则制定 QoS规则， 并根据所述 IP 流迁移路由规则将所述 QoS规则发送至指定的 BBERF;
所述 V-PCRF从所述业务数据流迁移前流经的 BBERF中删除所述业务数 据流对应的 QoS规则。
实施例一
图 7是根据本发明实施例的实例一 UE通过非 3GPP接入网初始附着的流 程图， 其中， 通过可信任非 3GPP接入时， UE釆用 DSMIPv6协议。
步骤 701 , UE发现非 3GPP接入网并发起附着。 若非 3GPP接入网是可 信任的， 那么 UE在可信任非 3GPP接入网中执行接入认证和授权， UE执行 层 3附着并获得本地 IP地址 IP Addressl作为 CoA。若非 3GPP接入网是不可 信任的， 那么 UE将与 ePDG建立 IPSec隧道并进行隧道认证， 在隧道建立过 程中， ePDG为 UE分配 IP地址 IP Addressl并作为 CoA。
步骤 702, 位于可信任非 3GPP接入网或 ePDG中的 BBERF向 V-PCRF 发送网关控制会话建立消息， 请求建立网关控制会话， 该消息中携带用户标 识和 IP Addressl ;
步骤 703 , V-PCRF才艮据用户标识判断该用户为漫游用户， 并判断该用户 没有对应的 S9会话， V-PCRF向 H-PCRF发起建立 S9会话， 携带用户标识 和 IP Addressl ;
步骤 704, 若 H-PCRF没有用户相关的签约数据， H-PCRF需要和用户签 约数据库（Subscriber Profile Repository, 简称为 SPR ) 交互获取用户的签约 数据。 H-PCRF根据签约数据、 网络策略等制定策略。 由于此时没有 PDN标 识信息， 因此 H-PCRF制定的策略不会针对某个 PDN。 H-PCRF制定的策略 可能包括 QoS规则和事件触发器。 H-PCRF向 V-PCRF返回建立 S9会话的确 认消息， 可能携带 QoS规则和事件触发器；
步骤 705 , V-PCRF向 BBERF返回建立网关控制会话的确认消息， 可能 携带 QoS规则和事件触发器；
步骤 706, UE通过移动 IPv6的自启动过程找到在 3GPP接入时选择的 P-GW。 UE和 PDN之间建立安全联盟。 UE釆用 IKEv2发起建立安全联盟。 EAP在 IKEv2之上用于认证。 P-GW与 AAA交互以完成 EAP认证。 并且在 该过程中， P-GW返回 UE在 3GPP接入时 P-GW分配的 IP地址 IP Address2 , UE将 IP Address2作为 DSMIPv6绑定时的 HoA。 此时， P-GW执行的是 HA 的功能；
步骤 707, UE向 P-GW/HA发送 DSMIPv6绑定更新消息， 该绑定更新消 息中携带有 （HoA, CoA, BID, FID, Routing Filters )路由规则。 对应关系 中包括带默认的路由规则， 即路由过滤器为通配符的过滤器， HoA取值为 IP Address2 , CoA取值为 IP Address 1；
步骤 708, P-GW/HA接收到绑定更新消息之后， 根据所携带的 （HoA, CoA, BID, FID, Routing Filters )执行多注册流绑定。 位于 P-GW的 PCEF 向 V-PCRF发送 IP-CAN会话建立指示， PCEF将向 V-PCRF发送 IP流迁移 路由规则信息， 对于该流程， IP流迁移路由规则信息中包括安装 IP流迁移路 由规则， IP流迁移路由规则信息中包括默认路由规则。这些路由规则包括（IP Address 1 , Routing Filters )的对应关系（因为目前只有非 3GPP—个接入网）； 步骤 709, V-PCRF安装 IP流迁移路由规则信息中携带的 IP流迁移路由 规则。 V-PCRF根据 H-PCRF之前订阅的事件触发器判断是否需要向 H-PCRF 上报 IP流迁移路由规则信息。 如果 H-PCRF订阅了 IP-CAN类型修改事件触 发或者接入网关修改事件触发， V-PCRF需要向 H-PCRF上报 IP流迁移路由 规则信息； 否则 V-PCRF不向 H-PCRF上报 IP流迁移路由规则信息， 进行拜 访地的本地处理；
其中， IP-CAN类型修改用 IP-CAN— CHANGE表示， 接入网关修改用 AN— GW— CHANGE表示， 则若在步骤 704 下发的事件触发器中取值包括 IP-CAN— CHANGE 或 AN— GW— CHANGE ( 即 H-PCRF 订 阅 了 IP-CAN— CHANGE 或 AN— GW— CHANGE 事件触发） 时， V-PCRF 需要向 H-PCRF上报 IP流迁移路由规则信息； 否则 V-PCRF不向 H-PCRF上报 IP流 迁移路由规则信息， 进行拜访地的本地处理； 其中， 本实施例中， IP-CAN类 型包括 3GPP-EPS和 Non-3GPP-EPS ,接入网关包括可信任非 3GPP接入网关、 S-GW、 ePDG。
步骤 710, V-PCRF向 H-PCRF发送 S9会话修改消息， 并请求建立一个 S9 Subsession (子会话 ) ,在该 Subsession中携带 IP Address2以及对应的 PDN 标识等信息。若在步骤 709中判断需要上报 IP流迁移路由规则信息， V-PCRF 在 Subsession中包含 IP流迁移路由规则信息，发送给 H-PCRF,否则 V-PCRF 不将 IP流迁移路由规则信息发送给 H-PCRF;
步骤 711 , H-PCRF安装所述 IP流迁移路由规则信息中携带的 IP流迁移 路由规则。 H-PCRF根据用户签约数据和网络策略制定 PCC规则， 并通过所 述 Subsession下发给 V-PCRF;
步骤 712, V-PCRF向 PCEF返回确认消息， 携带 PCC规则；
步骤 713 , P-GW/HA向 UE返回绑定确认消息， 消息中携带 HoA, CoA, BID和 FID以确认 UE的多注册即流绑定成功；
步骤 714, V-PCRF根据步骤 711中下发的 PCC规则制定 QoS规则， 并 向可信任非 3GPP接入网或 ePDG中的 BBERF提供该 QoS规则；
步骤 715, BBERF安装 QoS规则， 发起执行非 3GPP接入网特定的流程 进行资源分配；
步骤 716, BBERF向 V-PCRF返回确认消息；
步骤 717, UE完成了多注册流绑定， UE和 P-GW/HA之间存在 DSMIPv6 隧道。
实施例二
图 8是本发明实施例中实现 UE先通过 3GPP接入网接入建立 PDN连接 后又通过非 3GPP接入建立同一个 PDN连接， 并同时使用两个接入使用该 PDN连接的流程。 网络中部署了动态 PCC。 图中通过可信任非 3GPP接入时， UE釆用 DSMIPv6协议。
步骤 801 , UE通过 3GPP接入网接入 EPC, 其中， S-GW和 P-GW之间 通过 GTP或 PMIPv6协议建立隧道， 且已有业务在该隧道上传输； 步骤 802, UE发现非 3GPP接入网并决定发起多接入。 若非 3GPP接入 网是可信任的， 那么 UE在可信任非 3GPP接入网中执行接入认证和授权， UE执行层 3附着并获得本地 IP地址 IP Addressl作为 CoA。 若非 3GPP接入 网是不可信任的，那么 UE将与 ePDG建立 IPSec隧道，在隧道建立过程， ePDG 为 UE分配 IP地址 IP Addressl并作为 CoA;
步骤 803 , 位于可信任非 3GPP接入网或 ePDG中的 BBERF向 V-PCRF 发送网关控制会话建立消息， 请求建立网关控制会话， 携带用户标识和 IP Addressl ;
步骤 804, V-PCRF根据用户标识将该网关控制会话与该用户之前建立的 S9会话进行关联， V-PCRF向 H-PCRF发送 S9会话修改， 携带 IP Addressl ; 步骤 805 , 由于此时没有 PDN标识信息， 因此 H-PCRF制定的策略不会 针对某个 PDN。 H-PCRF制定的策略可能包括 QoS规则。 H-PCRF向 V-PCRF 返回修改 S9会话的确认消息， 可能携带 QoS规则；
步骤 806 , V-PCRF向 BBERF返回确认消息；
步骤 807, UE通过移动 IPv6的自启动过程找到在 3GPP接入时选择的
P-GW。 UE和 PDN之间建立安全联盟。 UE釆用 IKEv2发起建立安全联盟。 EAP在 IKEv2之上用于认证。 P-GW与 AAA交互以完成 EAP认证。 并且在 该过程中， P-GW返回 UE在 3GPP接入时 P-GW分配的 IP地址 IP Address2, UE将该 IP地址作为 DSMIPv6绑定时的 HoA。 此时， P-GW执行的是 HA的 功能；
步骤 808, UE向 P-GW/HA发送 DSMIPv6绑定更新消息， 该绑定更新消 息中携带有 （HoA, CoA, BID, FID ) 。 （HoA, CoA, BID, FID )是一个 对应关系。 该消息通过 HoA取值 IP Address2 , CoA取值 IP Addressl , 表明 对应的 BID是通过非 3GPP接入的一个绑定， FID唯一标识的用户访问业务 的某个数据流绑定到通过非 3GPP接入的连接上。 该消息通过 HoA取值 IP Address2 , CoA取值 IP Address2 , 表明对应的 BID是通过 3GPP接入的一个 绑定， FID标识的业务数据流绑定到通过 3GPP接入的连接上。若是新增的一 个流绑定， 那么对应关系中还包括路由过滤器 Routing Filters (即 IP五元组） 用来标识一个业务数据流。通过该消息 FID和 Routing Filters建立了对应关系， 在以后对该业务数据流的修改时可以用 FID来表示。 在该消息中 UE上报默 认的路由规则， 即 Routing Filters是一个通配符过滤器。 UE也可以请求将经 过 3GPP接入中传输的业务数据流 SDF迁移到非 3GPP接入网中；
步骤 809, P-GW/HA接收到绑定更新消息之后，根据所携带的参数 HoA, CoA, BID, FID以及 Routing Filters执行多注册流绑定。 即 , P-GW同时保持 与 S-GW的 GTP/PMIPv6隧道和与 UE的 DSMIPv6隧道， 并将业务数据流绑 定到 3GPP接入或非 3GPP接入上。位于 P-GW的 PCEF向 V-PCRF发送 IP-CAN 会 话 修 改 指 示 ， PCEF 将 向 V-PCRF 发 送 事 件 触 发 器 ROUTING— RULE— CHANGE和 IP流迁移路由规则信息 （对于该流程中的 IP 流迁移路由规则信息包括安装和 /或修改 IP流迁移路由规则， IP流迁移路由 规则即业务数据流与接入的对应关系， 通过 Routing Filters与 Routing Address 对应关系标识， Routing Address取值为 IP Address 1时， 表示为通过非 3GPP 接入， Routing Address取值为 IP Address2时， 表示为通过 3GPP接入） 。 该 消息包括默认的 IP流迁移路由规则， 即 Routing Filters是通配符。若 UE将某 个业务数据流从 3GPP接入中迁移到非 3GPP接入中， 则 PCEF将向 V-PCRF 提供该业务数据流对应的 IP流迁移路由规则， 以通知 V-PCRF该业务数据流 的路由发生的迁移。 该路由规则中， Routing Filters为该业务数据流的 IP五元 组 , Routing Address取值为 IP Address 1；
步骤 810, V-PCRF安装或修改 IP流迁移路由规则信息中携带的 IP流迁 移路由规则。 V-PCRF根据 H-PCRF之前订阅的事件触发器判断是否需要向 H-PCRF 上报 IP 流迁移路由规则信息。 若订阅的事件触发器中取值包括 IP-CAN— CHANGE 或 AN— GW— CHANGE ( 即 H-PCRF 订 阅 了 IP-CAN— CHANGE 或 AN— GW— CHANGE 事件触发） 时， V-PCRF 需要向 H-PCRF上报 IP流迁移路由规则信息和 ROUTING— RULE— CHANGE; 否则 V-PCRF 不 向 H-PCRF 上 4艮 IP 流 迁 移 路 由 规 则 信 息 和 ROUTING— RULE— CHANGE , 进行拜访地的本地处理；
步骤 811 , 若步骤 810中判断 V-PCRF需要向 H-PCRF上报 IP流迁移路 由规则信息和 ROUTING— RULE— CHANGE, 则 V-PCRF在该 IP-CAN会话对 应的 Subsession中包含 IP迁移路由规则信息和 ROUTING— RULE— CHANGE, 发送给 H-PCRF (即向 H-PCRF上报 ROUTING— RULE— CHANGE事件触发和 安装和 /或修改的 IP流迁移路由规则） ； 否则 V-PCRF不将 IP流迁移路由规 则信息和 ROUTING— RULE— CHANGE包含在 Subsession中发送给 H-PCRF; 步骤 812 , 若 V-PCRF 向 H-PCRF 上报了 IP 流迁移路由规则信息和 ROUTING— RULE— CHANGE, 那么 H-PCRF安装和 /或修改 IP流迁移路由规 则信息中携带的 IP流迁移路由规则。 若 IP流迁移路由规则对应的业务数据 流发生了迁移， 则 H-PCRF更新对应的 PCC规则并返回给 V-PCRF;
步骤 813 , V-PCRF向 PCEF返回确认消息 , 若 V-PCRF向 H-PCRF上报 了 IP流迁移路由规则信息和 ROUTING— RULE— CHANGE,则 V-PCRF向 PCEF 返回更新 PCC规则；
步骤 814, P-GW/HA向 UE返回绑定确认消息， 消息中携带 HoA, CoA, BID和 FID以确认 UE的多注册即流绑定成功或多注册即流绑定以及流迁移 成功；
步骤 815 , 若 V-PCRF 不向 H-PCRF 上^艮 IP 流迁移路由规则信息和 ROUTING— RULE— CHANGE, 则 V-PCRF进行本地处理， 若 IP流迁移路由规 则对应的业务数据流发生了迁移， 则 V-PCRF即根据 IP流迁移路由规则对应 的 PCC规则 （这些 PCC规则是在 3GPP接入时， H-PCRF下发的 )制定 QoS 规则 。 若 V-PCRF 向 H-PCRF 上报 IP 流迁移路由规则信息和 ROUTING— RULE— CHANGE,则 V-PCRF根据 H-PCRF新下发的 PCC规则制 定 QoS规则。 V-PCRF向可信任非 3GPP接入网或 ePDG中的 BBERF提供该 QoS规则；
步骤 816, BBERF安装 QoS规则， 发起执行非 3GPP接入网特定的流程 进行资源分配或修改；
步骤 817, BBERF向 V-PCRF返回确认消息；
步骤 818,若 UE将某个业务数据流从 3GPP接入迁移到了非 3GPP接入， 并且若 S-GW和 P-GW之间建立的是 PMIPv6隧道， 那么 V-PCRF将删除该 业务数据流对应的 QoS规则。 V-PCRF通过 UE在 3GPP接入时建立的网关控 制会话向 S-GW中的 BBERF提供需要删除的 QoS规则； 步骤 819, BBERF删除 QoS规则， 执行 3GPP的承载修改或释放流程， 释放迁移走的业务数据流的资源；
步骤 820 , BBERF向 V-PCRF返回确认消息；
若 S-GW和 P-GW之间建立的是 GTP隧道，那么 P-GW将在步骤 813后， 发起 3GPP的承载修改或释放流程， 释放迁移走的业务数据流的资源。 步骤 818-820将不执行。
步骤 821 , UE完成了多注册流绑定以及可能的流迁移， UE和 P-GW/HA 之间存在 DSMIPv6隧道， S-GW与 P-GW之间存在 GTP/PMIPv6隧道。 UE 或网络可以根据策略决定业务数据通过哪个接入进行传输。
实施例三
图 9是根据本发明实现 UE先通过非 3GPP接入网接入建立 PDN连接后 又通过 3GPP接入建立同一个 PDN连接， 并同时使用两个接入使用该 PDN 连接的流程。 网络中部署了动态 PCC。 图中通过可信任非 3GPP接入时， UE 釆用 DSMIPv6协议。
步骤 901 , UE通过非 3GPP接入网釆用 DSMIPv6协议接入 EPC, UE与 P-GW/HA之间建立 DSMIPv6隧道，并已有业务在该隧道上传输，其中非 3GPP 接入网为 UE分配的地址为 IP Address 1作为 CoA, P-GW为 UE分配的 IP地 址为 IP Address2作为 HoA;
步骤 902, UE发现 3GPP接入网并决定发起多接入。 UE通过 3GPP的附 着流程建立到同一个 PDN的 PDN连接，在建立过程中， P-GW为 UE分配 IP 地址为 IP Address2 , 以保证通过不同接入建立了同一个 PDN连接；
步骤 903 , UE向 P-GW/HA发送 DSMIPv6绑定更新消息， 该绑定更新消 息中携带有 （HoA, CoA, BID, FID ) 。 （HoA, CoA, BID, FID )是一个 对应关系。 该消息通过 HoA取值 IP Address2 , CoA取值 IP Address 1 , 表明 对应的 BID是通过非 3GPP接入的一个绑定， FID唯一标识的用户访问业务 的某个数据流绑定到通过非 3GPP接入的连接上。 该消息通过 HoA取值 IP Address2 , CoA取值 IP Address2 , 表明对应的 BID是通过 3GPP接入的一个 绑定， FID标识的业务数据流绑定到通过 3GPP接入的连接上。若是新增的一 个流绑定，那么对应关系中还包括 Routing Filters。通过该消息 FID和 Routing Filters建立了对应关系， 在以后对该业务数据流的修改时可以用 FID来表示。 在该消息中 UE可能上报默认的路由规则， 即 Routing Filters是一个通配符过 滤器。 UE也可以请求将经过非 3GPP接入中传输的业务数据流 SDF迁移到 3GPP接人网中；
步骤 904, P-GW/HA接收到绑定更新消息之后，根据所携带的参数 HoA, CoA, BID, FID以及 Routing Filters执行多注册流绑定。 即， P-GW同时保持 与 S-GW的 GTP/PMIPv6隧道和与 UE的 DSMIPv6隧道， 并将业务数据流绑 定到 3GPP接入或非 3GPP接入上。位于 P-GW的 PCEF向 V-PCRF发送 IP-CAN 会 话 修 改 指 示 ， PCEF 将 向 V-PCRF 发 送 事 件 触 发 器 ROUTING— RULE— CHANGE和 IP流迁移路由规则信息 （对于该流程中， IP 流迁移路由规则信息为安装和 /或修改 IP流迁移路由规则， IP流迁移路由规 则即业务数据流与接入的对应关系， 通过 Routing Filters与 Routing Address 对应关系标识， Routing Address取值为 IP Addressl时， 表示为通过非 3GPP 接入， Routing Address取值为 IP Address2时， 表示为通过 3GPP接入） 。 该 消息可能包括默认的 IP流迁移路由规则， 即 Routing Filters是通配符。 若 UE 将某个业务数据流从非 3GPP接入中迁移到 3GPP接入中， 则 PCEF将向 V-PCRF提供该业务数据流对应的 IP流迁移路由规则 , 以通知 V-PCRF该业 务数据流的路由发生的迁移。 该路由规则中， Routing Filters为该业务数据流 的 IP五元组， Routing Address取值为 IP Address2;
步骤 905 , V-PCRF安装和 /或修改 IP 流迁移路由规则。 V-PCRF根据 H-PCRF之前订阅的事件触发器判断是否需要向 H-PCRF上报 IP流迁移路由 规则信息。 若订阅的事件触发器中取值包括 IP-CAN— CHANGE 或 AN— GW— CHANGE ( 即 H-PCRF 订 阅 了 IP-CAN— CHANGE 或 AN— GW— CHANGE事件触发 )时， V-PCRF需要向 H-PCRF上报 IP流迁移路 由规则信息和 ROUTING— RULE— CHANGE; 否则 V-PCRF不向 H-PCRF上报 IP流迁移路由规则信息和 ROUTING— RULE— CHANGE,进行拜访地的本地处 理； 步骤 906, 若步骤 905中判断 V-PCRF需要向 H-PCRF上报 IP流迁移路 由规则信息和 ROUTING— RULE— CHANGE, 则 V-PCRF在该 IP-CAN会话对 应 的 Subsession 中 包 含 IP 流 迁 移 路 由 规 则 信 息 和 ROUTING— RULE— CHANGE , 发送给 H-PCRF ( 即向 H-PCRF 上报 ROUTING— RULE— CHANGE 事件触发和安装和 /或修改的 IP 流迁移路由规 则）；否则 V-PCRF不将 IP流迁移路由规则信息和 ROUTING— RULE— CHANGE 包含在 Subsession中发送给 H-PCRF;
步骤 907 , 若 V-PCRF 向 H-PCRF 上报了 IP 流路由规则信息和 ROUTING— RULE— CHANGE, 那么 H-PCRF安装和 /或修改 IP流迁移路由规 则。 若 IP流迁移路由规则对应的业务数据流发生了迁移， 则 H-PCRF根据 IP 流迁移路由规则更新对应的 PCC规则并返回给 V-PCRF;
步骤 908, V-PCRF向 PCEF返回确认消息 , 若 V-PCRF向 H-PCRF上报 了 IP流迁移路由规则信息和 ROUTING— RULE— CHANGE,则 V-PCRF向 PCEF 返回更新 PCC规则；
步骤 909 , P-GW/HA向 UE返回绑定确认消息， 消息中携带 HoA, CoA,
BID和 FID以确认 UE的多注册即流绑定成功或多注册即流绑定以及流迁移 成功；
步骤 910 , 若 V-PCRF 不向 H-PCRF 上报 IP 流迁移路由规则信息和 ROUTING— RULE— CHANGE, 则 V-PCRF进行本地处理， 若 IP流迁移路由规 则对应的业务数据流发生了迁移， 则 V-PCRF即根据 IP流迁移路由规则对应 的 PCC规则 （这些 PCC规则是在非 3GPP接入时， H-PCRF下发的 )制定 QoS 规则； 若 V-PCRF 向 H-PCRF 上报 IP 流迁移路由规则信息和 ROUTING— RULE— CHANGE,则 V-PCRF根据 H-PCRF新下发的 PCC规则制 定 QoS规则。 V-PCRF向 S-GW中的 BBERF提供该 QoS规则；
步骤 911 , BBERF安装 QoS规则， S-GW发起执行 3GPP的承载修改或 建立流程进行资源分配或修改；
步骤 912, BBERF向 V-PCRF返回确认消息；
若 S-GW和 P-GW之间建立的是 GTP隧道，那么 P-GW将在步骤 908后， 发起 3GPP的承载修改或建立流程， 分配迁移入的业务数据流的资源。 步骤 910-912将不执行。
步骤 913 , 若某个业务数据流从非 3GPP接入迁移到了 3GPP接入， 那么 V-PCRF将删除在非 3GPP接入网或 ePDG中该业务数据流对应的 QoS规则。 V-PCRF通过 UE在非 3GPP接入时建立的网关控制会话向非 3GPP接入网或 ePDG中的 BBERF提供需要删除的 QoS规则；
步骤 914, BBERF删除 QoS规则， 并发起执行非 3GPP的特定的资源修 改或释放流程；
步骤 915, BBERF向 V-PCRF返回确认消息；
步骤 916, UE完成了多注册流绑定以及流迁移， UE和 P-GW/HA之间存 在 DSMIPv6隧道， S-GW与 P-GW之间存在 GTP/PMIPv6隧道。 UE或网络 可以根据策略决定业务数据通过哪个接入进行传输。
实施例四
图 10是根据本发明实现 UE通过图 8或图 9的流程实现多注册流绑定后， 在两个接入网之间进行数据流迁移、 新增业务数据流或删除业务数据流的流 程图。 网络中部署了动态 PCC。
步骤 1001 , UE通过图 8或图 9的流程同时连接到 3GPP接入和非 3GPP 接入， 并进行了多注册流绑定；
步骤 1002 , UE向 P-GW/HA发送 DSMIPv6绑定更新消息， 该绑定更新 消息中携带有（HoA, BID, FID )„在该消息中， UE可以请求将经过非 3GPP 接入中传输的业务数据流 SDF (用 FID表示)迁移到 3GPP接入网中 （用 BID 表示）或反之 (即修改路由规则 )。 UE也可以请求删除路由规则或增加一个 的路由规则。 若是新增路由规则， 则消息中还包括 Routing Filters;
步骤 1003 , P-GW/HA接收到绑定更新消息之后，根据所携带的参数 HoA,
BID和 FID执行流绑定更新，包括流迁移，新增或删除等。位于 P-GW的 PCEF 向 V-PCRF发送 IP-CAN会话修改指示， PCEF将向 V-PCRF发送事件触发器 ROUTING— RULE— CHANGE和 IP流迁移路由规则信息， 包括安装、 修改和 删除 IP流迁移路由规则。 路由规则中用 IP Addressl表示当前传输的接入网 为非 3GPP,用 IP Address2表示当前传输的接入网为 3GPP。用 Routing Filters 来表示业务数据流；
步骤 1004, V-PCRF安装、 修改和 /或删除 IP流迁移路由规则。 V-PCRF 根据 H-PCRF之前订阅的事件触发器判断是否需要向 H-PCRF上报 IP流迁移 路由规则信息。 若订阅的事件触发器中取值包括 IP-CAN— CHANGE 或 AN— GW— CHANGE ( 即 H-PCRF 订 阅 了 IP-CAN— CHANGE 或 AN— GW— CHANGE事件触发 )时， V-PCRF需要向 H-PCRF上报 IP流迁移路 由规则信息和 ROUTING— RULE— CHANGE; 否则 V-PCRF不向 H-PCRF上报 IP流迁移路由规则信息和 ROUTING— RULE— CHANGE,进行拜访地的本地处 理；
步骤 1005,若步骤 S1004中判断 V-PCRF需要向 H-PCRF上^艮^流迁移 路由规则信息和 ROUTING— RULE— CHANGE, 则 V-PCRF在该 IP-CAN会话 对 应 的 Subsession 中 包 含 IP 流 迁 移 路 由 规 则 信 息 和 ROUTING— RULE— CHANGE , 发送给 H-PCRF ( 即向 H-PCRF 上报 ROUTING— RULE— CHANGE事件触发和安装、 修改和 /或删除 IP流迁移路由 规则 ） ； 否 则 V-PCRF 不 将 IP 流 迁移路 由 规则 信 息 和 ROUTING— RULE— CHANGE包含在 Subsession中发送给 H-PCRF;
步骤 1006, 若 V-PCRF 向 H-PCRF上报了 IP 流迁移路由规则信息和 ROUTING— RULE— CHANGE, 那么 H-PCRF安装、 修改和 /或删除 IP流迁移 路由规则。 若 IP流迁移路由规则对应的业务数据流发生了迁移， 则 H-PCRF 更新对应的 PCC规则并返回给 V-PCRF;
步骤 1007, V-PCRF向 PCEF返回确认消息， 若 V-PCRF向 H-PCRF上 报了 IP流迁移路由规则信息和 ROUTING— RULE— CHANGE, 则 V-PCRF向 PCEF返回的确认消息中包括更新 PCC规则；
步骤 1008, P-GW/HA向 UE返回绑定确认消息， 消息中携带 HoA, BID 和 FID以确认 UE路由规则更新成功， 即流迁移成功；
步骤 1009,若 S-GW和 P-GW之间建立的是 PMIPv6隧道，那么 V-PCRF 将根据 PCEF上报的路由规则在 S-GW中的 BBERF上安装或删除 QoS规则。 如果是从非 3GPP迁移入 3GPP, 则安装 QoS规则， 反之， 则删除 QoS规则。 若 V-PCRF不向 H-PCRF上报路由规则和 ROUTING— RULE— CHANGE, 则 V-PCRF进行本地处理，若 IP流迁移路由规则对应的业务数据流发生了迁移， 并且需要安装 QoS规则，则根据 IP流迁移路由规则对应的 PCC规则制定 QoS 规则。此处 PCC规则是 V-PCRF本地保存的 PCC规则，该 PCC规则是 H-PCRF 以前下发的， 可能是在非 3GPP接入时， H-PCRF下发的， 或者， 3GPP接入 时， H-PCRF下发的， 或者， 在其他过程中 H-PCRF下发的。 若 V-PCRF向 H-PCRF上报了 IP流迁移路由规则信息和 ROUTING— RULE— CHANGE, 则 V-PCRF根据 H-PCRF新下发的 PCC规则制定 QoS规则， V-PCRF向 S-GW 中的 BBERF提供该 QoS规则。若需要删除 QoS规则，则 V-PCRF请求 BBERF 删除从 3GPP接入中迁移走的业务数据流对应的 QoS规则；
步骤 1010, BBERF安装或删除 QoS规则， S-GW发起执行 3GPP的承载 建立、 修改或删除流程进行资源分配、 修改或释放；
步骤 1011 , BBERF向 V-PCRF返回确认消息；
若 S-GW和 P-GW之间建立的是 GTP隧道， 那么 P-GW将在步骤 1007 后， 发起 3GPP的承载建立、 修改或删除流程。 步骤 1009-1011将不执行。
步骤 1012, V-PCRF将根据 PCEF上报的 IP流迁移路由规则信息在可信 任非 3GPP接入网或 ePDG中的 BBERF上安装或删除 QoS规则。 如果是从 3GPP迁移入非 3GPP,则安装 QoS规则，反之，则删除 QoS规则。若 V-PCRF 不向 H-PCRF上报 IP流迁移路由规则信息和 ROUTING— RULE— CHANGE, 则 V-PCRF进行本地处理， 若 IP流迁移路由规则对应的业务数据流发生了迁 移， 并且需要安装 QoS规则， 则根据 IP流迁移路由规则对应的 PCC规则制 定 QoS规则。 此处 PCC规则是 V-PCRF本地保存的 PCC规则， 该 PCC规则 是 H-PCRF以前下发的， 可能是在非 3GPP接入时， H-PCRF下发的， 或者， 3GPP接入时， H-PCRF 下发的， 或者， 在其他过程中 H-PCRF 下发的。 若 V-PCRF 向 H-PCRF 上 4艮 了 IP 流 迁 移 路 由 规 则 信 息 和 ROUTING— RULE— CHANGE,则 V-PCRF根据 H-PCRF新下发的 PCC规则制 定 QoS规则， V-PCRF向可信任非 3GPP接入网或 ePDG中的 BBERF提供该 QoS规则。 若需要删除 QoS规则， 则 V-PCRF请求 BBERF删除从非 3GPP 接入中迁移走的业务数据流对应的 QoS规则；
步骤 1013 , BBERF安装或删除 QoS规则，并发起执行非 3GPP的特定的 资源分配、 修改或释放流程；
步骤 1014, BBERF向 V-PCRF返回确认消息。
本发明还提供一种漫游场景下支持 IP流迁移的策略计费控制系统，包括： 拜访地策略和计费规则功能 （V-PCRF ) 和归属地策略和计费规则功能 ( H-PCRF ) , 其中：
所述 V-PCRF用于： 接收到策略和计费执行功能（PCEF )上报的 IP流 迁移路由规则信息时， 如果所述 H-PCRF 订阅了 IP-CAN 类型修改 ( IP-CAN_CHANGE )事件触发或接入网关修改（ AN_GW_CHANGE )事件 触发， 上报所述 IP流迁移路由规则信息至所述 H-PCRF, 所述 IP流迁移路由 规则信息中包括如下一种或多种 IP流迁移规则： 安装、 修改或删除 IP流迁 移路由规则。
其中， 所述 V-PCRF, 还用于接收到所述 IP流迁移路由规则信息后， 执 行如下一种或多种操作： 安装、 修改或删除所述 IP流迁移路由规则信息中携 带的 IP流迁移路由规则。
其中， 所述 H-PCRF, 还用于在 IP连接接入网 ( IP - CAN )会话建立过 程中， 接收到所述 IP流迁移路由规则信息后， 安装所述 IP流迁移路由规则 信息中携带的 IP流迁移路由规则。
其中， 所述 V-PCRF还用于： 在 IP-CAN会话修改过程中， 上报 IP流迁 移路 由 规则 信 息 至 所述 H-PCRF 时 ， 上报路 由 规则 修改 ( ROUTING RULE CHANGE )事件触发至所述 H-PCRF。
其中， 所述 H-PCRF还用于： 在 IP - CAN会话修改过程中， 接收到所述 IP流迁移路由规则信息后， 执行如下一种或多种操作： 安装、 修改或删除所 述 IP流迁移路由规则信息中携带的 IP流迁移路由规则。
其中， 所述 H-PCRF还用于， 安装、 修改或删除 IP流迁移路由规则后， 若所述 IP流迁移路由规则对应的业务数据流发生了迁移， 则更新 PCC规则， 下发更新后的 PCC规则至所述 V-PCRF;
所述 V-PCRF还用于， 下发所述更新后的 PCC规则至所述 PCEF。
其中，所述 V-PCRF还用于，根据所述更新后的 PCC规则制定 QoS规则， 根据所述 IP流迁移路由规则将所述 QoS规则发送至指定的 BBERF。
其中， 所述 V-PCRF还用于， 从所述业务数据流迁移前流经的 BBERF 中删除所述业务数据流对应的 QoS规则。
其中， 所述 V-PCRF 还用于： 如果所述 H-PCRF 未订阅所述 IP-CAN— CHANGE事件触发或所述 AN— GW— CHANGE事件触发， 在本地处 理 IP流迁移。
其中， 所述 V-PCRF本地处理 IP流迁移包括： 若所述 IP流迁移路由规 则对应的业务数据流发生了迁移， 所述 V-PCRF根据所述 IP流迁移路由规则 对应的 PCC规则制定 QoS规则， 并根据所述 IP流迁移路由规则将所述 QoS 规则发送至指定的 BBERF。
其中， 所述 V-PCRF在本地处理 IP流迁移还包括： 从所述业务数据流迁 移前流经的 BBERF中删除所述业务数据流对应的 QoS规则。
显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布 在多个计算装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程 序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 或 者将它们分别制作成各个集成电路模块， 或者将它们中的多个模块或步骤制 作成单个集成电路模块来实现。 这样， 本发明不限制于任何特定的硬件和软 件结合。
以上所述仅为本发明的优选实施例而已， 并不用于限制本发明， 对于本 领域的技术人员来说， 本发明可以有各种更改和变化。 凡在本发明的精神和 原则之内， 所作的任何修改、 等同替换、 改进等， 均应包含在本发明的保护 范围之内。 工业实用性
通过本发明实施例可以实现如下有益效果：
1) H-PCRF不支持 IP流迁移时 ,如果 H-PCRF没有订阅 IP-CAN— CHANGE 或 AN— GW— CHANGE , 那么拜访网络可以本地执行 IP流迁移；
2) H-PCRF支持 IP流迁移时， 如果 H-PCRF没有订阅 IP-CAN— CHANGE 或 AN— GW— CHANGE, V-PCRF就不需要与 H-PCRF交互， 相比任何时候都 需要与 H-PCRF交互的方案， 可以节省 V-PCRF与 H-PCRF之间的信令开销。

Claims

权 利 要 求 书
1、 一种漫游场景下支持 IP流迁移的策略计费控制方法， 包括： 拜访地策略和计费规则功能 （V-PCRF )接收到策略和计费执行功能 ( PCEF )上报的 IP 流迁移路由规则信息时， 如果归属地策略和计费规则功 能 ( H-PCRF )订阅了 IP-CAN类型修改（ IP-CAN_CHANGE )事件触发或接 入网关修改（ AN— GW— CHANGE )事件触发， 所述 V-PCRF上报所述 IP流迁 移路由规则信息至所述 H-PCRF, 所述 IP流迁移路由规则信息中包括如下一 种或多种 IP流迁移规则： 安装、 修改或删除 IP流迁移路由规则。
2、 如权利要求 1所述的方法， 其中，
所述 V-PCRF接收到所述 IP流迁移路由规则信息后， 执行如下一种或多 种操作： 安装、 修改或删除所述 IP流迁移路由规则信息中携带的 IP流迁移 路由规则。
3、 如权利要求 1所述的方法， 其中， 所述方法还包括：
在 IP连接接入网 （ IP - CAN )会话建立过程中， 所述 H-PCRF接收到所 述 IP流迁移路由规则信息后， 安装所述 IP流迁移路由规则信息中携带的所 述 IP流迁移路由规则。
4、 如权利要求 1所述的方法， 其中，
在 IP-CAN会话修改过程中， 所述 V-PCRF上报 IP流迁移路由规则信息 至所述 H-PCRF时， 还上报路由规则修改 （ ROUTING_RULE_CHANGE )事 件触发至所述 H-PCRF。
5、 如权利要求 4所述的方法， 其中， 所述方法还包括：
在 IP - CAN会话修改过程中， 所述 H-PCRF接收到所述 IP流迁移路由 规则信息后， 执行如下一种或多种操作： 安装、 修改或删除所述 IP流迁移路 由规则信息中携带的 IP流迁移路由规则。
6、 如权利要求 5所述的方法， 其中， 所述方法还包括：
所述 H-PCRF安装、修改或删除 IP流迁移路由规则后，若所述 IP流迁移 路由规则对应的业务数据流发生了迁移， 则更新策略和计费控制 （PCC )规 则， 下发更新后的 PCC规则至所述 V-PCRF;
所述 V-PCRF下发所述更新后的 PCC规则至所述 PCEF。
7、 如权利要求 6所述的方法， 其中， 所述方法还包括： 根据所述 IP流迁移路由规则将所述 QoS规则发送至指定的承载绑定及事件报 告功能（BBERF ) 。
8、 如权利要求 6或 7所述的方法， 其中， 所述方法还包括：
所述 V-PCRF从所述业务数据流迁移前流经的 BBERF中删除所述业务数 据流对应的 QoS规则。
9、如权利要求 1所述的方法，其中，所述方法还包括，如果所述 H-PCRF 未订阅所述 IP-CAN— CHANGE事件触发或所述 AN— GW— CHANGE事件触发， 所述 V-PCRF在本地处理 IP流迁移。
10、 如权利要求 9所述的方法， 其中， 所述 V-PCRF在本地处理 IP流迁 移包括：
若所述 IP流迁移路由规则对应的业务数据流发生了迁移， 所述 V-PCRF 根据所述 IP流迁移路由规则对应的 PCC规则制定 QoS规则， 并根据所述 IP 流迁移路由规则将所述 QoS规则发送至指定的 BBERF。
11、 如权利要求 9或 10所述的方法， 其中， 所述 V-PCRF在本地处理 IP 流迁移还包括：
所述 V-PCRF从所述业务数据流迁移前流经的 BBERF中删除所述业务数 据流对应的 QoS规则。
12、 一种漫游场景下支持 IP流迁移的策略计费控制系统， 包括： 拜访地 策略和计费规则功能（V-PCRF )和归属地策略和计费规则功能（H-PCRF ) , 其中：
所述 V-PCRF设置为： 接收到策略和计费执行功能（PCEF )上报的 IP 流迁移路由规则信息时， 如果所述 H-PCRF 订阅了 IP-CAN 类型修改 ( IP-CAN_CHANGE )事件触发或接入网关修改（ AN_GW_CHANGE )事件 触发， 上报所述 IP流迁移路由规则信息至所述 H-PCRF, 所述 IP流迁移路由 规则信息中包括如下一种或多种 IP流迁移规则： 安装、 修改或删除 IP流迁 移路由规则。
13、 如权利要求 12所述的系统， 其中，
所述 V-PCRF还设置为： 接收到所述 IP流迁移路由规则信息后， 执行如 下一种或多种操作： 安装、 修改或删除所述 IP流迁移路由规则信息中携带的 IP流迁移路由规则。
14、 如权利要求 12所述的系统， 其中，
所述 H-PCRF设置为： 在 IP连接接入网 （ IP - CAN )会话建立过程中， 接收到所述 IP流迁移路由规则信息后， 安装所述 IP流迁移路由规则信息中 携带的 IP流迁移路由规则。
15、 如权利要求 12所述的系统， 其中，
所述 V-PCRF还设置为： 在 IP-CAN会话修改过程中， 上报 IP流迁移路 由 规 则 信 息 至 所 述 H-PCRF 时 ， 上 报 路 由 规 则 修 改 ( ROUTING RULE CHANGE )事件触发至所述 H-PCRF。
16、 如权利要求 15所述的系统， 其中，
所述 H-PCRF还设置为： 在 IP - CAN会话修改过程中， 接收到所述 IP 流迁移路由规则信息后， 执行如下一种或多种操作： 安装、 修改或删除所述 IP流迁移路由规则信息中携带的 IP流迁移路由规则。
17、 如权利要求 16所述的系统， 其中，
所述 H-PCRF还设置为： 安装或修改 IP流迁移路由规则后， 若所述 IP 流迁移路由规则对应的业务数据流发生了迁移， 则更新 PCC规则， 下发更新 后的 PCC规则至所述 V-PCRF;
所述 V-PCRF还设置为： 下发所述更新后的 PCC规则至所述 PCEF。
18、 如权利要求 17所述的系统， 其中，
所述 V-PCRF还设置为：根据所述更新后的 PCC规则制定 QoS规则，根 据所述 IP流迁移路由规则将所述 QoS规则发送至指定的 BBERF。
19、 如权利要求 17或 18所述的系统， 其中， 所述 V-PCRF还设置为：从所述业务数据流迁移前流经的 BBERF中删除 所述业务数据流对应的 QoS规则。
20、 如权利要求 12所述的系统， 其中， 所述 V-PCRF还设置为： 如果所 述 H-PCRF 未订 阅 所 述 IP-CAN— CHANGE 事 件 触 发或 所 述 AN— GW— CHANGE事件触发， 在本地处理 IP流迁移。
21、 如权利要求 20所述的系统， 其中，
所述 V-PCRF本地处理 IP流迁移包括： 若所述 IP流迁移路由规则对应 的业务数据流发生了迁移， 所述 V-PCRF根据所述 IP流迁移路由规则对应的 PCC规则制定 QoS规则， 并根据所述 IP流迁移路由规则将所述 QoS规则发 送至指定的 BBERF。
22、 如权利要求 20或 21所述的系统， 其中， 所述 V-PCRF在本地处理 IP流迁移还包括： 从所述业务数据流迁移前流经的 BBERF中删除所述业务 数据流对应的 QoS规则。
23、一种拜访地策略和计费规则功能（ V-PCRF ) , 所述 V-PCRF设置为： 接收到策略和计费执行功能（PCEF )上报的 IP 流迁移路由规则信息时， 如 果归属地策略和计费规则功能 （H-PCRF ) 订阅了 IP-CAN 类型修改 ( IP-CAN_CHANGE )事件触发或接入网关修改（ AN_GW_CHANGE )事件 触发， 上报所述 IP流迁移路由规则信息至所述 H-PCRF, 所述 IP流迁移路由 规则信息中包括如下一种或多种 IP流迁移规则： 安装、 修改或删除 IP流迁 移路由规则。
24、 如权利要求 23所述的 V-PCRF, 其中， 所述 V-PCRF还设置为： 接 收到所述 IP流迁移路由规则信息后， 执行如下一种或多种操作： 安装、 修改 或删除所述 IP流迁移路由规则信息中携带的 IP流迁移路由规则。
25、 如权利要求 23所述的 V-PCRF, 其中， 所述 V-PCRF还设置为： 在 IP-CAN会话修改过程中， 上报 IP流迁移路由规则信息至所述 H-PCRF时， 上报路由规则修改 ( ROUTING— RULE— CHANGE )事件触发至所述 H-PCRF。
26、 如权利要求 23所述的 V-PCRF, 其中， 所述 V-PCRF还设置为： 下 发更新后的 PCC规则至所述 PCEF; 所述更新的 PCC规则是， 在所述 H-PCRF安装或修改 IP流迁移路由规 则后， 若所述 IP 流迁移路由规则对应的业务数据流发生了迁移， 由所述 H-PCRF更新 PCC规则得到； 并由所述 H-PCRF下发更新后的 PCC规则至所 述 V-PCRF。
27、 如权利要求 26所述的 V-PCRF, 其中， 所述 V-PCRF还设置为： 根 据所述更新后的 PCC规则制定 QoS规则， 根据所述 IP流迁移路由规则将所 述 QoS规则发送至指定的 BBERF。
28、 如权利要求 27所述的 V-PCRF, 其中， 所述 V-PCRF还设置为： 从 所述业务数据流迁移前流经的 BBERF中删除所述业务数据流对应的 QoS规 则。
29、 如权利要求 23所述的 V-PCRF, 其中， 所述 V-PCRF还设置为： 如 果所述 H-PCRF 未订阅所述 IP-CAN— CHANGE 事件触发或所述 AN— GW— CHANGE事件触发， 在本地处理 IP流迁移。
30、 如权利要求 29所述的 V-PCRF, 其中， 所述 V-PCRF本地处理 IP流 迁移包括： 若所述 IP 流迁移路由规则对应的业务数据流发生了迁移， 所述
V-PCRF根据所述 IP流迁移路由规则对应的 PCC规则制定 QoS规则， 并根 据所述 IP流迁移路由规则将所述 QoS规则发送至指定的 BBERF。
PCT/CN2011/080730 2010-11-05 2011-10-13 漫游场景下支持ip流迁移的策略计费控制方法和系统 WO2012058998A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US13/882,591 US9380446B2 (en) 2010-11-05 2011-10-13 Policy and charging control method supporting IP flow mobility in roaming scenario
EP11837524.5A EP2624607A4 (en) 2010-11-05 2011-10-13 Policy and charging control method supporting ip flow mobility in roaming scenario

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010534700.0A CN102469431B (zh) 2010-11-05 2010-11-05 漫游场景下支持ip流迁移的策略计费控制方法和系统
CN201010534700.0 2010-11-05

Publications (1)

Publication Number Publication Date
WO2012058998A1 true WO2012058998A1 (zh) 2012-05-10

Family

ID=46024005

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/080730 WO2012058998A1 (zh) 2010-11-05 2011-10-13 漫游场景下支持ip流迁移的策略计费控制方法和系统

Country Status (4)

Country Link
US (1) US9380446B2 (zh)
EP (1) EP2624607A4 (zh)
CN (1) CN102469431B (zh)
WO (1) WO2012058998A1 (zh)

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2578009A1 (en) * 2010-05-28 2013-04-10 Telefonaktiebolaget LM Ericsson (publ) Flow mobility filter rule verification
US8743885B2 (en) 2011-05-03 2014-06-03 Cisco Technology, Inc. Mobile service routing in a network environment
CN103379512A (zh) * 2012-04-20 2013-10-30 中兴通讯股份有限公司 Wlan网络用户策略分发装置及方法
CN103716775B (zh) 2012-09-29 2017-10-10 华为终端有限公司 数据流控制方法及相关设备和通信系统
US10776384B1 (en) * 2013-04-30 2020-09-15 Ping Identity Corporation Method, server and system for criteria-based assured replication
CN104782151B (zh) * 2013-10-11 2018-10-19 华为技术有限公司 信息传输方法和装置
CN104955085A (zh) * 2014-03-24 2015-09-30 中兴通讯股份有限公司 一种漫游场景下的应用检测控制方法及v-pcrf
US9379931B2 (en) * 2014-05-16 2016-06-28 Cisco Technology, Inc. System and method for transporting information to services in a network environment
US9479443B2 (en) 2014-05-16 2016-10-25 Cisco Technology, Inc. System and method for transporting information to services in a network environment
US9654645B1 (en) * 2014-09-04 2017-05-16 Google Inc. Selection of networks for voice call transmission
WO2016033811A1 (zh) * 2014-09-05 2016-03-10 华为技术有限公司 一种分流策略协商方法及装置
US9872319B2 (en) * 2014-09-23 2018-01-16 Blackberry Limited Method and apparatus for selecting an IP type during roaming
US10417025B2 (en) 2014-11-18 2019-09-17 Cisco Technology, Inc. System and method to chain distributed applications in a network environment
WO2016090576A1 (zh) * 2014-12-10 2016-06-16 华为技术有限公司 一种无线通信系统的管理方法和相关装置
WO2016155753A1 (en) * 2015-03-31 2016-10-06 Telefonaktiebolaget Lm Ericsson (Publ) Selective inactivation of control rules parameters
US9762402B2 (en) 2015-05-20 2017-09-12 Cisco Technology, Inc. System and method to facilitate the assignment of service functions for service chains in a network environment
CN106789117A (zh) * 2015-11-19 2017-05-31 中兴通讯股份有限公司 Pcc规则的处理方法及装置
CN108476388B (zh) * 2015-12-31 2020-08-07 华为技术有限公司 处理数据包的方法及装置
US11044203B2 (en) 2016-01-19 2021-06-22 Cisco Technology, Inc. System and method for hosting mobile packet core and value-added services using a software defined network and service chains
US10361969B2 (en) 2016-08-30 2019-07-23 Cisco Technology, Inc. System and method for managing chained services in a network environment
US11902890B2 (en) * 2018-02-03 2024-02-13 Nokia Technologies Oy Application based routing of data packets in multi-access communication networks
US11991603B2 (en) 2019-01-10 2024-05-21 Telefonaktiebolagget LM Ericsson (Publ) Methods and apparatuses for facilitating roaming of terminal device
CN114423026A (zh) * 2019-02-18 2022-04-29 华为技术有限公司 通信方法、装置及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080046963A1 (en) * 2006-08-18 2008-02-21 Cisco Technology, Inc. System and method for implementing policy server based application interaction manager
CN101198171A (zh) * 2007-12-27 2008-06-11 中兴通讯股份有限公司 一种漫游场景下的策略计费控制消息的路由方法
CN101242655A (zh) * 2008-03-04 2008-08-13 中兴通讯股份有限公司 一种漫游情况下归属网选择媒体路由模式的方法

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100471160C (zh) * 2006-07-31 2009-03-18 华为技术有限公司 实现在不同网络之间协商策略信息的方法和系统
CN101370006B (zh) * 2007-08-15 2011-07-27 华为技术有限公司 网络协议连通接入网会话建立方法及会话删除方法
WO2009086759A1 (zh) 2007-12-27 2009-07-16 Zte Corporation 一种策略和计费规则功能的选择方法
CN101677437B (zh) * 2008-09-18 2012-02-29 华为技术有限公司 多分组数据网场景下实现策略和计费控制的方法和系统
US8654716B2 (en) * 2008-11-14 2014-02-18 Futurewei Technologies, Inc. System and method for name binding for multiple packet data network access
US8498208B2 (en) * 2009-07-20 2013-07-30 Qualcomm Incorporated Turning on flows in network initiated QoS
US8769098B2 (en) * 2009-08-20 2014-07-01 Telefonaktiebolaget L M Erisson (Publ) Fair usage enforcement in roaming packet based access
US9503483B2 (en) * 2010-02-16 2016-11-22 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatuses for identifying and reporting quality of service rules applicable to a communication session

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080046963A1 (en) * 2006-08-18 2008-02-21 Cisco Technology, Inc. System and method for implementing policy server based application interaction manager
CN101198171A (zh) * 2007-12-27 2008-06-11 中兴通讯股份有限公司 一种漫游场景下的策略计费控制消息的路由方法
CN101242655A (zh) * 2008-03-04 2008-08-13 中兴通讯股份有限公司 一种漫游情况下归属网选择媒体路由模式的方法

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
EP2624607A4 (en) 2017-08-09
CN102469431B (zh) 2015-04-01
US9380446B2 (en) 2016-06-28
US20130223290A1 (en) 2013-08-29
EP2624607A1 (en) 2013-08-07
CN102469431A (zh) 2012-05-23

Similar Documents

Publication Publication Date Title
WO2012058998A1 (zh) 漫游场景下支持ip流迁移的策略计费控制方法和系统
US9351325B2 (en) Policy control method and system for converged network
US9137652B2 (en) Method for implementing policy and charging control in a roaming scene
WO2011006317A1 (zh) 删除家乡策略和计费规则功能冗余信息的方法及系统
WO2009135362A1 (zh) 一种隐藏拜访地网络拓扑结构的策略计费控制的方法
WO2010081329A1 (zh) 业务流迁移过程中对网络资源进行控制的方法和系统
US8463889B2 (en) Method for provisioning and installing event triggers
WO2010108356A1 (zh) 一种终端通过多接入网接入的计费方法和系统及上报方法
EP2571327A1 (en) Method and system for reporting fixed network access information
WO2010015133A1 (zh) Dra中的会话信息的删除方法
KR20120062804A (ko) 차징 시스템 및 방법
US9544832B2 (en) Method, apparatus and system for policy control
WO2009124436A1 (zh) 一种承载绑定和事件报告功能策略控制的方法及系统
WO2011029289A1 (zh) 漫游场景下承载控制模式的发送方法和系统
WO2012019507A1 (zh) 一种实现固定宽带接入网接入的策略控制方法及系统
WO2010078761A1 (zh) 基于多接入技术的策略计费控制方法、装置和系统
WO2010111944A1 (zh) 释放接入连接的方法、装置、策略控制实体及系统
WO2010054560A1 (zh) 一种实现多接入的方法及系统
WO2014094488A1 (zh) 漫游本地业务的计费策略方法及装置
WO2011018020A1 (zh) 控制pcrf负载均衡的方法、系统及重定向dra
JP5009970B2 (ja) ネットワーク接続装置による認証方法、ＱｏＳ制御方法、トラフィック制御方法およびＩＰ移動性制御方法
CN101742471B (zh) 一种数据流与接入网连接绑定的方法
WO2012129992A1 (zh) 被赞助数据连接的处理方法及策略与计费规则功能实体
WO2012146092A1 (zh) 一种ip流迁移的策略控制方法及系统
WO2011134315A1 (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: 11837524

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 13882591

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2011837524

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE