WO2011029289A1 - 漫游场景下承载控制模式的发送方法和系统 - Google Patents

漫游场景下承载控制模式的发送方法和系统 Download PDF

Info

Publication number
WO2011029289A1
WO2011029289A1 PCT/CN2010/070349 CN2010070349W WO2011029289A1 WO 2011029289 A1 WO2011029289 A1 WO 2011029289A1 CN 2010070349 W CN2010070349 W CN 2010070349W WO 2011029289 A1 WO2011029289 A1 WO 2011029289A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
vpcrf
control mode
hpcrf
bearer
Prior art date
Application number
PCT/CN2010/070349
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 EP10814891.7A priority Critical patent/EP2472918B1/en
Priority to US13/257,593 priority patent/US8661145B2/en
Publication of WO2011029289A1 publication Critical patent/WO2011029289A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • 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/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
    • 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
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and system for transmitting a bearer control mode in a roaming scenario.
  • the 3GPP (3rd Generation Partnership Project) Policy and Charging Control (PCC) architecture is a functional framework that can be applied to multiple access technologies, for example, it can be applied.
  • UTRAN Universal Mobile Telecommunications System
  • GSM Global System for Mobile Communication
  • UMTS Universal Mobile Telecommunications System
  • EDGE GSM Data Enhanced for Evolution
  • I-WLAN interworking wireless local area network
  • EPS Evolved Packet System
  • FIG. 1 is a related diagram of a Rel-8 PCC non-roaming architecture of the related art.
  • the following describes the logical function entities and their interface functions in the PCC architecture with reference to FIG. 1 :
  • Application Function Entity (AF) to provide service applications Access points, the network resources used by these business applications require dynamic policy control.
  • the AF sends the related service information to the Policy and Charging Rules Function (PCRF). If the service information is consistent with the policy of the PCRF, the PCRF accepts the negotiation; otherwise, the PCRF rejects the negotiation and simultaneously gives the business parameters acceptable to the PCRF in the feedback.
  • the AF can then return these parameters to the User Equipment (UE).
  • UE User Equipment
  • the interface between AF and PCRF is the Rx interface.
  • the Policy Control and Charging Rules Function Entity is the core of the PCC and is responsible for policy decision making and charging rules.
  • the PCRF provides network control rules based on service data flows, including the detection of traffic data flows, Gating Control, and Quality of Service. Service, referred to as QoS) control and data flow based charging rules.
  • QoS Quality of Service
  • the PCRF sends its formulated policies and charging rules to the policy and accounting enforcement function entity (Policy and Control).
  • the Enforcement Function (abbreviated as PCEF) is executed.
  • PCEF The Enforcement Function
  • the PCRF also needs to ensure that these rules are consistent with the user's subscription information.
  • the basis for formulating policies and charging rules by the PCRF includes: obtaining information related to the service from the AF; obtaining subscription information with the user policy charging control from the Subscriber Profile Repository (SPR); and acquiring the bearer-related network from the PCEF Information.
  • the Policy and Charging Enforcement Function Entity is usually located in the Gateway (Gate-Way, GW for short), and performs the policy and charging rules defined by the PCRF on the bearer plane.
  • the PCEF detects the service data flow according to the service data flow filter in the rule sent by the PCRF, and then executes the policy and charging rules formulated by the PCRF for these service data flows.
  • the PCEF performs QoS authorization according to the rules sent by the PCRF, and performs gate control according to the execution of the AF.
  • the charging rule sent by the PCRF the PCEF performs the corresponding service data flow charging operation, and the charging can be either online charging or offline charging.
  • PCEF In the case of online charging, the PCEF needs to perform credit management with the Online Charging System (OCS). During offline charging, the PCEF and the Offline Charging System (OFCS) exchange relevant accounting information.
  • the interface between PCEF and PCRF is Gx interface
  • the interface between OCE and OCS is Gy interface
  • the interface between OFCS and OFCS is Gz interface.
  • PCEFs are generally located on the gateway of the network, such as the GPRS Gateway Support Node (GGSN) in GPRS and the Packet Data Gateway (PDG) in I-WLAN.
  • GGSN GPRS Gateway Support Node
  • PDG Packet Data Gateway
  • the functions of the Bearer Binding and Event Reporting Function include bearer binding, verification of uplink bearer binding, and event reporting.
  • the BBERF is located.
  • S-GW when the UE accesses through the trusted non-3GPP access system, the BBERF is located in the trusted non-3GPP access gateway, and when the UE accesses through the untrusted non-3GPP access system, the BBERF is located in the evolved packet data gateway ( Evolved Packet Data Gateway, referred to as ePDG).
  • ePDG evolved packet data gateway
  • the User Contracting Database stores user policy charging control subscription information related to policy control and charging.
  • the interface between SPR and PCRF is the Sp interface.
  • the online charging system (OCS) and PCEF are used to control and manage user credits in the online charging mode.
  • the offline charging system (OFCS) and the PCEF complete the charging operation in the offline charging mode.
  • the PCC architecture implements a policy plan for the IP Connectivity Access Network (IP-CAN) session established by the UE to access a Packet Data Network (PDN) through the above functional entities. Fee control.
  • IP-CAN IP Connectivity Access Network
  • PDN Packet Data Network
  • the bearer In a packet system (such as EPS, UMTS, etc.), the bearer is the basic unit that the network provides QoS guarantee for service data stream transmission. Different bearers have different QoS Class Identifiers (QoS Class Identifiers, QCIs) and Allocation and Retention Priority (ARPs). The service data flows transmitted in the same bearer have the same QCI and ARP. Each network element in the packet network uses the same packet forwarding processing mechanism for the service data stream transmitted in the same bearer, and uses different packet forwarding processing mechanisms for the service data streams transmitted in different bearers.
  • the PCC architecture's policy control over the packet system is ultimately achieved by establishing, modifying, and terminating bearers with different QoS capabilities.
  • the bearer can usually be initiated and controlled by the network or UE.
  • UE-only and UE-NW There are two types of bearer control modes: UE-only and UE-NW.
  • the UE-NW indicates that the bearer in the IP-CAN session established by the UE can be controlled by the UE or the network, that is, both the UE and the network can determine the establishment, modification, and release of the bearer.
  • the protocol used in the PCC architecture is a Diameter application protocol developed on the basis of the Diameter Base Protocol, for example, an application protocol applied to the Gx interface, an application protocol applied to the Rx interface, Gxx.
  • Application protocols for interfaces (including Gxa and Gxc interfaces) and application protocols for roaming interface S9. Messages, commands, and AVPs (Attribute Value Pairs) for PCC are defined in these application protocols.
  • the Diameter sessions established with these protocols can be Gx sessions, Gxx sessions, Rx sessions, and S9 sessions, respectively. Through these sessions, each functional entity of the PCC performs policy charging control for establishing a PDN connection to the UE accessing the network.
  • FIGS. 2 and Figure 3 are the architecture diagrams of the PCC in the roaming scenario of home routing and local grooming.
  • the PCRF of the attribution ie HPLMN, Home Public Land Mobile Network, home public land mobile network
  • hPCRF hometown policy control and charging rules functional entity
  • visit place ie VPLMN, Visit Public Land Mobile Network, visit
  • the PCRF of the public land mobile network is the vPCRF (Visit Policy Control and Charging Rules Function Entity).
  • the PCEF is at the home location, and if there is a BBERF, the BBERF is at the visited place.
  • the PCEF is in the visited place, and if there is a BBERF, BBERF is also visiting the place.
  • the solution for implementing the S9 roaming interface is that for each UE, the vPCRF terminates all the IP-CAN sessions established by the UE in the visited Gx session, the Gxx session, and the S9 session to transmit the Gx session of all IP-CAN sessions.
  • the information on the Gxx session without terminating the Rx session of all IP-CAN sessions in the visited network, simply forwards the Rx session message to the hPCRF and the vPCRF as a proxy (Proxy).
  • the hPCRF When the hPCRF sends the policy control information to the vPCRF, if the information is sent at the command level (that is, the information is not included in any sub-session), the vPCRF will consider the information to be applied to all IP-CAN sessions of the UE; if the information is at the sub-session level The sender (ie, the information is included in the subsession), the vPCRF considers that the information only applies to the IP-CAN session corresponding to the subsession.
  • the hPCRF can only deliver bearer control mode at the command level. This limits the ability of the hPCRF to determine different bearer control modes for different IP-CAN sessions of the UE based on subscription information, network policies, and network capabilities.
  • the UE establishes two IP-CAN sessions.
  • the two IP-CAN sessions select two GGSNs, and the capabilities of the two GGSNs are inconsistent.
  • the PCRF may have different bearer control modes selected for the two IP-CAN sessions.
  • the PCRF can also choose different bearer control modes depending on the PDN network accessed by the two IP-CAN sessions, depending on the network policy.
  • Such a defect in a multiple access scenario may result in the hPCRF not being able to use different bearer control modes for different IP-CAN sessions of the UE according to different access network capabilities.
  • Multiple access support UEs simultaneously access multiple PDNs through different P-GWs through multiple access networks.
  • the UE accesses PDN1 and PDN2 through the non-3GPP IP access network and the 3GPP access network under the coverage of non-3GPP and 3GPP access.
  • Due to different access network capabilities such as the network does not support network-initiated bearer establishment, etc.
  • the PDN connection established by the UE through different access network accesses should use different bearer control.
  • Mode however, hPCRF cannot set different bearer control modes for this PDN connection.
  • the present invention provides a method and system for transmitting a bearer control mode in a roaming scenario, which solves the problem that the hPCRF cannot set different bearer control modes for different IP-CAN sessions in the prior art.
  • the present invention provides a method for transmitting a bearer control mode in a roaming scenario, including:
  • the hPCRF sets a bearer control mode of the gateway control session, and sends the S9 sub-session corresponding to the gateway control session to the vPCRF.
  • the above method may further include:
  • the vPCRF sends the bearer control mode to the policy and charging enforcement function entity PCEF or bearer binding and event reporting function entity BBERF.
  • the hPCRF supports the NRS, the access network information, the subscription information, and the network policy according to the network request, and sets the bearer control mode of the IP-CAN session.
  • the bearer control mode of the IP-CAN session is set in the hPCRF, and the step sent to the vPCRF is sent to the hPCRF.
  • the present invention further provides a transmission system for carrying a control mode in a roaming scenario, including an hPCRF and a vPCRF.
  • the hPCRF is set to set a bearer control mode of the IP-CAN session, and is sent to the vPCRF through the S9 sub-session corresponding to the IP-CAN session.
  • the vPCRF is arranged to send the bearer control mode to a PCEF or BBERF.
  • the above system can also have the following characteristics:
  • the hPCRF is a bearer control mode configured to set the IP-CAN session according to an NRS, access network information, subscription information, and a network policy.
  • the present invention further provides a transmission system for carrying a control mode in a roaming scenario, including an hPCRF and a vPCRF.
  • the hPCRF is set to set a bearer control mode of the gateway control session, and is sent to the vPCRF through the S9 sub-session corresponding to the gateway control session.
  • the vPCRF is arranged to send the bearer control mode to the BBERF.
  • the present invention enables the hPCRF to select different bearer control modes for multiple IP-CAN sessions established by the UE and send them to the vPCRF.
  • the vPCRF can further send the bearer control mode to the corresponding execution network element for execution.
  • FIG. 1 is a structural diagram of a prior art PCC non-roaming
  • FIG. 2 is an architectural diagram of a prior art PCC home routing roaming scenario
  • FIG. 3 is an architectural diagram of a prior art PCC local grooming roaming scenario
  • FIG. 5 is a flow chart of Embodiment 1 of the present invention.
  • Figure 6 is a flowchart of Embodiment 2 of the present invention
  • Figure ⁇ is a flow chart of the third embodiment of the present invention.
  • the hPCRF sets the bearer control mode of the IP-CAN session, and sends the S9 sub-session corresponding to the IP-CAN session to the visited policy control and charging rule function entity (vPCRF); or, the hPCRF is set.
  • the gateway controls the bearer control mode of the session, and sends the S9 sub-session corresponding to the session to the vPCRF.
  • the vPCRF sends the bearer control mode to the PCEF or BBERF.
  • the PCEF then sends the bearer control mode to other network elements and UEs related to the IP-CAN session, and the UE and each network element apply the bearer control mode to the IP-CAN session.
  • the BBERF then sends the bearer control mode to other network elements and UEs related to the gateway control session, and the UE and each network element apply the bearer control mode to the gateway control session.
  • This embodiment describes a flow chart for a UE to establish an IP-CAN session through a trusted non-3GPP access gateway in a roaming scenario in which the UE is in the home route.
  • the PMIPv6 protocol is used between the access gateway and the P-GW. as follows:
  • Step S501 The BBERF receives an IP-CAN session request message, where the message carries a user identifier NAI (Network Access Identifier), and the PDN identifies an access point name (Access Point Name).
  • NAI Network Access Identifier
  • Access Point Name an access point name
  • Step S502 The BBERF sends a gateway control session establishment request message to the vPCRF, where the message carries the user identifier NAI, the PDN identifies the APN, whether the UE and the access network support the network initiation process indication (NRS (Network Requested Support), the address of the BBERF. And access network information (ie, bearer attributes) used to formulate policies.
  • the Diameter session requested by the message request is represented as Gxx session 1;
  • Step S503 the vPCRF determines, according to the NAI, that the user is a roaming user, and determines that the user is not yet The user establishes S9, so the vPCRF sends an S9 session establishment indication message to the hPCRF, and requests to establish an S9 subsession Subsession1, and includes the NAI, APN, NRS, access network information, and the address of the BBERF in the Subsession1;
  • Step S504 If the hPCRF does not have user-related subscription information, the hPCRF exchanges with the SPR to obtain subscription information.
  • Step S505 The hPCRF formulates a default policy PCC rule and a corresponding QoS rule according to the IP-CAN session requested by the UE, such as the subscription information, the network policy, and the bearer attribute.
  • the bearer control mode (Bearer Control Mode, referred to as BCM) of the IP-CAN session is set.
  • BCM Bearer Control Mode
  • Step S506 the vPCRF sends the QoS rule and the BCM to the BBERF through the gateway control session establishment confirmation message.
  • BBERF installs QoS rules.
  • the trusted non-3GPP access network applies the bearer control mode indicated therein to the gateway control session requesting establishment according to the BCM. In this scenario, the gateway control session and the IP-CAN session are - corresponding. Therefore, it can also be considered that the bearer control mode indicated in the BCM will be applied to the IP-CAN session requesting establishment;
  • Step S507 the gateway where the BBERF resides sends an IP-CAN session request message to the gateway where the PCEF resides, and the message carries the NAI and the APN;
  • Step S507 can be sent simultaneously with step S502.
  • Step S508 The gateway where the PCEF resides allocates an IP address for the IP-CAN session requested by the UE.
  • the PCEF sends an IP-CAN session establishment indication message to the hPCRF, and the message carries the NAL APN and the IP Address.
  • the Diam session that the message requests to establish is represented as Gx session 1;
  • Step S509 the hPCRF associates the Gx session 1 with the Subsession1 according to the NAI and the APN.
  • the hPCRF sends the PCC rule defined in step S505 to the PCEF;
  • Step S510 the PCEF installs the PCC rule.
  • the gateway where the PCEF resides returns an IP-CAN session response message to the BBERF;
  • Step S511 the BBERF returns to establish an IP-CAN session response message.
  • the BBERF may then send the bearer control mode to other network elements and UEs in the trusted non-3GPP access network.
  • the UE and the trusted non-3GPP access network will proceed according to the instructions of the BCM.
  • Management of IP-CAN session bearers such as the establishment, modification, and release of bearers.
  • the BBERF will send a gateway control session establishment request message to the vPCRF (the Diameter session requested to be established is Gxx session 2), the message carries the NAI and ⁇ ', and the vPCRF will send the S9 session modification to the hPCRF.
  • the message Indicates the message and requests to establish the S9 subsession Subsession2, NAI, ⁇ ' and NRS (since single access, NRS is consistent with the first IP-CAN session) is included in Subsession2.
  • the hPCRF will determine the BCM of the second IP-CAN session according to the subscription information, the access network information, the network policy, and the NRS, and send it to the vPCRF through the Subsession2 of the S9 session modification message.
  • the vPCRF sends a BCM' to the BBERF via the Gateway Control Session Setup Acknowledgement message of Gxx Session 2.
  • the BBERF may then send the bearer control mode to other network elements and UEs in the trusted 3GPP access network.
  • the UE and the trusted non-3GPP access network will perform management of the second IP-CAN session bearer according to the indication of the BCM', such as establishment, modification and release of the bearer.
  • BCM and BCM' may be different.
  • the BBERF of the other access network will send a gateway control session establishment request message to the vPCRF (the Diameter session requested to be established is Gxx session 2), and the message carries NAI and ⁇ ', and the vPCRF will Sending an S9 session modification indication message to the hPCRF, and requesting to establish an S9 subsession Subsession2, NAI, APN, and NRS, (due to multiple access, NRS, the NRS may be different from the first IP-CAN session) In Subsession2.
  • the hPCRF will determine the BCM' of the second IP-CAN session based on the subscription information, the access network information, the network policy, and the NRS', and send it to the vPCRF through Subsession2 of the S9 session modification message.
  • the vPCRF sends the BCM' to the BBERF' via the Gateway Control Session Setup Confirmation message of the Gxx Session 2.
  • the BBERF may then send the bearer control mode to other network elements and UEs in the trusted non-3GPP access network.
  • the UE and the trusted non-3GPP access network will perform management of the second IP-CAN session bearer according to the indication of the BCM', such as establishment, modification and release of the bearer. BCM and BCM may not be the same.
  • This embodiment describes a flow chart of a UE establishing an IP-CAN session through a 3GPP access gateway in a local grooming roaming scenario. The specific steps are as follows:
  • Step S601 the gateway where the PCEF resides receives the established IP-CAN session request message, which is IP-CAN session assignment IP address;
  • Step S602 The PCEF sends an IP-CAN session establishment indication message to the vPCRF, where the message carries NAI, APN, NRS, and IP Address.
  • the Diam session that the message requests to establish is represented as Gx Session 1.
  • the NRS identifies whether the UE, the access network, and the gateway where the PCEF resides support the network initiation process.
  • Step S603 The vPCRF determines that the user is a roaming user according to the NAI, and has not established an S9 session for the user. Therefore, the vPCRF sends an S9 session establishment indication message to the hPCRF, and requests to establish an S9 subsession Subsession1, and includes the NAI, the APN, and the NRS in the Subsession1. Step S604, if the hPCRF does not have user-related subscription information, the hPCRF will interact with the SPR to obtain subscription information;
  • Step S605 The hPCRF formulates a default policy PCC rule according to the IP-CAN session requested by the UE, such as the subscription information, the network policy, and the bearer attribute.
  • the bearer control mode BCM of the IP-CAN session is set according to the NRS, the access network information, the subscription information and the network policy.
  • the hPCRF returns an S9 session establishment confirmation message to the vPCRF, and the PCC rule and the BCM are included in the Subsession1;
  • Step S606 the vPCRF sends the PCC rule and the BCM to the PCEF through the IP-CAN session establishment confirmation message of the Gx session 1.
  • the PCEF installs the PCC rule, and applies the bearer control mode indicated therein to the IP-CAN session requested to be established according to the BCM;
  • Step S607 The gateway where the PCEF resides returns an IP-CAN session response message.
  • the PCEF may then send the bearer control mode to other network elements and UEs in the 3GPP access network.
  • the UE and the 3GPP access network will perform management of the IP-CAN session bearer according to the indication of the BCM, such as establishment, modification and release of the bearer.
  • the PCEF' will send an IP-CAN session establishment request message to the vPCRF.
  • the Diameter session requested to be established is Gx session 2
  • the message carries NAI, APN' and NRS'(NRS' and NRS may be inconsistent due to different PCEFs selected)
  • vPCRF will send S9 session modification indication message to hPCRF, and request Establish S9 subsessions Subsession2, NAI, APN, and NRS, which are included in Subsession2.
  • hPCRF will determine the BCM' of the second IP-CAN session based on the subscription information, access network information, network policy and NRS' Subsession2 that has passed the S9 session modification message is sent to the vPCRF.
  • the vPCRF sends the BCM' to the PCEF' via the IP-CAN Session Setup Confirmation message of the Gx Session 2.
  • the PCEF' may then send the bearer control mode to other network elements and UEs in the 3GPP access network.
  • the UE and the 3GPP access network will perform management of the second IP-CAN session bearer according to the indication of the BCM', such as establishment, modification and release of the bearer.
  • BCM and BCM may be different.
  • the PCEF will send an IP-CAN session modification indication message through the Gx session 1, and carry the new NRS' to the vPCRF, and the vPCRF will send the NRS' to the hPCRF through Subsession1.
  • the hPCRF determines the new BCM' based on the subscription information, access network information, network policy, and NRS', and sends it to the vPCRF through Subsession1.
  • the vPCRF sends the BCM' to the PCEF via the IP-CAN Session Modification Confirmation message of Gx Session 1.
  • the PCEF may then send the bearer control mode to other network elements and UEs in the 3GPP access network.
  • the UE and 3GPP access system will perform the management of the modified IP-CAN session bearer according to the BCM' indication.
  • the BBERF of the other access network will send a gateway control session establishment request message to the vPCRF (request to establish The Diameter session is a Gxx session 2), the message carries the NAI and APN', the vPCRF will send an S9 session modification indication message to the hPCRF, and request to establish the S9 subsession Subsession2, NAI, APN' and NRS' (due to the multiple access, The NRS' may be different from the NRS of the first IP-CAN session) is included in Subsession2.
  • the hPCRF will determine the BCM' of the second IP-CAN session based on the subscription information, the access network information, the network policy, and the NRS', and send it to the vPCRF through the Subsession2 of the S9 session modification message.
  • the vPCRF sends the BCM' to the BBERF' via the Gxx Session 2 gateway control session setup acknowledgment message.
  • the BBERF may then send the bearer control mode to other network elements and UEs in the non-3GPP access network.
  • the UE and the trusted non-3GPP access network will perform management of the second IP-CAN session bearer according to the indication of the BCM', such as establishment, modification and release of the bearer.
  • BCM and BCM may be different.
  • Step S701 the new BBERF (New BBERF) receives the setup gateway control session request message sent by the original BBERF (Old BBERF), and the New BBERF obtains the user identifier NAI, the PDN identifies the APN, and the access network information used to formulate the policy, and the like;
  • Step S702 The New BBERF sends a gateway control session establishment request message to the vPCRF, where the message carries the user identifier NAI, the PDN identifies the address of the APN, the New BBERF, and whether the UE and the access network support the network initiation procedure indication NRS ' (Network Requested Support, network Request support) and access network information used to develop policies.
  • the Diameter session requested by the message request is represented as Gxx session 2;
  • Step S703 The vPCRF determines, according to the NAI, that the user is a roaming user and identifies the APN according to the user identifiers NAI and PDN, and determines that the S9 session and the S9 subsession Subsession1 have been established for the user. Therefore, the vPCRF sends an S9 session modification indication message to the hPCRF, and includes the address of the NRS', the New BBERF, and the access information used for formulating the policy in the Subsession1;
  • Step S704 The hPCRF determines, according to the address of the New BBERF, that the UE has performed handover (ie, BBERF reselection), and the UE, the subscription information, the access network information, the network policy, the new access network information, and the like modify the previous PCC rules and QoS rules.
  • the new BCM of the IP-CAN session is set according to the NRS', the subscription information and the network policy.
  • the hPCRF returns an S9 session setup confirmation message to the vPCRF, and the QoS rules, BCM, and New BBERF addresses are included in Subsession1.
  • BCM may not be the same as BCM before the switch;
  • Step S705 the vPCRF judges that the information in the Subsession1 is sent to the New BBERF according to the address of the New BBERF, so the vPCRF sends the QoS rule and the BCM' to the New BBERF through the Gxx Session 2 sending gateway control session establishment confirmation message.
  • the New BBERF installs the QoS rules and applies the bearer control mode indicated therein to the gateway control session requested to be established according to the BCM. Also in this scenario, the newly established gateway control session and the modified IP-CAN session are one-to-one. Therefore, it can also be considered that the BBERF applies the bearer control mode indicated therein to the IP-CAN session according to the BCM;
  • Step S706 The gateway where the New BBERF resides sends IP-CAN session signaling to the gateway where the PCEF resides, and the message carries the NAI and the APN.
  • the message is usually implemented as a proxy binding update message; step S706 can be sent simultaneously with step S702.
  • Step S707 The gateway where the PCEF resides allocates the IP address before the handover to the UE according to the user identifier and the PDN identifier.
  • the PCEF sends an IP-CAN session modification indication message to the hPCRF, and the message carries the NAI, APN, and IP Address.
  • the message requesting the modified Diameter session is the Gx session 1 established in FIG. 5;
  • Step S708 The hPCRF sends the PCC rule defined in step S704 to the PCEF.
  • the hPCRF may modify the PCC rule and the QoS rule defined in step S704. At this time, the hPCRF sends the modified PCC rule to the PCEF, and the modified QoS rule is passed to the vPCRF. Send to BBERF 0
  • Step S709 the PCEF installs the PCC rule.
  • the gateway where the PCEF resides returns IP-CAN session signaling to the BBERF, carrying the IP address.
  • the message is usually a proxy binding update acknowledgement message when implemented; step S710, New BBERF returns to establish a gateway control session response message.
  • the BBERF may then send the bearer control mode to other network elements and UEs in the non-3GPP access network.
  • the UE and the trusted non-3GPP access system will perform management of the IP-CAN session bearer according to the indication of the BCM', such as establishment, modification and release of the bearer.
  • the transmission system of the bearer control mode in the roaming scenario of the embodiment of the present invention includes an hPCRF and a vPCRF,
  • the hPCRF is set to set a bearer control mode of the IP-CAN session, and is sent to the vPCRF through the S9 sub-session corresponding to the IP-CAN session.
  • the vPCRF is arranged to send the bearer control mode to a PCEF or BBERF.
  • the hPCRF is a bearer control mode configured to set the IP-CAN session according to an NRS, access network information, subscription information, and a network policy.
  • the transmission system of the bearer control mode in the roaming scenario of the embodiment of the present invention includes an hPCRF and a vPCRF,
  • the hPCRF is set to set a bearer control mode of the gateway control session, and is sent to the vPCRF through the S9 sub-session corresponding to the gateway control session.
  • the vPCRF is arranged to send the bearer control mode to the BBERF.
  • modules or steps of the present invention may be Implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of computing devices, optionally, they may be implemented by program code executable by the computing device, such that They may be stored in a storage device by a computing device, or they may be fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof may be implemented as a single integrated circuit module.
  • a general-purpose computing device which may be centralized on a single computing device or distributed over a network of computing devices, optionally, they may be implemented by program code executable by the computing device, such that They may be stored in a storage device by a computing device, or they may be fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof may be implemented as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the present invention enables the hPCRF to select different bearer control modes for multiple IP-CAN sessions established by the UE and send them to the vPCRF.
  • the vPCRF can further send the bearer control mode to the corresponding execution network. Meta execution.

Landscapes

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

Description

漫游场景下承载控制模式的发送方法和系统
技术领域
本发明涉及通信领域， 尤其涉及一种漫游场景下承载控制模式的发送方 法和系统。
背景技术
3GPP ( 3rd Generation Partnership Project, 第三代合作伙伴计划） 的策略 和计费控制（Policy and Charging Control, 简称为 PCC )架构是一个能够应用 于多种接入技术的功能框架， 例如， 其可以应用于通用移动通信系统 ( Universal Mobile Telecommunications System, 简称为 UMTS )的陆上无线接 入网 （ UMTS Terrestrial Radio Access Network, 简称为 UTRAN ) 、 全球移动 通信系统（ Global system for Mobile Communication, 简称为 GSM ) /GSM数 据增强演进 ( Enhanced Data rates for Global Evolution, 简称为 EDGE )无线接 入网、 互通无线局域网 （ I-WLAN ) 以及演进的分组系统 （ Evolved Packet System, 简称为 EPS )等。
图 1为相关技术的 Rel-8 PCC非漫游架构图， 以下参照图 1对 PCC架构 中的各个逻辑功能实体及其接口功能进行描述： 应用功能实体（Application Function, 简称为 AF ) , 提供业务应用的接入点， 这些业务应用所使用的网 络资源需要进行动态的策略控制。 在业务面进行参数协商时， AF将相关业务 信息传递给策略控制与计费规则功能实体 （Policy and Charging Rules Function,简称为 PCRF )。如果这些业务信息与 PCRF的策略相一致，则 PCRF 接受该协商； 否则， PCRF拒绝该协商， 并在反馈中同时给出 PCRF可接受的 业务参数。 随后， AF可将这些参数返回给用户设备（User Equipment, 简称 为 UE ) 。 其中， AF和 PCRF之间的接口是 Rx接口。
策略控制与计费规则功能实体（PCRF )是 PCC的核心， 负责策略决策 和计费规则的制定。 PCRF提供了基于业务数据流的网络控制规则，这些网络 控制包括业务数据流的检测、 门控（ Gating Control ) 、 服务质量（ Quality of Service, 简称为 QoS )控制以及基于数据流的计费规则等。 PCRF将其制定的 策略和计费规则发送给策略和计费执行功能实体 （Policy and Control
Enforcement Function, 简称为 PCEF )执行， 同时， PCRF还需要保证这些规 则和用户的签约信息一致。 PCRF制定策略和计费规则的依据包括： 从 AF获 取与业务相关的信息； 从用户签约数据库（ Subscription Profile Repository, 简 称为 SPR )获取与用户策略计费控制签约信息； 从 PCEF获取与承载相关网 络的信息。
策略和计费执行功能实体（PCEF )通常位于网关 （Gate-Way, 简称为 GW ) 内， 在承载面执行 PCRF所制定的策略和计费规则。 PCEF按照 PCRF 所发送的规则中的业务数据流过滤器对业务数据流进行检测， 进而对这些业 务数据流执行 PCRF所制定的策略和计费规则。 在承载建立时， PCEF按照 PCRF发送的规则进行 QoS授权，并根据 AF的执行进行门控控制。根据 PCRF 发送的计费规则， PCEF执行相应的业务数据流计费操作，计费既可以是在线 计费， 也可以是离线计费。 如果是在线计费， 则 PCEF需要和在线计费系统 ( Online Charging System, 简称为 OCS ) —起进行信用管理。 离线计费时， PCEF和离线计费系统（ Offline Charging System, 简称为 OFCS )之间交换相 关计费信息。 PCEF与 PCRF之间的接口是 Gx接口， 与 OCS之间的接口是 Gy接口， 与 OFCS之间的接口是 Gz接口。 PCEF—般都位于网络的网关上， 如 GPRS中的 GPRS网关支持节点 （GGSN ) 以及 I-WLAN中的分组数据网 关 （Packet Data Gateway, 简称为 PDG ) 。
承载绑定和事件报告功能实体 （Bearer Binding and Event Reporting Function, 简称为 BBERF ) 的功能包括承载绑定、 上行承载绑定的验证、 以 及事件报告。 当 UE通过 E-UTRAN接入， 并且服务网关 （Serving Gateway, 简称为 S-GW )与分组数据网络网关 （ Packet Data Network Gateway , 简称为 P-GW )之间釆用 PMIPv6协议时， BBERF就位于 S-GW, 当 UE通过可信任 非 3GPP接入系统接入时 , BBERF位于可信任非 3GPP接入网关， 当 UE通 过不可信任非 3GPP接入系统接入时、 BBERF 位于演进的分组数据网关 ( Evolved Packet Data Gateway, 简称为 ePDG ) 。 此时， PCEF不再执行承载 绑定功能。 用户签约数据库 （SPR )存储了和策略控制与计费相关的用户策略计费 控制签约信息。 SPR和 PCRF之间的接口是 Sp接口。
在线计费系统（OCS )和 PCEF—起进行在线计费方式下用户信用的控 制和管理。
离线计费系统（OFCS )与 PCEF—起完成离线计费方式下的计费操作。
PCC 架构通过以上各功能实体实现了对 UE 为访问一个分组数据网络 ( Packet Data Network,简称为 PDN )所建立的 IP连接接入网 ( IP Connectivity Access Network, 简称为 IP-CAN )会话的策略计费控制。
在分组系统中 （如 EPS, UMTS等） ， 承载是网络为业务数据流传输提 供 QoS保障的基本单位。 不同的承载具有不同的 QoS等级标识（ QoS Class Identifier,简称为 QCI )和分配与保持优先级（ Allocation and Retention Priority, 简称为 ARP ) , 同一承载中传输的业务数据流具有相同的 QCI和 ARP。 分组 网络中的各网元对同一承载中传输的业务数据流釆用相同的包转发处理机 制， 而对不同承载中传输的业务数据流釆用不同的包转发处理机制。 PCC架 构对分组系统的策略控制最终是通过对建立、 修改和终结具有不同 QoS能力 的承载来实现的。 承载通常可以由网络或 UE发起建立并进行控制。 目前在 PCC架构中， 承载控制模式有两种： UE— Only和 UE— NW。 UE— Only表示 UE 建立的 IP-CAN会话中的所有承载必须由 UE进行控制， 即 UE决定承载的建 立、 修改和释放。 UE— NW表示 UE建立的 IP-CAN会话中的承载可以由 UE 或网络进行控制， 即 UE和网络都可以决定承载的建立、 修改和释放。
在目前的技术中， PCC 架构中釆用的协议是在 Diameter基础协议 ( Diameter Base Protocol )基础上发展的 Diameter应用协议， 例如， 应用于 Gx接口的应用协议，应用于 Rx接口的应用协议、 Gxx接口（包括 Gxa和 Gxc 接口）的应用协议和应用于漫游接口 S9的应用协议等。在这些应用协议中定 义了用于 PCC的消息、 命令以及 AVP ( Attribute Value Pairs, 属性值对）等。 用这些协议建立的 Diameter会话分别可以成为 Gx会话、 Gxx会话、 Rx会话 和 S9会话。 PCC各功能实体通过这些会话对 UE接入网络建立 PDN连接进 行策略计费控制。
图 2和图 3分别是家乡路由和本地疏导两种漫游场景下的 PCC的架构图。 其中， 归属地（即 HPLMN, Home Public Land Mobile Network, 家乡公共陆 上移动网） 的 PCRF为 hPCRF (家乡策略控制与计费规则功能实体） ， 拜访 地（即 VPLMN, Visit Public Land Mobile Network, 拜访公共陆上移动网）的 PCRF为 vPCRF (拜访策略控制与计费规则功能实体）。 在家乡路由场景下， PCEF在归属地，若存在 BBERF, BBERF在拜访地。在本地疏导漫游场景下， PCEF在拜访地， 若存在 BBERF, BBERF也在拜访地。
目前， 实现 S9漫游接口的方案为针对每一个 UE, vPCRF终结 UE建立 的所有 IP-CAN会话在拜访地网络存在的 Gx会话、 Gxx会话， 用一个 S9会 话来传送所有 IP-CAN会话的 Gx会话、 Gxx会话上的信息， 而不终结所有 IP-CAN会话在拜访地网络中的 Rx会话， 只是将 Rx会话的消息转发给 hPCRF, 将 vPCRF作为一个代理（Proxy ) 。 在一个 S9会话中可能存在多个 子会话 (称为 S9 subsession )。 每一个 subsession用来传送一个 IP-CAN会话 的 Gx、 Gxx会话上的信息。 hPCRF向 vPCRF发送策略控制信息时， 若信息 在命令级下发（即信息不包含在任何一个子会话中） ， vPCRF将认为信息应 用于 UE的所有 IP-CAN会话； 若信息在子会话级下发（即信息包含在子会话 中） ， vPCRF认为信息只应用与子会话对应的 IP-CAN会话。 目前， hPCRF 只能以命令级下发承载控制模式， 这限制了 hPCRF不能根据签约信息、 网络 策略以及网络能力决定 UE不同的 IP-CAN会话釆用不同的承载控制模式的能 力。如： UE建立了两个 IP-CAN会话，这两个 IP-CAN会话选择了两个 GGSN, 而两个 GGSN的能力是不一致的。 一个支持网络发起的承载建立， 另一个不 支持。 那么 PCRF为两个 IP-CAN会话所选择的承载控制模式就有可能不同。 当然， PCRF也可以根据两个 IP-CAN会话接入的 PDN网络的不同而选择不 同的承载控制模式， 这取决于网络策略。
这样的缺陷在多接入场景下会导致 hPCRF无法根据不同的接入网能力来 为 UE不同的 IP-CAN会话釆用不同的承载控制模式的能力。 多接入支持 UE 同时通过多种接入网经不同 P-GW接入多种 PDN。 如图 4所示， UE同时在 非 3GPP和 3GPP接入的覆盖下，通过非 3GPP IP接入网和 3GPP接入网接入 PDN1和 PDN2。 由于接入网网络能力的不同（如网络不支持网络发起的承载 建立等） ， UE通过不同接入网接入建立的 PDN连接应该釆用不同的承载控 制模式， 但是， hPCRF却无法为该 PDN连接设置不同的承载控制模式。
发明内容
为了解决现有技术问题， 本发明提出一种漫游场景下承载控制模式的发 送方法和系统， 解决现有技术中 hPCRF无法为不同的 IP-CAN会话设置不同 的承载控制模式的问题。
为了解决上述技术问题， 本发明提供一种漫游场景下承载控制模式的发 送方法， 包括：
家乡策略控制与计费规则功能实体 hPCRF设定 IP连接接入网 IP-CAN会 略控制与计费规则功能实体 vPCRF;
或者， hPCRF设定网关控制会话的承载控制模式， 并通过所述网关控制 会话对应的 S9子会话下发给 vPCRF。
上述方法还可包括：
所述 vPCRF将所述承载控制模式发送给策略和计费执行功能实体 PCEF 或者承载绑定和事件报告功能实体 BBERF。
上述方法还可具有以下特点：
所述 hPCRF根据网络请求支持 NRS、接入网信息、签约信息和网络策略 设定所述 IP-CAN会话的承载控制模式。
上述方法还可具有以下特点：
在所述 hPCRF设定 IP-CAN会话的承载控制模式，并下发给 vPCRF的步 送给 hPCRF。
上述方法还可具有以下特点：
在所述 hPCRF设定所述网关控制会话的承载控制模式，并下发给 vPCRF 的步骤之前，所述 vPCRF通过所述网关控制会话对应的 S9子会话将所述 NRS 发送给 hPCRF。 为了解决上述技术问题， 本发明还提供一种漫游场景下承载控制模式的 发送系统， 包括 hPCRF和 vPCRF,
所述 hPCRF设置成设定 IP-CAN会话的承载控制模式， 并通过所述 IP-CAN会话对应的 S9子会话下发给 vPCRF。
上述系统还可具有以下特点：
所述 vPCRF设置成将所述承载控制模式发送给 PCEF或者 BBERF。 上述系统还可具有以下特点：
所述 hPCRF是设置成根据 NRS、接入网信息、签约信息和网络策略设定 所述 IP-CAN会话的承载控制模式。
为了解决上述技术问题， 本发明还提供一种漫游场景下承载控制模式的 发送系统， 包括 hPCRF和 vPCRF,
所述 hPCRF设置成设定网关控制会话的承载控制模式，并通过所述网关 控制会话对应的 S9子会话下发给 vPCRF。
上述系统还可具有以下特点：
所述 vPCRF设置成将所述承载控制模式发送给 BBERF。
本发明使得 hPCRF能够为 UE建立的多个 IP-CAN会话选择不同的承载 控制模式并下发给 vPCRF, vPCRF可以进一步将承载控制模式发送给相应的 执行网元执行。
附图概述
图 1是现有技术的 PCC非漫游的架构图；
图 2是现有技术的 PCC家乡路由漫游场景的架构图；
图 3是现有技术的 PCC本地疏导漫游场景的架构图；
图 4是现有技术的多接入示意图；
图 5是本发明实施例一的流程图；
图 6是本发明实施例二的流程图； 图 Ί是本发明实施例三的流程图。
本发明的较佳实施方式
在本发明中， hPCRF设定 IP-CAN会话的承载控制模式， 并通过所述 IP-CAN会话对应的 S9 子会话下发给拜访策略控制与计费规则功能实体 ( vPCRF ) ； 或者， hPCRF设定网关控制会话的承载控制模式， 并通过所述 网关控制会话对应的 S9子会话下发给 vPCRF。
所述 vPCRF将所述承载控制模式发送给 PCEF或者 BBERF。
所述 PCEF再将所述承载控制模式发送给所述 IP-CAN会话相关的其他网 元和 UE, UE和各网元将所述承载控制模式应用于所述 IP-CAN会话。
所述 BBERF再将所述承载控制模式发送给所述网关控制会话相关的其 他网元和 UE, UE和各网元将所述承载控制模式应用于所述网关控制会话。
以下结合附图对本发明的优选实施例进行说明， 应当理解， 此处所描述 的优选实施例仅用于说明和解释本发明， 并不用于限定本发明。 需要说明的 是， 在不冲突的情况下， 本申请中的实施例及实施例中的特征可以相互组合。
实施例一
本实施例描述 UE在家乡路由的漫游场景下， UE通过可信任非 3GPP接 入网关接入建立 IP-CAN会话的流程图， 其中接入网关与 P-GW之间釆用 PMIPv6协议， 具体步骤如下：
步骤 S501 , BBERF收到建立 IP-CAN会话请求消息， 消息中携带用户标 识 NAI( Network Access Identifier,网络接入标识符） , PDN标识 APN( Access Point Name, 接入点名 ) ；
步骤 S502 , BBERF向 vPCRF发送网关控制会话建立请求消息， 消息中 携带用户标识 NAI , PDN标识 APN , UE和接入网是否支持网络发起流程指 示 NRS ( Network Requested Support, 网络请求支持） ， BBERF的地址以及 用于制定策略的接入网信息 （即承载属性） 。 该消息请求建立的 Diameter会 话表示为 Gxx会话 1；
步骤 S503 , vPCRF根据 NAI判断用户为漫游用户， 并判断还没有为该 用户建立 S9 , 因此 vPCRF向 hPCRF发送 S9会话建立指示消息， 并请求建立 S9子会话 Subsessionl , 将 NAI、 APN, NRS、 接入网信息以及 BBERF的地 址包含在 Subsessionl中；
步骤 S504 , 若 hPCRF没有用户相关的签约信息， hPCRF将与 SPR交互 获取签约信息；
步骤 S505 , hPCRF根据签约信息、 网络策略、 承载属性等 UE请求建立 的 IP-CAN会话制定默认策略 PCC规则和相应的 QoS规则。 同时根据 NRS、 接入网信息、签约信息和网络策略设定 IP-CAN会话的承载控制模式（Bearer Control Mode, 简称为 BCM ) 。 hPCRF向 vPCRF返回 S9会话建立确认消息， QoS规则和 BCM包含在 Subsessionl中；
步骤 S506 , vPCRF将 QoS规则和 BCM通过网关控制会话建立确认消息 发送给 BBERF。 BBERF安装 QoS规则。 可信任非 3GPP接入网根据 BCM将 其中指示的承载控制模式应用于请求建立的网关控制会话。 在这种场景下， 网关控制会话和 IP-CAN会话是——对应的。 因此， 也可以认为 BCM中指示 的承载控制模式将应用于请求建立的 IP-CAN会话；
步骤 S507 , BBERF驻留的网关向 PCEF驻留的网关发送建立 IP-CAN会 话请求消息， 消息中携带 NAI和 APN;
步骤 S507可与步骤 S502同时发送。
步骤 S508 , PCEF驻留的网关为 UE请求建立的 IP-CAN会话分配 IP地 址。 PCEF向 hPCRF发送 IP-CAN会话建立指示消息， 消息中携带 NAL APN 和 IP Address。 该消息请求建立的 Diameter会话表示为 Gx会话 1；
步骤 S509 , hPCRF根据 NAI和 APN将 Gx会话 1与 Subsessionl进行关 联。 hPCRF将步骤 S505制定的 PCC规则发送给 PCEF;
步骤 S510 , PCEF安装 PCC规则。 PCEF驻留的网关向 BBERF返回建立 IP-CAN会话应答消息；
步骤 S511 , BBERF返回建立 IP-CAN会话应答消息。
BBERF可能再将所述承载控制模式发送给可信任非 3GPP接入网中的其 他网元和 UE。 UE和可信任非 3GPP接入网将根据 BCM 的指示， 来进行 IP-CAN会话承载的管理， 如承载的建立、 修改和释放。
当 UE决定发起建立第二个 IP-CAN会话时，
( 1 )若在单接入场景下， BBERF将向 vPCRF发送网关控制会话建立请 求消息（请求建立的 Diameter会话为 Gxx会话 2 ) ,消息中携带 NAI和 ΑΡΝ' , vPCRF 将向 hPCRF发送 S9 会话修改指示消息， 并请求建立 S9 子会话 Subsession2 , NAI、 ΑΡΝ'和 NRS (由于是单接入， NRS与第一个 IP-CAN会 话一致）包含在 Subsession2中。 hPCRF将根据签约信息、 接入网信息、 网络 策略和 NRS决定第二个 IP-CAN会话的 BCM，， 并通过 S9会话修改消息的 Subsession2发送给 vPCRF。 vPCRF通过 Gxx会话 2的网关控制会话建立确认 消息将 BCM'发送给 BBERF。 BBERF可能再将所述承载控制模式发送给可信 任非 3GPP接入网中的其他网元和 UE。 UE和可信任非 3GPP接入网将根据 BCM'的指示， 来进行第二个 IP-CAN会话承载的管理， 如承载的建立、 修改 和释放。 BCM和 BCM'有可能是不一样的。
( 2 )若在多接入场景下， 另一个接入网的 BBERF将向 vPCRF发送网关 控制会话建立请求消息 （请求建立的 Diameter会话为 Gxx会话 2 ) , 消息中 携带 NAI和 ΑΡΝ' , vPCRF将向 hPCRF发送 S9会话修改指示消息， 并请求 建立 S9子会话 Subsession2, NAI, APN，和 NRS， (由于是多接入， NRS，与 第一个 IP-CAN会话的 NRS可能是不同的） 包含在 Subsession2中。 hPCRF 将根据签约信息、 接入网信息、 网络策略和 NRS'决定第二个 IP-CAN会话的 BCM' , 并通过 S9会话修改消息的 Subsession2发送给 vPCRF。 vPCRF通过 Gxx会话 2的网关控制会话建立确认消息将 BCM'发送给 BBERF'。 BBERF 可能再将所述承载控制模式发送给可信任非 3GPP接入网中的其他网元和 UE。UE和可信任非 3GPP接入网将根据 BCM'的指示，来进行第二个 IP-CAN 会话承载的管理， 如承载的建立、 修改和释放。 BCM和 BCM，有可能是不一 样的。
实施例二
本实施例描述 UE在本地疏导漫游场景下， UE通过 3GPP接入网关接入 建立 IP-CAN会话的流程图， 具体步骤如下具体步骤如下：
步骤 S601 , PCEF驻留的网关收到建立的 IP-CAN会话请求消息， 为 IP-CAN会话分配 IP地址；
步骤 S602, PCEF向 vPCRF发送 IP-CAN会话建立指示消息， 消息中携 带 NAI、 APN、 NRS和 IP Address。 该消息请求建立的 Diameter会话表示为 Gx会话 1。 NRS标识 UE、 接入网以及 PCEF驻留的网关是否支持网络发起 流程
步骤 S603、 vPCRF根据 NAI判断用户为漫游用户， 并且还没有为用户 建立 S9会话， 因此 vPCRF向 hPCRF发送 S9会话建立指示消息， 并请求建 立 S9子会话 Subsessionl , 将 NAI、 APN以及 NRS包含在 Subsessionl中； 步骤 S604, 若 hPCRF没有用户相关的签约信息， hPCRF将与 SPR交互 获取签约信息；
步骤 S605, hPCRF根据签约信息、 网络策略、 承载属性等 UE请求建立 的 IP-CAN会话制定默认策略 PCC规则。 同时根据 NRS、 接入网信息、 签约 信息和网络策略设定 IP-CAN会话的承载控制模式 BCM。 hPCRF向 vPCRF 返回 S9会话建立确认消息， PCC规则和 BCM包含在 Subsessionl中；
步骤 S606 , vPCRF将 PCC规则和 BCM通过 Gx会话 1的 IP-CAN会话 建立确认消息发送给 PCEF。 PCEF安装 PCC规则， 同时根据 BCM将其中指 示的承载控制模式应用于请求建立的 IP-CAN会话；
步骤 S607 , PCEF驻留的网关返回建立 IP-CAN会话应答消息。
PCEF 可能再将所述承载控制模式发送给 3GPP接入网中的其他网元和 UE。 UE和 3GPP接入网将根据 BCM的指示， 来进行 IP-CAN会话承载的管 理， 如承载的建立、 修改和释放。
( 1 )若 UE决定通过 3GPP接入网发起建立第二个 IP-CAN会话 (即单 接入） ， 并且选择的 PCEF'与之前的不同， PCEF'将向 vPCRF发送 IP-CAN 会话建立请求消息 （请求建立的 Diameter会话为 Gx会话 2 ) , 消息中携带 NAI、 APN'以及 NRS' (由于选择的 PCEF不同， NRS'和 NRS可能不一致 ) , vPCRF 将向 hPCRF发送 S9 会话修改指示消息， 并请求建立 S9 子会话 Subsession2, NAI, APN，和 NRS，含在 Subsession2中。 hPCRF将根据签约信 息、 接入网信息、 网络策略和 NRS'决定第二个 IP-CAN会话的 BCM' , 并通 过 S9会话修改消息的 Subsession2发送给 vPCRF。 vPCRF通过 Gx会话 2的 IP-CAN会话建立确认消息将 BCM'发送给 PCEF'。 PCEF'可能再将所述承载 控制模式发送给 3GPP接入网中的其他网元和 UE。 UE和 3GPP接入网将根 据 BCM'的指示， 来进行第二个 IP-CAN会话承载的管理， 如承载的建立、修 改和释放。 BCM和 BCM，有可能是不一样的。
( 2 )若 UE发生了切换导致 NRS发生了改变， 那么 PCEF将通过 Gx会 话 1发送 IP-CAN会话修改指示消息， 携带新的 NRS'发送给 vPCRF, vPCRF 将通过 Subsessionl将 NRS'发送给 hPCRF。 hPCRF根据签约信息、 接入网信 息、 网络策略和 NRS'决定新的 BCM' , 并通过 Subsessionl发送给 vPCRF。 vPCRF通过 Gx会话 1的 IP-CAN会话修改确认消息将 BCM'发送给 PCEF。 PCEF可能再将所述承载控制模式发送给 3GPP接入网中的其他网元和 UE。 UE和 3GPP接入系统将根据 BCM'的指示进行修改后的 IP-CAN会话承载的 管理。
( 3 )若 UE决定通过另外一个非 3GPP接入发起建立第二个 IP-CAN会 话时（即多接入 ) , 另一个接入网的 BBERF将向 vPCRF发送网关控制会话 建立请求消息 （请求建立的 Diameter会话为 Gxx会话 2 ) , 消息中携带 NAI 和 APN' , vPCRF将向 hPCRF发送 S9会话修改指示消息， 并请求建立 S9子 会话 Subsession2, NAI、 APN'和 NRS' (由于是多接入， NRS'与第一个 IP-CAN 会话的 NRS可能是不同的 )包含在 Subsession2中。 hPCRF将根据签约信息、 接入网信息、 网络策略和 NRS'决定第二个 IP-CAN会话的 BCM' , 并通过 S9 会话修改消息的 Subsession2发送给 vPCRF。 vPCRF通过 Gxx会话 2的网关 控制会话建立确认消息将 BCM'发送给 BBERF'。 BBERF可能再将所述承载 控制模式发送给非 3GPP接入网中的其他网元和 UE。 UE和可信任非 3GPP 接入网将根据 BCM'的指示， 来进行第二个 IP-CAN会话承载的管理，如承载 的建立、 修改和释放。 BCM和 BCM，有可能是不一样的。
实施例三
本实施例描述 UE如图 5的流程建立 IP-CAN会话后切换到另一个可信任 非 3GPP接入网关的切换流程，其中新的接入网关与 P-GW之间釆用 PMIPv6 协议， 如图 7所示， 具体步骤如下： 步骤 S701 , 新 BBERF ( New BBERF )接收到原 BBERF ( Old BBERF ) 发送的建立网关控制会话请求消息， 并且 New BBERF获得了用户标识 NAI, PDN标识 APN以及用于制定策略的接入网信息等；
步骤 S702, New BBERF向 vPCRF发送网关控制会话建立请求消息， 消 息中携带用户标识 NAI , PDN标识 APN , New BBERF的地址， UE和接入网 是否支持网络发起流程指示 NRS ' ( Network Requested Support , 网络请求支 持） 以及用于制定策略的接入网信息。 该消息请求建立的 Diameter会话表示 为 Gxx会话 2;
步骤 S703 , vPCRF根据 NAI判断用户为漫游用户并根据用户标识 NAI 和 PDN标识 APN并判断已经为该用户建立 S9会话和 S9子会话 Subsessionl。 因此 vPCRF向 hPCRF发送 S9会话修改指示消息， 并将 NRS'、 New BBERF 的地址以及用于制定策略的接入信息包含在 Subsessionl中；
步骤 S704, hPCRF根据 New BBERF的地址判断 UE发生了切换（即 BBERF 重选） ， 并签约信息、 接入网信息、 网络策略、 新的接入网信息等 UE修改之前的 PCC规则和 QoS规则。 同时根据 NRS'、 签约信息和网络策 略设定 IP-CAN会话新的 BCM，。 hPCRF向 vPCRF返回 S9会话建立确认消息， QoS规则、 BCM，和 New BBERF的地址包含在 Subsessionl中。 BCM，与之前 切换前的 BCM可能是不一样的；
步骤 S705 , vPCRF根据 New BBERF的地址判断 Subsessionl中的信息是 发送给 New BBERF的， 因此 vPCRF通过 Gxx会话 2发送网关控制会话建立 确认消息将 QoS规则和 BCM'发送给 New BBERF。 New BBERF安装 QoS规 则， 同时根据 BCM将其中指示的承载控制模式应用于请求建立的网关控制 会话。 同样在这种场景下， 新建立网关控制会话和修改的 IP-CAN会话是一 一对应的。 因此， 也可以认为 BBERF根据 BCM将其中指示的承载控制模式 应用于 IP-CAN会话；
步骤 S706 , New BBERF驻留的网关向 PCEF驻留的网关发送 IP-CAN会 话信令， 消息中携带 NAI和 APN。 该消息实现时通常是代理绑定更新消息； 步骤 S706可与步骤 S702同时发送。 步骤 S707 , PCEF驻留的网关根据用户标识和 PDN标识为 UE分配切换 前的 IP地址。 PCEF向 hPCRF发送 IP-CAN会话修改指示消息， 消息中携带 NAI、 APN和 IP Address。 该消息请求修改的 Diameter会话为图 5中建立的 Gx会话 1 ;
步骤 S708 , hPCRF将步骤 S704制定的 PCC规则发送给 PCEF； hPCRF可能会修改 S704步制定的 PCC规则和 QoS规则， 此时 hPCRF 将把修改后的 PCC规则发送 PCEF, 将修改后的 QoS规则经 vPCRF发送给 BBERF0
步骤 S709 , PCEF安装 PCC规则。 PCEF驻留的网关向 BBERF返回 IP-CAN 会话信令， 携带 IP地址。 该消息在实现时通常是代理绑定更新确认消息； 步骤 S710 , New BBERF返回建立网关控制会话应答消息。
BBERF可能再将所述承载控制模式发送给非 3GPP接入网中的其他网元 和 UE。 UE和可信任非 3GPP接入系统将根据 BCM'的指示， 来进行 IP-CAN 会话承载的管理， 如承载的建立、 修改和释放。
如图 3所示， 本发明实施例的漫游场景下承载控制模式的发送系统， 包 括 hPCRF和 vPCRF,
所述 hPCRF设置成设定 IP-CAN会话的承载控制模式， 并通过所述 IP-CAN会话对应的 S9子会话下发给 vPCRF。
所述 vPCRF设置成将所述承载控制模式发送给 PCEF或者 BBERF。 所述 hPCRF是设置成根据 NRS、接入网信息、签约信息和网络策略设定 所述 IP-CAN会话的承载控制模式。
如图 2所示， 本发明实施例的漫游场景下承载控制模式的发送系统， 包 括 hPCRF和 vPCRF,
所述 hPCRF设置成设定网关控制会话的承载控制模式，并通过所述网关 控制会话对应的 S9子会话下发给 vPCRF。
所述 vPCRF设置成将所述承载控制模式发送给 BBERF。
显然， 本领域的技术人员应该明白， 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现， 它们可以集中在单个的计算装置上， 或者分布 在多个计算装置所组成的网络上， 可选地， 它们可以用计算装置可执行的程 序代码来实现， 从而， 可以将它们存储在存储装置中由计算装置来执行， 或 者将它们分别制作成各个集成电路模块， 或者将它们中的多个模块或步骤制 作成单个集成电路模块来实现。 这样， 本发明不限制于任何特定的硬件和软 件结合。
当然， 本发明还可有其它多种实施例， 在不背离本发明精神及其实质的 但这些相应的改变和变形都应属于本发明所附的权利要求的保护范围。
工业实用性 与现有技术相比， 本发明使得 hPCRF能够为 UE建立的多个 IP-CAN会 话选择不同的承载控制模式并下发给 vPCRF, vPCRF可以进一步将承载控制 模式发送给相应的执行网元执行。

Claims

权 利 要 求 书
1、 一种漫游场景下承载控制模式的发送方法， 包括：
家乡策略控制与计费规则功能实体 hPCRF设定 IP连接接入网 IP-CAN会 话的承载控制模式， 并将所述 IP-CAN会话的承载控制模式通过所述 IP-CAN 会话对应的 S9子会话下发给拜访策略控制与计费规则功能实体 vPCRF;
或者， hPCRF设定网关控制会话的承载控制模式， 并将所述网关控制会 话的承载控制模式通过所述网关控制会话对应的 S9子会话下发给 vPCRF。
2、 如权利要求 1所述的方法， 其还包括：
所述 vPCRF将所述 IP-CAN会话的承载控制模式或所述网关控制会话的 承载控制模式发送给策略和计费执行功能实体 PCEF或者承载绑定和事件报 告功能实体 BBERF。
3、 如权利要求 1所述的方法， 其中， 设定 IP-CAN会话的承载控制模式 的步骤中， 所述 hPCRF是根据网络请求支持 NRS、接入网信息、 签约信息和 网络策略设定所述 IP-CAN会话的承载控制模式。
4、 如权利要求 3所述的方法， 其在设定 IP-CAN会话的承载控制模式的 步骤之前还包括： 所述 vPCRF通过所述 IP-CAN会话对应的 S9子会话将所 述 NRS发送给所述 hPCRF。
5、如权利要求 3所述的方法， 其在设定所述网关控制会话的承载控制模 式的步骤之前还包括： 所述 vPCRF通过所述网关控制会话对应的 S9子会话 将所述 NRS发送给所述 hPCRF。
6、 一种漫游场景下承载控制模式的发送系统， 其包括家乡策略控制与计 费规则功能实体 hPCRF和拜访策略控制与计费规则功能实体 vPCRF， 其中， 所述 hPCRF设置成设定 IP-CAN会话的承载控制模式， 并将所设定的承 7、 如权利要求 6所述的系统， 其中，
所述 vPCRF设置成将所述 IP-CAN会话的承载控制模式发送给 PCEF或 者 BBERF0
8、 如权利要求 6所述的系统， 其中，
所述 hPCRF是设置成根据 NRS、接入网信息、签约信息和网络策略设定 所述 IP-CAN会话的承载控制模式。
9、 一种漫游场景下承载控制模式的发送系统， 包括家乡策略控制与计费 规则功能实体 hPCRF和拜访策略控制与计费规则功能实体 vPCRF， 其中， 所述 hPCRF设置成设定网关控制会话的承载控制模式，并将所设定的承 载控制模式通过所述网关控制会话对应的 S9子会话下发给所述 vPCRF。
10、 如权利要求 9所述的系统， 其中，
所述 vPCRF设置成将所述承载控制模式发送给 BBERF。
PCT/CN2010/070349 2009-09-08 2010-01-25 漫游场景下承载控制模式的发送方法和系统 WO2011029289A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP10814891.7A EP2472918B1 (en) 2009-09-08 2010-01-25 Method, apparatus and system for transmitting a bearer control mode in roaming scenarios
US13/257,593 US8661145B2 (en) 2009-09-08 2010-01-25 Method and system for transmitting a bearer control mode in roaming scenarios

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2009101699120A CN102014517A (zh) 2009-09-08 2009-09-08 漫游场景下承载控制模式的发送方法和系统
CN200910169912.0 2009-09-08

Publications (1)

Publication Number Publication Date
WO2011029289A1 true WO2011029289A1 (zh) 2011-03-17

Family

ID=43731954

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/070349 WO2011029289A1 (zh) 2009-09-08 2010-01-25 漫游场景下承载控制模式的发送方法和系统

Country Status (4)

Country Link
US (1) US8661145B2 (zh)
EP (1) EP2472918B1 (zh)
CN (1) CN102014517A (zh)
WO (1) WO2011029289A1 (zh)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931928B (zh) * 2009-06-19 2014-08-13 中兴通讯股份有限公司 漫游场景下单apn多pdn连接的策略计费控制的方法及系统
CN101959257B (zh) * 2009-07-20 2013-06-12 中兴通讯股份有限公司 一种承载绑定和事件报告功能的重选方法
US8948007B2 (en) * 2011-06-13 2015-02-03 Verizon Patent And Licensing Inc. Interoperable quality of service pre-negotiation
US8948750B1 (en) * 2011-09-19 2015-02-03 Cellco Partnership LTE roaming APN adaptation
CN103167562B (zh) * 2011-12-16 2016-04-27 中国移动通信集团上海有限公司 实现WLAN终端端到端QoS控制的方法、装置及系统
CN103209401B (zh) 2012-01-12 2018-07-24 中兴通讯股份有限公司 一种融合网络中策略控制方法及系统
US9749933B2 (en) * 2012-06-29 2017-08-29 Cable Television Laboratories, Inc. Dynamic network selection
CN103796250B (zh) * 2012-10-31 2018-06-12 中兴通讯股份有限公司 确定回传网络中wlan业务qos的方法和系统
WO2015051536A1 (zh) 2013-10-11 2015-04-16 华为技术有限公司 信息传输方法和装置
US20150244537A1 (en) * 2014-02-23 2015-08-27 Tata Communications (America) Inc. System and methods for enabling policy exchange across multiple carriers
EP3182654B1 (en) * 2014-09-05 2019-11-06 Huawei Technologies Co., Ltd. Offload strategy negotiation method and apparatus
CN110692281B (zh) * 2017-07-10 2023-10-13 摩托罗拉移动有限责任公司 移动网络中的多接入数据连接

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101272534A (zh) * 2008-05-08 2008-09-24 中兴通讯股份有限公司 一种隐藏拜访地网络拓扑结构的策略计费控制的方法
CN101459951A (zh) * 2008-04-11 2009-06-17 中兴通讯股份有限公司 一种承载绑定和事件报告功能策略控制的方法及系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6791958B2 (en) * 2002-02-06 2004-09-14 Motorola, Inc. Method of routing control information and bearer traffic between a wireless communications device and infrastructure equipment
US20030214958A1 (en) * 2002-04-12 2003-11-20 Lila Madour Linking of bearer and control for a multimedia session
CN101496387B (zh) * 2006-03-06 2012-09-05 思科技术公司 用于移动无线网络中的接入认证的系统和方法
JP5181472B2 (ja) * 2006-04-21 2013-04-10 日本電気株式会社 通信制御方法
CN101355793B (zh) * 2007-07-27 2011-08-31 华为技术有限公司 识别用户设备的方法和装置及临时标识传递和分配方法
US8320329B2 (en) * 2008-03-24 2012-11-27 Cisco Technology, Inc. Policy for a roaming terminal based on a home internet protocol (IP) address
PT2301301T (pt) * 2008-04-30 2017-01-09 ERICSSON TELEFON AB L M (publ) Gestão de modo de controlo de portador (apenas rede ou apenas utilizador) numa transferência intersistema

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101459951A (zh) * 2008-04-11 2009-06-17 中兴通讯股份有限公司 一种承载绑定和事件报告功能策略控制的方法及系统
CN101272534A (zh) * 2008-05-08 2008-09-24 中兴通讯股份有限公司 一种隐藏拜访地网络拓扑结构的策略计费控制的方法

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LI, HAIHUA: "Research and Progress of Transmission Resource Control and Mobility Management", TELECOMMUNICATIONS TECHNOLOGY, no. 8, August 2009 (2009-08-01), pages 23 - 26, XP008167776 *
ZHAO, YONG ET AL: "Introduction and Standard Progress of Policy and Charging Control Technologies", TELECOMMUNICATIONS NETWORK TECHNOLOGY, no. 6, June 2009 (2009-06-01), pages 33 - 36, XP008159038 *

Also Published As

Publication number Publication date
EP2472918A1 (en) 2012-07-04
US8661145B2 (en) 2014-02-25
CN102014517A (zh) 2011-04-13
EP2472918A4 (en) 2018-01-10
US20120158977A1 (en) 2012-06-21
EP2472918B1 (en) 2019-05-15

Similar Documents

Publication Publication Date Title
EP2339781B1 (en) Method and system for realizing the policy and charging control in the multiple packet data networks (pdn) scene
US9137652B2 (en) Method for implementing policy and charging control in a roaming scene
US8799440B2 (en) Policy and charging control method and system for multi-PDN connections of single APN
WO2011029289A1 (zh) 漫游场景下承载控制模式的发送方法和系统
EP2790455A1 (en) Policy control method and system for converged network
WO2007143940A1 (fr) procédé, système et équipement de contrôle des conditions d'utilisation et de la facturation lorsque l'utilisateur est mobile
EP2456278A1 (en) Method and system for deleting redundant information of home policy and charging rules function
WO2010108356A1 (zh) 一种终端通过多接入网接入的计费方法和系统及上报方法
WO2010006491A1 (zh) 一种事件触发器的下发和安装方法
WO2011085621A1 (zh) 业务处理方法及系统
WO2015055063A1 (zh) 应用接入控制方法及应用功能实体装置
WO2011026385A1 (zh) 一种本地疏导漫游场景在线计费的方法和系统
WO2011091682A1 (zh) 增强的策略和计费控制的方法及系统、策略和计费控制（pcc）系统
CN102111740B (zh) 一种支持多接入的策略计费控制方法和系统
WO2014107985A1 (zh) 漫游本地业务的在线计费方法、h-ocs及v-ocs
WO2014094488A1 (zh) 漫游本地业务的计费策略方法及装置
CN102098653A (zh) 一种实现服务质量控制的方法及系统
WO2011018020A1 (zh) 控制pcrf负载均衡的方法、系统及重定向dra
WO2013135213A1 (zh) Tdf会话的处理方法及pcrf
WO2012129992A1 (zh) 被赞助数据连接的处理方法及策略与计费规则功能实体
CN102791042B (zh) S9子会话建立方法、系统及pcrf
US9532205B2 (en) Method and system for identifying application detection and control function mode
WO2011029349A1 (zh) 多承载绑定和事件报告功能的处理方法及系统
WO2014079323A1 (zh) 一种漫游本地业务功能实现方法、装置和系统
CN101378522B (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: 10814891

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 13257593

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2010814891

Country of ref document: EP