WO2008019626A1 - Procédé, système et appareil de gestion des informations concernant les règles d'utilisation et de facturation associées au profil d'utilisateur dans un réseau évolutif - Google Patents

Procédé, système et appareil de gestion des informations concernant les règles d'utilisation et de facturation associées au profil d'utilisateur dans un réseau évolutif Download PDF

Info

Publication number
WO2008019626A1
WO2008019626A1 PCT/CN2007/070471 CN2007070471W WO2008019626A1 WO 2008019626 A1 WO2008019626 A1 WO 2008019626A1 CN 2007070471 W CN2007070471 W CN 2007070471W WO 2008019626 A1 WO2008019626 A1 WO 2008019626A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
policy
identifier
information
function entity
Prior art date
Application number
PCT/CN2007/070471
Other languages
English (en)
French (fr)
Inventor
Guofeng Mao
Original Assignee
Huawei Technologies Co., Ltd.
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 Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2008019626A1 publication Critical patent/WO2008019626A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications

Definitions

  • the present invention relates to a technique for managing data in an evolved network, and more particularly to a method, system and apparatus for managing user policy charging control subscription information in an evolved network. Background of the invention
  • the telecommunication network is an operational network. To this end, accurate, timely and comprehensive control of the services used in the telecommunication network and the resources used by the service is required. Strategy and charging control is one of the most important contents.
  • the policy and charging functions are implemented by the Policy and Charging Control (PCC) framework.
  • the PCC framework is a functional framework that can be applied to multiple access technologies.
  • Some typical access technologies include the wireless access network of the Universal Mobile Telecommunication System (UMTS), and the global mobile communication system (GSM, Global System). For Mobile) / GSM (Enhanced Data Rates for GSM Evolution) Radio Access Network and Interworking-Wireless Access Network (I-WLAN).
  • UMTS Universal Mobile Telecommunication System
  • GSM Global System
  • GSM Global System
  • I-WLAN Interworking-Wireless Access Network
  • SBLP Service Based Local Prolicy
  • FBC Flow Based Charging
  • PCC combines the basic functions of SBLP and FBC, and further evolves in some aspects, such as implementing policy and charging control based on user policy charging control subscription information, and also updating the binding. mechanism.
  • Figure 1 shows the overall framework of the PCC.
  • the PCC mainly implements two major functions. First, strategic control System function; Second, the billing function.
  • the policy control function mainly includes: a. monitoring the service parameters of the user, such as the QoS (Quality of Service) parameter negotiation process; b, based on the obtained service information, the network bearer used by the service Authorize the resource; c. Control the passing of the service flow in real time on the data bearing surface; d. Notify the data bearing surface of the relevant changes in the business plane; e. Notify the relevant changes of the data bearing surface to the business plane; f. Perform policy control based on user policy charging control subscription information.
  • the logical entities involved in the policy control function include the Application Function Entity (AF), the Policy and Charging Rules Function (PCRF), and the Policy and Charging Enforcement Function Entity (PCEF, Policy). And Charging Enforcement Function ) and User Policy Signing Database (SPR, Subscription Profile Repository).
  • the charging function mainly includes: a. comprehensive service information, bearer information, and user policy charging control subscription information, and formulating charging rules; b. correlating between charging data of the service plane and charging data of the bearer plane; In the dynamic billing mode, credit control is performed.
  • the accounting entities involved in the accounting function include AF, PCRF, PCEF, SPR, Online Charging System (OCS), and Offline Charging System (OFCS).
  • AF An application function logic entity that provides access points for business applications.
  • the network resources used by these business applications require dynamic policy control.
  • the AF delivers related service information to the PCRF. If the service information is consistent with the policy of the PCRF, the PCRF accepts the negotiation; otherwise, the PCRF rejects the negotiation and simultaneously gives the business parameters acceptable to the PCRF in the feedback. The AF can then return these parameters to the user equipment (UE, User Equipment).
  • UE User Equipment
  • the interface between AF and PCRF is the Rx interface.
  • the Proxy Call Session Control Function P-CSCF
  • IMS IP Multimedia Subsystem
  • the policy control and charging rule function logic entity is the core of the PCC and is responsible for policy decision making and charging rules.
  • the PCRF provides network control rules based on traffic data flows, including traffic data flow detection, gating, QoS control, and data flow based charging control.
  • the PCRF sends its formulated policies and charging rules to the PCEF for execution, and the PCRF also ensures that these rules are consistent with the user's subscription information.
  • the basis for formulating policies and charging rules by the PCRF includes: obtaining information related to the service from the AF; obtaining subscription information with the user policy charging control from the SPR; and acquiring information related to the bearer network from the PCEF.
  • PCEF The policy control and charging rule execution function logic entity, usually located in the gateway (GW, GateWay), executes the policy and charging rules formulated by the PCRF on the bearer plane.
  • the PCEF performs service data flow detection according to the traffic filter in the rules sent by the PCRF, and then performs the policy and charging control established by the PCRF for these service flows.
  • the PCEF performs QoS authorization according to the rules sent by the PCRF, and performs gating operations according to the indication of the AF.
  • the charging rule sent by the PCRF the PCEF performs a corresponding service flow charging operation.
  • Billing can be either online or offline. In the case of online billing, PCEF needs to be credit managed with OCS.
  • the interface between the PCEF and the PCRF is a Gx interface
  • the interface with the OCS is a Gy interface
  • the interface between the OFCS and the OFCS is a Gz interface.
  • the PCEF is generally located on the gateway of the network, for example, a GPRS Gateway Support Node (GGSN) in GPRS and a Packet Data Gateway (PDG) in the I-WLAN.
  • GGSN GPRS Gateway Support Node
  • PGW Packet Data Gateway
  • SPR Stores user policy charging control subscription information related to policy control and charging, for example, service information that can be used by users, QoS information that can be used by user services, and Fee-related user policy charging control subscription information and user group categories.
  • the PCRF can perform policy control and charging operations based on user policy charging control subscription information.
  • the interface between SPR and PCRF is the Sp interface.
  • OCS Online billing system
  • PCEF PCEF - control and management of user credit in online charging mode.
  • PCEF In the process of bearer establishment, modification and suspension, PCEF must go to OCS for credit authentication.
  • the result of the credit authentication will directly affect the use of the user's service. For example, if the user's credit has been exhausted, the data bearer used by the service will be deleted immediately, and the user's service will be interrupted.
  • OFCS The offline charging system, together with the PCEF, completes the charging operation in the offline charging mode.
  • the PCEF addresses the appropriate PCRF based on the Public Data Network (PDN) information in the bearer setup process and the user ID (user ID is optional).
  • PDN Public Data Network
  • AF to PCRF addressing AF addresses the appropriate PCRF according to Internet Protocol (IP) address information and user identification (user identification is optional).
  • IP Internet Protocol
  • the PCRF receives a policy charging rule request message from the PCEF, and detects whether it stores the user policy charging control subscription information related to the message, if If not, the user policy charging control subscription information related to the message is obtained from the SPR. Subsequently, the PCRF uses the user policy charging control subscription information stored in the SPR or related to the message, and performs policy charging rule decision based on the user policy charging control subscription information related to the message, and determines the policy. The policy charging rule is sent to the PCEF. Finally, the PCEF performs policy charging for the user related to the message according to the received policy charging rule.
  • the same user usually allows network services to be used through one or more access points (APs, Access Point), that is, for the same user, there may be one or more user policy charging controls corresponding to the SPR.
  • Signing information, and the process of using the framework diagram shown in Figure 1 for policy and charging control only discloses the process of the PCRF to obtain the user policy charging control subscription information, and does not disclose that there are multiple user policies for the same user in a specific service.
  • the fee control subscription information how to selectively obtain the corresponding user policy charging control subscription information, so that the specific service is not implementable.
  • the PCRF finds that the user policy charging control subscription information related to the user is not stored, and the user identifier is sent.
  • the user policy charging control subscription information is requested to the SPR, and the SPR sends the corresponding user policy charging control subscription information to the PCRF according to the user identifier carried in the request, and the PCRF then controls the subscription information and the service requested by the user according to the received user policy.
  • Request a policy charging decision and send the policy charging decision to the PCEF for execution.
  • the specific process is as shown in FIG.
  • Step 201 The PCEF receives the service bearer setup request sent from the external node, and the PCEF addresses the correct PCRF according to the information carried in the received message. And sending a policy charging rule request message to the message, where the message carries the user identifier.
  • Step 203 The PCRF determines, according to the received user identifier carried in the message, whether the user policy charging control subscription information corresponding to the user identifier is stored, and if yes, proceeds to step 205 (this step is not shown in the figure); Otherwise, the user policy charging control subscription information request message is sent to the SPR.
  • Step 204 The SPR sends the stored user policy charging control subscription information to the PCRF according to the received information carried by the message.
  • Step 205 The PCRF carries the message according to the policy charging rule request received from the PCEF.
  • Step 206 The PCRF sends the policy charging rule after the decision to the PCEF, and the PCEF performs the policy charging control.
  • Step 207 If the current service bearer is related to online charging, the PCEF sends a credit request message to the OCS.
  • Step 208 The OCS sends a credit response message to the PCEF, where the message carries information about whether the service is provided for the service, and the PCEF performs policy charging control on the current service according to the information carried in the response message.
  • Step 209 The PCEF sends a service bearer setup response to the external node.
  • the technical solution only clarifies how the PCRF obtains the user subscription data from the SPR, but does not describe in detail how the SPR stores the address information of the PCRF.
  • the detailed description of how to delete the user policy charging control subscription information in the PCRF is not described in detail.
  • the SPR if the stored user policy charging control subscription information is deleted, the impact on the modification process in the PCRF is not described in detail; the related registration process after the user changes the registered PCRF is not described in detail.
  • Step 301 After the SPR modifies the user policy charging control subscription information stored by the SPR, the PCRF address corresponding to the subscription information is controlled according to the modified user policy saved by the SPR. The information, the user policy charging control subscription information modification request message is sent to the PCRF having the PCRF address information, and the message carries the modified user policy charging control subscription information and the user identifier.
  • Step 302 After receiving the message, the PCRF sends a response message to the SPR.
  • Step 303 The PCRF re-performs the policy charging decision according to the user policy charging control subscription information carried in the message and the existing service bearer information.
  • Step 304 The PCRF carries the re-decision policy charging rule in the policy charging rule request message to the PCEF.
  • Step 305 The PCEF initiates a service bearer modification request to the external node according to the policy charging rule carried in the received message.
  • Step 306 After the external node completes the service bearer modification, the service bearer modification response is sent to the PCEF.
  • Step 307 The PCEF sends a policy charging rule response to the PCRF.
  • Step 308 After detecting the service bearer resource transformation, the PCRF sends a notification request to the AF.
  • the technical solution described in FIG. 3 only clarifies that the SPR modifies the user policy charging control subscription information, and then sends a user policy charging control subscription information modification message to the corresponding PCRF, and the PCRF completes the modification process of the related service bearer.
  • the address information of the PCRF is not described in detail.
  • the user policy charging control subscription information before the modification is deleted in the PCRF is not described in detail.
  • the PCRF is The impact of the modification process is not described in detail; there is no detailed description of the relevant registration process after the user changes the registered PCRF.
  • the current scheme only proposes two processes: the PCRF obtains the user subscription data information from the SPR, and the SPR sends the modified user policy charging control subscription information to the PCRF and the PCRF to initiate the service bearer modification. Policy Billing Control Signing Letter The management of interest is still not perfect.
  • the PCEF addresses the PCRF based on the network identifier plus the user identifier, when the same user wants to access different services in multiple networks, it is possible to find different PCRFs, and the same user.
  • the user policy charging control subscription information may need to be saved in multiple PCRFs at the same time, that is, the address information of multiple PCRFs may need to be saved in the SPR. How the SPR stores one or more PCRF address information, and how to notify the PCRF that currently provides the policy charging service for the user to modify or delete the user policy according to the stored PCRF address information when modifying or deleting the user policy charging control subscription information.
  • the fee control contract information is not currently described. Summary of the invention
  • An embodiment of the present invention provides a method for managing user policy charging control subscription information in an evolved network, which can comprehensively manage user subscription data in an evolved network, and implement PCRF address information or PCRF connection identifier in the SPR.
  • the PCRF can correctly obtain the corresponding user policy charging control subscription information.
  • the embodiment of the present invention further provides a system for managing user policy charging control subscription information in an evolved network, which can comprehensively manage user subscription data in an evolved network, and implement PCRF address information or PCRF connection identifier in the SPR.
  • the PCRF can correctly obtain the corresponding user policy charging control subscription information.
  • the embodiment of the present invention further provides an apparatus for managing user policy charging control subscription information in an evolved network, where the device can comprehensively manage user subscription data in an evolved network, and implement PCRF address information or PCRF connection identifier in the SPR.
  • the PCRF can correctly obtain the corresponding user policy charging control subscription information.
  • Method for managing user policy charging control subscription information in an evolved network includes:
  • the user policy subscription database corresponding to the user identifier storage user policy charging control subscription information obtains the stored corresponding user policy charging control subscription information from the user policy subscription database according to the user identifier, or/and the user policy subscription database is modified or deleted according to the user identifier.
  • the corresponding user policy charging control subscription information is stored, or / and the user identifier is used to store, modify, or delete the current policy of using the user policy charging control subscription information and the address information or connection identifier of the charging rule function entity.
  • a system for managing user policy charging control subscription information in an evolved network comprising: a user policy subscription database and a policy and charging rule function entity, wherein information interaction is performed between the two, wherein
  • a user policy subscription database configured to store user policy charging control subscription subscription information corresponding to the user identifier, or/and a policy and charging rule function entity that stores, modifies, or deletes the current user policy charging control subscription information according to the user identifier.
  • the address information or the connection identifier; the policy and charging rule function entity is configured to obtain the corresponding user policy charging control subscription information from the user policy subscription database according to the user identifier, and is also used to control the subscription information according to the user policy subscription number.
  • the first storage module is configured to store a user policy charging control subscription information first information processing module corresponding to the user identifier, and is configured to modify according to the user identifier or Deleting corresponding user policy charging control subscription information in the first storage module;
  • a second storage module configured to store a current policy of using the user policy charging control subscription information and an address information or a connection identifier of the charging rule function entity;
  • a second information processing module configured to modify or delete the policy of the currently used user policy charging control subscription information and the address information or the connection identifier of the charging rule function entity in the second storage module according to the user identifier.
  • An apparatus for managing user policy charging control subscription information in an evolved network comprising a processing module, a receiving module, and a storage module, where
  • a receiving module configured to obtain, according to the user identifier, the corresponding user policy charging control subscription information from the user policy subscription database, and send the information to the processing module;
  • a processing module configured to store the user policy charging control subscription information received from the receiving module into the storage module, and perform, according to the processing of the user policy subscription database, modify or delete the corresponding user policy charging control subscription stored by the storage module according to the user identifier. information.
  • the SPR when the SPR stores the user policy charging control subscription information, the SPR stores the user identifier for storing; when storing the PCRF address information or the connection identifier of the current user policy charging control subscription information, It is also stored at least corresponding to the user identifier and the user policy charging control subscription information used. Further, the user policy charging control subscription information and the PCRF address information or the connection identifier using the user policy charging control subscription information may also be stored for the network identifier.
  • the PCRF when the PCRF obtains the user subscription data, the PCRF notifies the SPR to delete the stored PCRF address information or the connection identifier, and when the SPR initiates the user policy charging control subscription information deletion and the SPR initiates the PCRF cancellation registration, the corresponding The user identifier is obtained by obtaining the user policy charging control subscription information according to the corresponding user identifier and the network identifier, or obtaining the PCRF address information or the PCRF connection identifier to determine the corresponding PCRF, and performing corresponding processing.
  • the method, system, and device provided by the embodiments of the present invention comprehensively manage user subscription data in an evolved network, and implement PCRF address information or PCRF connection identifier in the SPR, and implement The PCRF can correctly obtain the corresponding user policy charging control subscription information.
  • FIG. 1 is a schematic diagram of a PCC overall frame of the prior art
  • FIG. 2 is a process flow diagram of the prior art using the framework diagram shown in FIG. 1 for policy charging control;
  • FIG. 3 is a flowchart of a method for performing policy charging control after a user policy charging control subscription information stored in an SPR modification
  • FIG. 4 is a flowchart of a method 1 for acquiring a user policy charging control subscription information by a PCRF to an SPR according to an embodiment of the present invention
  • FIG. 5 is a flowchart of a method 2 for acquiring a user policy charging control subscription information by a PCRF to an SPR according to an embodiment of the present invention
  • FIG. 6 is a flowchart of a third method for acquiring a user policy charging control subscription information by a PCRF to an SPR according to an embodiment of the present invention
  • FIG. 7 is a flowchart of a method for deleting a partial user policy charging control subscription information of a user by using an SPR according to an embodiment of the present invention
  • FIG. 8 is a flowchart of a method for deleting all user policy charging control subscription information of a user by using an SPR according to an embodiment of the present invention
  • FIG. 9 is a flowchart of a method for a PCRF to notify a SPR to delete a stored PCRF address information according to an embodiment of the present invention.
  • FIG. 10 is a flowchart of a second method for a PCRF to notify a SPR to delete a stored PCRF address information or a connection identifier according to an embodiment of the present invention
  • FIG. 11 is a flowchart of a third method for a PCRF to notify a SPR to delete a stored PCRF address information or a connection identifier according to an embodiment of the present invention
  • FIG. 12 is an SSR notification by the HSS according to an embodiment of the present invention, and the registration is cancelled by the SPR.
  • FIG. 13 is a first-class diagram of an implementation method of the second processing flow of the fourth processing flow according to an embodiment of the present invention.
  • FIG. 14 is a second flowchart of an implementation method of a second processing flow for implementing a second processing flow according to an embodiment of the present invention
  • FIG. 15 is a flowchart of a method for implementing a fourth process flow according to an embodiment of the present invention
  • FIG. 16 is a schematic diagram of a system for managing user policy charging control subscription information according to an embodiment of the present invention
  • FIG. 17 is a schematic diagram of an apparatus for managing user policy charging control subscription information according to an embodiment of the present invention.
  • FIG. 18 is a schematic diagram of an apparatus for managing user policy charging control subscription information according to an embodiment of the present invention. Mode for carrying out the invention
  • the SPR uses the network identifier and the user identifier to store a PCRF address information or a connection identifier to store different PCRFs that currently provide services for the user.
  • the user policy charging control subscription information is also distinguished by the network identifier and the user identifier, so that the PCRF can obtain the correct user policy charging control subscription information according to the two identifiers, and the network identifier can be a PDN identifier or an access point name (APN, Access Point Name ).
  • the network policy and the user identifier may also be used to indicate the modified or deleted user policy charging control subscription information, so that the PCRF correctly knows which user the network in which the service has been modified or deleted, and initiates the corresponding The business bears the modification or deletion operation.
  • the PCRF is notified when the service bearer is deleted in the PCEF.
  • the PCRF determines whether the last service-related bearer of the user has been deleted. If not, the processing is not performed; if yes, the set time is waited after the set time. It is used to ensure that the user policy charging control subscription information is used in the subsequent service bearer establishment process, which can reduce the service bearer establishment time.
  • the PCRF determines whether the service bearer request of the user is not received after the set time expires. If yes, the PCRF deletes the user policy charging control subscription information of the user stored by the PCRF, and notifies the SPR of the user policy charging control of the user. The subscription information has been deleted, and the SPR will delete the address information or connection identifier of the PCRF that initiated the notification. The user policy payment control subscription information that informs the user that the subscription information has been deleted is notified by sending a cancellation notification request message.
  • the SPR initiates a PCRF deregistration process for the stored PCRF address information or connection identifier.
  • the SPR save user policy charging control subscription information is saved for the user identifier, or is saved for the user identifier and the network identifier.
  • the PCRF sends a policy charging rule request message to the SPR, where the message includes a user identifier, and may also include a network identifier, which is used to identify a PCRF that provides services for the UE.
  • the SPR stores the address information of the PCRF or stores a connection identifier that can represent the PCRF address information.
  • the user ID and the PCRF address information or the PCRF connection identifier may be saved in the SPR.
  • a PCRF is shown; it may also be a user identifier, a network identifier currently serving the UE, and a PCRF connection identifier or a PCRF connection identifier indicating a PCRF.
  • the SPR carries information according to the request message sent by the PCRF (in this case, the request message needs to carry information about whether the subscription notification is signed), and determines whether the user policy charging control is required.
  • the subscription information is used for subscription notification. If yes, the method of the present invention is used to store the address information or the connection identifier of the PCRF; otherwise, the SPR does not store the address information or the connection identifier of the PCRF.
  • the network identifier currently serving the UE is a PDN identifier or an APN identifier.
  • the SPR sends the user policy charging control subscription information corresponding to the user identifier carried in the request message to the PCRF. If the request message has a network identifier, the sent user policy charging control subscription information also needs to correspond to the network identifier.
  • FIG. 4 is a flowchart of a method 1 for acquiring a user policy charging control subscription information by a PCRF to an SPR according to an embodiment of the present invention.
  • the method is applied to an AF bearer-free service bearer establishment or modification process, and the specific steps are as follows:
  • Step 401 The PCEF receives a request for establishing or modifying a service bearer from an external node.
  • Step 402 The PCEF sends a policy charging rule request message to the PCRF, where the message carries information such as a user identifier and service related information.
  • Step 403 The PCRF detects that there is no user policy charging control subscription information that carries the user identifier in the message, and a policy charging rule that is required by the service, and sends a policy charging rule request message to the SPR, where the message carries the user identifier, and may also carry The network identifier of the network where it is located.
  • Step 404 The SPR stores the address information of the PCRF or stores a connection identifier that can represent the PCRF address.
  • the storage manner is stored by using the address information or the connection identifier of the PCRF corresponding to the user identifier, or the address of the PCRF corresponding to the user identifier and the network identifier. Letter Information or connection identifier storage.
  • the SPR determines whether to subscribe to the user policy charging control according to the information in the request message sent by the PCRF (in this case, the request message carries information that is subscribed to the notification information). The information is signed with a subscription notification. If yes, the SPR stores the PCRF address information or the connection identifier; otherwise the SPR does not store the PCRF address information or the connection identifier.
  • Step 405 The SPR sends the user policy charging control subscription information corresponding to the user identifier to the PCRF.
  • Step 406 The PCRF performs policy decision according to the received user policy charging control subscription information corresponding to the user identifier.
  • Step 407 The PCRF sends a policy charging rule information response to the PCEF, and carries the policy charging rule that has been decided.
  • Step 408 The PCEF sends a response message of the bearer establishment or modification to the external node.
  • FIG. 5 is a flowchart of a method 2 for acquiring a user policy charging control subscription information from a PCRF to an SPR according to an embodiment of the present invention. The method is applied to an AF bearer service bearer establishment or modification process, and the specific steps are as follows:
  • Step 501 The AF sends application or service related data information to the PCRF, including user identification, and application or service content.
  • Step 502 The PCRF sends a response message to the AF.
  • Step 503 The PCEF receives a request message for establishing or modifying a service bearer from an external node.
  • Step 505 The PCRF associates the service related information in the request message with the application or service related data information received from the AF.
  • Step 506 The PCRF detects that there is no user policy that has the user identifier of the message.
  • the fee control subscription information and the policy charging rule required by the service send a policy charging rule request message to the SPR, where the message carries the user identifier, and may also carry the network identifier of the network.
  • Step 507 The SPR stores the address information of the PCRF or stores a connection identifier that may indicate a PCRF address, where the storage is performed by using the address information or the connection identifier of the PCRF corresponding to the user identifier, or the address of the PCRF corresponding to the user identifier and the network identifier. Information or connection ID storage.
  • the SPR determines whether to subscribe to the user policy charging control according to the information in the request message sent by the PCRF (in this case, the request message carries information that is subscribed to the notification information). The information is signed with a subscription notification. If yes, the SPR stores the PCRF address information or the connection identifier; otherwise the SPR does not store the PCRF address information or the connection identifier.
  • Step 508 The SPR sends the user policy charging control subscription information corresponding to the user identifier to the PCRF.
  • Step 509 The PCRF performs policy decision according to the received user policy charging control subscription information corresponding to the user identifier.
  • Step 510 The PCRF sends a policy charging rule information response to the PCEF, and carries the policy charging rule that has been decided.
  • Step 511 The PCEF sends a response message of the bearer establishment or modification to the external node.
  • FIG. 6 is a flowchart of a third method for acquiring a user policy charging control subscription information by a PCRF to an SPR according to an embodiment of the present invention.
  • the method is applied to a service bearer establishment or modification process initiated by a network side related to an AF, and the specific steps are as follows:
  • Step 601 The AF sends the application or service related data information to the PCRF, including the user identifier, and the content of the application or the service.
  • Step 602 The PCRF detects that there is no user policy charging control subscription information with the user identifier of the message and a policy charging rule required by the service, and sends a policy charging rule to the SPR.
  • the request message carries the user identifier and can also carry the network identifier of the network.
  • the SPR determines whether to subscribe to the user policy charging control according to the information in the request message sent by the PCRF (in this case, the request message carries information that is subscribed to the notification information). The information is signed with a subscription notification. If yes, the SPR stores the PCRF address information or the connection identifier; otherwise the SPR does not store the PCRF address information or the connection identifier.
  • Step 604 The SPR sends the user policy charging control subscription information corresponding to the user identifier to the PCRF.
  • Step 605 The PCEF sends a policy charging rule request message to the PCRF, where the message includes the user identifier and the service related information.
  • Step 606 The PCRF performs policy decision according to the received user policy charging control subscription information and information included in the request message received from the PCEF.
  • Step 607 The PCRF sends a policy charging rule response to the PCEF, and carries the policy charging rule that is determined.
  • Step 608 The PCEF sends a request message for establishing or modifying a service bearer to the external node.
  • the method for modifying the user policy charging control subscription information initiated by the SPR and the method for deleting the user policy charging control subscription information initiated by the SPR is the same as the prior art. The only difference is that the method for saving the PCRF address information or the connection identifier is specifically limited in the first processing, so it can be easily After the PCRF having the PCRF address information or the connection identifier is found according to the manner, the user policy charging control subscription information modification is initiated to the PCRF.
  • the method may further include the process of increasing user subscription data.
  • the process of deleting the user policy charging control subscription information initiated by the SPR is as follows: First, all or part of the user policy charging control subscription information of one user is deleted in the SPR, and the SPR is based on the saved PCRF address information or the connection identifier of the user. And transmitting a user policy charging control subscription information deletion request message to the PCRF (one or more) corresponding to all or part of the user policy charging control subscription information to be deleted. If the subscription notification is used between the PCRF and the SPR, the SPR needs to determine whether the user has subscribed to the subscription notification. If the subscription notification is signed, the SPR sends the user policy charging control subscription information deletion request message to the PCRF. Otherwise, the SPR The user policy charging control subscription information deletion request message is not sent to the PCRF.
  • the PCRF sends a service bearer notification of the user to the PCEF, and the corresponding service bearer is deleted by the PCEF.
  • the SPR deletes the address information or the connection identifier of the PCRF corresponding to all or part of the user policy charging control subscription information to be deleted.
  • FIG. 7 is a flowchart of a method for deleting a partial user policy charging control subscription information of a user by using an SPR according to an embodiment of the present invention.
  • deleting some user policy charging control subscription information of the user in the SPR it is required to notify the stored in the SPR.
  • the user needs to delete the PCRF corresponding to the partial user policy charging control subscription information.
  • the PCRF deletes the user policy charging control subscription information corresponding to the user, and sends the deletion by the PCRF.
  • Corresponding service bearer notification message to PCEF sent by PCEF
  • the service bearer corresponding to the user is deleted, and the specific steps are as follows:
  • Step 701 Delete part of the user policy charging control subscription information of the specified user in the SPR, and send the delete user policy charging control according to the PCRF address information or the connection identifier that stores the partial user policy charging control subscription information to be deleted.
  • the subscription information request message is sent to the PCRF, and the message carries the user identifier corresponding to the partial user policy charging control subscription information to be deleted, and may also carry the network identifier corresponding to the partial user policy charging control subscription information to be deleted.
  • the user can store different user policy charging control subscription information in the SPR for different network services. Therefore, when deleting, only part of the user policy charging control subscription information may be deleted.
  • the SPR needs to determine whether the user signs a subscription notification (pre-sent in the SPR whether the user has subscribed to the subscription notification). If yes, the SPR sends the deletion user policy to the PCRF. The charging control subscription information request message; otherwise, the SPR does not send the delete user policy charging control subscription information request message to the PCRF.
  • Step 702 The PCRF sends a delete user policy charging control subscription information response to the SPR, and the SPR deletes the stored address information or the connection identifier of the PCRF.
  • Step 703 The PCRF determines, according to the user identifier and the network identifier that is received by the request message, that the corresponding service bearer is to be deleted, and sends the corresponding service bearer request message to the corresponding PCEF (which is saved in the corresponding service bearer in the PCRF).
  • the address information of the PCEF, the request message includes information such as a user identifier, a session identifier, and a bearer identifier for identifying a corresponding service bearer.
  • the PCRF may determine that the corresponding service bearer is to be deleted according to the network identifier and the user identifier of the network where the user is located.
  • Step 704 The PCRF deletes the user identifier network identifier carried in the request message. Corresponding policy charging rule information stored in addition to itself.
  • Step 705 The PCEF sends a service bearer deletion request message to the external node, and carries the service bearer to be deleted, and instructs the external node to finally complete the deletion of the service bearer.
  • Step 706 Delete the policy charging rule information corresponding to the service bearer in the PCEF.
  • Step 707 The PCEF sends a credit end report request to the OCS, and returns the remaining credit of the user to the OCS. This step is an optional step.
  • Step 708 The OCS sends a credit end report response message to the PCEF. This step is optional.
  • Step 709 The PCEF receives the service bearer deletion response sent by the external node.
  • Step 710 The PCEF sends a delete service bearer response message to the PCRF.
  • Step 711 The PCRF notifies the AF of the information deleted by the service bearer. This step is optional.
  • Step 712 The AF sends a service bearer deletion response message to the PCRF.
  • FIG. 8 is a flowchart of a method for deleting all user policy charging control subscription information of a user by using an SPR according to an embodiment of the present invention.
  • the PCRF deletes the user policy charging control subscription information of the user, and sends and deletes the corresponding service.
  • the bearer's notification message is sent to the PCEF, and the PCEF initiates the deletion of the service bearer corresponding to the user.
  • Step 801 Delete all user policy charging control subscription information of the specified user in the SPR, and send the delete user policy charging control subscription according to the PCRF address information or the connection identifier that stores the accounting control subscription information corresponding to all user policies of the user.
  • the information request message is sent to the PCRF, and the message carries the user identifier corresponding to the user policy charging control subscription information, and may also carry the network identifier corresponding to the user policy charging control subscription information. If the working mode of the subscription notification is used between the PCRF and the SPR, the SPR needs to determine whether the user signs a subscription notification. If the subscription notification is signed, the SPR sends a message request for deleting the user policy charging control subscription information to the PCRF; otherwise, the SPR does not send to the PCRF. Send a delete user policy charging control subscription information request message.
  • Step 802 The PCRF sends a delete user policy charging control subscription information response to the SPR, and the SPR deletes the saved PCRF address information or connection identifier corresponding to all user policy charging control subscription information of the user to be deleted.
  • Step 803 The PCRF determines the corresponding service bearer according to the user identifier and the network identifier that are received by the request message, and sends a delete service bearer request message to the corresponding PCEF, where the request message includes the user identifier, the session identifier, and the bearer identifier. Identifies the information carried by the service.
  • the PCRF may determine that the corresponding service bearer is to be deleted according to the network identifier and the user identifier of the network where the user is located.
  • Step 804 The PCRF deletes the corresponding policy charging rule information stored by the user according to the user identifier and the network identifier that are received by the request message.
  • Step 805 The PCEF sends a bearer deletion request message to the external node, and carries the service bearer to be deleted, and instructs the external node to finally complete the deletion of the service bearer.
  • Step 806 Delete the policy charging rule information corresponding to the service bearer in the PCEF.
  • Step 807 The PCEF sends a credit end report request to the OCS, and returns the remaining credit of the user to the OCS. This step is an optional step.
  • Step 808 The OCS sends a credit end report response message to the PCEF. This step is optional.
  • Step 809 The PCEF receives the service bearer deletion response sent by the external node.
  • Step 810 The PCEF sends a delete service bearer response message to the PCRF.
  • Step 811 The PCRF notifies the AF of the information that the service bearer is deleted. This step is optional.
  • Step 812 The AF sends a service bearer deletion response message to the PCRF. This step is optional.
  • the time is determined by the configuration, and may be zero, if the user is detected. If there are other service bearers, the user policy charging control subscription information is saved; if not, the process proceeds to the next step.
  • the user policy charging control subscription information carrying the indication PCRF address information or the connection identifier is sent to the SPR, and the indication may be a cancellation notification request message, and the SPR is deleted.
  • This PCRF address information or connection identifier of the user is sent to the SPR, and the indication may be a cancellation notification request message, and the SPR is deleted.
  • the SPR only deletes the user identifier and The PCRF address information or the connection identifier corresponding to the network identifier; if the indication PCRF address information or the connection identifier received by the SPR is the UE identity identifier, that is, the cancellation notification request message only includes the PCRF address information or the connection identifier is the UE identifier identifier, The SPR deletes all the address information or the connection identifier of the PCRF that holds the user policy charging control subscription information.
  • the PCRF sends a connection disconnection indication to the SPR, and clears the address information or the connection identifier of the saved disconnected PCRF.
  • the PCRF needs to determine whether the user has subscribed to the SPR. If yes, the PCRF sends a user policy charging control subscription information deletion indication to the SPR, and the indication may be The notification request message is cancelled; otherwise, the PCRF does not need to send the user policy charging control subscription information deleted indication to the SPR, and the indication may be a cancellation notification request message. Finally, after the SPR is processed, a response message is sent to the PCRF.
  • the third processing flow is generally implemented.
  • FIG. 9 is a flowchart of a method for a PCRF to notify a SPR to delete a stored PCRF address information or a connection identifier according to an embodiment of the present invention. The method is triggered by a PCRF to delete a service bearer, and a user-related user policy charging control subscription is deleted in the PCRF. Information, the specific steps are:
  • Step 901 The PCEF receives the indication that the external node deletes the service or decides to delete the service, and sends the service bearer deletion indication request message to the PCRF, where the message carries the user identifier corresponding to the service bearer and the bearer related information.
  • Step 902 The PCRF modifies or deletes the policy charging rule information related to the service bearer according to the information carried in the request message.
  • Step 903 The PCRF sends a bearer deletion notification request message to the AF. This step is optional.
  • Step 904 The AF sends a notification response message to the PCRF. This step is optional.
  • Step 905 The PCRF sends a delete related service bearer response message to the PCEF.
  • Step 906 After detecting that there is no service bearer related to the user corresponding to the service bearer to be deleted, the PCRF continues to save the user policy charging control subscription information for a certain period of time; no new service bearer is established for a certain period of time. The process, the PCRF deletes the user policy charging control subscription information of the user.
  • This can be configured in a range for a certain period of time, or it can be set to zero.
  • the setting is zero, it means that when the PCRF detects that the user does not have any related service bearers, it directly deletes the user policy charging control subscription information of the user.
  • Step 907 The PCRF sends the user policy charging control subscription information to delete the indication message to
  • the message carries the user ID of the user, and optionally includes information such as a network identifier.
  • the message may be a cancel notification request message.
  • the PCRF needs to determine whether the user signs a subscription notification to the SPR (in this case, whether the subscription notification information is pre-stored in the PCRF), and if so, the PCRF The SPR sends the user policy charging control subscription information deleted indication message; otherwise, the PCRF does not send the user policy charging control subscription information deleted indication message to the SPR.
  • Step 908 After receiving the indication message, the SPR deletes the PCRF address information or the connection identifier that is stored corresponding to the UE identity user identifier carried in the message.
  • the SPR deletes only the PCRF address information or the connection identifier indicated by the user identifier and the network identifier; if the SPR receives the indication message carrying the user identifier, the SPR deletes All PCRF address information or connection identifier corresponding to the user indicated by the user identifier.
  • Step 909 The SPR sends the user policy charging control subscription information to delete the response message to the PCRF.
  • the response may be a cancellation notification response.
  • the user policy charging control subscription information in the PCRF can be saved for a long time when there is no service bearer, and the bearer setup time can be reduced when the service is continued for a certain period of time, and the interface between the PCRF and the SPR can be reduced.
  • FIG. 10 is a flowchart of a second method for a PCRF to notify a SPR to delete a stored PCRF address information or a connection identifier according to an embodiment of the present invention.
  • the method is triggered by an AF to delete a service bearer, and the user policy charging control corresponding to the service bearer is deleted in the PCRF. Signing information, the specific steps are:
  • Step 1001 The AF receives an indication that the external node deletes the service, and sends a service bearer deletion indication request message to the PCRF, where the message carries the user identifier corresponding to the service bearer. Contain relevant information.
  • Step 1002 The PCRF sends a service bearer deletion notification request message to the PCEF.
  • Step 1003 The PCRF modifies or deletes the policy charging rule information corresponding to the service bearer according to the received request message.
  • step 1003 and step 1002 can be interchanged.
  • Step 1004 The PCEF completes the main operation of the service bearer deletion, and needs to interact with the external node. After completing the service bearer deletion, the PCEF sends a service deletion response message to the PCRF.
  • Step 1005 The PCRF sends a bearer deletion notification response message to the AF.
  • Step 1006 After the PCRF detects that there is no service bearer corresponding to the user corresponding to the service bearer to be deleted, the user policy charging control subscription information of the user is saved for a long time; no new service bearer is established for a certain period of time. The process, the PCRF deletes the user policy charging control subscription information of the user.
  • This can be configured in a range for a certain period of time, or it can be set to zero.
  • the setting is zero, it means that when the PCRF detects that the user does not have any related service bearers, it directly deletes the user policy charging control subscription information of the user.
  • Step 1007 The PCRF sends a user policy charging control subscription information deletion indication message to the SPR, where the message carries the user identifier of the user, and optionally includes information such as a network identifier.
  • the message may be a cancel notification request message.
  • the PCRF needs to determine whether the user signs a subscription notification to the SPR (in this case, whether the subscription notification information is pre-stored in the PCRF), and if so, the PCRF The SPR sends the user policy charging control subscription information deleted indication message; otherwise, the PCRF does not send the user policy charging control subscription information deleted indication message to the SPR.
  • Step 1008 After receiving the indication message, the SPR deletes the stored corresponding to the message carrying The PCRF address information or connection identifier of the user ID.
  • the SPR deletes only the PCRF address information or the connection identifier indicated by the user identifier and the network identifier; if the SPR receives the indication message carrying the user identifier, the SPR deletes All PCRF address information or connection identifier corresponding to the user indicated by the user identifier.
  • Step 1009 The SPR sends the user policy charging control subscription information to delete the response message to the PCRF.
  • the response may be a cancellation notification response.
  • FIG. 11 is a flowchart of a third method for the PCRF to notify the SPR to delete the stored PCRF address information or the connection identifier according to the embodiment of the present invention.
  • the method deletes the user policy charging control subscription information of a user in the PCRF, To inform SPR, the specific steps are:
  • Step 1101 Delete the user policy charging control subscription information of the user in the PCRF.
  • Step 1102 The PCRF sends the user connection disconnection indication message to the SPR.
  • the PCRF needs to determine whether the user signs a subscription notification to the SPR. If yes, the PCRF needs to send the user connection disconnection indication message to the SPR; otherwise, the PCRF does not send the subscription to the SPR. The user disconnects the indication message.
  • Step 1103 The SPR deletes the stored address information or connection identifier of the PCRF corresponding to the initiate disconnection indication message.
  • Step 1104 The SPR sends the user connection disconnection response message to the PCRF, and deletes the related connection with the sending the user connection disconnection indication message.
  • Implementation method one First, the UE initiates an attach operation to a Mobile Management Equipment (MME), and the MME sends a registration request message to a Home Subscriber Server (HSS), and indicates in the registration request message that the registration request message is an attach operation of the UE. And information such as user identification.
  • MME Mobile Management Equipment
  • HSS Home Subscriber Server
  • the HSS determines whether the MME that the UE currently provides the service changes, and if yes, sends a notification message to the SPR; if not, does not send the notification message to the SPR, the notification message includes the user identifier, It is indicated as an attachment operation.
  • the SPR receives the notification message, and detects whether to save the PCRF address information or the connection identifier of the user policy charging control subscription information corresponding to the user identifier, where the PCRF address information or the connection identifier further corresponds to the network identifier currently serving the UE. If so, a deregistration request message is sent to the one or more PCRFs (possibly storing multiple PCRF address information in the SPR); otherwise, the deregistration request message is not sent.
  • the deregistration request message includes the user ID and other possible information, and the SPR deletes the saved user policy charging control subscription information corresponding to the user identifier.
  • the one or more PCRFs delete the user policy charging control subscription information in the PCRF corresponding to the user identifier according to the user identifier and other possible information, if the PCRF detects that there is still a corresponding The service bearers, then the PCRF deletes these corresponding service bearers.
  • the MME and the user plane entity (UPE) are separated or unrelated.
  • the user policy charging control subscription information buffered by some PCRFs before the attach operation procedure can be deleted.
  • the implementation of the method can ensure that the user policy charging control subscription information stored in the PCRF is deleted in some abnormal situations, such as when the service bearer is deleted, and the user subscription data on the PCRF is not correctly deleted.
  • the UE initiates an attach operation to the MME/UPE.
  • the PCEF (located at the UPE or the anchor) sends a registration request message to the PCRF to which the UE switches, and indicates in the registration request message that the operation is an attach operation and carries a user identifier.
  • the PCRF After receiving the registration request message from the PCEF, the PCRF that the UE switches to sends a user policy charging control subscription information acquisition request message to the SPR, where the request message indicates an attach operation, and carries information such as the user identifier.
  • the SPR receives the request message, and after checking the indication of the attach operation, detects whether the PCRF address information or the connection identifier corresponding to the user identifier is saved, and if yes, sends a cancel registration request message to the corresponding user identifier. Or multiple PCRFs (possibly storing multiple PCRF address information or connection identifiers in the SPR); otherwise, the unregistration request message is not sent.
  • the SPR deletes the saved user policy charging control subscription information corresponding to the UE.
  • the one or more PCRFs After receiving the unregistering request message of the SPR, the one or more PCRFs delete the user policy charging control subscription information corresponding to the UE in the PCRF according to the user identifier and other possible information, if the PCRF detects that there is still a corresponding service bearer Then, the PCRF deletes these corresponding service bearers.
  • the AF or PCEF initiates a service bearer setup process to interact with the PCRF, and sends the user identifier and related information carried by the service to the PCRF in the process of interaction.
  • the PCRF detects that there is no user policy charging control subscription information with the user identifier, and sends a user policy charging control subscription information request message to the SPR, where the message carries information such as the user identifier and the network identifier;
  • the user policy charging control subscription information does not send the user policy charging control subscription information request message to the SPR.
  • the SPR detects whether there is a corresponding PCRF address information or a connection identifier according to the user identifier and the network identifier carried in the received request message, and if yes, sends an unregister.
  • the message is sent to the PCRF with the PCRF address information or connection identifier.
  • the unregistration message includes information such as a user identifier and a network identifier for providing services to the user, and the SPR deletes the PCRF address information or the connection identifier.
  • connection ID is not deleted.
  • the PCRF After receiving the unregistration message, the PCRF deletes the corresponding user policy charging control subscription information according to the user identifier carried in the message and the network identifier. If the PCRF detects that there is still a service corresponding to the user policy charging control subscription information, After the bearer, the PCRF deletes these corresponding service bearers.
  • the PCRF may also continue to store user policy charging control subscription information related to other network identifiers serving the user.
  • FIG. 12 is a flowchart of a method for notifying an SPR by an HSS, and initiating a registration cancellation operation to a PCRF by an SPR according to an embodiment of the present invention, where the specific steps are as follows:
  • Step 1201 The UE determines that an attach operation needs to be initiated.
  • Step 1202 The UE sends an attach request message to the MME, where the message carries information such as a user identifier and an attach indication.
  • Step 1203 The MME sends a registration request message to the HSS, where the message carries the user identifier and indicates an attach operation.
  • Step 1204 The HSS detects whether the MME serving the UE changes, and if yes, sends a cancel location request message to the MME before handover.
  • Step 1205 The MME before the handover sends a cancel location response to the HSS.
  • Step 1206 The HSS detects whether the MME serving the UE changes. If yes, the HSS sends a notification request message to the SPR, where the notification message carries the user identifier and indicates an attach operation.
  • Steps 1204 and 1206 have no clear timing requirements and can be interchanged.
  • Step 1207 The HSS initiates a process of inserting user data, and inserts related user data into the switched MME. This step is optional.
  • Step 1208 The SPR detects whether the PCRF address information or the connection identifier corresponding to the user identifier is saved, and if yes, sends a deregistration request message to each PCRF (multiple PCRF address information or connection identifier may be saved in the SPR); if not, Then the unregistration request message is not sent to the PCRF.
  • the SPR sends a deregistration request message to the PCRF before the handover, which carries the user identifier and other possible information.
  • Step 1209 The PCRF before the handover deletes all the user policy charging control subscription information corresponding to the user identifier according to the information carried in the received message. If the related bearer is still present, the process of deleting the related service bearer is initiated.
  • Step 1210 The PCRF before the handover sends a cancel registration response message to the SPR, and the SPR deletes the address information or the connection identifier of the PCRF before the handover; and the operation of deleting the PCRF before the handover may also be completed after the step 1208.
  • Step 1211 The SPR sends a notification response message to the HSS.
  • Step 1212 The HSS sends a registration accept message to the MME.
  • Step 1213 The MME sends an attach accept message to the UE.
  • FIG. 13 is a flowchart of a method for implementing the second processing flow of the second embodiment of the present invention. The method is applied to the scenario where the MME and the UPE are merged. The specific steps are as follows: Step 1301: The UE determines that an attach operation is required.
  • Step 1302 The UE sends an attach request message to the switched MME/UPE.
  • the message contains information such as the user ID and attachment indication.
  • Step 1303 The switched MME/UPE sends a registration request message to the HSS.
  • Step 1304 The HSS performs a process of inserting user data, and inserts user data into the MME/UPE that is switched to. This step is optional.
  • the HSS sends a Cancel Location message to the MME/UPE before the UE handover.
  • Step 1305 The HSS sends a registration response to the MME/UPE to which the handover is made.
  • Step 1306 The MME/UPE that is switched to selects a PCRF according to the requirement of the service bearer establishment and the user policy charging control subscription information, and sends a registration request message to the PCRF, indicating that the operation is initiated by the attach operation, specifically Specify in a field.
  • step 1306 can be performed prior to step 1304.
  • Step 1307 The PCRF sends a user policy charging control subscription information request message to the SPR, where the request message indicates the UE attach operation, and the user identifier and the like.
  • Step 1308 The SPP detects whether the PCRF address information or the connection identifier corresponding to the user identifier is saved, and if yes, sends a cancel registration request message to each PCRF (several PCRF address information or connection identifier may be saved in the SPR); if not, Then the unregistration request message is not sent to the PCRF.
  • the SPR sends a deregistration request message to the PCRF before the handover according to the originally stored PCRF address information or connection identifier, and the message includes the user identifier and other possible information.
  • Step 1309 After receiving the unregistration request message, the PCRF before the handover deletes the user policy charging control subscription information corresponding to the user identifier, and deletes the corresponding service bearer.
  • Step 1310 The PCRF before the handover sends a cancel registration response message to the SPR.
  • Step 1311 The SPR deletes the PCRF address information or the connection identifier before the handover, and saves the switched PCRF address information or the connection identifier.
  • the SPR sends a user policy charging control subscription information response to the switched PCRF, where the message carries the user identifier and the user policy charging control subscription information.
  • Step 1312 The switched PCRF sends a registration response message to the switched MME/UPE.
  • Step 1313 The switched MME/UPE sends an attach accept message to the UE.
  • the scenario of MME/UPE merging is depicted in Figure 13, and the PCEF is located at MME/UPE. If the PCEF is in the Anchor and the UPE is not in a network element, the MME/UPE needs to send a registration request message to the PCEF (Anchor), and then the PCEF (Anchor) registers with the PCRF to perform a message relay.
  • FIG. 14 is a second flowchart of a method for implementing the second processing flow of the second embodiment of the present invention, where the method is applied to a scenario in which the MME and the UPE are separated, and the specific steps are as follows:
  • Step 1401 The UE determines to perform an attach operation.
  • Step 1402 The UE sends an attach request message to the MME after the handover, and carries information such as a user identifier and an attach indication in the message.
  • Step 1403 The switched MME sends a registration request message to the HSS.
  • Step 1404 The HSS performs a process of inserting user data, and inserts user data into the switched MME. This step is optional.
  • the HSS Prior to step 1404, the HSS sends a Cancel Location message to the MME prior to handover.
  • Step 1405 The HSS sends a registration response to the MME after the handover.
  • Step 1406 The switched MME selects a UPE (PCEF) according to the service bearer establishment requirement and the user policy charging control subscription information, and sends a registration request message to the UPE (PCEF), indicating in the message that the operation is initiated by the attach operation.
  • PCEF UPE
  • Specific can be at some Specify in the field.
  • step 1406 can be performed prior to step 1404.
  • Step 1407 UPE (PCEF) selects a PCRF, and sends a registration request message to the PCRF, indicating in the message that the operation is initiated by an attach operation. This can be specified in a field.
  • Step 1408 The PCRF sends a user subscription data request message to the SPR, where the request message indicates an attach operation, and a user identifier.
  • Step 1409 The SPR detects whether the address information or the connection identifier of the PCRF corresponding to the user identifier is saved. If yes, the unregistration message is sent to each PCRF (several PCRF addresses may be saved in the SPR); if not, the unregistration is not sent. Message to the PCRF.
  • the SPR Based on the originally stored PCRF address information or connection identifier, the SPR sends a deregistration request to the pre-switched PCRF, which contains the user ID and other possible information (including the type of access technology).
  • Step 1410 After receiving the unregistration request message, the PCRF before the handover deletes the subscription data information corresponding to the user identifier, and deletes the corresponding service bearer.
  • Step 1411 The PCRF sends a registration response message to the SPR.
  • Step 1412 The SPR sends a user policy charging control subscription information response to the PCRF after the handover, where the message includes the user identifier and the user policy charging control subscription information, and the SPR deletes the address information or the connection identifier of the PCRF before the handover, and saves Address information or connection identifier of the switched PCRF.
  • Step 1413 The switched PCRF sends a registration response message to the UPE (PCEF).
  • Step 1414 The UPE (PCEF) sends an attach accept message to the MME.
  • Step 1415 The MME sends an attach accept message to the UE.
  • the PCEF is located in the UPE. If the PCEF is located in the SAE Anchor and the UPE is not in a network element, you can register in two cases. If there is an interface between the MME and the PCEF (SAE Anchor), the MME needs to send a registration request message to the PCEF (SAE Anchor), and then register with the PCF (SAE Anchor) to the PCRF. If there is an interface between the MME and the PCEF (SAE Anchor), the MME needs to send a registration request message to the UPE, and then the UPE forwards it to the PCEF (SAE Anchor) and registers it in the PCRF.
  • FIG. 15 is a flowchart of a third method for implementing the fourth processing flow according to an embodiment of the present invention, where the specific steps are as follows:
  • Step 1501 The PCRF receives the service bearer setup information from the external node such as the PCEF or the AF, and the PCRF sends a user policy charging control subscription information request message to the SPR, where the message carries the user identifier of the user and the network identifier for providing the service to the user. information.
  • Step 1502 In the SPR, according to the information carried in the received message, it is detected whether the network serving the user has already registered the PCRF to the SPR. If yes, the unregistered message is sent to the relevant PCRF, and the unregistered message is carried. Other information such as the user ID of the user and the network identifier that provides the service to the user, and the SPR deletes the original PCRF address information or connection identifier stored.
  • Step 1503 After receiving the unregistration request message, the related PCRF determines the user according to the carried user identifier and the network identifier that provides the service for the user, and deletes the user policy charging control subscription information of the user in the PCRF.
  • Step 1504 The related PCRF sends a cancel registration response message to the SPR.
  • Step 1505 The SPR sends the user policy charging control subscription information response to the PCRF in step 1500, where the message includes information such as the user identifier and the user policy charging control subscription information, and saves the PCRF address information or the connection identifier described in step 1500. . How to save It can refer to the first processing flow.
  • the embodiment of the invention further provides a management user policy charging control sign in an evolved network.
  • a system for information as shown in FIG. 16, the system includes an SPR and a PCRF, and information is exchanged between the two, wherein
  • the SPR is configured to store the user policy charging control subscription information corresponding to the user identifier, and is further configured to modify or delete the stored corresponding user policy charging control subscription information according to the user identifier, or/and store, modify, or delete the current usage according to the user identifier.
  • the PCRF is used to obtain the user policy charging control subscription information of the corresponding user policy charging control signature from the SPR according to the user identifier.
  • the embodiment of the present invention further provides an apparatus 1 for managing user policy charging control subscription information in an evolved network.
  • the apparatus is SPR.
  • FIG. 17 the following modules are included:
  • the first storage module is configured to store a user policy charging control subscription information corresponding to the user identifier, and the first information processing module is configured to modify or delete the corresponding user policy charging control subscription information in the first storage module according to the user identifier;
  • a second storage module configured to store address information or a connection identifier of a policy entity of the policy and charging rule currently using the user policy charging control subscription information
  • a second information processing module configured to modify or delete the policy of the currently used user policy charging control subscription information and the address information or the connection identifier of the charging rule function entity in the second storage module according to the user identifier.
  • the embodiment of the present invention further provides a device 2 for managing user policy charging control subscription information in an evolved network, where the device is a PCRF, as shown in FIG. 18, including a processing module, a receiving module, and a storage module, where
  • a receiving module configured to acquire, according to the user identifier, a corresponding user policy charging control from the SPR
  • the contract information is sent to the processing module
  • the processing module is configured to store the user policy charging control subscription information received from the receiving module into the storage module, and modify or delete the corresponding user policy charging control subscription information stored by the storage module according to the user identifier according to the SPR processing.
  • the user policy charging control subscription information is obtained from the PCRF to the SPR, and the PCRF operation flow caused by the modification of the user policy charging control subscription information in the SPR has a detailed description.
  • the SPR stores the PCRF address information or the connection identifier.
  • the operation flow after deleting the user policy charging control subscription information in the PCRF is not described in detail; after the user policy charging control subscription information is deleted in the SPR, The impact of the modification process in the PCRF is also not described in detail; the related registration process after the user changes the registered PCRF is not described in detail. Therefore, the embodiment of the present invention describes in detail the detailed processing procedure of the user policy charging control subscription information management in the existing PCC, so that the PCC is more perfect and more reasonable, and the user policy charging control subscription information can be used correctly and efficiently. .

Description

一种在演进网络中管理用户策略计费控制签约信息的方法、 系 统及装置
技术领域
本发明涉及在演进网络中管理数据的技术, 特别涉及一种在演进网 络中管理用户策略计费控制签约信息的方法、 系统及装置。 发明背景
电信网络是一个可运营的网络, 为此, 需要对电信网络中的业务以 及业务所使用的资源进行准确、 及时和全面的控制, 策略和计费控制就 是其中最重要的内容之一。
在演进网络中 ,如在第三代移动通信标准化的伙伴项目阶段 7( 3GPP release7 )体系中, 策略和计费功能由策略与计费规则功能( PCC , Policy and Charging Control )框架来实现。 PCC框架是一个能够应用于多种接 入技术的功能框架, 一些典型的接入技术包括通用移动通信系统 ( UMTS , Universal Mobile Telecommunication System )的无线接入网 , 全球移动通信系统(GSM, Global System for Mobile ) /GSM数据增强 演进( EDGE , Enhanced Data rates for GSM Evolution )无线接入网以及 互通无线局域网 ( I-WLAN, Interworking -Wireless Access Network )等。 在 3GPP rdease7之前, 策略控制由基于业务的本地策略控制 (SBLP, Service Based Local Prolicy )完成, 而计费则由基于流计费( FBC, Flow Based Charging )完成。 在 3GPP release7中 , PCC融合了 SBLP和 FBC 的基本功能, 并在某些方面作了进一步的演进, 例如实现了基于用户策 略计费控制签约信息的策略和计费控制 , 同时还更新了绑定机制。
图 1为 PCC的整体框架图 , PCC主要实现了两大功能。一是策略控 制功能; 二是计费功能。
其中, 策略控制功能主要包括: a、 对用户的业务参数, 如服务质量 ( QoS, Quality of Service )参数协商过程进行监控; b、 才艮据所获得 的业务信息,对业务所使用的网络承载资源进行授权; c、在数据承载面 实时地控制业务流的通过与否; d、 将业务面的相关变化情况通知数据 承载面; e、 将数据承载面的相关变化情况通知到业务面等; f、 进行基 于用户策略计费控制签约信息的策略控制。在 PCC中,策略控制功能主 要涉及的逻辑实体包括应用功能实体(AF, Application Function )、 策略 与计费规则功能(PCRF, Policy and Charging Rules Function ), 策略与 计费执行功能实体 ( PCEF, Policy and Charging Enforcement Function ) 以及用户策略签约数据库(SPR, Subscription Profile Repository )等。
计费功能主要包括: a、 综合业务信息、承载信息以及用户策略计费 控制签约信息, 制定计费规则; b、 在业务面的计费数据和承载面的计 费数据之间进行关联; c、 在动态计费模式下, 进行信用控制。 在 PCC 中, 计费功能主要涉及的逻辑实体包括 AF、 PCRF, PCEF, SPR、 在线 计费系统(OCS, Online Charging System ) 以及离线计费系统(OFCS, Offline Charging System )等。
以下对图 1所示 PCC框架中各个逻辑功能实体及其接口的功能进行 描述。
AF : 应用功能逻辑实体, 提供了业务应用的接入点, 这些业务应 用所使用的网络资源需要进行动态的策略控制。 在业务面进行参数协商 时, AF将相关业务信息传递给 PCRF。 如果这些业务信息与 PCRF的策 略相一致, PCRF接受该协商; 否则, PCRF拒绝该协商, 并在反馈中同 时给出 PCRF可接受的业务参数。 随后, AF可将这些参数返回给用户 设备 ( UE, User Equipment )。 AF和 PCRF之间的接口是 Rx接口。 在 多媒体子系统( IMS , IP Multimedia Subsystem ) 中 , 代理呼叫会话控制 功能(P-CSCF , Proxy Call Session Control Function )就是 AF。
PCRF : 策略控制与计费规则功能逻辑实体, 是 PCC的核心, 负责 策略决策和计费规则的制定。 PCRF提供了基于业务数据流的网络控制 规则, 这些网络控制包括业务数据流的探测、 门控(gating )、 QoS控制 以及基于数据流的计费控制等。 PCRF将其制定的策略和计费规则发送 给 PCEF执行,同时 PCRF还保证这些规则和用户的签约信息是一致的。 PCRF制定策略和计费规则的依据包括: 从 AF获取与业务相关的信息; 从 SPR获取与用户策略计费控制签约信息;从 PCEF获取与承载网络相 关的信息。
PCEF :策略控制与计费规则执行功能逻辑实体,通常位于网关( GW, GateWay )内, 在承载面执行 PCRF所制定的策略和计费规则。 PCEF按 照 PCRF所发送的规则中的流量过滤器进行业务数据流的探测 , 进而对 这些业务流执行 PCRF所制定的策略和计费控制。在承载建立时, PCEF 按照 PCRF发送的规则进行 QoS授权,并根据 AF的指示进行门控操作。 根据 PCRF发送的计费规则, PCEF执行相应的业务流计费操作。 计费 既可以是在线计费, 也可以是离线计费。 如果是在线计费, PCEF 需要 和 OCS—起进行信用管理。 离线计费时, PCEF和 OFCS之间交换相关 计费信息。 PCEF与 PCRF之间的接口是 Gx接口, 与 OCS之间的接口 是 Gy接口, 与 OFCS之间的接口是 Gz接口。 PCEF—般都位于网络的 网关上,例如, GPRS中的 GPRS网关支持节点(GGSN , Gateway GPRS Support Node ) 以及 I-WLAN 中的分组数据网关 (PDG, Packet Data Gateway )。
SPR : 存储了和策略控制与计费相关的用户策略计费控制签约信 息, 例如, 用户可使用的业务信息、 用户业务可使用的 QoS信息、 和计 费相关的用户策略计费控制签约信息以及用户的群类别等。利用 SPR所 存储的信息, PCRF就可以进行基于用户策略计费控制签约信息的策略 控制和计费操作。 SPR和 PCRF之间的接口是 Sp接口。
OCS : 在线计费系统, 和 PCEF—起进行在线计费方式下用户信用 ( credit ) 的控制和管理。 在承载建立、 修改和中止过程中, PCEF都必 须到 OCS 进行信用鉴权。 信用鉴权的结果会直接地影响用户业务的使 用, 例如, 如果用户信用已经用完, 则业务所使用的数据承载会被立即 删除, 用户业务中断。
OFCS : 离线计费系统, 与 PCEF—起完成离线计费方式下的计费 操作。
PCEF到 PCRF的寻址: PCEF根据承载建立过程中的公共数据网 ( PDN , Public Data Network ) 信息以及用户标识(用户标识为可选项) 来寻址合适的 PCRF。
AF到 PCRF 的寻址: AF才艮据网际协议 ( IP, Internet Protocol ) 地址信息以及用户标识(用户标识为可选项 )来寻址合适的 PCRF。
在本申请所示的图中, 虚线箭头表示可选步骤, 实线箭头表示必选 步骤。
目前, 利用图 1 所示的框架图进行策略计费控制的过程为: PCRF 接收到来自 PCEF的策略计费规则请求消息, 检测自身是否存储有该消 息相关的用户策略计费控制签约信息,如果没有则向 SPR获取该消息相 关的用户策略计费控制签约信息。随后, PCRF利用自身存储的或从 SPR 中获取到的该消息相关的用户策略计费控制签约信息进行基于该消息 相关的用户策略计费控制签约信息的策略计费规则决策, 并将决策后的 策略计费规则发送给 PCEF。 最后, PCEF根据接收到的策略计费规则对 该消息相关的用户进行策略计费。 但是, 由于同一用户通常允许通过一个或多个接入点 (AP, Access Point )使用网络服务, 也就是说, 对于同一用户, SPR中可能存在与之 对应的一个或多个用户策略计费控制签约信息, 而利用图 1所示的框架 图进行策略和计费控制的过程仅仅公开了 PCRF要获取用户策略计费控 制签约信息的过程, 没有公开针对具体业务中同一用户有多个用户策略 计费控制签约信息时, 如何有选择的获取相应的用户策略计费控制签约 信息的过程, 从而使得具体业务不具备可实施性。
在 3GPP release7的 23.203协议中, 已经明确了在承载建立过程中, PCEF与 PCRF进行交互过程中, PCRF发现没有存储此次交互涉及用户 的用户策略计费控制签约信息时, 发送携带有用户标识的用户策略计费 控制签约信息请求到 SPR, SPR根据该请求携带的用户标识发送对应的 用户策略计费控制签约信息到 PCRF, PCRF再根据接收到的用户策略计 费控制签约信息和用户请求的业务请求进行策略计费决策, 并将策略计 费决策发送给 PCEF进行执行。 具体过程如图 2所示, 其具体步骤为: 步骤 201、 PCEF接收到从外部节点发送来的业务承载建立请求消 步骤 202、 PCEF根据接收到消息携带的信息, 寻址到一个正确的 PCRF后, 向其发送策略计费规则请求消息, 在该消息携带用户标识。
步骤 203、 PCRF根据接收到的该消息携带的用户标识判断是否存储 有该用户标识对应的用户策略计费控制签约信息, 如果是, 则转入步骤 205 (该步骤未在图中示出); 否则, 向 SPR发送获取用户策略计费控制 签约信息请求消息。
步骤 204、 SPR根据接收到的该消息携带的信息, 发送所存储的用 户策略计费控制签约信息到 PCRF。
步骤 205、 PCRF根据从 PCEF接收到的策略计费规则请求消息携带 的业务承载信息、以及从 SPR接收到的或存储的对应该用户标识的用户 策略计费控制签约信息对策略计费进行决策。
步骤 206、 PCRF将决策后的策略计费规则发送给 PCEF, 由 PCEF 来执行策略计费控制。
步骤 207、 如果本次业务承载与在线计费相关, 则 PCEF发送信用 请求消息到 OCS。
步骤 208、 OCS发送信用响应消息到 PCEF,该消息携带是否为本次 业务提供服务的信息, PCEF根据接收到响应消息携带的信息为对本次 业务进行策略计费控制。
步骤 209、 PCEF发送业务承载建立响应给外部节点。
从图 2可以看出, 该技术方案只是明确了 PCRF如何向 SPR获取用 户签约数据, 但对于 SPR如何存储 PCRF的地址信息没有详细描述; 对 于在 PCRF如何删除用户策略计费控制签约信息没有详细描述; 对于在 SPR如果删除了已存储的用户策略计费控制签约信息后, 对 PCRF中修 改流程的影响没有详细描述; 对于用户改变了注册的 PCRF后的相关注 册流程也没有详细的描述。 另外, 当有多个网络为用户服务时, 有可能 就会有一个用户具有多个用户策略计费控制签约信息, 这时, SPR不知 道应该将所存储的哪一个用户策略计费控制签约信息提供给 PCRF。
在 23.203协议中, 已经明确了在业务承载建立过程中, 当 SPR修改 了存储的用户策略计费控制签约信息后, 会将修改后的用户策略计费控 制签约信息发送给对应的 PCRF, 对应的 PCRF再次进行策略计费规则 决策后, 将决策后的策略计费规则发送给 PCEF执行, 其具体过程如图 3所示:
步骤 301、 SPR修改自身存储的用户策略计费控制签约信息后, 根 据 SPR所保存的修改后的用户策略计费控制签约信息对应的 PCRF地址 信息, 发送用户策略计费控制签约信息修改请求消息到具有 PCRF地址 信息的 PCRF上, 该消息携带修改后的用户策略计费控制签约信息以及 用户标识等。
步骤 302、 PCRF接收到该消息后, 给 SPR发送响应消息。
步骤 303、 PCRF根据接收到该消息携带的用户策略计费控制签约信 息以及已经存在的业务承载信息 , 重新进行策略计费决策。
步骤 304、 PCRF将重新决策的策略计费规则携带在策略计费规则请 求消息中给 PCEF。
步骤 305、 PCEF根据接收到的消息携带的策略计费规则,发起业务 承载修改请求到外部节点。
步骤 306、 在外部节点完成业务承载修改后, 发送业务承载修改响 应给 PCEF。
步骤 307、 PCEF发送策略计费规则响应给 PCRF。
步骤 308、 PCRF检测到业务承载资源变换后,向 AF发送通知请求。 步骤 309、 AF发送通知响应给 PCRF。
图 3所述的技术方案只是明确了 SPR修改用户策略计费控制签约信 息以后, 向对应的 PCRF发送用户策略计费控制签约信息修改消息, 并 由 PCRF完成相关业务承载的修改过程。 但是对于如何存储 PCRF的地 址信息没有详细描述; 对于在 PCRF如何删除修改前的用户策略计费控 制签约信息没有详细描述;对于在 SPR如果删除了已存储的修改前的用 户签约数据后, 对 PCRF中修改流程的影响没有详细描述; 对于用户改 变了注册的 PCRF后的相关注册流程也没有详细的描述。
综上所述, 目前方案中只是提出了包括 PCRF从 SPR获取用户签约 数据信息 ,以及 SPR将修改的用户策略计费控制签约信息发送给 PCRF、 PCRF发起业务承载修改的两个处理过程, 对用户策略计费控制签约信 息的管理还是不够完善。
另夕卜, 由于 PCEF对 PCRF的寻址方式是基于网络标识加上用户标 识的方法, 当同一用户要访问多个网络中的不同业务时, 就有可能找到 不同的 PCRF, 这时同一个用户的用户策略计费控制签约信息可能同时 需要保存在多个 PCRF中, 即 SPR中可能需要保存多个 PCRF的地址信 息。 SPR如何存储一个或多个 PCRF地址信息, 以及后续在修改或删除 用户策略计费控制签约信息时如何根据所存储的 PCRF地址信息通知当 前为用户提供策略计费服务的 PCRF修改或删除用户策略计费控制签约 信息, 目前也没有叙述。 发明内容
本发明实施例提供一种在演进网络中管理用户策略计费控制签约信 息的方法, 该方法能够在演进网络中全面的管理用户签约数据, 实现在 SPR中存储 PCRF地址信息或 PCRF连接标识、 实现 PCRF可以正确的 获取到对应的用户策略计费控制签约信息。
本发明实施例还提供一种在演进网络中管理用户策略计费控制签约 信息的系统, 该系统能够在演进网络中全面的管理用户签约数据, 实现 在 SPR中存储 PCRF地址信息或 PCRF连接标识、 实现 PCRF可以正确 的获取到对应的用户策略计费控制签约信息。
本发明实施例还提供一种在演进网络中管理用户策略计费控制签约 信息的装置, 该装置能够在演进网络中全面的管理用户签约数据, 实现 在 SPR中存储 PCRF地址信息或 PCRF连接标识、 实现 PCRF可以正确 的获取到对应的用户策略计费控制签约信息。
根据上述目的 , 本发明实施例的技术方案是这样实现的:
一种在演进网络中管理用户策略计费控制签约信息的方法, 该方法 包括:
用户策略签约数据库对应用户标识存储用户策略计费控制签约信 根据用户标识从用户策略签约数据库获取所存储对应的用户策略计 费控制签约信息, 或 /和用户策略签约数据库根据用户标识修改或删除 所存储对应的用户策略计费控制签约信息, 或 /和^^据用户标识存储、 修改或删除当前使用用户策略计费控制签约信息的策略和计费规则功 能实体的地址信息或连接标识。
一种在演进网络中管理用户策略计费控制签约信息的系统, 其特征 在于, 包括用户策略签约数据库以及策略和计费规则功能实体, 两者之 间进行信息交互, 其中,
用户策略签约数据库, 用于对应用户标识存储用户策略计费控制签 制签约信息, 或 /和根据用户标识存储、修改或删除当前使用用户策略计 费控制签约信息的策略和计费规则功能实体的地址信息或连接标识; 策略和计费规则功能实体, 用于根据用户标识从用户策略签约数据 库获取对应的用户策略计费控制签约信息 , 还用于根据用户策略签约数 控制签约信息。
一种在演进网络中管理用户策略计费控制签约信息的装置, 其中, 第一存储模块, 用于对应用户标识存储用户策略计费控制签约信 第一信息处理模块, 用于根据用户标识修改或删除第一存储模块中 对应的用户策略计费控制签约信息;
或 /和、 第二存储模块 , 用于存储当前使用用户策略计费控制签约信息的策 略和计费规则功能实体的地址信息或连接标识;
第二信息处理模块, 用于根据用户标识修改或删除第二存储模块中 的当前使用用户策略计费控制签约信息的策略和计费规则功能实体的 地址信息或连接标识。
一种在演进网络中管理用户策略计费控制签约信息的装置, 包括处 理模块、 接收模块和存储模块, 其中,
接收模块, 用于根据用户标识从用户策略签约数据库获取对应的用 户策略计费控制签约信息, 发送给处理模块;
处理模块, 用于将从接收模块接收的用户策略计费控制签约信息存 储到存储模块中, 根据用户策略签约数据库的处理进行根据用户标识修 改或删除存储模块所存储对应的用户策略计费控制签约信息。
从上述方案可以看出 ,本发明实施例在 SPR存储用户策略计费控制 签约信息时, 是针对用户标识进行存储; 在存储当前使用用户策略计费 控制签约信息的 PCRF地址信息或连接标识时, 也是至少对应用户标识 以及所使用的用户策略计费控制签约信息进行存储。 更进一步地, 存储 用户策略计费控制签约信息和使用用户策略计费控制签约信息的 PCRF 地址信息或连接标识, 还可以针对网络标识存储。 因此, 在 PCRF获取 用户签约数据时, PCRF通知 SPR删除所存储的 PCRF地址信息或连接 标识时, 在 SPR发起用户策略计费控制签约信息删除时以及 SPR发起 PCRF取消注册时, 都可以根据对应的用户标识, 甚至是根据对应的用 户标识和网络标识获取到用户策略计费控制签约信息, 或获取到 PCRF 地址信息或 PCRF连接标识确定对应的 PCRF, 进行相应的处理。 因此, 本发明实施例提供的方法、 系统及装置在演进网络中全面的管理用户签 约数据, 实现在 SPR中存储 PCRF地址信息或 PCRF连接标识、 实现 PCRF可以正确的获取到对应的用户策略计费控制签约信息。 附图简要说明
图 1为现有技术的 PCC整体框架图;
图 2为现有技术利用图 1所示的框架图进行策略计费控制的过程流 程图;
图 3为现有技术 SPR修改所存储的用户策略计费控制签约信息后进 行策略计费控制的方法流程图;
图 4为本发明实施例 PCRF向 SPR获取用户策略计费控制签约信息 的方法一的流程图;
图 5为本发明实施例 PCRF向 SPR获取用户策略计费控制签约信息 的方法二的流程图;
图 6为本发明实施例 PCRF向 SPR获取用户策略计费控制签约信息 的方法三的流程图;
图 7为本发明实施例 SPR删除一个用户的部分用户策略计费控制签 约信息的方法流程图;
图 8为本发明实施例 SPR删除一个用户的所有用户策略计费控制签 约信息的方法流程图;
图 9为本发明实施例 PCRF通知 SPR删除所存储的 PCRF地址信息 的方法一流程图;
图 10为本发明实施例 PCRF通知 SPR删除所存储的 PCRF地址信 息或连接标识的方法二流程图;
图 11为本发明实施例 PCRF通知 SPR删除所存储的 PCRF地址信 息或连接标识的方法三流程图;
图 12为本发明实施例由 HSS通知 SPR, 并且由 SPR发起注册取消 操作到 PCRF的方法流程图;
图 13 为本发明实施例第四个处理流程实现方法二的实现方法一流 程图;
图 14 为本发明实施例第四个处理流程实现方法二的实现方法二流 程图;
图 15为本发明实施例第四个处理流程实现方法三的流程图; 图 16 为本发明实施例管理用户策略计费控制签约信息的系统示意 图;
图 17 为本发明实施例管理用户策略计费控制签约信息的装置一示 意图;
图 18 为本发明实施例管理用户策略计费控制签约信息的装置二示 意图。 实施本发明的方式
为使本发明的目的、技术方案和优点更加清楚明白 ,以下举实施例 , 并参照附图, 对本发明进一步详细说明。
本发明实施例针对现有技术所提供方案的不足, 可以进行如下处 理:
―, PCRF向 SPR获取用户策略计费控制签约信息的过程中, SPR 采用网络标识和用户标识对应一个 PCRF地址信息或连接标识进行存 储, 从而区分当前为用户提供服务的不同 PCRF, 同样地, 对于用户策 略计费控制签约信息也采用网络标识和用户标识进行区分, 从而使 PCRF可以根据这两个标识获取正确的用户策略计费控制签约信息, 网 络标识可以为 PDN标识或访问点名称( APN, Access Point Name )标识。
二, 当 SPR中的用户策略计费控制签约信息修改或删除以后,根据 自身所保存的 PCRF地址信息或连接标识发送修改或删除请求消息到对 应的 PCRF上,再由 PCRF发起对应的业务承载修改或删除操作。这时 , 也可以采用网络标识和用户标识指示所修改或删除的用户策略计费控 制签约信息, 从而使 PCRF正确得知是哪一个用户在哪个网络中的业务 发生了修改或删除 , 发起对应的业务承载修改或删除操作。
三, 在 PCEF中业务承载删除时通知 PCRF, PCRF判断是否已经删 除了用户的最后一个业务相关承载,如果不是, 则不进行处理; 如果是, 则等待设定的时间后 , 该设定的时间用于保证用户策略计费控制签约信 息在后续业务承载建立过程中使用, 这样可以减少业务承载建立时间。
PCRF判断在设定时间到时后是否没有接收到该用户的业务承载请求, 如果是, PCRF删除自身存储的该用户的用户策略计费控制签约信息, 向 SPR通知该用户的用户策略计费控制签约信息已经删除, SPR将删除 发起该通知的 PCRF的地址信息或连接标识。 通知该用户的用户策略计 费控制签约信息已经删除是通过发送取消通知请求消息通知的。
四, SPR针对所存储的 PCRF地址信息或连接标识发起 PCRF取消 注册的过程。
在本发明实施例中 , SPR保存用户策略计费控制签约信息是针对用 户标识进行保存的, 或者针对用户标识和网络标识进行保存的。
以下分别对这四个处理过程进行详细说明。
第一个处理过程
首先, PCRF向 SPR发送策略计费规则请求消息, 该消息包括用户 标识, 还可以包括网络标识, 用于标识一个为 UE提供服务的 PCRF。
其次, 在 PCRF向 SPR获取用户策略计费控制签约信息时, SPR存 储 PCRF的地址信息或者存储可以表示 PCRF地址信息的连接标识。 在 SPR中保存的可能是用户标识以及 PCRF地址信息或 PCRF连接标识指 示一个 PCRF; 也可以是用户标识、 当前为 UE提供服务的网络标识以 及 PCRF地址信息或 PCRF连接标识指示一个 PCRF。
如果 PCRF与 SPR之间采用订阅通知的工作方式,则 SPR根据 PCRF 发送的请求消息携带的信息(这时, 请求消息需要携带是否签约了订阅 通知的信息), 判断是否需要对用户策略计费控制签约信息进行订阅通 知, 如果是, 则采用本发明的方法存储 PCRF的地址信息或连接标识; 否则, SPR不存储 PCRF的地址信息或连接标识。
在这里,当前为 UE提供服务的网络标识为 PDN标识或 APN标识。 最后 , SPR发送对应该请求消息携带的用户标识的用户策略计费控 制签约信息给 PCRF, 如果该请求消息还有网络标识, 则发送的用户策 略计费控制签约信息还需要对应该网络标识。
以下举几个具体实施例进行说明。
图 4为本发明实施例 PCRF向 SPR获取用户策略计费控制签约信息 的方法一的流程图, 该方法应用在与 AF无关的业务承载建立或修改过 程中, 其具体步骤为:
步骤 401、 PCEF从外部节点接收到业务承载建立或修改的请求消 步骤 402、 PCEF向 PCRF发送策略计费规则请求消息, 消息中携 带用户标识以及业务相关信息等信息。
步骤 403、 PCRF检测到没有具有该消息携带用户标识的用户策略计 费控制签约信息及该业务需要的策略计费规则,向 SPR发送策略计费规 则请求消息,消息中携带用户标识,还可以携带有所在网络的网络标识。
步骤 404、 SPR存储 PCRF的地址信息或者存储可以表示 PCRF地 址的连接标识, 存储的方式为用用户标识对应一个 PCRF的地址信息或 连接标识存储 , 也可以用用户标识和网络标识对应一个 PCRF的地址信 息或连接标识存储。
如果 PCRF 与 SPR之间采用订阅通知的工作方式, 则 SPR根据 PCRF发送的请求消息中的信息 (这时, 该请求消息携带是否订阅了通 知信息的信息), 判断是否对用户策略计费控制签约信息签订了订阅通 知, 如果是, 则 SPR存储 PCRF地址信息或连接标识; 否则 SPR不存 储 PCRF地址信息或连接标识。
步骤 405、 SPR发送对应该用户标识的用户策略计费控制签约信息 给 PCRF。
步骤 406、 PCRF根据接收到的对应该用户标识的用户策略计费控制 签约信息进行策略决策。
步骤 407、 PCRF发送策略计费规则信息响应给 PCEF, 携带经过决 策的策略计费规则。
步骤 408、 PCEF向外部节点发送承载建立或修改的响应消息。 图 5为本发明实施例 PCRF向 SPR获取用户策略计费控制签约信息 的方法二的流程图, 该方法应用在与 AF相关的业务承载建立或修改过 程中, 其具体步骤为:
步骤 501、 AF向 PCRF发送应用或业务相关数据信息, 包括用户标 识, 以及应用或业 ^言息等内容。
步骤 502、 PCRF向 AF发送响应消息。
步骤 503、 PCEF从外部节点收到业务承载建立或修改的请求消息。 步骤 504、 PCEF向 PCRF发送策略计费规则请求消息, 消息中包括 用户标识以及业务相关信息等信息。
步骤 505、 PCRF将请求消息中的业务相关信息与从 AF接收来的应 用或业务相关数据信息进行关联。
步骤 506、 PCRF检测到没有具有该消息携带用户标识的用户策略计 费控制签约信息及该业务需要的策略计费规则,向 SPR发送策略计费规 则请求消息,消息中携带用户标识,还可以携带有所在网络的网络标识。
步骤 507、 SPR存储 PCRF的地址信息或者存储可以表示 PCRF地 址的连接标识, 存储的方式为用用户标识对应一个 PCRF的地址信息或 连接标识存储 , 也可以用用户标识和网络标识对应一个 PCRF的地址信 息或连接标识存储。
如果 PCRF 与 SPR之间采用订阅通知的工作方式, 则 SPR根据 PCRF发送的请求消息中的信息 (这时, 该请求消息携带是否订阅了通 知信息的信息), 判断是否对用户策略计费控制签约信息签订了订阅通 知, 如果是, 则 SPR存储 PCRF地址信息或连接标识; 否则 SPR不存 储 PCRF地址信息或连接标识。
步骤 508、 SPR发送对应该用户标识的用户策略计费控制签约信息 给 PCRF。
步骤 509、 PCRF根据接收到的对应该用户标识的用户策略计费控制 签约信息进行策略决策。
步骤 510、 PCRF发送策略计费规则信息响应给 PCEF, 携带经过决 策的策略计费规则。
步骤 511、 PCEF向外部节点发送承载建立或修改的响应消息。
图 6为本发明实施例 PCRF向 SPR获取用户策略计费控制签约信息 的方法三的流程图, 该方法应用在与 AF相关的由网络侧发起的业务承 载建立或修改过程, 其具体步骤为:
步骤 601、 AF向 PCRF发送应用或业务相关数据信息, 包括用户标 识, 以及应用或业 ^言息等内容。
步骤 602、 PCRF检测到没有具有该消息携带用户标识的用户策略计 费控制签约信息及该业务需要的策略计费规则,向 SPR发送策略计费规 则请求消息,消息中携带用户标识,还可以携带有所在网络的网络标识。 步骤 603、 SPR存储 PCRF的地址信息或者存储可以表示 PCRF地 址的连接标识, 存储的方式为用用户标识对应一个 PCRF的地址信息或 连接标识存储 , 也可以用用户标识和网络标识对应一个 PCRF的地址信 息或连接标识存储。
如果 PCRF 与 SPR之间采用订阅通知的工作方式, 则 SPR根据 PCRF发送的请求消息中的信息 (这时, 该请求消息携带是否订阅了通 知信息的信息), 判断是否对用户策略计费控制签约信息签订了订阅通 知, 如果是, 则 SPR存储 PCRF地址信息或连接标识; 否则 SPR不存 储 PCRF地址信息或连接标识。
步骤 604、 SPR发送对应该用户标识的用户策略计费控制签约信息 给 PCRF。
步骤 605、 PCEF向 PCRF发送策略计费规则请求消息, 消息中包括 用户标识以及业务相关信息等内容。
步骤 606、 PCRF根据收到的用户策略计费控制签约信息以及从 PCEF接收到的请求消息中包括的信息进行策略决策。
步骤 607、 PCRF发送策略计费规则响应给 PCEF, 携带经过决策的 策略计费规则。
步骤 608、 PCEF向外部节点发送业务承载建立或修改的请求消息。 步骤 609、 PCEF 收到外部节点发送业务承载建立或修改的响应消 步骤 610、 PCEF向 PCRF发送策略计费规则响应消息。
第二个处理过程
分为 SPR发起的用户策略计费控制签约信息修改的方法和 SPR发 起的用户策略计费控制签约信息删除的方法。 其中, SPR发起的用户策略计费控制签约信息修改方法与现有技术 相同, 唯一区别是由于在第一个处理过程中具体限定了保存 PCRF地址 信息或连接标识的方式, 因此, 可以很容易的根据该方式查找到具有 PCRF地址信息或连接标识的 PCRF后, 向该 PCRF发起用户策略计费 控制签约信息修改。另夕卜,该方法还可以包括增加用户签约数据的过程。
SPR发起的用户策略计费控制签约信息删除方法的过程为: 首先,在 SPR中删除一个用户的全部或部分用户策略计费控制签约 信息, SPR根据所保存的该用户的 PCRF地址信息或连接标识, 向对应 于要删除的全部或部分用户策略计费控制签约信息的 PCRF (—个或一 个以上)发送用户策略计费控制签约信息删除请求消息。 如果该 PCRF 与 SPR之间采用订阅通知的方式, 则 SPR需要先判断该用户是否签订 了订阅通知, 如果签订了订阅通知, 则 SPR向 PCRF发送用户策略计费 控制签约信息删除请求消息,否则 SPR不向 PCRF发送用户策略计费控 制签约信息删除请求消息。
其次, 该 PCRF发送该用户的业务承载通知到 PCEF, 由 PCEF删 除对应的业务承载。
最后 , SPR删除对应于要删除的全部或部分用户策略计费控制签约 信息的 PCRF的地址信息或连接标识。
以下举几个具体例子说明第二个处理过程。
图 7为本发明实施例 SPR删除一个用户的部分用户策略计费控制签 约信息的方法流程图 ,在 SPR中删除该用户的部分用户策略计费控制签 约信息时,需要通知存储在 SPR中的与该用户要删除部分用户策略计费 控制签约信息对应的 PCRF, 该 PCRF接收到这个删除用户策略计费控 制签约信息的通知后, 删除该用户对应的用户策略计费控制签约信息, 并且 PCRF发送删除对应的业务承载的通知消息到 PCEF, 由 PCEF发 起删除该用户对应的业务承载, 其具体步骤为:
步骤 701、 在 SPR中删除指定用户的部分用户策略计费控制签约信 息, SPR根据存储对应于要删除的部分用户策略计费控制签约信息的 PCRF地址信息或连接标识, 发送删除用户策略计费控制签约信息请求 消息到 PCRF, 该消息携带对应于要删除的部分用户策略计费控制签约 信息的用户标识 , 还可以携带对应于要删除的部分用户策略计费控制签 约信息的网络标识。
在本发明中, 由于对于不同的网络业务, 用户可以在 SPR存储不同 的用户策略计费控制签约信息, 所以在删除时, 可以只删除其中的部分 用户策略计费控制签约信息。
如果 PCRF与 SPR之间采用订阅通知的工作方式, 则 SPR需要判 断该用户是否签订订阅通知(预先在 SPR中存储了该用户是否签订了订 阅通知), 如果是, 则 SPR向 PCRF发送删除用户策略计费控制签约信 息请求消息;否则 SPR不向 PCRF发送删除用户策略计费控制签约信息 请求消息。
步骤 702、 PCRF发送删除用户策略计费控制签约信息响应给 SPR, SPR删除保存的该 PCRF的地址信息或连接标识。
步骤 703、 PCRF根据接收到该请求消息携带的用户标识和网络标 识, 确定要删除对应的业务承载, 并发送删除对应的业务承载请求消息 给对应的 PCEF (在 PCRF中对应的业务承载中保存了 PCEF的地址信 息), 该请求消息包括用户标识、 会话标识以及承载标识等用于标识对 应的业务承载的信息。
如果该请求消息只携带该用户的用户标识, 则 PCRF可以根据自身 所在网络的网络标识和用户标识确定要删除对应的业务承载。
步骤 704、 PCRF根据接收到该请求消息携带的用户标识网络标识删 除自身存储的对应的策略计费规则信息。
步骤 705、 PCEF发送业务承载删除请求消息到外部节点,携带要删 除的业务承载, 指示外部节点最终完成业务承载的删除。
步骤 706、 在 PCEF中删除该业务承载对应的策略计费规则信息。 步骤 707、 PCEF发送信用结束报告请求到 OCS, 把该用户剩余的 信用返回到 OCS。 这个步骤为可选步骤。
步骤 708、 OCS发送信用结束报告响应消息到 PCEF。 这个步骤可 选。
步骤 709、 PCEF收到外部节点发送回来的业务承载删除响应。
步骤 710、 PCEF发送删除业务承载响应消息给 PCRF。
步骤 711、 PCRF将业务承载删除的信息通知 AF。 这个步骤可选。 步骤 712、 AF发送业务承载删除响应消息给 PCRF。这个步骤可选。 图 8为本发明实施例 SPR删除一个用户的所有用户策略计费控制签 约信息的方法流程图 ,在 SPR中删除这个用户的所有用户策略计费控制 签约信息时,需要通知存储在 SPR中的与要删除所有用户策略计费控制 签约信息对应的各个 PCRF, 该 PCRF接收到这个删除用户策略计费控 制签约信息的通知后, 删除该用户的用户策略计费控制签约信息, 并且 发送删除对应的业务承载的通知消息到 PCEF, 由 PCEF发起删除该用 户对应的业务承载, 其具体步骤为:
步骤 801、 在 SPR中删除指定用户的所有用户策略计费控制签约信 息, SPR根据存储对应于该用户所有用户策略计费控制签约信息的 PCRF地址信息或连接标识, 发送删除用户策略计费控制签约信息请求 消息到 PCRF, 该消息携带要删除用户策略计费控制签约信息对应的用 户标识, 还可以携带要删除用户策略计费控制签约信息对应的网络标 识。 如果 PCRF与 SPR之间采用订阅通知的工作方式, 则 SPR需要判 断该用户是否签订订阅通知, 如果签订订阅通知, 则 SPR向 PCRF发送 删除用户策略计费控制签约信息请求消息;否则 SPR不向 PCRF发送删 除用户策略计费控制签约信息请求消息。
步骤 802、 PCRF发送删除用户策略计费控制签约信息响应给 SPR, SPR删除保存的对应于要删除的该用户所有用户策略计费控制签约信息 的 PCRF地址信息或连接标识。
步骤 803、 PCRF根据接收到该请求消息携带的用户标识和网络标 识, 确定对应的业务承载, 并发送删除业务承载请求消息给对应的 PCEF ,该请求消息包括用户标识、会话标识以及承载标识等用于标识业 务承载的信息。
如果该请求消息只携带该用户的用户标识, 则 PCRF可以根据自身 所在网络的网络标识和用户标识确定要删除对应的业务承载。
步骤 804、 PCRF根据接收到该请求消息携带的用户标识和网络标识 删除自身存储的对应的策略计费规则信息。
步骤 805、 PCEF发送承载删除请求消息到外部节点,携带要删除的 业务承载, 指示外部节点最终完成业务承载的删除。
步骤 806、 在 PCEF中删除该业务承载对应的策略计费规则信息。 步骤 807、 PCEF发送信用结束报告请求到 OCS, 把该用户剩余的 信用返回到 OCS。 这个步骤为可选步骤。
步骤 808、 OCS发送信用结束报告响应消息到 PCEF。 这个步骤可 选。
步骤 809、 PCEF收到外部节点发送回来的业务承载删除响应。
步骤 810、 PCEF发送删除业务承载响应消息给 PCRF。
步骤 811、 PCRF将业务承载删除的信息通知 AF。 这个步骤可选。 步骤 812、 AF发送业务承载删除响应消息给 PCRF。这个步骤可选。 第三个处理流程
首先, PCRF按照现有技术检测到用户没有任何业务承载时, 为该 用户的用户策略计费控制签约信息再保存设定时间后, 该时间由配置确 定, 可以为零, 如果检测到的该用户还有其他的业务承载, 则将该用户 策略计费控制签约信息继续保存; 如果没有, 则转入下一个步骤继续进 行。
然后, PCRF删除该用户的用户策略计费控制签约信息后, 发送携 带指示 PCRF地址信息或连接标识的用户策略计费控制签约信息已删除 指示到 SPR, 该指示可以为取消通知请求消息, SPR删除该用户的这个 PCRF地址信息或连接标识。 如果 SPR接收到的指示 PCRF地址信息或 连接标识为 UE标识户标识以及网络标识, 即取消通知请求消息包含 PCRF地址信息或连接标识为 UE标识户标识以及网络标识, 则 SPR只 删除与用户标识以及网络标识对应的该 PCRF地址信息或连接标识; 如 果 SPR接收到的指示 PCRF地址信息或连接标识为 UE标识户标识, 即 取消通知请求消息仅包含 PCRF地址信息或连接标识为 UE标识户标识, 则 SPR删除所有保存有该用户策略计费控制签约信息的 PCRF的地址信 息或连接标识。
或者 PCRF与 SPR之间断开连接后, PCRF发送连接断开指示到 SPR, 清除所保存断开连接的 PCRF的地址信息或连接标识。
如果 PCRF与 SPR之间采用订阅通知的工作方式,则 PCRF需要判 断该用户是否向 SPR签订了订阅通知, 如果是, 则 PCRF向 SPR发送 用户策略计费控制签约信息已删除指示, 该指示可以为取消通知请求消 息; 否则, PCRF不需要向 SPR发送用户策略计费控制签约信息已删除 指示, 该指示可以为取消通知请求消息。 最后, SPR处理完毕后给 PCRF发送响应消息。
在具体实现中, 一般采用第三个处理流程实现。
以下举几个具体实施例说明第三个处理流程。
图 9为本发明实施例 PCRF通知 SPR删除所存储的 PCRF地址信息 或连接标识的方法一流程图, 该方法由 PCRF触发删除业务承载, 并在 PCRF 中删除一个用户相关的用户策略计费控制签约信息, 其具体步骤 为:
步骤 901、 PCEF 收到外部节点删除业务的指示或自身决定删除业 务, 发送业务承载删除指示请求消息到 PCRF, 该消息携带要删除业务 承载对应的用户标识以及承载相关信息。
步骤 902、 PCRF根据请求消息携带的信息,修改或删除该业务承载 相关的策略计费规则信息。
步骤 903、 PCRF发送承载删除通知请求消息到 AF。 这个步骤为可 选。
步骤 904、 AF发送通知响应消息到 PCRF。 这个步骤为可选。 步骤 905、 PCRF发送删除相关业务承载响应消息给 PCEF。
步骤 906、 PCRF检测到没有任何与要删除业务承载对应的用户相关 的业务承载后 , 将该用户的用户策略计费控制签约信息继续保存一定长 时间; 在一定长时间内没有任何新业务承载建立过程, PCRF删除该用 户的用户策略计费控制签约信息。
这个一定长时间可以在一个范围内进行配置, 也可以设置为零。 设 置为零时, 就意味着 PCRF检测到该用户没有任何相关业务承载时, 就 直接删除该用户的用户策略计费控制签约信息。
步骤 907、 PCRF发送用户策略计费控制签约信息已删除指示消息到
SPR, 该消息中携带该用户的用户标识, 还可选包含网络标识等信息。 在本步骤中, 该消息可以为取消通知请求消息。
如果 PCRF与 SPR之间采用订阅通知的工作方式,则 PCRF需要判 断该用户是否向 SPR签订订阅通知(这时, 可以将是否签订了订阅通知 信息预先存储在 PCRF中), 如果是, 则 PCRF向 SPR发送用户策略计 费控制签约信息已删除指示消息; 否则 PCRF不向 SPR发送用户策略 计费控制签约信息已删除指示消息。
步骤 908、 SPR收到该指示消息后, 删除所存储对应于该消息携带 的 UE标识用户标识的 PCRF地址信息或连接标识。
如果 SPR收到指示消息携带的是用户标识和网络标识, 则 SPR只 删除与用用户标识和网络标识指示的 PCRF地址信息或连接标识; 如果 SPR收到指示消息携带的是用户标识,则 SPR删除所有该用户标识指示 的该用户对应的 PCRF地址信息或连接标识。
步骤 909、 SPR发送用户策略计费控制签约信息已删除响响应消息 给 PCRF。
具体地, 该响应可以为取消通知响应。
当然, PCRF 中的用户策略计费控制签约信息在没有业务承载时再 继续保存一定长时间 , 可以在这一定长时间内继续发起业务时减少承载 建立时间, 而且可以减少 PCRF与 SPR之间接口上的消息, 尤其是在一 个业务承载删除后马上进行重新建立时。
图 10为本发明实施例 PCRF通知 SPR删除所存储的 PCRF地址信 息或连接标识的方法二流程图, 该方法由 AF触发删除业务承载, 并在 PCRF 中删除业务承载所对应的用户策略计费控制签约信息, 其具体步 骤为:
步骤 1001、 AF收到外部节点删除业务的指示, 发送业务承载删除 指示请求消息到 PCRF, 消息中携带该业务承载对应的用户标识以及承 载相关的信息。
步骤 1002、 PCRF发送业务承载删除通知请求消息到 PCEF。
步骤 1003、 PCRF根据接收到的请求消息, 修改或删除该业务承载 对应的策略计费规则信息。
步骤 1003与步骤 1002的顺序可以互换。
步骤 1004、 PCEF完成业务承载删除的主要操作, 并需要与外部节 点进行交互。 完成业务承载删除后, PCEF发送业务删除响应消息到 PCRF。
步骤 1005、 PCRF发送承载删除通知响应消息到 AF。
步骤 1006、 PCRF检测到没有任何与要删除业务承载对应的用户对 应的业务承载后 , 将该用户的用户策略计费控制签约信息继续保存一定 长时间; 在一定长时间内没有任何新业务承载建立过程, PCRF删除该 用户的用户策略计费控制签约信息。
这个一定长时间可以在一个范围内进行配置, 也可以设置为零。 设 置为零时, 就意味着 PCRF检测到该用户没有任何相关业务承载时, 就 直接删除该用户的用户策略计费控制签约信息。
步骤 1007、 PCRF发送用户策略计费控制签约信息已删除指示消息 到 SPR,该消息中携带该用户的用户标识,还可选包含网络标识等信息。
具体地 , 该消息可以为取消通知请求消息。
如果 PCRF与 SPR之间采用订阅通知的工作方式,则 PCRF需要判 断该用户是否向 SPR签订订阅通知(这时, 可以将是否签订了订阅通知 信息预先存储在 PCRF中), 如果是, 则 PCRF向 SPR发送用户策略计 费控制签约信息已删除指示消息; 否则 PCRF不向 SPR发送用户策略 计费控制签约信息已删除指示消息。
步骤 1008、 SPR收到该指示消息后,删除所存储对应于该消息携带 的用户标识的 PCRF地址信息或连接标识。
如果 SPR收到指示消息携带的是用户标识和网络标识, 则 SPR只 删除与用用户标识和网络标识指示的 PCRF地址信息或连接标识; 如果 SPR收到指示消息携带的是用户标识,则 SPR删除所有该用户标识指示 的该用户对应的 PCRF地址信息或连接标识。
步骤 1009、 SPR发送用户策略计费控制签约信息已删除响应消息 给 PCRF。
具体地, 该响应可以为取消通知响应。
图 11为本发明实施例 PCRF通知 SPR删除所存储的 PCRF地址信 息或连接标识的方法三流程图, 该方法在 PCRF中删除一个用户的用户 策略计费控制签约信息时, 通过断开连接的指示来通知 SPR, 其具体步 骤为:
步骤 1101、 在 PCRF中删除该用户的用户策略计费控制签约信息。 步骤 1102、 PCRF发送该用户连接断开指示消息到 SPR。
如果 PCRF与 SPR之间采用订阅通知的工作方式,则 PCRF需要判 断该用户是否向 SPR签订订阅通知, 如果是, 则 PCRF需要向 SPR发 送该用户连接断开指示消息; 否则 PCRF不向 SPR发送该用户连接断 开指示消息。
步骤 1103、 SPR删除所存储的对应于发起连接断开指示消息的 PCRF的地址信息或连接标识。
步骤 1104、 SPR发送该用户连接断开响应消息到 PCRF, 删除与发 送该用户连接断开指示消息的相关连接。
第四个处理流程
有三个主要的实现方法, 以下进行伴细说明。
实现方法一: 首先, UE发起附着操作到移动管理实体(MME, Mobile Manage Equipment ), MME发送注册请求消息到归属用户服务器( HSS , Home Subscriber Server ), 在注册请求消息中指明这个注册请求消息是 UE的 附着操作以及用户标识等信息。
其次, HSS接收到该注册请求消息后, 判断为 UE当前提供服务的 MME是否更改, 如果是, 则发送通知消息到 SPR; 如果否, 则不发送 通知消息到 SPR, 该通知消息包括用户标识, 其指明是附着操作。
再次, SPR接收到通知消息, 检测是否保存对应该用户标识的用户 策略计费控制签约信息的 PCRF地址信息或连接标识, 该 PCRF地址信 息或连接标识还对应于当前为 UE提供服务的网络标识, 如果有, 则发 送取消注册请求消息到该一个或多个 PCRF ( SPR 中有可能保存多个 PCRF地址信息); 否则, 则不发送取消注册请求消息。 取消注册请求消 息中包含用户标识以及其他可能信息, SPR删除保存的对应该用户标识 的用户策略计费控制签约信息。
最后, 该一个或多个 PCRF接收到 SPR的取消注册请求消息后, 根 据用户标识以及其他可能信息删除该用户标识对应的在 PCRF中的用户 策略计费控制签约信息, 如果 PCRF检测到还存在对应的业务承载, 则 PCRF删除这些对应的业务承载。
在该实现方法中, MME和用户面实体 ( UPE )分离还是合并无关。 采用该实现方法, 可以删除在附着操作流程前一些 PCRF所緩存的用户 策略计费控制签约信息。 采用该实现方法, 可以保证在一些异常情况下 实现 PCRF中存储的用户策略计费控制签约信息的删除, 如当业务承载 删除时, 而在 PCRF上的用户签约数据没有被正确删除的情况。
实现方法二:
首先, UE发起附着操作到 MME/UPE上。 其次 , 在建立缺省业务承载过程中或业务缺省承载建立完成以后 ,
PCEF(位于 UPE或锚( Anchor ) )发送注册请求消息到 UE切换到的 PCRF 上, 在注册请求消息中指明是附着操作, 以及携带用户标识等信息。
再次, UE切换到的 PCRF接收到来自 PCEF的注册请求消息后,发 送用户策略计费控制签约信息获取请求消息到 SPR, 在该请求消息中指 明是附着操作, 以及携带用户标识等信息。
最后, SPR接收到请求消息, 且检查到有附着操作的指示后, 检测 是否保存有对应该用户标识的 PCRF地址信息或连接标识, 如果有, 则 发送取消注册请求消息到对应该用户标识的一个或多个 PCRF ( SPR中 有可能保存多个 PCRF地址信息或连接标识); 否则,则不发送取消注册 请求消息。 SPR删除保存的对应该 UE的用户策略计费控制签约信息。 该一个或多个 PCRF接收到 SPR的取消注册请求消息后,根据用户标识 以及其他可能信息删除对应该 UE的在 PCRF中的用户策略计费控制签 约信息, 如果 PCRF检测到还存在对应的业务承载, 则 PCRF删除这些 对应业务承载。
实现方法三:
首先, AF或 PCEF发起业务承载建立过程与 PCRF进行交互,在交 互过程中将业务承载的用户标识以及相关信息发送给 PCRF。
其次, PCRF检测到没有具有用户标识的用户策略计费控制签约信 息, 向 SPR发送获取用户策略计费控制签约信息请求消息, 该消息携带 用户标识以及网络标识等信息; 如果 PCRF存在具有用户标识的用户策 略计费控制签约信息,则不向 SPR发送获取用户策略计费控制签约信息 请求消息。
再次, SPR根据接收到的请求消息携带的用户标识以及网络标识检 测是否有对应的 PCRF地址信息或连接标识, 如果有, 则发送取消注册 消息到注册消息到具有该 PCRF地址信息或连接标识的 PCRF上。 取消 注册消息中包括用户标识以及为用户提供服务的网络标识等信息 , 同时 SPR删除该 PCRF地址信息或连接标识。
值得注意的是, 如果该 PCRF与具有该用户标识的用户的多个提供 服务的网络标识相关联, 并存在对应的业务承载, 这时只删除与所发起
连接标识不进行删除。
最后, PCRF接收到取消注册消息后, 根据该消息携带的用户标识 以及为网络标识, 删除对应的用户策略计费控制签约信息; 如果 PCRF 检测到还存在与用户策略计费控制签约信息对应的业务承载, 则 PCRF 删除这些对应的业务承载。
值得注意的是, PCRF还可能继续保存与其他为用户服务的网络标 识相关的用户策略计费控制签约信息。
以下举几个具体实施例分别说明这三个实现方法。
实现方法一的具体实施例
图 12为本发明实施例由 HSS通知 SPR, 并且由 SPR发起注册取消 操作到 PCRF的方法流程图 , 其具体步骤为:
步骤 1201、 UE确定需要发起附着操作。
步骤 1202、 UE发送附着请求消息到 MME, 在消息中携带用户标 识以及附着指示等信息。
步骤 1203、 MME发送注册请求消息到 HSS, 在消息中携带用户标 识且指明是附着操作。
步骤 1204、 HSS检测到为 UE服务的 MME是否发生改变,如果是, 则发送取消位置请求消息到切换前的 MME中。 步骤 1205、 切换前的 MME发送取消位置响应到 HSS。
步骤 1206、 HSS检测到为 UE服务的 MME是否发生改变,如果是, 则 HSS发送通知请求消息到 SPR, 该通知消息中携带用户标识并指明 是附着操作。
步骤 1204与步骤 1206没有明确的时序要求, 可以互换先后关系。 步骤 1207、 HSS发起插入用户数据过程, 向切换后的 MME插入相 关的用户数据。 这个步骤为可选。
步骤 1208、 SPR检测是否保存有该用户标识对应的 PCRF地址信息 或连接标识, 如果有, 则发送取消注册请求消息到各个 PCRF ( SPR中 可能保存多个 PCRF地址信息或连接标识);如果没有 ,则不发送取消注 册请求消息到 PCRF。
SPR发送取消注册请求消息到切换前的 PCRF, 该消息中携带用户 标识以及其他可能的信息。
步骤 1209、 切换前的 PCRF 据收到的消息携带的信息, 删除该用 户标识对应的所有的用户策略计费控制签约信息; 如果还存在相关承 载, 则发起删除相关业务承载的过程。
步骤 1210、切换前的 PCRF发送取消注册响应消息给 SPR,SPR删 除切换前的 PCRF的地址信息或连接标识; 删除切换前 PCRF的操作也 可以在步骤 1208后完成。
步骤 1211、 SPR发送通知响应消息给 HSS。
步骤 1212、 HSS发送注册接受消息给 MME。
步骤 1213、 MME发送附着接受消息给 UE。
在图 12中与 MME和 UPE分离还是合并无关。
图 13 为本发明实施例第四个处理流程实现方法二的实现方法一流 程图, 该方法应用在 MME和 UPE合并的场景, 其具体步骤为: 步骤 1301、 UE确定需要进行附着操作。
步骤 1302、 UE发送附着请求消息到切换到的 MME/UPE。 在消息 中包含用户标识和附着指示等信息。
步骤 1303、 切换到的 MME/UPE发送注册请求消息到 HSS。
步骤 1304、 HSS执行插入用户数据过程,把用户数据插入到切换到 的 MME/UPE中。 该步骤可选。
在步骤 1304 之前, HSS 发送取消位置消息到 UE 切换前的 MME/UPE。
步骤 1305、 HSS发送注册响应给切换到的 MME/UPE。
步骤 1306、切换到的 MME/UPE根据业务承载建立的需要以及用户 策略计费控制签约信息选择一个 PCRF, 发送注册请求消息到该 PCRF, 在消息中指明该操作是由附着操作发起的, 具体可以在某个字段中进行 指定。
如果在步骤 1304之前可以确定选择的 PCRF, 则步骤 1306可以在 步骤 1304之前执行。
步骤 1307、 该 PCRF向 SPR发送用户策略计费控制签约信息请求 消息, 在请求消息中指明是 UE附着操作, 以及用户标识等信息。
步骤 1308、 SPP检测是否保存有对应该用户标识的 PCRF地址信息 或连接标识, 如果有, 则发送取消注册请求消息到各个 PCRF ( SPR中 可能保存多个 PCRF地址信息或连接标识);如果没有 ,则不发送取消注 册请求消息到 PCRF。
SPR根据原来存储的 PCRF地址信息或连接标识,向切换前的 PCRF 发送取消注册请求消息, 该消息中包含用户标识以及其他可能的信息。
步骤 1309、切换前的 PCRF 收到取消注册请求消息后,删除对应该 用户标识的用户策略计费控制签约信息 , 并且删除对应的业务承载。 步骤 1310、 切换前的 PCRF发送取消注册响应消息到 SPR。
步骤 1311、 SPR删除切换前的 PCRF地址信息或连接标识, 保存切 换后的 PCRF地址信息或连接标识。 SPR发送用户策略计费控制签约信 息响应给切换后的 PCRF, 该消息中携带用户标识以及用户策略计费控 制签约信息。
步骤 1312、 切换后的 PCRF 发送注册响应消息给切换到的 MME/UPE。
步骤 1313、 切换到的 MME/UPE发送附着接受消息给 UE。
在图 13 中描述了 MME/UPE 合并的场景, 并且 PCEF 位于 MME/UPE。 如果 PCEF位于 Anchor 时, 与 UPE 不在一个网元时, MME/UPE 需要将注册请求消息发送到 PCEF ( Anchor ), 再由 PCEF ( Anchor ) 注册到 PCRF, 进行一次消息中转。
图 14 为本发明实施例第四个处理流程实现方法二的实现方法二流 程图, 该方法应用在 MME和 UPE分离的场景, 其具体步骤为:
步骤 1401、 UE确定进行附着操作。
步骤 1402、 UE发送附着请求消息到切换后的 MME, 在消息中携 带用户标识及附着指示等信息。
步骤 1403、 切换后的 MME发送注册请求消息到 HSS。
步骤 1404、 HSS执行插入用户数据过程,把用户数据插入到切换后 的 MME中。 该步骤可选。
在步骤 1404之前, HSS发送取消位置消息到切换前的 MME。
步骤 1405、 HSS发送注册响应给切换后的 MME。
步骤 1406、切换后的 MME根据业务承载建立的需要以及用户策略 计费控制签约信息选择一个 UPE ( PCEF ), 并发送注册请求消息到 UPE ( PCEF ), 在消息中指明该操作是由附着操作发起的。 具体可以在某个 字段中进行指定。
如果在步骤 1404之前可以确定选择的 PCRF, 则步骤 1406可以在 步骤 1404之前执行。
步骤 1407、 UPE ( PCEF )选择一个 PCRF, 并发送注册请求消息到 PCRF,在消息中指明该操作是由附着操作发起的。具体可以在某个字段 中进行指定。
步骤 1408、 该 PCRF向 SPR发送用户签约数据请求消息, 在请求 消息中指明是附着操作, 以及用户标识等信息。
步骤 1409、 SPR检测是否保存有对应用户标识的 PCRF的地址信息 或连接标识, 如果是, 则发送取消注册消息到各个 PCRF ( SPR中可能 保存多个 PCRF地址); 如果否, 则不发送取消注册消息到 PCRF。
SPR根据原来存储的 PCRF地址信息或连接标识, 向切换前 PCRF 发送取消注册请求, 消息中包含用户标识以及其他可能的信息(包括接 入技术的类型)。
步骤 1410、切换前的 PCRF 收到取消注册请求消息后,删除对应该 用户标识的签约数据信息, 并且删除对应的业务承载。
步骤 1411、 PCRF发送注册响应消息到 SPR。
步骤 1412、 SPR发送用户策略计费控制签约信息响应给切换后的 PCRF, 消息中包括用户标识以及用户策略计费控制签约信息等信息 ,并 且 SPR删除切换前的 PCRF的地址信息或连接标识,保存切换后的 PCRF 的地址信息或连接标识。
步骤 1413、 切换后的 PCRF发送注册响应消息给 UPE ( PCEF )。 步骤 1414、 UPE ( PCEF )发送附着接受消息给 MME。
步骤 1415、 MME发送附着接受消息给 UE。
在图 14中描述了 MME, UPE分离的场景, 并且 PCEF位于 UPE。 如果 PCEF位于 SAE Anchor时 , 与 UPE不在一个网元时, 可以有两种 情况进行注册。 如果 MME与 PCEF ( SAE Anchor )之间存在接口, 则 MME需要将注册请求消息发送到 PCEF( SAE Anchor ),再由 PCEF( SAE Anchor )注册到 PCRF。 如果 MME与 PCEF ( SAE Anchor )之间存在接 口, 则 MME需要将注册请求消息发送到 UPE,再由 UPE转发到 PCEF ( SAE Anchor ), 再注册到 PCRF中。
图 15 为本发明实施例第四个处理流程实现方法三的流程图, 其具 体步骤为:
步骤 1501、 PCRF接收到来自 PCEF或 AF等外部节点的业务承载 建立信息 , PCRF向 SPR发送用户策略计费控制签约信息请求消息 , 消 息中携带该用户的用户标识以及为用户提供服务的网络标识等信息。
步骤 1502、 在 SPR中根据接收到消息携带的信息检测为该用户提 供服务的网络是否已经有相关的 PCRF注册到 SPR中 , 如果是, 则发送 取消注册消息到相关的 PCRF, 取消注册消息中携带该用户的用户标识 以及为用户提供服务的网络标识等其他信息 ,并且 SPR删除原来存储的 相关的 PCRF地址信息或连接标识。
步骤 1503、相关 PCRF收到取消注册请求消息后, 根据携带的用户 标识以及为用户提供服务的网络标识确定该用户, 删除该用户在 PCRF 中的用户策略计费控制签约信息。
步骤 1504、 相关 PCRF发送取消注册响应消息到 SPR。
步骤 1505、 SPR发送用户策略计费控制签约信息响应给步骤 1500 所述的 PCRF, 该消息包括用户标识以及用户策略计费控制签约信息等 信息,并且保存步骤 1500所述的 PCRF地址信息或连接标识。保存方式 可以参照第一个处理流程。
本发明实施例还提供一种在演进网络中管理用户策略计费控制签 约信息的系统, 如图 16所示, 该系统包括 SPR以及 PCRF, 两者之间 进行信息交互, 其中,
SPR, 用于对应用户标识存储用户策略计费控制签约信息, 还用于 根据用户标识修改或删除所存储对应的用户策略计费控制签约信息, 或 /和根据用户标识存储、修改或删除当前使用用户策略计费控制签约信息 的策略和计费规则功能实体的地址信息或连接标识;
PCRF, 用于根据用户标识从 SPR获取对应的用户策略计费控制签 应的用户策略计费控制签约信息。
本发明实施例还提供一种在演进网络中管理用户策略计费控制签 约信息的装置一, 该装置为 SPR, 如图 17所示, 包括以下模块:
第一存储模块, 用于对应用户标识存储用户策略计费控制签约信 第一信息处理模块, 用于根据用户标识修改或删除第一存储模块中 对应的用户策略计费控制签约信息;
或 /和
第二存储模块 , 用于存储当前使用用户策略计费控制签约信息的策 略和计费规则功能实体的地址信息或连接标识;
第二信息处理模块, 用于根据用户标识修改或删除第二存储模块中 的当前使用用户策略计费控制签约信息的策略和计费规则功能实体的 地址信息或连接标识。
本发明实施例还提供一种在演进网络中管理用户策略计费控制签 约信息的装置二, 该装置为 PCRF, 如图 18所示, 包括处理模块、 接收 模块和存储模块, 其中,
接收模块,用于根据用户标识从 SPR获取对应的用户策略计费控制 签约信息, 发送给处理模块;
处理模块, 用于将从接收模块接收的用户策略计费控制签约信息存 储到存储模块中,根据 SPR的处理进行根据用户标识修改或删除存储模 块所存储对应的用户策略计费控制签约信息。
在现有的 PCC中, 已经对 PCRF向 SPR获取用户策略计费控制签 约信息, 以及当 SPR 中用户策略计费控制签约信息修改以后引起的对 PCRF操作流程, 均有比较详细的描述。 但对于 SPR如何存储 PCRF地 址信息或连接标识的流程没有详细的描述;在 PCRF 中删除用户策略计 费控制签约信息以后的操作流程没有详细的描述;在 SPR中删除用户策 略计费控制签约信息以后, 对 PCRF中修改流程的影响也没有详细的描 述; 用户改变了注册的 PCRF后的相关注册流程也没有详细的描述。 因 此,本发明实施例详细描述了在现有的 PCC中,用户策略计费控制签约 信息管理的详细处理流程, 使 PCC更加完善, 更加合理, 用户策略计费 控制签约信息能够正确 , 高效地使用。
以上所述的具体实施例, 对本发明的目的、 技术方案和有益效果进 行了进一步详细说明, 所应理解的是, 以上所述仅为本发明的具体实施 例而已, 并不用于限制本发明, 凡在本发明的精神和原则之内, 所做的 任何修改、 等同替换、 改进等, 均应包含在本发明的保护范围之内。

Claims

权利要求书
1、 一种在演进网络中管理用户策略计费控制签约信息的方法, 其 特征在于, 该方法包括:
用户策略签约数据库对应用户标识存储用户策略计费控制签约信 根据用户标识从用户策略签约数据库获取所存储对应的用户策略 计费控制签约信息 ,或 /和用户策略签约数据库根据用户标识修改或删除 所存储对应的用户策略计费控制签约信息, 或 /和根据用户标识存储、修 改或删除当前使用用户策略计费控制签约信息的策略和计费规则功能 实体的地址信息或连接标识。
2、 如权利要求 1 所述的方法, 其特征在于, 所述获取用户策略计 费控制签约信息 , 和存储策略和计费规则功能实体地址信息或连接标识 的过程为:
策略和计费规则功能实体向用户策略签约数据库发送携带用户标 识策略计费规则请求消息;
用户策略签约数据库接收到该消息后 , 对应该消息携带的用户标识 存储策略和计费规则功能实体的地址信息或连接标识;
用户策略签约数据库发送对应该请求消息携带的用户标识的用户 策略计费控制签约信息给策略和计费规则功能实体。
3、 如权利要求 2所述的方法, 其特征在于, 在存储策略和计费规 则功能实体的地址信息或连接标识之前, 还包括:
所述请求消息携带具有用户标识的用户是否签约了订阅通知信息, 用户策略签约数据库^^据所述请求消息携带的具有用户标识的用 户是否签约了订阅通知信息判断是否对用户策略计费控制签约信息进 行订阅通知,如果是,则继续执行存储策略和计费规则功能实体的步骤; 否则, 不存储策略和计费规则功能实体的地址信息或连接标识, 等到对 用户策略计费控制签约进行订阅后, 再存储对应的策略和计费规则功能 实体的地址信息或连接标识。
4、 如权利要求 1 所述的方法, 其特征在于, 所述修改或删除所存 储对应的用户策略计费控制签约信息为用户策略签约数据库发起时, 该 过程为:
在.
费控制签约信息, 用户策略签约数据库根据所保存的对应用户标识的策 略和计费规则功能实体地址信息或连接标识, 向具有策略和计费规则功 能实体地址信息或连接标识的一个或一个以上的策略和计费规则功能 实体发送携带用户标识的用户策略计费控制签约信息修改或删除请求 消息;
该一个或一个以上的策略和计费规则功能实体修改或删除对应用 户标识的用户策略计费控制签约信息 , 发送携带用户标识的修改或删除 业务承载通知到策略和计费执行功能实体, 由策略和计费执行功能实体 修改或删除对应的业务承载;
用户策略签约数据库删 I
用户策略计费控制签约信息的策略和计费规则功能实体地址信息或连 接标识。
5、 如权利要求 4所述的方法, 其特征在于, 所述发送用户策略计 费控制签约信息修改或删除请求消息过程为: 制签约信息的用户是否签约了订阅通知信息 , 根据该信息判断具有用户 标识的用户是否签约了订阅通知, 如果是, 发送用户策略计费控制签约 信息修改或删除请求消息; 否则, 不发送用户策略计费控制签约信息修 改或删除请求消息。
6、 如权利要求 1 所述的方法, 其特征在于, 所述修改或删除所存 储对应的用户策略计费控制签约信息为策略和计费规则功能实体发起 时 , 所述用户策略签约数据库删除策略和计费规则功能实体地址信息或 连接标识的过程为:
al、 策略和计费规则功能实体检测到具有用户标识的用户没有任何 业务承载时, 为该用户的用户策略计费控制签约信息再保存设定时间 后, 如果检测到的该用户还有其他的业务承载, 则将该用户策略计费控 制签约信息继续保存; 如果没有, 则转入步骤 bl;
bl、 策略和计费规则功能实体删除该用户标识对应的用户策略计费 控制签约信息后, 发送携带该用户标识的用户策略计费控制签约信息已 删除指示到用户策略签约数据库, 用户策略签约数据库删除该用户标识 对应的策略和计费规则功能实体地址信息或连接标识, 向策略和计费规 则功能实体发送响应消息。
7、 如权利要求 6所述的方法, 其特征在于, 在步骤 bl所述在用户 签约了订阅通知后 , 发送用户策略计费控制签约信息已删除指示到用户 策略签约数据库包括:
策略和计费规则功能实体预先存储有具有用户标识的用户策略计 费控制签约信息的用户是否签约了订阅通知信息 , 根据该信息判断具有 用户标识的用户是否签约了订阅通知, 如果是, 发送所述指示到用户策 略签约数据库; 否则, 不发送所述指示到用户策略签约数据库。
8、 如权利要求 6或 7所述的方法, 其特征在于, 步骤 bl所述用户 策略计费控制签约信息已删除指示为取消通知请求消息, 所述响应消息 为取消通知响应消息。
9、 如权利要求 1 所述的方法, 其特征在于, 所述修改或删除所存 储对应的用户策略计费控制签约信息为策略和计费规则功能实体发起 时 , 所述用户策略签约数据库删除策略和计费规则功能实体地址信息或 连接标识的过程为:
在策略和计费规则功能实体中删除对应用户标识的用户策略计费 控制签约信息后, 策略和计费规则功能实体发送该用户连接断开指示消 息到用户策略签约数据库; 的策略和计费规则功能实体的地址信息或连接标识后 , 给策略和计费规 则功能实体发送该指示消息的响应消息。
10、 如权利要求 9所述的方法, 其特征在于, 在发送该用户连接断 开指示消息到用户策略签约数据库之前 , 该方法还包括:
策略和计费规则功能实体预先存储有具有用户标识的用户策略计 费控制签约信息的用户是否签约了订阅通知信息 , 根据该信息判断具有 用户标识的用户是否签约了订阅通知, 如果是, 发送该用户连接断开指 示消息; 否则, 不发送该用户连接断开指示消息, 结束本方法。
11、 如权利要求 1所述的方法, 其特征在于, 所述删除当前使用用 户策略计费控制签约信息的策略和计费规则功能实体的地址信息或连 接标识是通过用户策略签约数据库发起的策略和计费规则功能实体取 消注册实现的, 过程为:
a2、 用户设备发起附着操作到移动管理实体, 移动管理实体发送携 带附着操作指示和用户标识的注册请求消息到归属用户服务器;
b2、 归属用户服务器接收到该注册请求消息后, 判断为用户设备当 前提供服务的移动管理实体是否更改, 如果是, 则发送携带用户标识的 通知消息到用户策略签约数据库, 执行步骤 c2; 如果否, 则不发送通知 消息到用户策略签约数据库, 结束本方法;
c2、 用户策略签约数据库接收到通知消息, 检测是否保存对应该用 户标识的策略和计费规则功能实体地址信息或连接标识, 如果有, 则发 送携带用户标识的取消注册请求消息到该一个或多个策略和计费规则 功能实体, 用户策略签约数据库删除对应用户标识的策略和计费规则功 能实体地址信息或连接标识, 执行步骤 d2; 否则, 则不发送取消注册请 求消息, 结束本方法;
d2、 该一个或多个策略和计费规则功能实体接收到用户策略签约数 据库的取消注册请求消息后, 据用户标识删除该用户标识对应的在策 略和计费规则功能实体中的用户策略计费控制签约信息 , 如果策略和计 费规则功能实体检测到存在对应的业务承载 , 则策略和计费规则功能实 体删除这些对应的业务承载。
12、 如权利要求 1所述的方法, 其特征在于, 所述删除当前使用用 户策略计费控制签约信息的策略和计费规则功能实体的地址信息或连 接标识是通过用户策略签约数据库发起的策略和计费规则功能实体取 消注册实现的, 过程为:
a3、 用户设备发起附着操作到移动管理实体 /用户面实体上; b3、 在建立缺省业务承载过程中或业务缺省承载建立完成以后, 策 略和计费执行功能实体发送携带附着操作指示和用户标识的注册请求 消息到用户设备切换到的策略和计费规则功能实体上;
c3、 用户设备切换到的策略和计费规则功能实体接收到来自策略和 计费执行功能实体的注册请求消息后, 发送携带附着操作指示和用户标 识的用户策略计费控制签约信息获取请求消息到用户策略签约数据库; d3、 用户策略签约数据库接收到请求消息, 且检查到有附着操作的 指示后 , 检测是否保存有对应该用户标识的策略和计费规则功能实体地 址信息, 如果有, 则发送携带用户标识的取消注册请求消息到对应该用 户标识的一个或多个策略和计费规则功能实体, 用户策略签约数据库删 除对应用户标识的策略和计费规则功能实体地址信息或连接标识, 转入 步骤 e3; 否则, 则不发送取消注册请求消息, 结束本方法;
e3、 该一个或多个策略和计费规则功能实体接收到用户策略签约数 据库的取消注册请求消息后, 据用户标识删除该用户标识对应的在策 略和计费规则功能实体中的用户策略计费控制签约信息 , 如果策略和计 费规则功能实体检测到存在对应的业务承载 , 则策略和计费规则功能实 体删除这些对应的业务承载。
13、 如权利要求 1所述的方法, 其特征在于, 所述删除当前使用用 户策略计费控制签约信息的策略和计费规则功能实体的地址信息或连 接标识是通过用户策略签约数据库发起的策略和计费规则功能实体取 消注册实现的, 过程为:
a4、 应用功能实体或策略计费执行功能实体发起业务承载建立过程 与策略和计费规则功能实体进行交互, 在交互过程中将业务承载的用户 标识发送给策略和计费规则功能实体;
b4、 策略和计费规则功能实体检测到没有具有用户标识的用户策略 计费控制签约信息, 向用户策略签约数据库发送携带用户标识的获取用 户策略计费控制签约信息请求消息, 执行步骤 c4; 如果策略和计费规则 功能实体存在具有用户标识的用户策略计费控制签约信息, 则不向用户 策略签约数据库发送获取用户策略计费控制签约信息请求消息 , 结束本 方法;
c4、 用户策略签约数据库根据接收到的请求消息携带的用户标识检 测是否有对应的策略和计费规则功能实体地址信息或连接标识, 如果 有 , 则发送携带用户标识的取消注册消息到具有该策略和计费规则功能 实体地址信息的策略和计费规则功能实体上 , 用户策略签约数据库删除 该策略和计费规则功能实体地址信息;
d4、 策略和计费规则功能实体接收到取消注册消息后, 根据该消息 携带的用户标识, 删除对应的用户策略计费控制签约信息; 如果策略和 计费规则功能实体检测到存在与用户策略计费控制签约信息对应的业 务承载 , 则策略和计费规则功能实体删除对应的业务承载。
14、 如权利要求 1所述的方法, 其特征在于, 所述用户策略计费控 制签约信息还对应于网络标识进行存储;
所述从用户策略签约数据库获取、 用户策略签约数据库修改或删除 所存储对应的用户策略计费控制签约信息还根据网络标识进行;
所述存储、 修改或删除当前使用用户策略计费控制签约信息的策略 和计费规则功能实体的地址信息或连接标识还根据网络标识进行。
15、 如权利要求 14所述的方法, 其特征在于, 所述网络标识为公 共数据网标识或接入点名称标识。
16、 如权利要求 14所述的方法, 其特征在于, 所述获取用户策略 计费控制签约信息 , 和存储策略和计费规则功能实体地址信息或连接标 识的过程为:
策略和计费规则功能实体向用户策略签约数据库发送携带用户标 识和网络标识的策略计费规则请求消息;
用户策略签约数据库接收到该消息后 , 对应该消息携带的用户标识 和网络标识存储策略和计费规则功能实体的地址信息或连接标识; 用户策略签约数据库发送对应该请求消息携带的用户标识和网络 标识的用户策略计费控制签约信息给策略和计费规则功能实体。
17、 如权利要求 16 所述的方法, 其特征在于, 在存储策略和计费 规则功能实体的地址信息或连接标识之前, 该方法还包括: 所述请求消息携带具有用户标识和网络标识的用户是否签约了订 阅通知信息,
用户策略签约数据库^^据所述请求消息携带的具有用户标识和网 络标识的用户是否签约了订阅通知信息判断是否对用户策略计费控制 签约信息进行订阅通知, 如果是, 则继续执行存储策略和计费规则功能 实体的步骤; 否则, 用户策略签约数据库不存储策略和计费规则功能实 体的地址信息或连接标识。
18、 如权利要求 14所述的方法, 其特征在于, 所述修改或删除所 存储对应的用户策略计费控制签约信息为用户策略签约数据库发起时, 过程为: 费控制签约信息, 用户策略签约数据库根据所保存的对应用户标识和网 络标识的策略和计费规则功能实体地址信息或连接标识, 向具有策略和 计费规则功能实体地址信息或连接标识的一个或一个以上的策略和计 费规则功能实体发送携带用户标识和网络标识的用户策略计费控制签 约信息修改或删除请求消息;
该一个或一个以上的策略和计费规则功能实体修改或删除对应用 户标识和网络标识的用户策略计费控制签约信息, 发送携带用户标识和 网络标识的修改或删除业务承载通知到策略和计费执行功能实体, 由策 略和计费执行功能实体修改或删除对应的业务承载; 已经删除了用户策略计费控制签约信息的策略和计费规则功能实体地 址信息或连接标识。
19、 如权利要求 18 所述的方法, 其特征在于, 在发送用户策略计 费控制签约信息修改或删除请求消息之前, 该方法还包括: 策略计费控制签约信息的用户是否签约了订阅通知信息 , 根据该信息判 断具有用户标识和网络标识的用户是否签约了订阅通知, 如果是, 发送 用户策略计费控制签约信息修改或删除请求消息; 否则, 不发送用户策 略计费控制签约信息修改或删除请求消息 , 结束本方法。
20、 如权利要求 14所述的方法, 其特征在于, 所述修改或删除所 存储对应的用户策略计费控制签约信息为策略和计费规则功能实体发 起时 , 所述用户策略签约数据库删除策略和计费规则功能实体地址信息 或连接标识的过程为:
a5、 策略和计费规则功能实体检测到具有用户标识的用户没有任何 业务承载时, 为该用户的用户策略计费控制签约信息再保存设定时间 后, 如果检测到的该用户还有其他的业务承载, 则将该用户策略计费控 制签约信息继续保存; 如果没有, 则转入步骤 b5;
b5、 策略和计费规则功能实体删除该用户标识和网络标识对应的用 户策略计费控制签约信息后, 发送携带该用户标识和网络标识的用户策 略计费控制签约信息已删除指示到用户策略签约数据库 , 用户策略签约 数据库删除该用户标识和网络标识对应的策略和计费规则功能实体地 址信息或连接标识, 向策略和计费规则功能实体发送响应消息。
21、 如权利要求 20所述的方法, 其特征在于, 在步骤 b5所述发送 指示到用户策略签约数据库之前, 该方法还包括:
策略和计费规则功能实体预先存储有具有用户标识和网络标识的 用户策略计费控制签约信息的用户是否签约了订阅通知信息 , 根据该信 息判断具有用户标识和网络标识的用户是否签约了订阅通知 , 如果是, 发送所述指示到用户策略签约数据库; 否则, 不发送所述指示到用户策 略签约数据库, 结束本方法。
22、 如权利要求 20或 21所述的方法, 其特征在于, 步骤 b5所述 的指示为取消通知请求消息, 所述地响应消息为取消通知响应消息。
23、 如权利要求 14所述的方法, 其特征在于, 所述删除当前使用 用户策略计费控制签约信息的策略和计费规则功能实体的地址信息或 连接标识是通过用户策略签约数据库发起的策略和计费规则功能实体 取消注册实现的, 过程为:
a6、 应用功能实体或策略计费执行功能实体发起业务承载建立过程 与策略和计费规则功能实体进行交互, 在交互过程中将业务承载的用户 标识发送给策略和计费规则功能实体;
b6、 策略和计费规则功能实体检测到没有具有用户标识的用户策略 计费控制签约信息, 向用户策略签约数据库发送携带用户标识和网络标 识的获取用户策略计费控制签约信息请求消息, 执行步骤 c6; 如果策略 和计费规则功能实体存在具有用户标识的用户策略计费控制签约信息, 则不向用户策略签约数据库发送获取用户策略计费控制签约信息请求 消息, 结束本方法;
c6、 用户策略签约数据库根据接收到的请求消息携带的用户标识和 网络标识检测是否有对应的策略和计费规则功能实体地址信息或连接 标识, 如果有, 则发送携带用户标识和网络标识的取消注册消息到注册 消息到具有该策略和计费规则功能实体地址信息的策略和计费规则功 能实体上 , 用户策略签约数据库删除该策略和计费规则功能实体地址信 d6、 策略和计费规则功能实体接收到取消注册消息后, 根据该消息 携带的用户标识和网络标识, 删除对应的用户策略计费控制签约信息; 如果策略和计费规则功能实体检测到存在与用户策略计费控制签约信 息对应的业务承载, 删除对应的业务承载。
24、 一种在演进网络中管理用户策略计费控制签约信息的系统, 其 特征在于, 包括用户策略签约数据库以及策略和计费规则功能实体, 两 者之间进行信息交互, 其中,
用户策略签约数据库, 用于对应用户标识存储用户策略计费控制签 制签约信息, 或 /和根据用户标识存储、修改或删除当前使用用户策略计 费控制签约信息的策略和计费规则功能实体的地址信息或连接标识; 策略和计费规则功能实体, 用于根据用户标识从用户策略签约数据 库获取对应的用户策略计费控制签约信息, 还用于根据用户策略签约数 据库的处理进
控制签约信息。
25、 一种在演进网络中管理用户策略计费控制签约信息的装置, 其 特征在于, 其中,
第一存储模块, 用于对应用户标识存储用户策略计费控制签约信 第一信息处理模块, 用于根据用户标识修改或删除第一存储模块中 对应的用户策略计费控制签约信息;
或 /和、
第二存储模块 , 用于存储当前使用用户策略计费控制签约信息的策 略和计费规则功能实体的地址信息或连接标识;
第二信息处理模块, 用于根据用户标识修改或删除第二存储模块中 的当前使用用户策略计费控制签约信息的策略和计费规则功能实体的 地址信息或连接标识。
26、 一种在演进网络中管理用户策略计费控制签约信息的装置, 其 特征在于, 包括处理模块、 接收模块和存储模块, 其中, 接收模块, 用于根据用户标识从用户策略签约数据库获取对应的用 户策略计费控制签约信息, 发送给处理模块;
处理模块, 用于将从接收模块接收的用户策略计费控制签约信息存 储到存储模块中, 根据用户策略签约数据库的处理进行根据用户标识修 改或删除存储模块所存储对应的用户策略计费控制签约信息。
PCT/CN2007/070471 2006-08-14 2007-08-14 Procédé, système et appareil de gestion des informations concernant les règles d'utilisation et de facturation associées au profil d'utilisateur dans un réseau évolutif WO2008019626A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNB2006101095926A CN100544264C (zh) 2006-08-14 2006-08-14 一种在演进网络中管理用户策略计费控制签约信息的方法
CN200610109592.6 2006-08-14

Publications (1)

Publication Number Publication Date
WO2008019626A1 true WO2008019626A1 (fr) 2008-02-21

Family

ID=39081957

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/070471 WO2008019626A1 (fr) 2006-08-14 2007-08-14 Procédé, système et appareil de gestion des informations concernant les règles d'utilisation et de facturation associées au profil d'utilisateur dans un réseau évolutif

Country Status (2)

Country Link
CN (1) CN100544264C (zh)
WO (1) WO2008019626A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102143468A (zh) * 2010-09-25 2011-08-03 华为软件技术有限公司 计费、资费更新、提供服务的方法及系统
CN103686656A (zh) * 2012-09-07 2014-03-26 电信科学技术研究院 一种基于wlan网络标识的策略和计费控制方法及系统
CN107454123A (zh) * 2016-05-31 2017-12-08 株式会社日立制作所 数据收集方法和数据收集装置
CN109802837A (zh) * 2017-11-15 2019-05-24 中国移动通信有限公司研究院 一种计费方法、装置、设备及计算机可读存储介质

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296517B (zh) * 2008-04-22 2013-01-23 中国移动通信集团设计院有限公司 异构网络中保证服务质量管理的切换方法、系统及装置
CN101729511B (zh) * 2008-10-23 2012-11-21 华为技术有限公司 一种通用业务架构下用户动态签约的方法、装置与系统
ES2422590T3 (es) * 2008-11-03 2013-09-12 Nokia Siemens Networks Oy Control de cobro que proporciona corrección de información de control de cobro
WO2010118566A1 (zh) * 2009-04-13 2010-10-21 华为技术有限公司 策略与计费控制的实现方法、设备及策略与计费系统
CN101540980B (zh) * 2009-04-24 2012-03-21 华为技术有限公司 业务优先级更新指示方法、业务优先级更新方法及装置
CN101729978B (zh) * 2009-05-26 2013-06-12 中兴通讯股份有限公司 一种实现制定业务计费策略的方法及系统
CN102014343A (zh) * 2009-09-04 2011-04-13 华为技术有限公司 群组策略与计费规则处理方法、装置以及通信系统
CN102045867B (zh) * 2009-10-19 2014-04-30 中兴通讯股份有限公司 网络连接建立方法及装置、pcc策略制定方法及系统
US8594684B2 (en) * 2009-12-18 2013-11-26 Motorola Solutions, Inc. Method for bearer establishment in a radio access network
WO2011110020A1 (zh) * 2010-09-26 2011-09-15 华为技术有限公司 策略控制器选择方法、系统以及直径协议路由代理实体
WO2012095697A1 (en) * 2011-01-10 2012-07-19 Telefonaktiebolaget L M Ericsson (Publ) Recovery of a system for policy control and charging, said system having a redundancy of policy and charging rules function
CN102711072A (zh) * 2012-05-23 2012-10-03 华为软件技术有限公司 一种实现计费的方法和预取服务器
CN104685827B (zh) * 2012-06-14 2018-07-06 泰科来股份有限公司 用于提供具有集成的openflow控制器的策略与计费规则功能(PCRF)的方法、系统和计算机可读介质
CN103686654B (zh) * 2012-09-05 2017-11-24 中国移动通信集团公司 Pcc会话关联方法、以及pcef单元和pa单元
US9838483B2 (en) 2013-11-21 2017-12-05 Oracle International Corporation Methods, systems, and computer readable media for a network function virtualization information concentrator
US11388082B2 (en) 2013-11-27 2022-07-12 Oracle International Corporation Methods, systems, and computer readable media for diameter routing using software defined network (SDN) functionality
US10051638B2 (en) * 2014-07-17 2018-08-14 Deutsche Telekom Ag Method for enhanced policy and charging control in telecommunications networks
US9917729B2 (en) 2015-04-21 2018-03-13 Oracle International Corporation Methods, systems, and computer readable media for multi-layer orchestration in software defined networks (SDNs)
US10148509B2 (en) 2015-05-13 2018-12-04 Oracle International Corporation Methods, systems, and computer readable media for session based software defined networking (SDN) management
CN106470412B (zh) * 2015-08-20 2021-08-24 中兴通讯股份有限公司 终端下线方法、备用pcrf装置、用户签约数据装置及系统
CN108476388B (zh) * 2015-12-31 2020-08-07 华为技术有限公司 处理数据包的方法及装置
CN107154901B (zh) * 2016-03-03 2021-07-06 中兴通讯股份有限公司 数据传输的控制方法及系统、数据传输方法及装置
CN109327395B (zh) * 2018-11-30 2021-09-10 新华三信息安全技术有限公司 一种报文处理方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003006153A (ja) * 2001-06-27 2003-01-10 Nec Corp 通信ネットワーク及びそれに用いる認証方法、課金方法、端末設定方法並びにそのプログラム
CN1442981A (zh) * 2002-03-04 2003-09-17 华为技术有限公司 实现认证授权计费过程中实时修改业务的方法
EP1437693A1 (en) * 2003-01-08 2004-07-14 Itsmobile Limited A mobile telecommunications billing routing system and method
CN1533543A (zh) * 2001-02-19 2004-09-29 ��˹��ŵ�� 控制通信系统中的计费

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1533543A (zh) * 2001-02-19 2004-09-29 ��˹��ŵ�� 控制通信系统中的计费
JP2003006153A (ja) * 2001-06-27 2003-01-10 Nec Corp 通信ネットワーク及びそれに用いる認証方法、課金方法、端末設定方法並びにそのプログラム
CN1442981A (zh) * 2002-03-04 2003-09-17 华为技术有限公司 实现认证授权计费过程中实时修改业务的方法
EP1437693A1 (en) * 2003-01-08 2004-07-14 Itsmobile Limited A mobile telecommunications billing routing system and method

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102143468A (zh) * 2010-09-25 2011-08-03 华为软件技术有限公司 计费、资费更新、提供服务的方法及系统
CN102143468B (zh) * 2010-09-25 2014-01-08 华为软件技术有限公司 计费、资费更新、提供服务的方法及系统
CN103686656A (zh) * 2012-09-07 2014-03-26 电信科学技术研究院 一种基于wlan网络标识的策略和计费控制方法及系统
CN103686656B (zh) * 2012-09-07 2017-08-04 电信科学技术研究院 一种基于wlan网络标识的策略和计费控制方法及系统
CN107454123A (zh) * 2016-05-31 2017-12-08 株式会社日立制作所 数据收集方法和数据收集装置
CN109802837A (zh) * 2017-11-15 2019-05-24 中国移动通信有限公司研究院 一种计费方法、装置、设备及计算机可读存储介质
CN109802837B (zh) * 2017-11-15 2023-01-13 中国移动通信有限公司研究院 一种计费方法、装置、设备及计算机可读存储介质

Also Published As

Publication number Publication date
CN100544264C (zh) 2009-09-23
CN101127609A (zh) 2008-02-20

Similar Documents

Publication Publication Date Title
WO2008019626A1 (fr) Procédé, système et appareil de gestion des informations concernant les règles d'utilisation et de facturation associées au profil d'utilisateur dans un réseau évolutif
US9137652B2 (en) Method for implementing policy and charging control in a roaming scene
US8817612B2 (en) Method for implementing limited policy and charging control and system thereof
US8874715B2 (en) Charging method, system and reporting method for terminal accessing through multiple access networks
JP4402714B2 (ja) フローベース課金におけるイベント・トリガと再認証トリガを取り扱う方法
US8463889B2 (en) Method for provisioning and installing event triggers
US20110161504A1 (en) Method and apparatus for identifying session information
WO2009086734A1 (zh) 非漫游场景下策略和计费规则功能实体的选择方法
US20120320801A1 (en) Nodes For Improved Credit Validation
US20120102174A1 (en) Policy And Charging Control Method And System For Multi-PDN Connections Of Single APN
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
WO2011063688A1 (zh) 策略和计费规则功能实体的选择方法及系统
WO2009094837A1 (en) A method for selecting a policy and charging rules function server on a non-roaming scene
EP2003917B1 (en) Deciding method and system for service information in mobile communication system
WO2007143940A1 (fr) procédé, système et équipement de contrôle des conditions d'utilisation et de la facturation lorsque l'utilisateur est mobile
WO2010031316A1 (zh) 多分组数据网场景下实现策略和计费控制的方法和系统
WO2009021462A1 (fr) Procédé et dispositif d'établissement de session ip-can
WO2011006317A1 (zh) 删除家乡策略和计费规则功能冗余信息的方法及系统
WO2008086754A1 (fr) Procédé, dispositif et système pour l'enregistrement émergent dans un réseau d'accès par connexion ip de l'équipement utilisateur
WO2012075875A1 (zh) 一种消费限制业务的签约和执行方法及系统
WO2013060170A1 (zh) 一种提供基于lipa承载的计费支持的方法及装置
WO2008092346A1 (fr) Procédé, système et appareil pour l'établissement d'un support de signalisation
US8516073B2 (en) Method, device and system for transferring information
WO2011018020A1 (zh) 控制pcrf负载均衡的方法、系统及重定向dra
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: 07800947

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

122 Ep: pct application non-entry in european phase

Ref document number: 07800947

Country of ref document: EP

Kind code of ref document: A1