[go: up one dir, main page]

WO2015154598A1 - Procédé, appareil et système de commande de politique - Google Patents

Procédé, appareil et système de commande de politique Download PDF

Info

Publication number
WO2015154598A1
WO2015154598A1 PCT/CN2015/073819 CN2015073819W WO2015154598A1 WO 2015154598 A1 WO2015154598 A1 WO 2015154598A1 CN 2015073819 W CN2015073819 W CN 2015073819W WO 2015154598 A1 WO2015154598 A1 WO 2015154598A1
Authority
WO
WIPO (PCT)
Prior art keywords
rcaf
pcrf
identifier
pdn
session
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2015/073819
Other languages
English (en)
Chinese (zh)
Inventor
周晓云
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Publication of WO2015154598A1 publication Critical patent/WO2015154598A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • the present invention relates to the field of mobile communications, and in particular, to a policy control method.
  • PCC Policy and Charging Control
  • 3GPP 3rd Generation Partnership Project
  • the Policy and Charging Rules Function is the core of the entire PCC architecture.
  • the PCRF needs to combine the service information received from the Application Function (AF), the user subscription information received from the Subscription Profile Repository (SPR), and the policy configured by the operator.
  • the PCRF sends the control policy for the service to the Policy and Charging Enforcement Function (PCEF) or the Bearer Binding and Event Report Function (BBERF).
  • PCEF Policy and Charging Enforcement Function
  • BBERF Bearer Binding and Event Report Function
  • the PCRF can subscribe to the bearer layer related events to the PCEF and/or the BBERF to sense in time when the bearer layer occurs, and change the control strategy.
  • the PCEF can also support application detection control functions.
  • the PCEF can perform application detection and perform policy enforcement (such as gating, redirection, and bandwidth limitation) according to the local configuration or the PCC rule that is sent by the PCRF and includes the application identifier.
  • the PCEF is typically located on the gateway of the network, such as the Packet Data Network Gateway (PDN-GW) of the EPS.
  • the network can implement application detection control by deploying a separate traffic detection function (Traffic Detection Function, TDF for short).
  • TDF Traffic Detection Function
  • the TDF and the PCRF are connected through the Sd interface.
  • the TDF can perform application detection and policy execution according to the application detection and control (ADC) rules that are pre-configured or sent by the PCRF.
  • ADC application detection and control
  • FIG. 2 is a structural diagram of a PCRF sensing wireless network access load information in the related art.
  • the RAN Congestion Awareness Function (RCAF) reports the RAN User Plane Congestion Information (RUCI) to the PCRF for policy decision by using the Np interface. Lightening network Network load.
  • the RCAF collects user plane congestion information from the RAN Operation Administration Maintenance (OAM) system.
  • OAM Operation Administration Maintenance
  • the RCAF obtains from the MME through the Nq interface for each activated APN under the Evolved Cell Global Identifier (ECGI) under the Evolved Cell Global Identifier (ECGI).
  • IMSI IMSI list.
  • the RCAF can directly obtain an IMSI list under a specific NB/CGI from the RAN and acquire an IMSI list for each activated APN through Nq'.
  • RCAF can be an IMSI list for each active APN under each Congested Base Station (eNB/NB)/Cell (ECGI/CGI).
  • the RCAF reports this information to the correct PCRF, and the PCRF can adjust these UE policies to reduce the load on the congested base station or cell.
  • the RCAF can report the RUCI of all users in a congested area to the PCRF in a message.
  • the RCAF can report the RUCI of the user in multiple congested areas to a message.
  • PCRF Congested Base Station
  • a plurality of PCRFs are usually deployed in a Public Land Mobile Network (PLMN), and the DRA will be responsible for managing these PCRFs and ensuring all policies related to one IP-CAN session or one UE.
  • Control sessions (such as Gx, Gxx, Sd sessions) are all associated with the same PCRF. If the RCAF needs to aggregate the RUCIs of multiple UEs into one correct PCRF, the RCAF must be able to encapsulate the RUCIs of the UEs managed by the same PCRF in the same message and send them to a PCRF.
  • the RCAF reports congestion information for a specific UE and APN (ie, PDN identity) combination. Sending a message to the correct PCRF based on the existing DRA routing mechanism;
  • the PCRF allocates a logical PCRF identifier and carries the logical PCRF identifier in the acknowledgement message.
  • the RCAF saves the correspondence between the UE and the APN combination and the logical PCRF identifier;
  • the RCAF performs the above operations for each new UE and APN combination, so that the RCAF can acquire the PCRF logical identity associated with each UE and APN combination.
  • the RCAF aggregates the RUCIs of the multiple UEs and the APNs in a message to the PCRF, where the message carries the PCRF logical identifier.
  • the PCRF returns a confirmation message.
  • the PCRF needs to return a logical PCRF identifier, so that the RCAF can obtain the correspondence between the UE and the APN combination and the PCRF logical identifier, so as to aggregate the RUCIs of the UE and the APN combination that belong to the same PCRF management in one message. Then, the PCRF needs to send the identifier of the PCRF to the RCAF, so that the PCRF is exposed to the client, especially for the Proxy DRA mode, and the ID of the PCRF is usually not sent to the client.
  • the embodiment of the invention provides a policy control method, device and system, which solves the problem that the PCRF is exposed to the client unsafe.
  • a policy control method including:
  • the diameter routing agent DRA receiving the radio access network congestion sensing function entity RCAF sends a first request message, where the first request message includes congestion information for the combination of the user identifier and the packet data network PDN identifier;
  • the acknowledgment information to the RCAF, where the acknowledgment information carries the first indication information of the established session between the RCAF and the PCRF, or the acknowledgment information carries the user identifier and the PDN
  • the identification combines the second indication information of the combination of other user identifiers and PDN identifiers of the same RCAF and PCRF pair.
  • the first indication information is one of the following:
  • the DRA is a shared session identifier allocated by an established session between the RCAF and the PCRF, where the same RCAF and the PCRF have the same shared session identifier;
  • the second indication information is one of the following:
  • the DRA is a shared session identifier assigned with messages of the same RCAF and PCRF pair;
  • All user identification and PDN identification combinations having the same RCAF and PCRF pairs are combined with the user identification and PDN identification.
  • the RCAF determines, according to the first indication information or the second indication information, a combination of a user identifier and a PDN identifier that have the same PCRF or a combination of the user identifier and the PDN identifier that can be aggregated and sent in one message.
  • the method further includes:
  • the DRA receives a second request message that is sent by the RCAF and includes congestion information for a combination of multiple user identifiers and PDN identifiers, where the second request message carries any session established between the RCAF and the PCRF.
  • the session identifier wherein the plurality of user identifiers and PDN identifier combinations correspond to the PCRF.
  • the method further includes: after receiving the second request message, the DRA sends the second request message according to the session identifier of the any session that has been established between the RCAF and the PCRF. Give the PCRF.
  • the authentication session state Auth-Session-State attribute value in the first request message is set to a stateless hold NO_STATE_MAINTAINED.
  • the method further includes:
  • the DRA receives a third request message that is sent by the RCAF and includes congestion information for a combination of multiple user identifiers and PDN identifiers, and the Auth-Session-State AVP in the third request message is set to NO_STATE_MAINTAINED, where Multiple uses The combination of the subscriber identity and the PDN identity corresponds to the PCRF.
  • the DRA after receiving the third request message, the DRA sends the third request message to the PCRF according to any combination of the multiple user identifiers and PDN identifier combinations carried.
  • a policy control method including:
  • the radio access network congestion awareness function entity RCAF sends a first request message to the diameter routing agent DRA, the first request message including congestion information for the combination of the user identity and the packet data network PDN identity;
  • the acknowledgment information carried the first indication information of the established session between the RCAF entity and the policy and charging rule function entity PCRF, or the acknowledgment information carries
  • the user identifier and the PDN identifier combination have second indication information of the same RCAF and other user identifiers and PDN identifier combinations of the PCRF pair.
  • the first indication information is one of the following:
  • the DRA is a shared session identifier allocated by an established session between the RCAF and the PCRF, where the same RCAF and the PCRF have the same shared session identifier;
  • the second indication information is one of the following:
  • the DRA is a shared session identifier assigned with messages of the same RCAF and PCRF pair;
  • All user identification and PDN identification combinations having the same RCAF and PCRF pairs are combined with the user identification and PDN identification.
  • the RCAF further includes:
  • the RCAF determines, according to the first indication information or the second indication information, a combination of a user identifier and a PDN identifier that have the same PCRF or a combination of the user identifier and the PDN identifier that can be aggregated and sent in one message.
  • the RCAF further includes:
  • a second request message including congestion information for a combination of multiple user identifiers and PDN identifiers to the DRA, the second request message carrying a session of any session established between the RCAF and the PCRF An identity, wherein the plurality of user identity and PDN identity combinations correspond to the PCRF.
  • the Auth-Session-State AVP in the first request message is set to stateless hold NO_STATE_MAINTAINED.
  • the RCAF further includes:
  • a diameter routing agent DRA comprising:
  • the message receiving module is configured to: receive a radio access network congestion sensing function entity RCAF to send a first request message, where the first request message includes congestion information for a combination of a user identifier and a packet data network PDN identifier;
  • a policy determining module configured to: determine, according to the combination of the user identifier and the PDN identifier, a corresponding policy and charging rule function entity PCRF;
  • a message sending module configured to: return an acknowledgement information to the RCAF, where the acknowledgement information carries first indication information of an established session between the RCAF and the PCRF, or The acknowledgment information carries second indication information that is combined with other user identities and PDN identities of the same RCAF and PCRF pair in combination with the user identity and the PDN identity.
  • the first indication information is one of the following:
  • the DRA is a shared session identifier allocated by an established session between the RCAF and the PCRF, where the same RCAF and the PCRF have the same shared session identifier;
  • the second indication information is one of the following:
  • the DRA is a shared session identifier assigned with messages of the same RCAF and PCRF pair;
  • All user identification and PDN identification combinations having the same RCAF and PCRF pairs are combined with the user identification and PDN identification.
  • the message receiving module is further configured to: receive, by the RCAF, a second request message that includes congestion information for a combination of multiple user identifiers and PDN identifiers, where the second request message carries the RCAF and a session identifier of any session established between the PCRFs, wherein the plurality of user identifiers and PDN identifier combinations correspond to the PCRF.
  • the message sending module is further configured to: after the message receiving module receives the second request message, according to any session that has been established between the RCAF and the PCRF that is carried The session identifier sends the second request message to the PCRF.
  • the authentication session state Auth-Session-State attribute value in the first request message Set the AVP to stateless NO_STATE_MAINTAINED.
  • the message receiving module is further configured to: receive, by the RCAF, a third request message that includes congestion information for a combination of multiple user identifiers and PDN identifiers, and Auth- in the third request message.
  • the Session-State AVP is set to NO_STATE_MAINTAINED, wherein the plurality of user identifiers and PDN identifier combinations correspond to the PCRF.
  • the message sending module is further configured to: after the message receiving module receives the third request message, according to any combination of the plurality of user identifiers and PDN identifier combinations carried The third request message is sent to the PCRF.
  • a radio access network congestion sensing function entity RCAF includes:
  • a request sending module configured to: send a first request message to the diameter routing agent DRA, where the first request message includes congestion information for a combination of a user identifier and a packet data network PDN identifier;
  • the information receiving module is configured to: receive the confirmation information returned by the DRA, where the confirmation information carries the first indication information of the established session between the RCAF and the policy and charging rule function entity PCRF, or the confirmation
  • the information carries second indication information that is combined with the user identifier and the PDN identifier and has the same RCAF and other user identifiers and PDN identifiers of the PCRF pair.
  • the first indication information is one of the following:
  • the DRA is a shared session identifier allocated by an established session between the RCAF and the PCRF, where the same RCAF and the PCRF have the same shared session identifier;
  • the second indication information is one of the following:
  • the DRA is a shared session identifier assigned to a message having the same RCAF and PCRF pair knowledge
  • All user identification and PDN identification combinations having the same RCAF and PCRF pairs are combined with the user identification and PDN identification.
  • the RCAF further includes:
  • the aggregation judging module is configured to: determine, according to the first indication information or the second indication information, a combination of a user identifier and a PDN identifier that have the same PCRF or a combination of the user identifier and the PDN identifier that can be aggregated and sent in one message.
  • the request sending module is further configured to: send, to the DRA, a second request message that includes congestion information of a combination of multiple user identifiers and PDN identifiers, where the second request message carries the RCAF and the A session identifier of any session established between the PCRFs, wherein the plurality of user identifiers and PDN identifier combinations correspond to the PCRF.
  • the Auth-Session-State AVP in the first request message is set to stateless hold NO_STATE_MAINTAINED.
  • the request sending module is further configured to: send, to the DRA, a third request message that includes congestion information of a combination of multiple user identifiers and PDN identifiers, and Auth-Session- in the third request message.
  • the State AVP is set to NO_STATE_MAINTAINED, wherein the plurality of user identification and PDN identification combinations correspond to the PCRF.
  • a policy control system comprising: a diameter routing agent DRA and a radio access network congestion sensing function entity RCAF;
  • the DRA is configured to: receive, by the RCAF, a first request message, where the first request message includes congestion information for a combination of a user identifier and a packet data network PDN identifier, and determine a corresponding according to the combination of the user identifier and the PDN identifier.
  • the policy and charging rule function entity PCRF returns an acknowledgement information to the RCAF, where the acknowledgement information carries the first indication information of the established session between the RCAF and the PCRF, or the acknowledgement information carries The user identifier and the PDN identifier combination have the same RCAF and PCRF pair other user identifier and PDN identifier combination Second indication information;
  • the RCAF is configured to: send the first request message to the DRA, and receive the acknowledgement information returned by the DRA.
  • the RCAF is further configured to: determine, according to the first indication information or the second indication information, a combination of a user identifier and a PDN identifier that have the same PCRF or a combination of the user identifier and the PDN identifier that can be aggregated and sent in one message. .
  • the RCAF is further configured to: send, to the DRA, a second request message that includes congestion information for a combination of multiple user identifiers and PDN identifiers, where the RCAF and the a session identifier of any session that has been established between the PCRFs, where the plurality of user identifiers and PDN identifier combinations correspond to the PCRF;
  • the DRA is further configured to: receive the second request message sent by the RCAF.
  • the DRA is further configured to: after receiving the second request message, according to the session identifier of the any session that is established between the RCAF and the PCRF that is carried, A request message is sent to the PCRF.
  • the RCAF is further configured to send, when the authentication session state Auth-Session-State attribute value in the first request message is set to stateless hold NO_STATE_MAINTAINED, to the DRA, including multiple users.
  • a third request message that identifies the congestion information combined with the PDN identifier, the Auth-Session-State AVP in the third request message is set to NO_STATE_MAINTAINED, wherein the plurality of user identifiers and PDN identifier combinations correspond to the PCRF;
  • the DRA is further configured to: receive a third request message that is sent by the RCAF and includes congestion information that is combined by multiple user identifiers and PDN identifiers.
  • the DRA is further configured to: after receiving the third request message, send the third request message according to any combination of the multiple user identifiers and PDN identifier combinations carried The PCRF.
  • the embodiment of the invention further provides a computer readable storage medium storing program instructions, which can be implemented when the program instructions are executed.
  • the embodiment of the invention solves the problem that the PCRF is exposed to the client is unsafe by using the aggregated message to report the RUCI without exposing the PCRF.
  • 1 is a schematic structural diagram of a 3GPP evolved packet system
  • FIG. 2 is a schematic structural diagram of a PCC in a non-roaming scenario in Rel-8;
  • FIG. 5 is a flowchart of a policy control method according to Embodiment 2 of the present invention.
  • FIG. 6 is a flowchart of a policy control method according to Embodiment 3 of the present invention.
  • FIG. 7 is a flowchart of a policy control method according to Embodiment 4 of the present invention.
  • Embodiment 8 is a flowchart of a policy control method according to Embodiment 5 of the present invention.
  • FIG. 9 is a schematic diagram of a process for sending a combination of a user identifier and a PDN identifier to a DRA aggregation according to Embodiment 5 of the present invention.
  • FIG. 10 is a schematic diagram of another RCAF sending a user identity and a PDN identity combination to a DRA aggregation according to Embodiment 5 of the present invention.
  • FIG. 11 is a schematic structural diagram of a DRA according to Embodiment 6 of the present invention.
  • FIG. 12 is a schematic structural diagram of an RCAF provided in Embodiment 6 of the present invention.
  • the PCRF In the process of reporting the RUCI by using the aggregated message, the PCRF needs to return a logical PCRF identifier, so that the RCAF can obtain the correspondence between the UE and the APN combination and the PCRF logical identifier, so as to aggregate the RUCIs of the UE and the APN combination that belong to the same PCRF management. In a message. Then, the PCRF needs to send the identifier of the PCRF to the RCAF, so that the PCRF is exposed to the client, especially for the Proxy DRA mode, and the ID of the PCRF is usually not sent to the client.
  • an embodiment of the present invention provides a policy control method, apparatus, and system. Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.
  • This embodiment provides a policy control method, and describes a process in which the RCAF perceives that a new UE needs to report the UE-related RUCI to the PCRF.
  • the DRA is in the Proxy mode, and the session state is maintained between the RCAF and the PCRF.
  • Step 401 The RCAF reports congestion information for a specific combination of user identifier (user identifier 1) and PDN identifier (PDN identifier 1). (The RCAF does not save the aggregation relationship between the user ID 1 and the PDN ID 1 combination with other user combinations and PDN combinations.)
  • the PCRF sends a Diameter RUCI_Report_Request, and the message carries the RCAF to allocate a session identifier for the Diameter session to be established (Diameter session). Identification 1), User ID 1, PDN ID 1 and RUCI of the combination of User ID 1 and PDN ID 1.
  • the message may also carry a Diameter session establishment indication identifier.
  • Step 402 After receiving the message, the DRA determines the PCRF that serves the user identifier or the combination of the user identifier and the PDN identifier according to the DRA binding information saved by the DRA, and sends a message to the PCRF.
  • the DRA selects a PCRF for the IP-CAN session and maintains a corresponding relationship, such as (User ID 1, PDN ID 1, IP address of UE1, PCRF address).
  • the DRA receives the message of step 401, the DRA matches the saved correspondence according to the user identifier 1 and the PDN1 identifier 1 and sends the message to the correct PCRF.
  • the corresponding DRA update relationship is as follows (session ID 1, user ID 1, PDN ID 1, IP address of UE1, PCRF address).
  • Step 403 The PCRF returns an acknowledgement message to the DRA.
  • the specific implementation is a Diameter RUCI_Report_Answer message carrying the session identifier 1 and the confirmation code.
  • the message may carry a reporting restriction condition, indicating under what conditions the RCAF reports the RUCI of the combination of the user identity and the PDN identity.
  • Step 404 After receiving the acknowledgement message, the DRA determines that there is already at least one Diameter session between the RCAF and the PCRF.
  • Step 405 The DRA returns an acknowledgement message to the RCAF, where the message carries the message in step 403.
  • a Diameter session identifier of the Diameter session between the parameter and the existing RCAF and the PCRF (session ID 2).
  • This session identifier is the session identifier of the Diameter session created by the RCAF when the RCAF reports the congestion information of the combination of the user ID 2 and the PDN ID 1. ) or a list of all session IDs that already exist for Diameter sessions with RCAF and PCRF.
  • the RCAF saves the above session identifier. Based on the session identifier, the RCAF knows all Diameter sessions that exist between the same RCAF and PCRF.
  • RCAF also knows all user identification and PDN identification combinations with the same RCAF and PCRF (for this RCAF, it is the combination of user identification and PDN identification with the same PCRF). That is, the RCAF knows that all user IDs and PDN identity combinations that can be sent are aggregated in one message.
  • Step 406 The RCAF needs to report congestion information of multiple users (such as user ID 1 and user ID 2). Specifically, the RCAF sends a Diameter RUCI_Report_Request message to the PCRF, where the message carries the session identifier 2, the RUCI of the combination of the user identifier 1 and the PDN1 identifier, and the RUCI of the combination of the user identifier 2 and the PDN identifier 1. (Of course, the message may also carry the session identifier 1. In general, the RCAF may select any session identifier of the Diameter session existing between the RCAF and the PCRF).
  • Step 407 The DRA forwards the message to the PCRF according to the saved session state information (that is, the correspondence between the session identifier 2 and the PCRF address);
  • Step 408 The PCRF returns an acknowledgement message to the DRA.
  • Step 409 The DRA forwards an acknowledgement message to the RCAF.
  • the DRA may return only one RCAF and the session identifier of the session that the PCRF has established to the RCAF.
  • the RCAF since the RCAF must acquire the aggregation relationship between the session and other sessions when the session corresponding to the returned session identifier is established, the RCAF can still pass the returned session identifier even though only the session identifier of one session is returned. Know the aggregation relationship between the session being established and other sessions.
  • the DRA may also carry the user identifier and PDN identity combination information with the same RCAF and PCRF pair in combination with the user identity 1 and the PDN identity 1 in the acknowledgment message (ie, the established relationship between the RCAF and the PCRF) Combination of user ID and PDN ID corresponding to a session) (DRA can return only one user ID and PDN ID combination information with the same RCAF and PCRF pair, or all user ID and PDN ID combination information with the same RCAF and PCRF pairs. ).
  • the RCAF After the RCAF receives the message, the user ID and the PDN identify the combined information. According to The user identification and PDN identification combination information, the RCAF knows the combination of the user identification and the APN identification of the same PCRF service.
  • the RCAF knows all the user identity and PDN identity combinations with the same RCAF and PCRF (for this RCAF, the user identity and PDN identity combination with the same PCRF). That is, the RCAF knows that all user IDs and PDN identity combinations that can be sent are aggregated in one message.
  • This embodiment provides a policy control method, and describes a process in which the RCAF perceives that a new UE needs to report the UE-related RUCI to the PCRF.
  • the DRA is in the Proxy mode, and the session state is maintained between the RCAF and the PCRF.
  • Step 501 The RCAF reports congestion information for a specific combination of user identifier (user identifier 1) and PDN identifier (PDN identifier 1). (The RCAF does not save the aggregation relationship between the user ID 1 and the PDN ID 1 combination with other user combinations and PDN combinations.)
  • the PCRF sends a Diameter RUCI_Report_Request, and the message carries the RCAF to allocate a session identifier for the Diameter session to be established (Diameter session). Identification 1), User ID 1, PDN ID 1 and RUCI of the combination of User ID 1 and PDN ID 1.
  • the message may also carry a Diameter session establishment indication identifier.
  • Step 502 After receiving the message, the DRA determines the PCRF that serves the combination of the user identifier and the PDN identifier according to the DRA binding information saved by the DRA, and sends a message to the PCRF.
  • the DRA selects a PCRF for the IP-CAN session and maintains a corresponding relationship, such as (User ID 1, PDN ID 1, IP address of UE1, PCRF address).
  • the DRA receives the message of step 501, the DRA matches the saved correspondence according to the user identifier 1 and the PDN1 identifier 1 and sends the message to the correct PCRF.
  • the corresponding DRA update relationship is as follows (session ID 1, user ID 1, PDN ID 1, IP address of UE1, PCRF address).
  • Step 503 The PCRF returns an acknowledgement message to the DRA.
  • the specific implementation is a Diameter RUCI_Report_Answer message carrying the session identifier 1 and the confirmation code.
  • the message may carry a reporting restriction condition, indicating under what conditions the RCAF reports the RUCI of the combination of the user identity and the PDN identity.
  • Step 504. The DRA returns an acknowledgement message to the RCAF, where the message carries the parameter in the message of step 503 and the shared session identifier (the DRA is the Diameter session assignment between each RCAF and the PCRF). An identical shared session ID). After receiving the message, the RCAF saves the above shared session identifier. Based on the shared session identity, the RCAF knows all Diameter sessions that exist between the same RCAF and PCRF. That is, RCAF also knows all user identification and PDN identification combinations with the same RCAF and PCRF (for this RCAF, it is the combination of user identification and PDN identification with the same PCRF). That is, the RCAF knows that all user IDs and PDN identity combinations that can be sent are aggregated in one message.
  • Step 505 The RCAF needs to report congestion information of multiple users (such as user ID 1 and user ID 2, and their Diameter sessions have the same shared session identifier). Specifically, the RCAF sends a Diameter RUCI_Report_Request message to the PCRF, where the message carries the session identifier 1, the RUCI of the combination of the user identifier 1 and the PDN1 identifier, and the RUCI of the combination of the user identifier 2 and the PDN identifier 1. (Of course, the message can also be identified by the session identifier 2. In general, the RCAF can select the session identifier of any Diameter session with the same shared session identifier).
  • Step 506 The DRA forwards the message to the PCRF according to the saved session state information, that is, the correspondence between the session identifier 1 and the PCRF address.
  • Step 507 The PCRF returns an acknowledgement message to the DRA.
  • Step 508 The DRA forwards an acknowledgement message to the RCAF.
  • This embodiment provides a policy control method, and describes a process in which the RCAF perceives that a new UE needs to report the UE-related RUCI to the PCRF.
  • the DRA is in the Proxy mode, and the session state is not maintained between the RCAF and the PCRF.
  • Step 601 The RCAF reports congestion information for a specific combination of user identifier (user identifier 1) and PDN identifier (PDN identifier 1).
  • the PCRF sends a Diameter RUCI_Report_Request, and the message carries the user identifier 1, the PDN identifier 1, and the RUCI of the combination of the user identifier 1 and the PDN identifier 1.
  • the Auth-Session-State AVP is set to NO_STATE_MAINTAINED.
  • Step 602 After receiving the message, the DRA determines the PCRF that serves the combination of the user identifier and the PDN identifier according to the DRA binding information saved by the DRA, and sends a message to the PCRF.
  • DRA in UE During the establishment of the IP-CAN session, a PCRF is selected for the IP-CAN session and a corresponding relationship is maintained, such as (user ID 1, PDN ID 1, IP address of UE1, PCRF address).
  • the DRA receives the message of step 601
  • the DRA matches the saved correspondence according to the user identifier 1 and the PDN1 identifier 1 and sends the message to the correct PCRF.
  • Step 603 The PCRF returns an acknowledgement message to the DRA.
  • the specific implementation is a Diameter RUCI_Report_Answer message carrying a confirmation code.
  • the message may carry a reporting restriction condition, indicating under what conditions the RCAF reports the RUCI of the combination of the user identity and the PDN identity.
  • Step 604. The DRA returns an acknowledgement message to the RCAF, where the message carries the parameter in the message of step 603 and the shared session identifier (the DRA allocates the same shared session identifier for the acknowledgement message with the same RCAF and PCRF (ie, the combination of the user identifier and the PDN identifier).
  • the RCAF saves the shared session identifier. According to the shared session identifier, the RCAF knows the combination of the user identifier and the APN identifier of the same PCRF service.
  • the RCAF knows all the user identifiers and PDN identifier combinations with the same RCAF and PCRF ( For this RCAF, it is the combination of the user ID and the PDN identity of the same PCRF. That is, the RCAF knows that all the user identity and PDN identity combinations that can be sent in one message can be aggregated.
  • Step 605 The RCAF needs to report congestion information of multiple users (such as user ID 1 and user ID 2, which have the same shared session identifier). Specifically, the RCAF sends a Diameter RUCI_Report_Request message to the PCRF, where the message carries the RUCI of the combination of the user identifier 1 and the PDN1 identifier, and the RUCI of the combination of the user identifier 2 and the PDN identifier 1.
  • the Auth-Session-State AVP is set to NO_STATE_MAINTAINED.
  • Step 606 The DRA forwards the message to the PCRF according to the saved DRA binding information.
  • the DRA obtains (User ID 1 or User ID 2) and the PDN ID 1 from step 605, and determines a PCRF address according to the correspondence relationship saved by the DRA in the IP-CAN session establishment process of the UE;
  • Step 607 The PCRF returns an acknowledgement message to the DRA.
  • Step 608 The DRA forwards the confirmation message to the RCAF.
  • This embodiment provides a policy control method, and describes that the RCAF needs to perceive a new UE.
  • the DRA is in the Proxy mode, and the session state is not maintained between the RCAF and the PCRF.
  • Step 701 The RCAF reports congestion information for a specific combination of user identifier (user identifier 1) and PDN identifier (PDN identifier 1).
  • the PCRF sends a Diameter RUCI_Report_Request, and the message carries the user identifier 1, the PDN identifier 1, and the RUCI of the combination of the user identifier 1 and the PDN identifier 1.
  • the Auth-Session-State AVP is set to NO_STATE_MAINTAINED.
  • Step 702 After receiving the message, the DRA determines the PCRF that serves the combination of the user identifier and the PDN identifier according to the DRA binding information saved by the DRA, and sends a message to the PCRF.
  • the DRA selects a PCRF for the IP-CAN session and maintains a corresponding relationship, such as (User ID 1, PDN ID 1, IP address of UE1, PCRF address).
  • the DRA receives the message of step 401, the DRA matches the saved correspondence according to the user identifier 1 and the PDN1 identifier 1 and sends the message to the correct PCRF.
  • Step 703 The PCRF returns an acknowledgement message to the DRA.
  • the specific implementation is a Diameter RUCI_Report_Answer message carrying a confirmation code.
  • the message may carry a reporting restriction condition, indicating under what conditions the RCAF reports the RUCI of the combination of the user identity and the PDN identity.
  • Step 704 The DRA returns an acknowledgement message to the RCAF, where the message carries the parameter in the message of step 703 and carries the combination of the user identifier and the PDN identifier of the same RCAF and PCRF pair combined with the user identifier 1 and the PDN identifier 1 (the DRA may only return with A combination of user identification and PDN identification of the same RCAF and PCRF pair may also return all user identification and PDN identification combination information having the same RCAF and PCRF pairs).
  • the RCAF receives the message, the user ID and the PDN identify the combined information. Based on the user identification and PDN identification combination information, the RCAF knows the combination of the user identification and the APN identification of the same PCRF service.
  • the RCAF knows all the user identity and PDN identity combinations with the same RCAF and PCRF (for this RCAF, the user identity and PDN identity combination with the same PCRF). That is, the RCAF knows that all user IDs and PDN identity combinations that can be sent are aggregated in one message.
  • Step 705 The RCAF needs to report congestion information of multiple users (such as user ID 1 and user ID 2, which have the same shared session identifier). Specifically, the RCAF sends a Diameter RUCI_Report_Request message to the PCRF, where the message carries the combination of the user identifier 1 and the PDN1 identifier. RUCI, the RUCI of the combination of User ID 2 and PDN ID 1. The Auth-Session-State AVP is set to NO_STATE_MAINTAINED.
  • Step 706 The DRA forwards the message to the PCRF according to the saved DRA binding information.
  • the DRA obtains (User ID 1 or User ID 2) and the PDN ID 1 from step 605, and determines a PCRF address according to the correspondence relationship saved by the DRA in the IP-CAN session establishment process of the UE;
  • Step 707 The PCRF returns an acknowledgement message to the DRA.
  • Step 708 The DRA forwards an acknowledgement message to the RCAF.
  • the embodiment of the present invention provides a policy control method, and the process of reporting congestion information by using the RCAF aggregation method is as shown in FIG. 8 , and includes:
  • Step 801. The RCAF sends a first request message with the congestion information of the combination of the user identifier and the PDN identifier to the DRA;
  • Step 802. The DRA receives the first request message sent by the RCAF with the congestion information of the combination of the user identifier and the PDN identifier.
  • Step 803. The DRA determines a corresponding PCRF according to the combination of the user identifier and the PDN identifier.
  • Step 804. The DRA returns confirmation information to the RCAF.
  • the acknowledgment information carries the first indication information of the established session between the RCAF and the PCRF, or carries other user identifiers and PDNs having the same RCAF and PCRF pair combined with the user identifier and the PDN identifier. Identifying the second indication of the combination.
  • the first indication information is one of the following:
  • the DRA is a shared session identifier allocated by an established session between the RCAF and the PCRF, where the same RCAF and the PCRF have the same shared session identifier;
  • the second indication information is one of the following:
  • the DRA is a shared session identifier assigned with messages of the same RCAF and PCRF pair;
  • All user identification and PDN identification combinations having the same RCAF and PCRF pairs are combined with the user identification and PDN identification.
  • the RCAF determines, according to the first indication information or the second indication information, a combination of a user identifier and a PDN identifier that have the same PCRF or a combination of the user identifier and the PDN identifier that can be aggregated and sent in one message.
  • Step 805. The RCAF receives the confirmation information returned by the DRA.
  • the RCAF can send a combination of the user identifier and the PDN identifier to the DRA aggregation, as shown in FIG. 9 and FIG. 10 respectively.
  • a process for sending a combination of a user identifier and a PDN identifier to an RCA aggregation includes:
  • Step 901 The RCAF sends, to the DRA, a second request message that includes congestion information of multiple user identifiers and PDN identifier combinations.
  • Step 902 After receiving the second request message, the DRA sends the second request message to the PCRF according to the session identifier of the any session that has been established between the RCAF and the PCRF. .
  • the authentication session state Auth-Session-State attribute in the first request message includes:
  • Step 1001 The RCAF sends, to the DRA, a third request message that includes congestion information of a combination of multiple user identifiers and PDN identifiers;
  • the Auth-Session-State AVP in the third request message is set to NO_STATE_MAINTAINED, wherein the plurality of user identifiers and PDN identifier combinations correspond to the PCRF.
  • Step 1002 After receiving the third request message, the DRA sends the third request message to the PCRF according to any combination of the multiple user identifiers and PDN identifier combinations carried.
  • the embodiment of the invention provides a DRA, and its structure is as shown in FIG. 11 and includes:
  • the message receiving module 1101 is configured to receive a first request message that is sent by the RCAF with the congestion information of the combination of the user identifier and the PDN identifier;
  • the policy determining module 1102 is configured to determine a corresponding PCRF according to the combination of the user identifier and the PDN identifier;
  • the message sending module 1103 is configured to return an acknowledgment information to the RCAF, where the acknowledgment information carries the first indication information of the established session between the RCAF and the PCRF, or carries the user identifier and
  • the PDN identity combines second indication information having the same RCAF and other user identity and PDN identity combinations of the PCRF pair.
  • the first indication information is one of the following:
  • the DRA is a shared session identifier allocated by an established session between the RCAF and the PCRF, where the same RCAF and the PCRF have the same shared session identifier;
  • the second indication information is one of the following:
  • the DRA is a shared session identifier assigned with messages of the same RCAF and PCRF pair;
  • All user identification and PDN identification combinations having the same RCAF and PCRF pairs are combined with the user identification and PDN identification.
  • the message receiving module 1101 is further configured to receive, by the RCAF, a second request message that includes congestion information of a combination of multiple user identifiers and PDN identifiers, where the RCAF is carried in the second request message.
  • a session identifier of any session established with the PCRF wherein the plurality of user identifiers and PDN identifier combinations correspond to the PCRF.
  • the message sending module 1103 is further configured to: after the message receiving module receives the second request message, according to any session that has been established between the RCAF and the PCRF that is carried The session identifier sends the second request message to the PCRF.
  • the authentication session state Auth-Session-State attribute value in the first request message is set to a stateless hold NO_STATE_MAINTAINED.
  • the message receiving module 1101 is further configured to receive a third request message that is sent by the RCAF and that includes congestion information of multiple user identifiers and PDN identifier combinations, and an Auth-Session in the third request message.
  • the -State AVP is set to NO_STATE_MAINTAINED, wherein the plurality of user identification and PDN identification combinations correspond to the PCRF.
  • the message sending module 1103 is further configured to: after the message receiving module receives the third request message, according to any combination of the multiple user identifiers and PDN identifier combinations carried The third request message is sent to the PCRF.
  • the DRA shown in FIG. 11 may be a Proxy DRA.
  • An embodiment of the present invention further provides an RCAF, and the structure thereof is as shown in FIG. 12, including:
  • the request sending module 1201 is configured to send, to the DRA, a first request message with congestion information of a combination of the user identifier and the PDN identifier;
  • the information receiving module 1202 is configured to receive the acknowledgment information returned by the DRA, where the acknowledgment information carries the first indication information of the established session between the RCAF and the PCRF, or carries the combination with the user identifier and the PDN identifier. Second indication information having a combination of other user identification and PDN identification of the same RCAF and PCRF pair.
  • the first indication information is one of the following:
  • the DRA is a shared session identifier allocated by an established session between the RCAF and the PCRF, where the same RCAF and the PCRF have the same shared session identifier;
  • the second indication information is one of the following:
  • the DRA is a shared session identifier assigned with messages of the same RCAF and PCRF pair;
  • All user identification and PDN identification combinations having the same RCAF and PCRF pairs are combined with the user identification and PDN identification.
  • the device further includes:
  • the aggregation determining module 1203 is configured to determine, according to the first indication information or the second indication information, a combination of a user identifier and a PDN identifier that have the same PCRF or a combination of the user identifier and the PDN identifier that can be aggregated and sent in one message.
  • the request sending module 1201 is further configured to send, to the DRA, a second request message that includes congestion information of a combination of multiple user identifiers and PDN identifiers, where the second request message carries the RCAF and a session identifier of any session established between the PCRFs, wherein the plurality of user identifiers and PDN identifier combinations correspond to the PCRF.
  • the Auth-Session-State AVP in the first request message is set to stateless NO_STATE_MAINTAINED.
  • the request sending module 1201 is further configured to send, to the DRA, a third request message that includes congestion information of a combination of multiple user identifiers and PDN identifiers, and Auth-Session- in the third request message.
  • the State AVP is set to NO_STATE_MAINTAINED, wherein the plurality of user identification and PDN identification combinations correspond to the PCRF.
  • the embodiment of the present invention further provides a policy control system, including DRA and RCAF; optionally, including a DRA as shown in FIG. 11 and an RCAF as shown in FIG.
  • the system also includes a PCRF.
  • the DRA is configured to receive a first request message that is sent by the RCAF with congestion information of a combination of a user identifier and a PDN identifier, determine a corresponding PCRF according to the combination of the user identifier and the PDN identifier, and return a confirmation information to the RCAF.
  • the acknowledgment information carries the first indication information of the established session between the RCAF and the PCRF, or carries other user identifiers with the same RCAF and PCRF pair combined with the user identifier and the PDN identifier.
  • the second indication information of the combination of the PDN identifiers is configured to receive a first request message that is sent by the RCAF with congestion information of a combination of a user identifier and a PDN identifier, determine a corresponding PCRF according to the combination of the user identifier and the PDN identifier, and return a confirmation information to the RCAF.
  • the acknowledgment information carries the first indication information of the established session between the RCA
  • the RCAF is configured to send a first request message with the congestion information of the user identifier and the PDN identifier combination to the DRA, and receive the acknowledgement information returned by the DRA.
  • the RCAF is further configured to determine, according to the first indication information or the second indication information, a combination of a user identifier and a PDN identifier that have the same PCRF or a combination of the user identifier and the PDN identifier that can be aggregated and sent in one message.
  • the RCAF is further configured to send, to the DRA, a second request message that includes congestion information of a combination of multiple user identifiers and PDN identifiers, where the RCAF and the PCRF are carried in the second request message.
  • the DRA is further configured to receive a second request message that is sent by the RCAF and includes congestion information of a combination of multiple user identifiers and PDN identifiers.
  • the DRA is further configured to, after receiving the second request message, send the second request according to the session identifier of the any session that is established between the RCAF and the PCRF that is carried. A message is sent to the PCRF.
  • the RCAF is further configured to send, when the authentication session state Auth-Session-State attribute value in the first request message is set to stateless hold NO_STATE_MAINTAINED, to the DRA, including multiple user identifiers. And a third request message of the congestion information combined with the PDN identifier, the Auth-Session-State AVP in the third request message is set to NO_STATE_MAINTAINED, wherein the plurality of user identifiers and PDN identifier combinations correspond to the PCRF.
  • the DRA is further configured to receive a third request message that is sent by the RCAF and includes congestion information of a combination of multiple user identifiers and PDN identifiers.
  • the DRA is further configured to, after receiving the third request message, send the third request message to the location according to any combination of the multiple user identifiers and PDN identifier combinations carried Said PCRF.
  • An embodiment of the present invention provides a policy control method, apparatus, and system.
  • a DRA receives a first request message sent by an RCAF with congestion information of a combination of a user identifier and a PDN identifier, according to the user identifier and the PDN identifier.
  • the acknowledgment information carries the first indication information of the established session between the RCAF and the PCRF, or carries And the second indication information that has the same RCAF and other user identifiers and PDN identifier combinations of the PCRF pair combined with the user identifier and the PDN identifier; on the RCAF side, the RCAF sends the congestion information with the user identifier and the PDN identifier combination to the DRA.
  • a request message receives the confirmation information returned by the DRA.
  • all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve. Thus, the invention is not limited to any specific combination of hardware and software.
  • the devices/function modules/functional units in the above embodiments may be implemented by a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • each device/function module/functional unit in the above embodiment When each device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
  • the embodiment of the invention solves the problem that the PCRF is exposed to the client is unsafe by using the aggregated message to report the RUCI without exposing the PCRF.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé de commande de politique qui concerne le domaine des communications mobiles. Le procédé comprend : un DRA reçoit un premier message de demande envoyé par un RCAF, transportant des informations d'encombrement d'une combinaison d'un identifiant d'utilisateur et d'un identifiant de PDN ; le DRA détermine un PCRF correspondant conformément à la combinaison de l'identifiant d'utilisateur et de l'identifiant de PDN ; et le DRA renvoie des informations d'accusé de réception au RCAF, les informations d'accusé de réception transportant des premières informations d'indication d'une session établie entre le RCAF et le PCRF ou transportant des deuxièmes informations d'indication d'autres combinaison d'identifiant d'utilisateur et d'identifiant de PDN qui présentent la même paire de RCAF et de PCRF que la combinaison de l'identifiant d'utilisateur et de l'identifiant de PDN.
PCT/CN2015/073819 2014-08-25 2015-03-06 Procédé, appareil et système de commande de politique Ceased WO2015154598A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410423073.1 2014-08-25
CN201410423073.1A CN105376200A (zh) 2014-08-25 2014-08-25 策略控制方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2015154598A1 true WO2015154598A1 (fr) 2015-10-15

Family

ID=54287304

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/073819 Ceased WO2015154598A1 (fr) 2014-08-25 2015-03-06 Procédé, appareil et système de commande de politique

Country Status (2)

Country Link
CN (1) CN105376200A (fr)
WO (1) WO2015154598A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2536179A1 (fr) * 2010-02-09 2012-12-19 ZTE Corporation Procédé, dispositif et système pour sélectionner une entité de fonction de politique et de règles de facturation
CN103781048A (zh) * 2012-10-19 2014-05-07 电信科学技术研究院 策略和计费控制实体的寻址方法和设备

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101753323A (zh) * 2008-11-27 2010-06-23 大唐移动通信设备有限公司 一种生成QoS策略的方法、系统和装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2536179A1 (fr) * 2010-02-09 2012-12-19 ZTE Corporation Procédé, dispositif et système pour sélectionner une entité de fonction de politique et de règles de facturation
CN103781048A (zh) * 2012-10-19 2014-05-07 电信科学技术研究院 策略和计费控制实体的寻址方法和设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON ET AL.: "Aggregation of Np messages.", 3GPP TSG-SA2 MEETING #104, 11 July 2014 (2014-07-11), pages 2 - 142873, XP050801935 *

Also Published As

Publication number Publication date
CN105376200A (zh) 2016-03-02

Similar Documents

Publication Publication Date Title
EP3563610B1 (fr) Sélection de tranches de réseau
US11729661B2 (en) MTC-IWF entity, PCFR entity, and communication method
CN104995867B (zh) 在移动电信网络中的选择性事件报告
CN107637101B (zh) 用于提供监控服务的系统和方法
JP6429866B2 (ja) Ｐｃｒｆを決定するための方法および装置
CN105103648A (zh) 使用中央节点来收集ran用户平面拥塞信息的系统和方法
US20190021124A1 (en) Change of radio access network in a network sharing architecture
CN102332985B (zh) 一种提供基于lipa承载的计费支持的方法及装置
US20170163431A1 (en) Notification of Network Events Relevant for Policy and Charging Decisions
WO2016062025A1 (fr) Procédé et dispositif de sélection de fonction de règles de politique et de facturation
WO2011134319A1 (fr) Procédé de commande de politique pour un service à commutation de paquets et système de service à commutation de paquets
CN102158835B (zh) 机器类型通信信息传输方法和设备及系统
CN105897608B (zh) 一种拥塞信息的管理方法和装置
WO2016062026A1 (fr) Procédé et dispositif de sélection de fonction de règles de politique et de facturation
US10321354B2 (en) Methods, network nodes, and computer program products for providing access point name (APN) based group congestion control
US9237595B2 (en) Diameter based communication session discovery and recovery
WO2013113263A1 (fr) Procédé et système d'identification de mode fonction de commande de détection d'application
WO2015154598A1 (fr) Procédé, appareil et système de commande de politique
US10116457B1 (en) Methods, systems, and computer readable media for usage monitoring
WO2016023363A1 (fr) Procédé et appareil de traitement de chaîne de service, classificateur de service et pcrf
WO2016074224A1 (fr) Procédé et appareil pour sélectionner une fonction de règles de politique et de facturation
EP3205128B1 (fr) Procédés, appareis et produit de programme informatique pour assurer une gestion des encombrements par groupes basée sur les noms de points d'accès (apn)
WO2016029674A1 (fr) Procédé de rapport d'état d'encombrement d'un réseau d'accès, procédé de traitement de mise à jour d'informations d'encombrement, et dispositif

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

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

Country of ref document: EP

Kind code of ref document: A1