WO2010078761A1 - 基于多接入技术的策略计费控制方法、装置和系统 - Google Patents
基于多接入技术的策略计费控制方法、装置和系统 Download PDFInfo
- Publication number
- WO2010078761A1 WO2010078761A1 PCT/CN2009/073755 CN2009073755W WO2010078761A1 WO 2010078761 A1 WO2010078761 A1 WO 2010078761A1 CN 2009073755 W CN2009073755 W CN 2009073755W WO 2010078761 A1 WO2010078761 A1 WO 2010078761A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- policy
- access network
- function entity
- network connection
- charging
- Prior art date
Links
Classifications
-
- 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/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
- H04L12/1457—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network using an account
Definitions
- the present invention relates to the field of communications, and in particular to a policy charging control method, apparatus, and system based on multiple access technologies.
- EPS Evolved Packet System
- E-UTRAN Evolved Universal Terrestrial Radio Access Network
- MME Mobility Management Entity
- MME Mobility Management Entity
- MME Monthly Gateway
- Packet Data Network Gateway Packet
- P-GW Packet Data Network Gateway
- HSS Home Subscriber Server
- AAA 3GPP Authentication 4
- the server and the Policy and Charging Rules Function are entities and other supporting nodes.
- the MME is responsible for control planes such as mobility management, non-access stratum signaling processing, and user mobility management context management
- S-GW is An access gateway device connected to the E-UTRAN, which forwards data between the E-UTRAN and the P-GW, and is responsible for buffering paging waiting data
- the P-GW is an EPS and packet data network (Packet Data Network) A border gateway called PDN), responsible for PDN access and forwarding data between EPS and PDN.
- PCRF is a policy and charging rule function entity. It receives the interface Rx and the carrier network. The service is connected to the service network.
- the gateway device in the network through the Gx/Gxa/Gxc interface. It is responsible for initiating the establishment of the IP bearer and guaranteeing the quality of service of the service data.
- the cartridge is called QoS) and performs charging control.
- EPS supports interworking with non-3GPP systems. Interworking with non-3GPP systems is implemented through the S2a/b/c interface, and the P-GW acts as an anchor between 3GPP and non-3GPP systems.
- non-3GPP systems are classified into trusted non-3GPP IP access and untrusted non-3GPP IP access. Trusted non-3GPP IP access can be directly connected to the P-GW through the S2a interface; Any non-3GPP IP access needs to be connected to the P-GW through an Evolved Packet Data Gateway (evolved Packet Data Gateway).
- Evolved Packet Data Gateway Evolved Packet Data Gateway
- the interface between the ePDG and the P-GW is S2b, and the S2c provides user equipment (User Equipment, The user-side control and mobility support between the UE and the P-GW, the supported mobility management, and the support for dual-stack mobile IPv6 (Moblie Internet Protocol Version 6 Support for Dual Stack Hosts and Routers, the tube is called DSMIPv6).
- the Policy and Charging Enforcement Function (PCEF) entity exists in the P-GW, and the Gx interface between the PCRF and the P-GW (see Figure 1) exchanges information.
- PCEF Policy and Charging Enforcement Function
- the S-GW When the interface between the P-GW and the S-GW is based on PMIPv6, the S-GW also has a Bearer Binding and Event Report Function (BBERF) entity to perform the service data flow.
- BBERF Bearer Binding and Event Report Function
- QoS control, the S-GW and the PCRF exchange information through the Gxc interface (see Figure 1).
- the BBERF When accessed through a trusted non-3GPP access system, the BBERF is also resident in the trusted non-3GPP access gateway.
- the trusted non-3GPP access gateway exchanges information with the PCRF through the Gxa interface (see Figure 1).
- the S9 interface functions as an interface between the home PCRF and the visited PCRF.
- the application function (Application Function, called AF) is provided for the UE, and is sent to the PCRF through the Rx interface for formulating policies and charging.
- Control the business information of the Policy and Charging Control (PCC) policy.
- the corresponding PDN network can be found by the access point name (Access Point Name, called APN).
- APN Access Point Name
- IP Connectivity Access Network IP Connectivity Access Network
- cartridge IP-CAN IP Connectivity Access Network
- the UE accesses one PDN through multiple access networks at the same time, that is, multiple access.
- 2 is a schematic diagram of a multiple access scenario according to the related art. As shown in FIG. 2, the UE simultaneously passes the same P- through the non-3GPP IP access network and the 3GPP access network under the coverage of the non-3GPP and 3GPP access. The GW accesses the PDN. In this scenario, the P-GW allocates an IP address to the UE, that is, there is only one IP-CAN session between the UE and the PDN. Thus, the data streams of different services requested by the UE can be transmitted in the access network suitable for its transmission.
- a non-3GPP access network is a wireless fidelity (Wireless Fidelity)
- a Hypertext Transfer Protocol Hypertext Transfer Protocol
- a File Transfer Protocol File Transfer Protocol
- VoIP Voice over IP
- VoIP traffic data flow can pass 3GPP Send to the UE.
- services with lower real-time requirements such as HTTP and FTP can take advantage of lower WiFi tariffs
- services with higher real-time requirements for VoIP can play 3GPP QoS control, and the advantages of mobility management are better.
- the network needs to reserve corresponding resources according to the corresponding QoS attributes of the service.
- there may be two methods for reserving resources one is a reserved resource request initiated by a UE, and the other is a reserved resource request initiated by a network.
- the UE determines in which access network to transmit the service data flow and requests the network to reserve resources; however, how is the resource reservation initiated by the network? Resource reservation is performed in a suitable access network, and no effective solution has been proposed yet.
- SUMMARY OF THE INVENTION The present invention has been made in view of the fact that when a UE accesses through multiple access networks at the same time, the network cannot propose a resource reservation process according to a service in a suitable access network connection.
- the main purpose of the present invention is An improved policy charging control scheme is provided to solve at least one of the above problems.
- a policy charging control method based on multiple access technologies includes: the policy charging execution function entity determines an access network connection for the service data stream transmission, and notifies the determined access network connection to the policy and charging. Rule function entity.
- the method further includes: the policy and charging rule function entity sending the corresponding quality of service rule to the access The bearer binding and event reporting function entity in the network connection, so that the bearer binding and event reporting function entity initiates a resource reservation or resource release process according to the quality of service rule.
- the policy charging execution function entity determines the access network connection of the service data stream transmission according to the configuration information or the network policy.
- the policy charging execution function entity notifying the determined access network connection to the policy and charging rule function entity includes: the policy charging execution function entity sending the binding indication to the policy and charging rule function entity, where The indication carries the information that uniquely distinguishes the access network connection.
- the policy charging execution function entity sends a binding indication to the policy and charging rule function entity by using a network protocol connection access network session establishment indication message.
- the policy charging execution function entity sends the binding indication by sending the access network session modification indication message, the policy charging rule confirmation message or the policy charging rule request message through the network protocol.
- the access network connection is uniquely identified by one of the following: a network protocol connection access network type and/or a radio access technology type, a network protocol address used to indicate an access network connection.
- the policy charging execution function entity includes: a determining module, configured to determine an access network connection for the service data stream transmission according to the configuration information; and a notification module, configured to notify the policy and the access network connection information determined by the determining module to the policy and Billing rule function entity.
- a policy charging control system based on multiple access technologies is provided.
- the policy-based charging control system based on the multiple access technology includes a policy charging execution function entity and a policy and charging rule function entity, where the policy charging execution function entity includes: a determining module, configured to determine a service An access network connection for data stream transmission; a notification module, configured to notify the policy and charging rule function entity of the access network connection determined by the determining module; the policy and charging rule function entity includes: a receiving module, configured to receive the policy from the policy The charging execution function entity access network connection information; the sending module, configured to send the corresponding service quality rule to the bearer binding and event reporting function in the access network connection according to the information about the access network connection received by the receiving module Entity, so that the bearer binding and event reporting function entity initiates a resource reservation or resource release procedure according to the quality of service rules.
- the policy charging execution function entity includes: a determining module, configured to determine a service An access network connection for data stream transmission; a notification module, configured to notify the policy and charging rule function entity of the access network connection determined by the determining module; the policy
- the method for determining the access network connection of the service data stream transmission and notifying the PCRF by using the PCEF solves the problem that when the UE accesses through multiple access networks at the same time, the network cannot be used according to the service in the appropriate access network.
- the problem of initiating the resource reservation process is implemented, and when the UE accesses through multiple access networks at the same time, the network may initiate a resource reservation process in a suitable access network according to the service.
- 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 a multiple access scenario according to the related art
- FIG. 3 is a flowchart of a multiple access procedure according to the related art
- FIG. 5 is a flowchart of a multiple access technology-based access processing method according to Embodiment 1 of the present invention
- FIG. 5 is a flowchart of an access processing method based on multiple access technology according to Embodiment 2 of the present invention
- FIG. 7 is a structural block diagram of a policy charging execution function entity according to an embodiment of the present invention
- FIG. 8 is a structural block diagram of a policy charging execution function entity according to an embodiment of the present invention
- a structural block diagram of a policy charging control system based on multiple access technologies. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention provides a multi-functional solution in consideration of the fact that when a UE accesses multiple access networks at the same time, the gateway cannot initiate a resource reservation process in a suitable access network according to the service.
- the PCEF determines the access network connection for the service data stream transmission and notifies the PCRF, and the PCRF ⁇ ) sends the corresponding QoS rule to the BBERF in the access network connection, and the BBERF installs the QoS. Rules, and initiate a resource reservation process in the access network according to QoS rules.
- a multi-access procedure of the related art related to the embodiments of the present invention is described below.
- 3 is a flowchart of a multiple access procedure according to the related art. As shown in FIG. 3, the dual coverage when the UE is in the 3GPP access network and the trusted non-3GPP access network is described.
- the UE After the range, the UE establishes a connection to the default PDN through the 3GPP access network and the trusted non-3GPP access network at the same time.
- the ⁇ protocol is adopted between the S-GW and the P-GW through the 3GPP access
- the ⁇ 6 protocol is adopted between the trusted non-3GPP access network management system and the P-GW when the non-3GPP access is trusted.
- the multiple access process specifically includes the following steps 301 to 323: Step 301: The UE sends an attach request message to the MME. Step 302: The MME initiates an authentication process for the UE, and exchanges authentication related information between the MME and the HSS according to the need.
- the MME initiates a location update process, and the contract data of the HSS UE is sent to the MME.
- the HSS sends the selection information of the P-GW to the MME, where the selection information includes a default APN.
- the MME selects the P-GW according to the APN, and at the same time, the MME selects the S-GW.
- Step 303 The MME sends a default bearer setup request message to the S-GW, where the default bearer setup request message carries the APN and the IP address of the selected P-GW.
- Step 304 The S-GW that resides in the BBERF carries the identifiers NAI and APN of the UE in the "Gateway Control Session Establishment Indication" message sent to the PCRFF.
- Step 305 The PCRF formulates PCC rules and QoS rules according to the user's subscription data, network policy, and bearer attributes. At the same time, it may also formulate corresponding event triggers, and the PCRF triggers QoS rules and events through a "gateway control session establishment confirmation" message.
- the device sends to the S-GW, and the S-GW installs QoS rules and event triggers.
- Step 306 The S-GW sends a "Proxy Binding Update” request message to the P-GW, where the "Proxy Binding Update” request message carries the NAI and the APN. It should be noted that step 306 can be performed after receiving the message of step 303 without waiting for the response of step 305.
- Step 307 The P-GW camping on the PCEF sends an "IP-CAN session establishment indication" message to the PCRF, where the message "IP-CAN session establishment indication" carries the NAI, APN, and carries the P-GW.
- Step 308 the PCRF returns an "IP-CAN Session Establishment Confirmation" message to the P-GW, wherein the "IP-CAN Session Establishment Confirmation" message carries the corresponding PCC rule and event trigger, PCEF
- the PCC rules and event triggers are installed; it should be noted that if the information carried in the IP-CAN session establishment indication message in step 307 causes the QoS rule to change, the PCRF will provide a new QoS rule through the gateway control and the QoS rule providing message. Sending to the trusted non-3GPP access gateway, if the event trigger has also changed, a new event trigger is provided, which can be performed concurrently with step 308. BBERF returns a confirmation message after receiving the message.
- Step 309 The P-GW returns a "Proxy Binding Acknowledgement" message to the S-GW, where the "Proxy Binding Acknowledgement” message carries the IP address assigned by the P-GW to the UE.
- Step 310 The S-GW returns a default bearer setup confirmation message to the MME, where the default bearer setup acknowledgement message carries the IP address of the UE.
- Step 311 The MME, the eNodeB, and the UE interact to establish a radio bearer.
- Step 312 After the radio bearer is established, the MME sends an update bearer request to the S-GW, notifies the eNodeB of the address information, and the S-GW returns a response message.
- Step 313 The UE performs a specific non-3GPP access procedure to access the trusted non-3GPP access network.
- Step 314 After the UE accesses the trusted non-3GPP access network, request the EPS access authentication from the HSS/AAA; after receiving the EPS access authentication request, the HSS/AAA authenticates the requesting UE; After the HSS/AAA completes the authentication of the UE, the PSN that is selected in the 3GPP access and the APN signed by the UE are sent back to the trusted non-3GPP access gateway, where the APN includes the default APN.
- Step 315 After the authentication succeeds, the attach procedure of layer 3 is triggered, and the message sent by the UE to the trusted access gateway carries a Multiple Access indication.
- Step 316 The trusted non-3GPP access gateway that resides in the BBERF sends a "Gateway Control Session Establishment Indication" message to the PCRF, where the "Gateway Control Session Establishment Indication" message carries the identifier of the UE, NAI, APN, and Multiple Access. Instructions.
- Step 317 The PCRF determines that the UE is multiple access according to the Multiple Access indication, and associates the message with the messages of step 304 and step 307 according to the NAI and the APN, thereby associating the information established by the three messages in the PCRF to the same IP-CAN session.
- PCC rules and QoS rules are formulated for services to be migrated to IP-CAN sessions through non-3GPP access, and corresponding event triggers may also be formulated; PCRF passes the "gateway" The Control Session Establishment Acknowledgement message sends these newly formulated QoS rules and event triggers to BBERF, which installs QoS rules and event triggers.
- Step 318 The trusted non-3GPP access gateway sends a "proxy binding update" request message to the P-GW, where the proxy binding update, the request message carries the NAI, APN, and Multiple Access indications, and step 318 can After receiving the message of step 315, it does not have to wait for the response of step 317.
- Step 319 the P-GW camping on the PCEF uses the Diameter session established in step 307 to send an "IP-CAN session 4 tampering indication" to the PCRF. " message, wherein the "IP-CAN session 4 tampering" message carries the NAI, APN, IP address.
- Step 320 the PCRF returns an "IP-CAN session tampering confirmation" message to the P-GW, where
- the "IP-CAN Session Modification Confirmation” message carries the PCC rules and event triggers set in step 317, and the P-GW updates the PCC rules and event triggers. It is possible for the PCRF to update the PCC rules again according to the information carried in step 319. It should be noted that if the information carried in the IP-CAN session modification indication message in step 319 causes the QoS rule defined in step 317 to change, the PCRF will send a new QoS rule to the device through the gateway control and QoS rule providing message.
- Trusting the non-3GPP access gateway if the event trigger has also changed, providing a new event trigger, the message can be sent simultaneously with step 320.
- the trusted non-3GPP access gateway returns the gateway control and QoS rule provision after receiving the message.
- the ACK message is carried by the P-GW to the IP address of the UE.
- the trusted non-3GPP access gateway returns a response message to the UE, where the response message carries the IP of the UE.
- an access processing method based on multiple access technologies is provided.
- the method is applied to a resource reservation process initiated by a network side in a multiple access scenario, where the method includes:
- the PCEF determines the access network connection for the service data stream transmission, and notifies the determined access network connection to the PCRF, wherein the PCEF can determine the access network connection for the service data stream transmission according to the configuration information or the network policy.
- the PCRF sends the corresponding QoS rule to the BBERF in the access network connection, so that the BBERF installs the QoS rule, and initiates the resource reservation process or the resource release process according to the QoS rule.
- the access network connection is uniquely identified by one of the following information: an IP-CAN type and/or a wireless access access type, a network protocol address used to indicate an access network connection, and the foregoing configuration information may be preset by the system. .
- the PCEF may send a binding indication to the PCRF, where the binding indication carries information about the access network connection.
- the PCEF may send the binding indication to the PCRF through one of the following messages: an IP-CAN session establishment indication message, an IP-CAN session modification indication message, a policy charging rule acknowledgement message, and a policy charging rule request message.
- the sending of the binding indication may be processed according to the following conditions: (1) When establishing an IP-CAN session, the PCEF may send a binding indication to the PCRF through an IP-CAN session establishment indication message.
- Embodiment 1 This embodiment describes the attachment based on the flow shown in FIG. 4 is a flowchart according to Embodiment 1 of the present invention. As shown in FIG. 4, it is described that the UE accesses multiple times through E-UTRAN and a trusted non-3GPP access network, and establishes an IP-CAN session to access a new one.
- Step 401 The UE requests to access a new service, and sends a request message to the AF 1 that provides the service information. After receiving the request message, the AF1 establishes a new AF session and provides service information. The corresponding service data stream (Service Data Function, called SDF) is SDF1. Further, the request message may further carry an indication that the UE selects to transmit the target access network connection of the SDF 1.
- Step 402 The AF 1 sends a service application message to the PCRF, where the service application message carries the IP address of the UE that accesses the service.
- the service application message may further carry the identifier of the UE and the target access network that the UE selects to transmit the SDF1. Instructions for connection.
- Step 403 The PCRF receives the service application message and saves the service information.
- Step 404 The PCRF returns an acknowledgement message to the AF 1.
- Step 405 The PCRF identifies the IP-CAN session established by the process in FIG. 3 according to the IP address of the UE and the identifier of the UE.
- the PCRF formulates PCC rules (Rulesl) based on the service characteristics of the user's subscription information, network policy, and service information.
- Step 406 The PCRF sends a PCC Rules1 to the PCEF in the P-GW through the policy charging rule, and the PCEF installs the PCC Rules1 and determines the data flow of the service to be transmitted through the E-UTRAN according to the configuration information or the network policy, and the PCC rule is adopted. Associated with an E-UTRAN access connection. When the PCEF detects the application data flow of the PCC Rules1, these service data flows are sent to the connection through the E-UTRAN access network.
- Step 407 The PCEF returns an acknowledgement message, and carries a binding indication in the acknowledgement message, where the binding indication indicates a binding relationship between the service data flow determined by the PCEF and the access network connection of the transport service data flow.
- the binding indication identifies the access network connection determined by the PCEF by carrying information that uniquely distinguishes the connections of the access networks.
- the binding indication carries an IP-CAN type and/or a radio access technology type (RAT Type),
- RAT Type radio access technology type
- the IP-CAN type value is 3GPP-EPS
- the RAT Type value is E-URTAN.
- the IP address of the S-GW/BBERF can also be carried to identify the access network connection.
- the other information that uniquely distinguishes the access network connections is also applicable.
- the PCRF determines, according to the binding indication, that the PCEF determines that the service data stream is transmitted through the E-UTRAN.
- the QoS Rules 1 corresponding to the PCC Rules1 are determined according to the access characteristics of the E-UTRAN, the user subscription information, and the network policy.
- PCRF passes to BBERF in S-GW Gateway Control and QoS Rules provide messaging QoS Rules 1. If the PCRF needs to modify the PCC Rules 1 defined in step 405, the PCRF will update the previously issued PCC rules to the PCEF through the policy charging rule providing message.
- the BBERF installs QoS Rules 1.
- the E-UTRAN executes the corresponding policy and initiates a resource reservation process. The BBERF returns a confirmation message to the PCRF.
- the IKEA PCEF carries a binding indication in the acknowledgment message returned to the PCRF, indicating that when the PCEF detects When applying the service data stream of PCC Rules1, these service data streams are to be sent to the access connection through the trusted non-3GPP access network.
- the implementation of the binding indication may be by carrying the IP-CAN Type and/or RAT Type of the trusted non-3GPP access network. If the trusted non-3GPP access network is WiMAX, the Bay' J IP-CAN Type is WiMAX. The implementation of the binding can also be carried by carrying the IP address of the trusted non-3GPP access gateway/BBERF.
- the PCRF formulates a corresponding QoS Rules 1 according to the binding indication, and sends QoS Rules 1 to the BBERF in the trusted non-3GPP access gateway.
- BBERF installs QoS Rules 1 to initiate a resource reservation process in a trusted non-3GPP access network.
- the processing method and process at this time are similar to the process described above, except that the PCEF determines the service data flow.
- connection indication can also carry the IP address of the ePDG/BBERF through the untrusted non-3GPP access network connection, and the PCRF sends the QoS Rules 1 to the BBERF in the ePDG.
- Embodiment 2 This embodiment includes the following two parts:
- the UE establishes a multi-access IP-CAN session, except that: in the "IP-CAN session modification indication" in step 319, the message carries not only the NAI, the APN, and the IP address.
- the binding indication is also carried in.
- the indication is represented by carrying the IP-CAN type and/or the radio access type RAT Type, which are represented by 3GPP-EPS and E-UTRAN, respectively.
- the binding indication can also be carried by the IP address carrying the S-GW/BBERF, PCRF.
- the binding indication is saved. Of course, other information that uniquely distinguishes each access network connection is also applicable.
- the binding indication can also be performed through step 307.
- the "IP-CAN Session Establishment Indication" message is sent to the PCRF, which is saved by the PCRF.
- FIG. 5 is a flowchart of Embodiment 2 of the present invention.
- the method includes the following steps 501 to 509: Step 501: The UE requests to access a new service, and sends a request message to the AF 1 that provides the service information. After receiving the request message, AF1 establishes a new AF session and provides service information, and the corresponding service data flow is SDF1. Further, the request message may further carry an indication that the UE selects a target access network connection for transmitting the SDF1.
- Step 502 The AF 1 sends a service application message to the PCRF, where the service application message carries the IP address of the UE that accesses the service. Further, the service application message may further carry the identifier of the UE and the UE selects the target of the transmission SDF 1. Instructions for connecting to the network.
- Step 503 The PCRF receives the service application message and saves the service information. In step 504, the PCRF returns an acknowledgement message to AF1.
- Step 505 The PCRF identifies the established IP-CAN session according to the IP address of the UE and the identifier of the UE.
- the PCRF determines that the UE is multi-accessed through a trusted non-3GPP access network (e.g., WLAN) and E-UTRAN. And, according to the binding indication obtained from the PCEF, it is determined that the resource reservation is performed in the access network connection of the E-UTRAN.
- the PCRF develops PCC Rules 1 and QoS Rules1 according to the characteristics of the access network, the subscription information of the user, the network policy, and the service information.
- Step 506 Since the resource reservation is performed in the access network connection of the E-UTRAN, the PCRF sends the QoS Rules 1 to the BBERF in the S-GW through the gateway control and the QoS rule providing message.
- step 507 the BBERF installs QoS Rules 1 , and the E-UTRAN executes a corresponding policy to perform resource reservation.
- the BBERF returns a confirmation message to the PCRF.
- the PCEF receives the binding indication and then modifies the binding in step 508, the PCEF will return a new binding indication to the PCRF in step 509. The PCRF then performs the corresponding 4 tampering.
- the binding indication implementation may carry the trusted The IP-CAN Type and/or RAT Type of the non-3GPP access network connection. If the trusted non-3GPP access network is WiMAX, the IP-CAN Type is WiMAX, and the binding indication can also carry the trusted non-3GPP. IP address of the access gateway/BBERF.
- the PCRF learns that the network-initiated resource reservation is to be performed in the connection through the trusted non-3GPP access network, that is, the service data flow is transmitted through the connection of the trusted non-3GPP access.
- the processing method and process at this time are similar to the process described above, except that:
- the binding indication can also carry the IP address of the ePDG/BBERF, and the PCRF sends QoS Rules 1 to the BBERF in the ePDG. It can be seen that the difference between the first embodiment and the second embodiment is as follows: In the first embodiment,
- the PCEF makes a decision for each service requested by the UE, determines the access network for the service data stream transmission, and then notifies the PCRF. In the second embodiment, the PCEF determines that all data flows of the UE that need to initiate the resource reservation service by the network are passed. An access network transmits a notification PCRF.
- Embodiment 3 This embodiment describes that when the P-GW decides to disconnect the UE through the E-UTRAN access or decides to change the binding relationship, the SDF service data stream is migrated to the UE and established through the trusted non-3GPP access. Connected, resulting in a flow chart that changes the data flow path.
- FIG. 6 is a flowchart of a third embodiment of the present invention. As shown in FIG.
- Step 601 The PCEF receives an internal trigger or an external trigger in the P-GW, requesting to migrate the SDF1 to Trusted non-3GPP access. When the PCEF detects the application data flow of the PCC Rules, these traffic data flows are sent to the connection accessed through the trusted non-3GPP access network.
- Step 602 The PCEF sends a policy charging rule request message to the PCRF, where the policy charging rule request message carries a binding indication that migrates the SDF1 to the trusted non-3GPP access network, and the binding indication indicates that the binding is performed.
- Step 603 After receiving the policy charging rule request message, the PCRF learns, according to the binding indication, that the PCEF determines that the SDF1 is transmitted through the trusted non-3GPP access network, and re-establishes the PCC Rules according to the access characteristics of the trusted non-3GPP access network.
- the PCRF sends the gateway control to the BBERF in the S-GW.
- the QoS rule provides an acknowledgment message carrying information indicating that the BBERF deletes the QoS Rules 1.
- Step 605 The BBERF returns an acknowledgment message to the PCRF.
- Step 606 the PCRF sends the QoS Rulesl 'to the trusted by the gateway control and the QoS rule providing message. BBERF in the non-3GPP access gateway.
- the BBERF installs QoS Rulesl' and returns an acknowledgment message to the PCRF.
- the UE establishes IP simultaneously through E-UTRAN and untrusted non-3GPP access network multiple access.
- the scenario of the CAN session, the method for the IPF to bind the IP data flow of the service to the access is similar to the above embodiment, and will not be described again.
- the scenario of establishing an IP-CAN session through E-UTRAN (where the GTP protocol is adopted between the S-GW and the P-GW) and the non-3GPP access network multiple access is similar to the above embodiment, and is no longer The difference is that the PCRF does not need to send the corresponding QoS Rules to the BBERF in the S-GW.
- FIG. 7 is a structural block diagram of a PCEF according to an embodiment of the present invention. As shown in FIG. 7, the PCEF includes: a determining module 72.
- the determining module 72 is configured to determine an access network connection for the service data stream transmission according to the configuration information or the network policy, where the foregoing configuration information may be preset by the system; the notification module 74 is connected to the determining module 72, and is configured to determine the module.
- the determined access network connection notification is sent to the PCRF, wherein the access network connection can be represented by one of the following information: an IP-CAN type and/or a wireless access type, a network protocol address used to indicate an access network connection.
- a PCEF of an access network that can determine a service data stream transmission is provided, and the PCEF notifies the determined access network connection to the PCRF, so that the PCRF sends the corresponding QoS rule to the BBERF in the access network connection.
- the BBERF installs the QoS rules and initiates a resource reservation process or a resource release process according to the QoS rules.
- FIG. 8 is a structural diagram of a policy-based charging control system based on a multi-access technology according to an embodiment of the present invention. As shown in FIG. 8, the system includes PCEF 2 and PCRF 4, and the following structure is performed. A detailed description.
- the PCEF 2 includes: a determining module 22, configured to determine an access network connection for the service data stream transmission according to the configuration information; the notification module 24 is connected to the determining module 22, and configured to obtain the access network connection notification determined by the determining module 22 PCRF.
- the PCEF 2 can be implemented using the PCEF of Figure 7.
- the PCRF 4 is coupled to the PCEF 2 and includes: a receiving module 42 for receiving information of an access network connection from the PCEF; a transmitting module 44 coupled to the receiving module 42 for receiving information of the access network connection according to the module 42
- the corresponding quality of service rule is sent to the BBERF in the access network connection, so that the BBERF initiates the resource reservation or resource release process according to the QoS rule.
- the method for determining the access network connection of the service data stream transmission and notifying the PCRF by using the PCEF solves the problem that when the UE accesses through multiple access networks at the same time, the network cannot be based on The service initiates a resource reservation process in a suitable access network connection, and thus, when the UE accesses through multiple access networks at the same time, the network can initiate resource pre-initiation in a suitable access network connection according to the service. Stay the process.
- a general purpose computing device which can be centralized on a single computing device, or distributed.
- the invention is not limited to any specific combination of hardware and software.
- the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Description
基于多接入技术的策略计费控制方法、 装置和系统 技术领域 本发明涉及通信领域, 具体而言, 涉及一种基于多接入技术的策略计费 控制方法、 装置和系统。 背景技术 第三代合作伙伴计划( 3rd Generation Partnership Project, 筒称为 3GPP ) 演进的分组系统 (Evolved Packet System , 筒称为 EPS ) 包括如下网元: 演 进的通用移动通信系统陆地无线接入网 (Evolved Universal Terrestrial Radio Access Network, 筒称为 E-UTRAN )、 移动管理单元 ( Mobility Management Entity, 筒称为 MME )、 月 务网关 ( Serving Gateway , 筒称为 S-GW )、 分组 数据网络网关( Packet Data Network Gateway, 筒称为 P-GW或者 PDN GW)、 归属用户月 务器 ( Home Subscriber Server, 筒称为 HSS )、 3GPP的认证 4受权 计费 ( Authentication、 Authorization and Accounting , 筒称为 AAA )月^务器, 策略和计费规则功能 ( Policy and Charging Rules Function, 筒称为 PCRF ) 实 体及其他支撑节点。 图 1是根据相关技术 EPS的系统架构示意图, 如图 1所示, MME负责 移动性管理、 非接入层信令的处理和用户移动管理上下文的管理等控制面的 相关工作; S-GW是与 E-UTRAN相连的接入网关设备,在 E-UTRAN和 P-GW 之间转发数据 , 并且负责对寻呼等待数据进行緩存; P-GW则是 EPS与分组 数据网络 ( Packet Data Network, 筒称为 PDN ) 网络的边界网关, 负责 PDN 的接入及在 EPS与 PDN间转发数据等功能; PCRF是策略和计费规则功能实 体, 它通过接收接口 Rx和运营商网络十办议 ( Internet Protocol, 筒称为 IP ) 业务网络相连, 获取业务信息, 此外, 它通过 Gx/Gxa/Gxc接口与网络中的 网关设备相连, 负责发起 IP承载的建立 , 保证业务数据的服务质量( Quality of Service, 筒称为 QoS ), 并进行计费控制。
EPS 支持与非 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提供了 用户设备 ( User Equipment , 筒称为 UE )与 P-GW之间的用户面 目关的控制 和移动性支持, 其支持的移动性管理 ¼、议为支持双栈的移动 IPv6 ( Moblie Internet Protocol Version 6 Support for Dual Stack Hosts and Routers , 筒称为 DSMIPv6 )。 在 EPS 系统之中, 策略和计费执行功能 ( Policy and Charging Enforcement Function, 筒称为 PCEF ) 实体存在于 P-GW中, PCRF与 P-GW 之间 Gx接口 (见图 1 ) 交换信息。 当 P-GW与 S-GW间的接口基于 PMIPv6 时 , S-GW也具有|c载绑定和事件 4艮告功能( Bearer Binding and Event Report Function, 筒称为 BBERF )实体对业务数据流进行 QoS控制 , S-GW与 PCRF 之间通过 Gxc接口 (见图 1 ) 交换信息。 当通过可信任非 3GPP接入系统接 入时, 可信任非 3GPP接入网关中也驻留 BBERF。 可信任非 3GPP接入网关 与 PCRF之间通过 Gxa接口 (见图 1 ) 交换信息。 当 UE漫游时, S9接口作 为归属地 PCRF和拜访地 PCRF的接口 , 同时, 为 UE提供业务的应用功能 ( Application Function, 筒称为 AF ), 通过 Rx接口向 PCRF发送用于制定策 略和计费控制 (Policy and Charging Control, 筒称为 PCC )策略的业务信息。 在 3GPP中, 通过接入点名称 ( Access Point Name, 筒称为 APN ) 可以找到 对应的 PDN网络。通常^ 1 UE到 PDN网络的一个连接称为一个 IP连接接入 网 (IP Connectivity Access Network, 筒称为 IP-CAN )会话。 在建立 IP-CAN 会话的过程中, BBERF和 PCEF分别与 PCRF之间建立 Diameter会话, 通 过这些 Diameter会话来传送对这个 IP-CAN会话进行控制的策略计费信息和 用于制定策略的信息等。
EPS支持 UE同时通过多个接入网接入一个 PDN, 即 ,多接入 ( Multiple Access )。 图 2是根据相关技术的多接入场景的示意图, 如图 2所示, UE同 时在非 3GPP和 3GPP接入的覆盖下,通过非 3GPP IP接入网和 3GPP接入网 通过同一个 P-GW接入到 PDN。 在这种场景下 , P-GW为 UE分配一个 IP地 址, 即, UE和 PDN之间只有一个 IP-CAN会话。 这样, UE请求的不同业 务的数据流可以在适合它传输的接入网中传输。 例如, 非 3GPP接入网是无 线保真 (Wireless Fidelity, 筒称为 WiFi ) 时, 超文本传输协议 ( Hypertext Transfer Protocol, 筒称为 HTTP ) 和文件传输十办议 ( File Transfer Protocol, 筒称为 FTP ) 的业务数据流就可以通过 WiFi接入网, 与此同时, 网络电话
(Voice over Internet Protocol, 筒称为 VoIP ) 的业务数据流就可以通过 3GPP
发送给 UE。 这样 , 对于 HTTP和 FTP这种实时性要求较低的业务可以发挥 WiFi 资费较低的优势, 而对于 VoIP 这种实时性要求较高的业务可以发挥 3GPP的 QoS控制 , 移动性管理较好的优势。 在网络传输业务数据流的过程中, 需要才艮据业务相应的 QoS属性为其 预留相应的资源。 在相关技术中, 可以有两种预留资源的方法,一种是由 UE 发起的预留资源请求, 另一种是由网络发起的预留资源请求。 其中, 在多接 入的场景下, 对于 UE发起的预留资源请求, 由 UE决定在哪个接入网络传 送业务数据流并请求网络预留资源; 但是, 对于由网络发起的资源预留, 如 何在合适的接入网进行资源预留 , 目前尚未提出有效的解决方案。 发明内容 针对目前当 UE同时通过多个接入网接入时, 网络无法根据业务在合适 的接入网连接中发起资源预留过程的问题而提出本发明, 为此, 本发明的主 要目的在于提供一种改进的策略计费控制方案, 以解决上述问题至少之一。 为了实现上述目的 , 根据本发明的一个方面, 提供了一种基于多接入技 术的策略计费控制方法。 才艮据本发明的基于多接入技术的策略计费控制方法包括:策略计费执行 功能实体确定业务数据流传输的接入网连接, 并将确定的接入网连接通知给 策略和计费规则功能实体。 优选地,在策略计费执行功能实体将确定的接入网连接通知给策略和计 费规则功能实体之后, 上述方法还包括: 策略和计费规则功能实体将相应的 服务质量规则发送给接入网连接中的承载绑定和事件报告功能实体, 以使承 载绑定和事件报告功能实体根据服务质量规则发起资源预留或资源释放过 程。 优选地,策略计费执行功能实体根据配置信息或网络策略确定业务数据 流传输的接入网连接。 优选地 ,策略计费执行功能实体将确定的接入网连接通知给策略和计费 规则功能实体包括: 策略计费执行功能实体将绑定指示发送给策略和计费规 则功能实体, 其中, 绑定指示中携带有唯一区分接入网连接的信息。
优选地, 在建立网络协议连接接入网会话时, 策略计费执行功能实体通 过网络协议连接接入网会话建立指示消息将绑定指示发送给策略和计费规则 功能实体。 优选地, 在建立网络协议连接接入网会话后, 策略计费执行功能实体通 过网络协议连接接入网会话修改指示消息、 策略计费规则确认消息或策略计 费规则请求消息将绑定指示发送给策略和计费规则功能实体。 优选地,接入网连接通过以下信息之一来唯一标识: 网络协议连接接入 网类型和 /或无线接入技术类型、 用于指示接入网连接的网络协议地址。 为了实现上述目的, 根据本发明的另一个方面, 提供了一种策略计费执 行功能实体。 根据本发明的策略计费执行功能实体包括: 确定模块, 用于根据配置信 息确定业务数据流传输的接入网连接; 通知模块, 用于将确定模块确定的接 入网连接信息通知给策略和计费规则功能实体。 为了实现上述目的, 才艮据本发明的再一个方面, 提供了一种基于多接入 技术的策略计费控制系统。 才艮据本发明的基于多接入技术的策略计费控制系统包括策略计费执行 功能实体和策略和计费规则功能实体, 其中, 策略计费执行功能实体包括: 确定模块, 用于确定业务数据流传输的接入网连接; 通知模块, 用于将确定 模块确定的接入网连接通知给策略和计费规则功能实体; 策略和计费规则功 能实体包括: 接收模块, 用于接收来自策略计费执行功能实体的接入网连接 的信息; 发送模块, 用于根据接收模块接收的接入网连接的信息将相应的服 务质量规则发送给接入网连接中的承载绑定和事件报告功能实体, 以使承载 绑定和事件报告功能实体根据服务质量规则发起资源预留或资源释放过程。 通过本发明, 采用 PCEF 决定业务数据流传输的接入网连接并通知 PCRF 的方法, 解决了目前当 UE 同时通过多个接入网接入时, 网络无法才艮 据业务在合适的接入网中发起资源预留过程的问题, 进而实现了当 UE同时 通过多个接入网接入时, 网络可以根据业务在合适的接入网中发起资源预留 过程。
附图说明 此处所说明的附图用来提供对本发明的进一步理解 ,构成本申请的一部 分, 本发明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的 不当限定。 在附图中: 图 1是根据相关技术的 EPS的系统架构的示意图; 图 2是根据相关技术的多接入场景的示意图; 图 3是根据相关技术的多接入过程的流程图; 图 4 是根据本发明实施例一的基于多接入技术的接入处理方法的流程 图; 图 5 是根据本发明实施例二的基于多接入技术的接入处理方法的流程 图; 图 6 是根据本发明实施例三的基于多接入技术的接入处理方法的流程 图; 图 7是才艮据本发明实施例的策略计费执行功能实体的结构框图; 图 8 是根据本发明实施例的基于多接入技术的策略计费控制系统的结 构框图。 具体实施方式 功能相克述 考虑到目前当 UE同时通过多个接入网接入时, 网关无法根据业务在合 适的接入网中发起资源预留过程的问题, 本发明实施例提供了一种多接入场 景下网络发起资源预留的方案, PCEF 决定业务数据流传输的接入网连接并 通知 PCRF , PCRF ^)夺相应的 QoS规则发送至该接入网连接中的 BBERF , 该 BBERF安装 QoS规则, 并根据 QoS规则在接入网中发起资源预留过程。 为了便于对本发明实施例的理解,下面对本发明实施例涉及的相关技术 的多接入过程进行描述。 图 3是根据相关技术的多接入过程的流程图, 如图 3所示,描述的是当 UE处于 3GPP接入网和可信任非 3GPP接入网的双覆盖
范围内后, UE 同时通过 3GPP接入网和可信任非 3GPP接入网建立到默认 PDN的连接的流程。 其中, 通过 3GPP接入时, S-GW和 P-GW之间采用 ΡΜΙΡνό协议 ,通过可信任非 3GPP接入时 ,可信任非 3GPP接入网管与 P-GW 之间采用 ΡΜΙΡν6协议。 该多接入过程具体包括以下的步骤 301至步骤 323: 步骤 301 , UE发送附着请求消息给 MME。 步骤 302 , MME发起对 UE的认证流程, 才艮据需要在 MME与 HSS之 间交换认证相关信息; 在认证成功之后, MME发起位置更新流程, HSS UE的签约数据发送给 MME。 在认证过程中, HSS将 P-GW的选择信息发送 给 MME, 其中, 选择信息包括默认 APN。 MME才艮据 APN选择 P-GW, 同 时, MME选择 S-GW。 步骤 303 , MME向 S-GW发送默认承载建立请求消息, 其中, 该默认 承载建立请求消息携带有 APN及选择的 P-GW的 IP地址。 步骤 304, 驻留有 BBERF的 S-GW在向 PCRFF发送的 "网关控制会话 建立指示" 消息中携带 UE的标识 NAI、 APN。 步骤 305 , PCRF根据用户的签约数据、网络策略、承载属性等制定 PCC 规则和 QoS规则, 同时, 也可能制定相应的事件触发器, PCRF通过 "网关 控制会话建立确认" 消息将 QoS规则和事件触发器发送给 S-GW, S-GW安 装 QoS规则和事件触发器。 步骤 306, S-GW向 P-GW发送 "代理绑定更新" 请求消息, 其中, 该 "代理绑定更新" 请求消息中携带有 NAI、 APN。 需要说明的是, 步骤 306可以在接收到步骤 303的消息后执行, 而不必 等待步骤 305的响应。 步骤 307, 驻留有 PCEF的 P-GW向 PCRF发送 "IP-CAN会话建立指 示,, 消息, 其中, 该 "IP-CAN会话建立指示" 消息中携带有 NAI、 APN, 还携带有 P-GW为 UE分配的 IP地址; PCRF通过 NAI和 APN "IP-CAN 会话建立指示" 消息和步骤 305中的 "网关控制会话建立指示" 消息进行关 联, 从而^ 1夺两消息在 PCRF建立的信息关联到同一个 IP-CAN会话。 步骤 308 , PCRF向 P-GW返回 "IP-CAN会话建立确认" 消息, 其中, 该 "IP-CAN会话建立确认"消息携带有相应的 PCC规则和事件触发器 , PCEF
安装 PCC规则和事件触发器; 需要说明的是,如果步骤 307中 IP-CAN会话建立指示消息中携带的信 息导致 QoS规则发生了变化, PCRF将通过网关控制和 QoS规则提供消息将 新的 QoS规则发送给可信任非 3GPP接入网关,若事件触发器也发生了改变, 则提供新的事件触发器, 该消息可以和步骤 308同时执行。 BBERF接收到消 息后返回确认消息。 步骤 309, P-GW向 S-GW返回 "代理绑定确认" 消息, 其中, 该 "代 理绑定确认" 消息中携带有 P-GW为 UE分配的 IP地址。 步骤 310 , S-GW向 MME返回默认 载建立确认消息, 其中, 该默认 载建立确认消息携带有 UE的 IP地址。 步骤 311 , MME、 eNodeB、 UE之间交互, 建立无线 载。 步骤 312 , 在无线承载建立之后, MME向 S-GW发送更新承载请求, 通知 eNodeB的地址信息等, S-GW返回应答消息。 步骤 313 , UE执行特定的非 3GPP接入过程,接入可信任非 3GPP接入 网。 步骤 314, 在 UE接入到可信任非 3GPP接入网之后, 向 HSS/AAA请 求进行 EPS接入认证; 在 HSS/AAA接收到 EPS接入认证请求之后, 对发出 请求的 UE进行认证;在 HSS/AAA完成对 UE的认证之后 ,向可信任非 3GPP 接入网关发送返回在 3GPP接入中选择的 P-GW和 UE签约的 APN, 这里的 APN包括默认 APN。 步骤 315 , 在认证成功之后, 层 3的附着流程被触发, UE向可信任接 入网关发送的消息携带 Multiple Access指示。 步骤 316 , 驻留有 BBERF的可信任非 3GPP接入网关在向 PCRF发送 "网关控制会话建立指示" 消息, 其中, "网关控制会话建立指示" 消息中携 带有 UE的标识 NAI、 APN、 Multiple Access指示。 步骤 317, PCRF才艮据 Multiple Access指示 , 判断 UE为多接入 , 并且 根据 NAI、 APN将该消息与步骤 304和步骤 307的消息进行关联, 从而将三 条消息在 PCRF 建立的信息关联到同一个 IP-CAN会话。 进一步地, PCRF
根据用户的签约数据、 网络策略、 承载属性等对将要迁移到通过非 3GPP接 入的 IP-CAN会话的业务制定 PCC规则和 QoS规则 , 同时, 也可能制定相 应的事件触发器; PCRF 通过 "网关控制会话建立确认" 消息将这些新制定 的 QoS规则和事件触发器发送给 BBERF, BBERF安装 QoS规则和事件触发 器。 步骤 318 , 可信任非 3GPP接入网关向 P-GW发送 "代理绑定更新" 请 求消息, 其中, 该 "代理绑定更新,,请求消息中携带有 NAI、 APN和 Multiple Access指示, 步骤 318可以在接收到步骤 315的消息后就执行, 不必等待步 骤 317的响应。 步骤 319 ,驻留有 PCEF的 P-GW采用步骤 307中建立的 Diameter会话 , 向 PCRF发送 "IP-CAN会话 4爹改指示" 消息, 其中, 该 "IP-CAN会话 4爹改 才旨示" 消息中携带有 NAI、 APN、 IP地址。 步骤 320, PCRF向 P-GW返回 "IP-CAN会话爹改确认" 消息, 其中, "IP-CAN会话修改确认" 消息中携带步骤 317中制定的 PCC规则和事件触 发器, P-GW更新 PCC规则和事件触发器。 PCRF有可能根据步骤 319携带 的信息 , 再次更新 PCC规则。 需要说明的是,如果步骤 319中 IP-CAN会话修改指示消息中携带的信 息导致步骤 317中制定的 QoS规则发生了变化, PCRF将通过网关控制和 QoS 规则提供消息将新的 QoS规则发送给可信任非 3GPP接入网关, 若事件触发 器也发生了改变, 提供新的事件触发器, 该消息可以和步骤 320同时发送。 可信任非 3GPP接入网关接收到消息后返回网关控制和 QoS规则提供确认消 息。 步骤 321 , P-GW将自己的 IP地址等信息保存到 HSS, 在 HSS中注册 多接入。 步骤 322, P-GW向可信任非 3GPP接入网关返回 "代理绑定确认" 消 息, 其中, 该 "代理绑定确认" 消息中携带有 P-GW为 UE分配的 IP地址。 步骤 323 , 可信任非 3GPP接入网关向 UE返回应答消息, 其中, 该应 答消息携带有 UE的 IP地址。 通过以上流程, PCRF可以针对同时通过 3GPP接入和非 3GPP接入的
IP-CAN会话进行策略计费控制。 需要说明的是, 在不冲突的情况下, 本申请中的实施例及实施例中的特 征可以相互组合。 下面将参考附图并结合实施例来详细说明本发明。 方法实施例 根据本发明的实施例, 提供了一种基于多接入技术的接入处理方法, 该 方法应用于多接入场景下, 由网络侧发起的资源预留过程中, 该方法包括: PCEF 确定业务数据流传输的接入网连接 , 并将确定的接入网连接通知给 PCRF, 其中, PCEF可以根据配置信息或网络策略进行确定业务数据流传输 的接入网连接。 此后, PCRF 将相应的 QoS 规则发送给接入网连接中的 BBERF, 以使该 BBERF安装 QoS规则, 并才艮据 QoS规则发起资源预留过程 或资源释放过程。 其中, 接入网连接通过以下信息之一来唯一标识: IP-CAN 类型和 /或无线接入接入类型、 用于指示接入网连接的网络协议地址, 上述的 配置信息可以由系统预先设置。 在具体的实现过程中, PCEF可以将绑定指示发送给 PCRF, 其中, 该 绑定指示中携带有接入网连接的信息。 其中, PCEF可以通过以下消息之一将绑定指示发送给 PCRF: IP-CAN 会话建立指示消息、 IP-CAN 会话修改指示消息、 策略计费规则确认消息、 策略计费规则请求消息。 具体地 , 对于该绑定指示的发送可以才艮据以下情况进行处理: ( 1 )在建立 IP-CAN会话时 , PCEF可以通过 IP-CAN会话建立指示消 息将绑定指示发送给 PCRF。
( 2 )在建立 IP-CAN会话之后, PCEF可以通过 IP-CAN会话 4爹改指示 消息、 策略计费规则确认消息或策略计费规则请求消息将绑定指示发送给 PCRF。 下面将结合实例对本发明实施例的实现过程进行详细描述。 实施例一 本实施例描述的是基于如图 3所示的流程附着。图 4是才艮据本发明实施 例一的流程图, 如图 4所示, 描述的是 UE通过 E-UTRAN和可信任非 3GPP 接入网多接入, 建立 IP-CAN会话后, 访问新的业务, 由网络侧发起资源预
留的过程包括如下的步骤 401至步骤 409: 步骤 401 , UE请求访问新的业务, 向提供业务信息的 AF 1发送请求消 息, AF1接收到该请求消息后, 建立新的 AF会话并提供业务信息, 对应的 业务数据流(Service Data Function, 筒称为 SDF ) 为 SDF1。 进一步地, 该 请求消息中还可以携带 UE选择传输 SDF 1的目标接入网连接的指示。 步骤 402 , AF 1向 PCRF发送业务应用消息, 该业务应用消息中携带有 访问业务的 UE的 IP地址, 进一步地, 该业务应用消息还可以携带 UE的标 识及 UE选择传输 SDF1的目标接入网连接的指示。 步骤 403 , PCRF接收业务应用消息, 并保存业务信息。 步骤 404 , PCRF向 AF 1返回确认消息。 步骤 405 , PCRF才艮据 UE的 IP地址和 UE的标识, 识别出图 3中流程 所建立的 IP-CAN会话。 PCRF根据用户的签约信息、 网络策略和业务信息 等业务特性制定 PCC规则 ( Rulesl )。 步骤 406, PCRF向 P-GW中的 PCEF通过策略计费规则提供消息发送 PCC Rulesl , PCEF安装 PCC Rulesl并才艮据配置信息或网络策略决定该业务 的数据流通过 E-UTRAN传送,将 PCC规则与 E-UTRAN接入连接进行关联。 当 PCEF检测到应用 PCC Rulesl的业务数据流时,这些业务数据流要发送给 通过 E-UTRAN接入网的连接。 步骤 407, PCEF返回确认消息, 并在确认消息中携带绑定指示, 绑定 指示表示 PCEF决定的业务数据流与传输业务数据流的接入网连接的绑定关 系。 该绑定指示通过携带唯一区分各接入网连接的信息来标识 PCEF确定的 接入网连接, 例如, 该绑定指示携带 IP-CAN 类型和 /或无线接入技术类型 ( RAT Type ),在这里由于 PCEF决定业务数据流通过 E-UTRAN接入网连接 传输, 所以 IP-CAN类型取值为 3GPP-EPS , RAT Type取值为 E-URTAN。 还 可以携带 S-GW/BBERF的 IP地址来标识接入网连接。 当然其他唯一区分各 接入网连接的信息同样适用。 步骤 408 , PCRF 根据绑定指示, 获知 PCEF 决定该业务数据流通过 E-UTRAN传输, 所示根据 E-UTRAN的接入特性、 用户签约信息、 网络策 略制定 PCC Rulesl对应的的 QoS Rules 1。 PCRF向 S-GW中的 BBERF通过
网关控制和 QoS规则提供消息发送 QoS Rules 1。 如果 PCRF需要修改步骤 405中制定的 PCC Rules 1 , 贝 ^ PCRF将通过策略计费规则提供消息向 PCEF 更新之前下发的 PCC规则。 步骤 409, BBERF安装 QoS Rules 1 , E-UTRAN执行相应的策略, 并发 起资源预留过程。 BBERF向 PCRF返回确认消息。 需要说明的是, 在其它实施例中, 如果 PCEF决定该业务将通过可信任 非 3GPP接入网连接传输, 贝' j PCEF在向 PCRF返回的确认消息中携带绑定 指示, 表明当 PCEF检测到应用 PCC Rulesl的业务数据流时, 这些业务数据 流要发送给通过可信任非 3GPP接入网接入连接。 绑定指示的实现可以通过 携带该可信任非 3GPP接入网的 IP-CAN Type和 /或 RAT Type, 如果可信任 非 3GPP接入网为 WiMAX, 贝' J IP-CAN Type 为 WiMAX。 绑定才旨示的实现 还可以通过携带可信任非 3GPP接入网关 /BBERF的 IP地址。 当然其他唯一 区分各接入网连接的信息同样适用。 PCRF根据绑定指示, 制定对应的 QoS Rules 1 ,并向可信任非 3GPP接入网关中的 BBERF发送 QoS Rules 1。 BBERF 安装 QoS Rules 1 , 在可信任非 3GPP接入网中发起资源预留过程。 在其他实施例中, 如果 UE同时通过 E-UTRAN和不可信任非 3GPP接 入的多接入, 则此时的处理方法和流程与上述描述的过程类似, 不同之处在 于当 PCEF决定业务数据流通过不可信任非 3GPP接入网连接, 该绑定指示 还可以携带 ePDG/BBERF的 IP地址, PCRF向 ePDG中的 BBERF发送 QoS Rules 1。 实施例二 该实施例包括以下两个部分:
( 1 )与图 3的流程类似, UE建立多接入的 IP-CAN会话, 不同之处在 于: 在步骤 319的 "IP-CAN会话修改指示,, 消息中除了携带有 NAI、 APN、 IP地址之外, 还携带有绑定指示。 当 PCEF根据配置信息或网络策略决定该 UE的所有需要由网络发起资源预留的业务, 其业务数据流都通过 E-URTAN 接入网连接传输。该绑定指示通过携带 IP-CAN类型和 /或无线接入类型 RAT Type, 取值分别是 3GPP-EPS和 E-UTRAN来表示。 该绑定指示还可以通过 携带 S-GW/BBERF的 IP地址, PCRF保存该绑定指示。 当然其他唯一区分 各接入网连接的信息同样适用。 此外, 绑定指示还可以通过步骤 307 的
"IP-CAN会话建立指示" 消息发送给 PCRF, PCRF进行保存。
( 2 ) UE发起业务请求 , 由网络发起资源预留。 图 5是才艮据本发明实施 例二的流程图, 如图 5所示, 包括如下的步骤 501至步骤 509: 步骤 501 , UE请求访问新的业务, 向提供业务信息的 AF 1发送请求消 息, AF1接收到该请求消息后, 建立新的 AF会话并提供业务信息, 对应的 业务数据流为 SDF1。进一步地,该请求消息中还可以携带 UE选择传输 SDF1 的目标接入网连接的指示。 步骤 502 , AF 1向 PCRF发送业务应用消息, 其中, 该业务应用消息携 带有访问业务的 UE的 IP地址 , 进一步地 , 该业务应用消息还可以携带 UE 的标识及 UE选择传输 SDF 1的目标接入网连接的指示。 步骤 503 , PCRF接收该业务应用消息, 并保存业务信息。 步骤 504, PCRF向 AF1返回确认消息。 步骤 505 , PCRF才艮据 UE的 IP地址和 UE的标识 ,识别出建立的 IP-CAN 会话。 jt匕时, PCRF确定 UE通过可信任非 3GPP接入网 (例如, WLAN )和 E-UTRAN多接入。并且,才艮据从 PCEF中获取的绑定指示 ,确定在 E-UTRAN 的接入网连接中进行资源预留。 PCRF 根据接入网特性、 用户的签约信息、 网络策略和业务信息等业务特性制定 PCC Rules 1、 QoS Rulesl。 步骤 506 ,由于在 E-UTRAN的接入网连接中进行资源预留,因此, PCRF 向 S-GW中的 BBERF通过网关控制和 QoS规则提供消息发送 QoS Rules 1。 步骤 507, BBERF安装 QoS Rules 1 , E-UTRAN执行相应的策略, 进行 资源预留。 BBERF向 PCRF返回确认消息。 步骤 508 , PCRF向 P-GW中的 PCEF通过策略计费规则提供消息发送 PCC Rules 1 , 其中, 该策略计费规则提供消息中可以进一步携带绑定指示, 向 PCEF进行确认。 步骤 509 , PCEF安装 PCC Rules 1 , 将 PCC规则与 E-UTRAN接入连接 进行关联,并向 PCRF返回确认消息。当 PCEF检测到该业务数据流时, PCEF 将向 E-UTRAN接入网连接发送业务数据流。
如果步骤 508 中, PCEF接收到绑定指示后对绑定进行修改, PCEF将 在步骤 509中返回新的绑定指示给 PCRF。 PCRF再进行相应的 4爹改。 需要说明的是, 在其它实施例中 , 如果 PCEF决定该业务将通过可信任 非 3GPP接入传输, 则在图 3的步骤 307或步骤 319的消息中, 绑定指示实 现时可以携带该可信任非 3GPP接入网连接的 IP-CAN Type和 /或 RAT Type, 如果可信任非 3GPP接入网为 WiMAX, 贝' J IP-CAN Type 为 WiMAX, 绑定 指示实现时还可以携带可信任非 3GPP接入网关 /BBERF的 IP地址。 PCRF 根据绑定指示, 获知网络发起的资源预留要在通过可信任非 3GPP接入网的 连接中进行, 即, 业务数据流通过可信任非 3GPP接入的连接传输。 在其他实施例中, 如果 UE同时通过 E-UTRAN和不可信任非 3GPP接 入的多接入, 则此时的处理方法和流程与上述描述的过程类似, 不同之处在 于: 当 PCEF决定业务数据流通过不可信任非 3GPP接入网连接, 该绑定指 示还可以携带 ePDG/BBERF的 IP地址, PCRF向 ePDG中的 BBERF发送 QoS Rules 1。 可以看出, 上述实施例一和实施例二的不同之处在于: 在实施例一中,
PCEF针对 UE请求的每一个业务的进行决策, 决定业务数据流传输的接入 网, 然后通知 PCRF; 在实施例二中, PCEF决定 UE的所有需要由网络发起 资源预留业务的数据流都通过一个接入网传输通知 PCRF。 实施例三 本实施例描述的是由于 P-GW决定断开 UE通过 E-UTRAN接入的连接 或者决定改变绑定关系时,将 SDF业务数据流迁移到 UE通过可信任非 3GPP 接入建立的连接上, 从而导致改变数据流传送路径的流程图。 图 6是根据本 发明实施例三的流程图, 如图 6所示, 具体包括如下的步骤 601至步骤 607: 步骤 601 , P-GW中 PCEF接收到内部触发或外部触发, 请求将 SDF1 迁移到可信任非 3GPP接入。 当 PCEF检测到应用 PCC Rules Γ的业务数据流 时, 这些业务数据流要发送给通过可信任非 3GPP接入网接入的连接。 步骤 602, PCEF向 PCRF发送策略计费规则请求消息, 该策略计费规 则请求消息中携带有将 SDF1迁移到可信任非 3GPP接入网的绑定指示,, 该 绑定指示,表明, 绑定指示,实现可以通过携带该可信任非 3GPP 接入网的 IP-CAN Type和 /或 RAT Type, 如果可信任非 3GPP接入网为 WiMAX, 则
IP-CAN Type 为 WiMAX。 绑定指示,实现还可以是可信任非 3GPP接入网关 /BBERF的 IP地址。 当然其他唯一区分各接入网连接的信息同样适用。 进一 步地, 该消息中还可以携带迁移的原因。 步骤 603 , PCRF接收到策略计费规则请求消息后, 根据绑定指示, 获 知 PCEF决定该 SDF1通过可信任非 3GPP接入网传输, 根据可信任非 3GPP 接入网的接入特性重新制定 PCC Rules 1,和对应的 QoS Rules 1, , 并通过策略 计费规则确认消息将 PCC Rulesl '发送给 PCEF , 然后, PCEF 安装 PCC Rules 1 '„ 步骤 604, PCRF向 S-GW中的 BBERF发送网关控制和 QoS规则提供 确认消息, 该确认消息中携带有指示 BBERF删除 QoS Rulesl的信息。 步骤 605 , BBERF向 PCRF返回确认消息。 步骤 606, PCRF通过网关控制和 QoS规则提供消息将 QoS Rulesl '发 送给可信任非 3GPP接入网关中的 BBERF。 步骤 607, BBERF安装 QoS Rulesl ' , 并向 PCRF返回确认消息。 需要说明的是, 对于 UE同时通过 E-UTRAN和不可信任非 3GPP接入 网多接入建立 IP-CAN会话的场景, PCRF将业务的 IP数据流与接入绑定的 方法与上述实施例类似, 在 不再赘述。 需要说明的是, 对于 UE同时通过 E-UTRAN (其中, S-GW和 P-GW 之间采用 GTP协议)和非 3GPP接入网多接入建立 IP-CAN会话的场景, 处 理方法与上述实施例类似, 在此不再赘述。 不同点在于 PCRF不需要将相应 的 QoS Rules发送给 S-GW中的 BBERF。 对于 UE同时通过 E-UTRAN和非 3GPP接入网多接入的场景,并且 UE 通过非 3GPP接入网接入时采用 DSMIPv6协议。 PCRF将业务的 IP数据流 与接入绑定的方法与上述实施例类似, 在 不再赘述。 装置实施例 居本发明的实施例, 提供了一种 PCEF , 应用于多接入场景下, 由网 络侧发起的资源预留过程中, 可以用于实现上述方法。 图 7是根据本发明实 施例的 PCEF的结构框图, 如图 7所示, 该 PCEF包括: 确定模块 72和通知
模块 74 , 下面对上述结构进行描述。 确定模块 72 , 用于根据配置信息或网络策略确定业务数据流传输的接 入网连接, 其中, 上述的配置信息可以由系统预先设置; 通知模块 74 , 连接 至确定模块 72 , 用于将确定模块 72确定的接入网连接通知给 PCRF , 其中, 接入网连接可以通过以下信息之一表示: IP-CAN类型和 /或无线接入类型、 用于指示接入网连接的网络协议地址。 通过该实施例, 提供了可以确定业务数据流传输的接入网的 PCEF, 该 PCEF将确定的接入网连接通知给 PCRF , 以便 PCRF将相应的 QoS规则发 送给接入网连接中的 BBERF , 该 BBERF安装 QoS规则 , 并才艮据 QoS规则 发起资源预留过程或资源释放过程。 系统实施例 根据本发明的实施例, 提供了一种基于多接入技术的策略计费控制系 统。 图 8是才艮据本发明实施例的基于多接入技术的策略计费控制系统的结构 才匡图, 如图 8所示, 该系统包括 PCEF 2和 PCRF 4 , 下面对其中的结构进行 详细描述。
PCEF 2包括: 确定模块 22 , 用于才艮据配置信息确定业务数据流传输的 接入网连接; 通知模块 24 , 连接至确定模块 22 , 用于夺确定模块 22确定的 接入网连接通知给 PCRF。 该 PCEF 2可以用图 7的 PCEF来实现。
PCRF 4连接至 PCEF 2 , 其包括: 接收模块 42 , 用于接收来自 PCEF 的接入网连接的信息; 发送模块 44 , 连接至接收模块 42 , 用于根据模块 42 接收的接入网连接的信息, 将相应的服务质量规则发送给接入网连接中的 BBERF , 以使 BBERF才艮据 QoS规则发起资源预留或资源释放过程。 综上所述, 通过本发明的上述实施例, 采用 PCEF决定业务数据流传输 的接入网连接并通知 PCRF的方法, 解决了目前当 UE同时通过多个接入网 接入时,网络无法根据业务在合适的接入网连接中发起资源预留过程的问题, 进而实现了当 UE同时通过多个接入网接入时, 网络可以才艮据业务在合适的 接入网连接中发起资源预留过程。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布
在多个计算装置所组成的网络上, 可选地, 它们可以用计算装置可执行的程 序代码来实现, 从而, 可以将它们存储在存储装置中由计算装置来执行, 或 者将它们分别制作成各个集成电路模块, 或者将它们中的多个模块或步骤制 作成单个集成电路模块来实现。 这样, 本发明不限制于任何特定的硬件和软 件结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本 领域的技术人员来说, 本发明可以有各种更改和变化。 凡在本发明的^^申和 原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护 范围之内。
Claims
1. 一种基于多接入技术的策略计费控制方法, 其特征在于, 所述方法包括: 策略计费执行功能实体确定业务数据流传输的接入网连接,并将确 定的所述接入网连接通知给策略和计费规则功能实体。
2. 才艮据权利要求 1所述的方法, 其特征在于, 在所述策略计费执行功能实 体将确定的所述接入网连接通知给策略和计费规则功能实体之后 , 所述 方法还包括:
所述策略和计费规则功能实体将相应的 ^^务质量规则发送给所述 接入网连接中的承载绑定和事件报告功能实体, 以使所述承载绑定和事 件报告功能实体根据所述服务质量规则发起资源预留或资源释放过程。
3. 根据权利要求 1所述的方法, 其特征在于, 所述策略计费执行功能实体 根据配置信息或网络策略确定业务数据流传输的所述接入网连接。
4. 根据权利要求 1所述的方法, 其特征在于, 所述策略计费执行功能实体 将确定的所述接入网连接通知给策略和计费规则功能实体包括:
所述策略计费执行功能实体将绑定指示发送给所述策略和计费规 则功能实体, 其中, 所述绑定指示中携带有唯一区分所述接入网连接的 信息。
5. 根据权利要求 4所述的方法, 其特征在于, 在建立网络协议连接接入网 会话时 , 所述策略计费执行功能实体通过网络协议连接接入网会话建立 指示消息将所述绑定指示发送给所述策略和计费规则功能实体。
6. 根据权利要求 4所述的方法, 其特征在于, 在建立网络协议连接接入网 会话后, 所述策略计费执行功能实体通过网络协议连接接入网会话修改 指示消息、 策略计费规则确认消息或策略计费规则请求消息将所述绑定 指示发送给所述策略和计费规则功能实体。
7. 根据权利要求 1至 6中任一项所述的方法, 其特征在于, 所述接入网连 接通过以下信息之一来唯一标识: 网络协议连接接入网类型和 /或无线接 入技术类型、 用于指示所述接入网连接的网络协议地址。
一种策略计费执行功能实体, 其特征在于, 包括:
确定模块 , 用于根据配置信息确定业务数据流传输的接入网连接; 通知模块,用于将所述确定模块确定的所述接入网连接信息通知给 策略和计费规则功能实体。 一种基于多接入技术的策略计费控制系统, 包括策略计费执行功能实体 和策略和计费规则功能实体, 其特征在于,
所述策略计费执行功能实体包括:
确定模块 , 用于确定业务数据流传输的接入网连接;
通知模块,用于将所述确定模块确定的所述接入网连接通知给策略 和计费规则功能实体;
所述策略和计费规则功能实体包括:
接收模块,用于接收来自所述策略计费执行功能实体的所述接入网 连接的信息;
发送模块 ,用于根据所述接收模块接收的所述接入网连接的信息将 相应的服务质量规则发送给所述接入网连接中的承载绑定和事件报告功 能实体, 以使所述承载绑定和事件报告功能实体根据所述服务质量规则 发起资源预留或资源释放过程。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200910002375.0 | 2009-01-06 | ||
CN200910002375A CN101771986A (zh) | 2009-01-06 | 2009-01-06 | 基于多接入技术的策略计费控制方法、装置和系统 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010078761A1 true WO2010078761A1 (zh) | 2010-07-15 |
Family
ID=42316224
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2009/073755 WO2010078761A1 (zh) | 2009-01-06 | 2009-09-04 | 基于多接入技术的策略计费控制方法、装置和系统 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN101771986A (zh) |
WO (1) | WO2010078761A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112994905A (zh) * | 2019-12-18 | 2021-06-18 | 中兴通讯股份有限公司 | 策略和计费的控制方法、系统、电子设备以及存储介质 |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102905390B (zh) * | 2011-07-26 | 2017-12-01 | 中兴通讯股份有限公司 | 会话关联方法、装置和系统 |
WO2018040073A1 (zh) * | 2016-09-02 | 2018-03-08 | 华为技术有限公司 | 一种多接入网的计费方法、装置及系统 |
CN108616957A (zh) * | 2016-12-09 | 2018-10-02 | 大唐移动通信设备有限公司 | 指示无线接入技术类型的方法、基站及移动性管理实体 |
CN108574969B (zh) | 2017-03-08 | 2021-04-09 | 华为技术有限公司 | 多接入场景中的连接处理方法和装置 |
WO2018161796A1 (zh) * | 2017-03-08 | 2018-09-13 | 华为技术有限公司 | 多接入场景中的连接处理方法和装置 |
WO2019213905A1 (zh) * | 2018-05-10 | 2019-11-14 | Oppo广东移动通信有限公司 | 一种绑定数据流的方法及装置、计算机存储介质 |
CN113950851B (zh) * | 2019-06-19 | 2024-07-23 | Oppo广东移动通信有限公司 | 无线通信方法和设备 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1894985A (zh) * | 2003-12-19 | 2007-01-10 | 诺基亚公司 | 通信系统中的控制决策 |
CN101127629A (zh) * | 2006-08-18 | 2008-02-20 | 华为技术有限公司 | 通信系统中策略与计费执行设备、在线计费系统及方法 |
CN101159563A (zh) * | 2007-11-02 | 2008-04-09 | 中兴通讯股份有限公司 | 一种策略计费控制服务器的选择方法及系统 |
CN101222482A (zh) * | 2007-01-11 | 2008-07-16 | 华为技术有限公司 | 一种确定策略规则的方法及系统 |
-
2009
- 2009-01-06 CN CN200910002375A patent/CN101771986A/zh active Pending
- 2009-09-04 WO PCT/CN2009/073755 patent/WO2010078761A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1894985A (zh) * | 2003-12-19 | 2007-01-10 | 诺基亚公司 | 通信系统中的控制决策 |
CN101127629A (zh) * | 2006-08-18 | 2008-02-20 | 华为技术有限公司 | 通信系统中策略与计费执行设备、在线计费系统及方法 |
CN101222482A (zh) * | 2007-01-11 | 2008-07-16 | 华为技术有限公司 | 一种确定策略规则的方法及系统 |
CN101159563A (zh) * | 2007-11-02 | 2008-04-09 | 中兴通讯股份有限公司 | 一种策略计费控制服务器的选择方法及系统 |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112994905A (zh) * | 2019-12-18 | 2021-06-18 | 中兴通讯股份有限公司 | 策略和计费的控制方法、系统、电子设备以及存储介质 |
CN112994905B (zh) * | 2019-12-18 | 2024-01-30 | 中兴通讯股份有限公司 | 策略和计费的控制方法、系统、电子设备以及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN101771986A (zh) | 2010-07-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9137652B2 (en) | Method for implementing policy and charging control in a roaming scene | |
US8874715B2 (en) | Charging method, system and reporting method for terminal accessing through multiple access networks | |
US8799440B2 (en) | Policy and charging control method and system for multi-PDN connections of single APN | |
WO2012058998A1 (zh) | 漫游场景下支持ip流迁移的策略计费控制方法和系统 | |
WO2009135362A1 (zh) | 一种隐藏拜访地网络拓扑结构的策略计费控制的方法 | |
WO2009094837A1 (en) | A method for selecting a policy and charging rules function server on a non-roaming scene | |
EP2790455A1 (en) | Policy control method and system for converged network | |
WO2008101392A1 (fr) | Procédé de transmission de qualité de service lors de transfert entre systèmes et système de réseau et réseau de destination correspondants | |
WO2010081329A1 (zh) | 业务流迁移过程中对网络资源进行控制的方法和系统 | |
EP2571327A1 (en) | Method and system for reporting fixed network access information | |
WO2011006317A1 (zh) | 删除家乡策略和计费规则功能冗余信息的方法及系统 | |
WO2010078761A1 (zh) | 基于多接入技术的策略计费控制方法、装置和系统 | |
WO2011124106A1 (zh) | 一种策略计费控制方法、系统和装置 | |
US9544832B2 (en) | Method, apparatus and system for policy control | |
WO2013064004A1 (zh) | 一种更新服务质量的方法及系统 | |
WO2010006491A1 (zh) | 一种事件触发器的下发和安装方法 | |
WO2011029289A1 (zh) | 漫游场景下承载控制模式的发送方法和系统 | |
WO2011095025A1 (zh) | 一种对移动用户本地接入的策略控制方法和系统 | |
WO2012022222A1 (zh) | 一种策略控制会话的关联方法及系统 | |
WO2010111944A1 (zh) | 释放接入连接的方法、装置、策略控制实体及系统 | |
WO2010054560A1 (zh) | 一种实现多接入的方法及系统 | |
WO2011018020A1 (zh) | 控制pcrf负载均衡的方法、系统及重定向dra | |
CN101742471B (zh) | 一种数据流与接入网连接绑定的方法 | |
WO2012010036A1 (zh) | 一种策略控制方法及系统 | |
WO2012129992A1 (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: 09837318 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 09837318 Country of ref document: EP Kind code of ref document: A1 |