[go: up one dir, main page]

WO2011131075A1 - Procédé et système servant à déterminer d'adopter ou non un mécanisme de commande de politique et de facturation - Google Patents

Procédé et système servant à déterminer d'adopter ou non un mécanisme de commande de politique et de facturation Download PDF

Info

Publication number
WO2011131075A1
WO2011131075A1 PCT/CN2011/072226 CN2011072226W WO2011131075A1 WO 2011131075 A1 WO2011131075 A1 WO 2011131075A1 CN 2011072226 W CN2011072226 W CN 2011072226W WO 2011131075 A1 WO2011131075 A1 WO 2011131075A1
Authority
WO
WIPO (PCT)
Prior art keywords
pcc
information
user
access
gateway
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2011/072226
Other languages
English (en)
Chinese (zh)
Inventor
毛玉欣
巴瑞杰·芮杰希
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Publication of WO2011131075A1 publication Critical patent/WO2011131075A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0892—Network architectures or network communication protocols for network security for authentication of entities by using authentication-authorization-accounting [AAA] servers or protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/20—Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • H04L63/205—Network architectures or network communication protocols for network security for managing network security; network security policies in general involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing

Definitions

  • the present invention relates to the field of communications, and more particularly to a method and system for deciding whether to apply a Policy and Charging Control (PCC) mechanism.
  • PCC Policy and Charging Control
  • PCC architecture of the 3rd Generation Partnership Project (3GPP) is mainly composed of Policy and Charging Rule Function (PCRF), bearer binding and event reporting (Bearer).
  • PCRF Policy and Charging Rule Function
  • BBERF Binding and Event Report Function
  • PCEF Policy and Charging Enforcement Function
  • the PCRF is used for policy decision-making, and authorizes the service usage resources according to the requirements of the user for the service, the user subscription information, and the operator control policy, and the authorized quality of service (QoS) and charging policy. Issued to BBERF and PCEF for execution. BBERF and PCEF implement QoS and charging control for traffic flows according to the authorization policy.
  • the PCC architecture includes Application Function (AF), Offline Charging System (OFCS), Online Charging System (OCS), and Subscription Profile Repository (SPR). Wait.
  • PCC is a dynamic resource control mechanism, which can dynamically control the use of network resources by the service, that is, according to the requirements of the network resources used by the service, how much is needed to be allocated, and is not required to be released immediately, thereby effectively avoiding the network.
  • the resources are not used, or the network resources are not enough, resulting in uneven resource allocation or waste of resources.
  • the network that introduces the PCC mechanism has more rich control modes for billing, such as implementing stream-based online or offline billing, and content billing.
  • the PCC mechanism defined by 3GPP can also be applied to code division multiple access high speed packet data (Code Division Multiple Access High Rate Packet Data (CDMA) network and Evolved High Rate Packet Data (eHRPD), which implement dynamic control and fine billing for CDMA users.
  • CDMA Code Division Multiple Access High Rate Packet Data
  • eHRPD Evolved High Rate Packet Data
  • the architecture of the CDMA HRPD network is shown in Figure 2. It mainly includes: Radio Access Network (RAN), which is the wireless access part; Packet Data Service Network (PDSN); Home Agent (Home) Agent, HA) and Authentication, Authorization and Accounting (AAA) are the core network packet switching part, which is responsible for authenticating the user access network and realizing the user data service. If the roaming user accesses the network, it also involves visiting AAA, Broker AAA and Home AAA.
  • RAN Radio Access Network
  • PDSN Packet Data Service Network
  • Home Agent Home Agent
  • AAA Authentication, Authorization and Accounting
  • the CDMA eHRPD network architecture is similar to the HRPD network and will not be described in detail here. It mainly includes: Evolved Radio Access Network (eRAN); HRPD Serving Gateway (HSGW). The network location of the HSGW is equivalent.
  • the PDSN is connected to the radio access network and is mainly responsible for the user's mobility management and context management.
  • the packet gateway (P-GW) and the P-GW have the same network location as the HA, which is the anchor for the user to access the network. Fixed point, responsible for data communication between the user and the external PDN network. The following takes the user accessing the HRPD network as an example to describe the process of authentication authentication and session negotiation between the user and the access network, as shown in FIG.
  • Step 301 The user terminal requests access to the network, where the user terminal A primary service connection between the mobile station (MS) and the PDSN is required to carry all signaling messages between the MS and the network.
  • Step 302. Link Control Protocol (LPP) is implemented between the MS and the PDSN.
  • LCP Link Control Protocol
  • Negotiation which method is used to authenticate between the MS and the network; for example, using the Password Authentication Protocol (PAP) or the Challenge Handshake Authentication Protocol (CHAP) ) Method for authentication.
  • PAP Password Authentication Protocol
  • CHAP Challenge Handshake Authentication Protocol
  • Step 303 The MS initiates authentication to the PDSN according to the authentication mode determined by the LCP phase negotiation. And, the MS and the PDSN exchange authentication related information;
  • the AAA authenticates the user access network according to the information contained in the access request message. After the authentication is passed, the AAA sends an Access Accept message to the PDSN, and returns the authentication result to allow the user to access the network. At the same time, the AAA needs to send the subscription information corresponding to the user to the PDSN. Step 306. The PDSN returns the authentication result to the MS at the same time. Step 307. The PDSN sends the subscription information of the user to the RAN. Step 308.
  • IPCP Internet Protocol Control Protocol
  • the terminal assigns an IP address. After the user terminal completes the IPCP negotiation and establishes a Point to Point Protocol (PPP) session, the user successfully accesses the network.
  • IPCP Internet Protocol Control Protocol
  • the CDMA network can provide data routing services for the user to conduct services.
  • the CDMA network can use Simple IP (SIP), Mobile IP (MIP) or Proxy Mobile IP (PMIP) as its communication protocol.
  • SIP Simple IP
  • MIP Mobile IP
  • PMIP Proxy Mobile IP
  • the PCEF function can be implemented on the Packet Data Serving Network (PDSN);
  • PDSN Packet Data Serving Network
  • MIP Mobile IP
  • PMIP Proxy Mobile IP
  • the PCEF function can be implemented on the Packet Data Serving Network
  • the BBERF can be implemented on the PDSN
  • the home agent Home Agent
  • HA Home Agent
  • LMA Localized Mobility Anchor
  • the PDSN is upgraded to support PCEF or BBERF.
  • the network needs to perform service decision for the user accessing the network according to whether the PDSN supports the PCC capability (that is, whether the PCEF or the BBERF is supported), whether to use the PCC for resource control and charging.
  • the network of the operator A deploys the PCC mechanism, and the users who sign the carrier network use the PCC for control when conducting business.
  • the PCC mechanism is not deployed on the network of the carrier B.
  • the network needs to determine the control mode for the user according to the subscription information of the user.
  • the network needs to be supported according to the network element.
  • the PCC's capabilities determines whether the user uses the PCC-based charging method or the traditional non-PCC charging method.
  • the network needs to decide whether to use the PCC mechanism to perform PCC on the users accessing the network.
  • the technical problem to be solved by the present invention is to provide a method and system for determining whether to use the PCC mechanism and an AAA server, so that the network side can decide whether to use the PCC mechanism for the user to control.
  • the present invention provides a method for deciding whether to use a policy and a charging control mechanism, the method comprising: when a user requests access to a network, an authentication and authorization charging (AAA) server according to at least one of the following information Or any combination of user access decision-making whether to use policy and charging control (PCC): the PCC support capability of the gateway responsible for the user access, the subscription information of the user, and the operator policy information.
  • AAA authentication and authorization charging
  • PCC policy and charging control
  • the method further includes: when the user requests to access the network, the gateway responsible for accessing the user sends an access request to the AAA server, and after receiving the access request, the AAA server obtains the The PCC support capability of the gateway: if the access request includes the PCC support capability information of the gateway, the AAA server obtains the PCC support capability information of the gateway from the access request message; The PCC support capability information of the gateway is not included in the request, then AAA The server requests the gateway to report PCC support capability information of the gateway. among them,
  • the PCC support capability information of the gateway refers to whether the gateway supports a Policy and Charging Enforcement Function (PCEF) or a Bearer Binding and Event Reporting Function (BBERF).
  • PCEF Policy and Charging Enforcement Function
  • BBERF Bearer Binding and Event Reporting Function
  • the subscription information of the user includes PCC capability information of the user, and the PCC capability information refers to information about whether the user accesses the used PCC according to the operation requirement. among them,
  • the operator policy information is policy information defined by the operator according to the operational requirements for whether the user accesses the PCC. among them,
  • the method is applied to a High Speed Packet Data Network (HRPD) or an Evolved High Speed Packet Data Network (eHRPD); when the method is applied to an HRPD network, the gateway is: a packet data monthly service network (PDSN); a PDSN and Home agent (HA); or, PDSN and Local Mobility Anchor (LMA); When the method is applied to an eHRPD network, the gateway is: HRPD Serving Gateway (HSGW); or, HSGW and Packet Gateway (P-GW) ). among them,
  • the AAA server determines whether to use the PCC for the user access decision in the following manner: When the AAA server makes a decision based on only one of the information, if the information indicates that the PCC is supported, the AAA server decides to connect the user. Initiating the PCC, if the information indicates that the PCC is not supported, the AAA server decides not to use the PCC for the user access; when the AAA server makes a decision according to two or more of the information, if the two or When the above information indicates that the PCC is supported, the AAA server decides to implement the PCC for the user access. If not all of the PCCs are supported, the AAA server decides that the user access does not use the PCC. among them,
  • the PCC includes: policy control and/or charging control.
  • the present invention also provides a system for deciding whether to use a policy and a charging control mechanism, the system includes an authentication and authorization charging (AAA) server, and the AAA server includes an access authentication module,
  • the access authentication module is configured to: when the user requests to access the network, authenticate the user, and use at least one or any combination of the following information to determine whether the user access decision uses the policy and charging control ( PCC): PCC support capability information of the gateway accessed by the user, subscription information of the user, and operator policy information.
  • PCC policy and charging control
  • the system further includes a gateway, the gateway includes a PCC capability reporting module, and the AAA server further includes an information acquiring module that is connected to the access authentication module, where: the PCC capability reporting module is configured as: When the network is sent to the network, the access request is sent to the access authentication module, and the PCC support capability information of the gateway is included in the access request and reported to the information acquiring module; or, according to the information.
  • the PCC capability reporting module is configured as: When the network is sent to the network, the access request is sent to the access authentication module, and the PCC support capability information of the gateway is included in the access request and reported to the information acquiring module; or, according to the information.
  • the request of the module reports the PCC support capability information of the gateway to the information acquisition module; the information acquisition module is configured to: according to the received access request, if the access request includes the gateway The PCC supports the capability information, and the PCC support capability of the gateway is obtained from the access request; if the PCC support capability information of the gateway is not included in the access request, requesting to report the gateway to the gateway PCC support capabilities.
  • the information acquiring module is further configured to: obtain the subscription information or the operator policy information of the user; the access authentication module is configured to be configured according to the gateway acquired by the information acquiring module.
  • One or more of the PCC support capability information, the subscription information of the user, and the operator policy information is whether the user access decision uses the PCC. among them,
  • the PCC includes: policy control and/or charging control.
  • the present invention further provides an authentication and authorization charging (AAA) server, where the AAA server includes an access authentication module, where: the access authentication module is configured to: when the user requests to access the network And authenticating the user, and according to at least one or any combination of the following information, whether the user access decision uses the policy and charging control (PCC): the PCC support capability of the gateway responsible for the user access Information, subscription information for the user, and operator policy information.
  • the AAA server further includes an information acquiring module connected to the access authentication module, where:
  • the access authentication module is further configured to: when receiving a user requesting to access the network, the access request sent by the gateway accessed by the user to the access authentication module, where the access request includes the gateway
  • the PCC supports the capability information, and reports the access request to the information acquisition module; or, according to the request of the information acquisition module, the PCC support capability information of the gateway is received and reported to the information acquisition module;
  • the information obtaining module is configured to: obtain the PCC support capability of the gateway from the access request, if the access request includes the PCC support capability information of the gateway, according to the received access request And if the access request does not include the PCC support capability information of the gateway, requesting, by the gateway, the PCC support capability of the gateway to be reported.
  • the information acquiring module is further configured to: obtain the subscription information or the operator policy information of the user; the access authentication module is configured to be configured according to the gateway acquired by the information acquiring module.
  • One or more of the PCC support capability information, the subscription information of the user, and the operator policy information is whether the user access decision uses the PCC.
  • the present invention considers the difference in network capabilities or the difference in subscription information, so that when the user accesses the network, the network side can decide whether to use the subscription information and/or network capability according to the user.
  • the PCC mechanism performs PCC for users accessing the network.
  • the PCC includes policy control and/or billing control.
  • FIG. 1 is a schematic diagram of a prior art 3GPP PCC architecture
  • FIG. 2 is a schematic diagram of a prior art CDMA packet data architecture
  • FIG. 3 is a schematic diagram of a prior art user accessing a CDMA network
  • Embodiment 1 of the present invention is a schematic diagram of a process for determining whether a user accesses a PCC according to a capability of a network-supported PCC.
  • FIG. 5 is a second embodiment of the present invention, according to the capability of the network to support the PCC and the user subscription information decision, whether the user accesses the PCC.
  • FIG. 6 is a schematic diagram of a process of determining whether a PCC is used by a user according to the capability of the network to support the PCC and the user subscription information in the third eHRPD network according to the embodiment of the present invention.
  • the basic idea of the present invention is: when the user requests to access the network, the network side supports the PCC capability information according to the network element, whether the PCC information is used in the subscription information of the user, and the operator policy information. One or more of the decisions to determine whether the user access uses PCC.
  • the PCC in the present invention may be only policy control, or only charging control, and may also be policy and charging control.
  • the present invention provides a method for determining whether to use PCC for user access decision.
  • the following technical solutions are used: When a user requests to access the network, the AAA uses the PCC according to at least one or any combination of the following information: the PCC support capability information of the gateway responsible for accessing the user, The subscriber's subscription information and carrier policy information.
  • the method further includes: when the user requests to access the network, the gateway responsible for the user access sends an access request to the AAA; after receiving the access request, the AAA obtains the PCC support capability information of the gateway by using the following manner: The access request includes the PCC support capability of the gateway, and the AAA obtains the PCC support capability of the gateway from the access request;
  • the AAA requests the gateway to report its PCC support capability.
  • the method further includes: after receiving the access request, the AAA acquires subscription information of the user.
  • the subscription information of the user includes PCC capability information of the user.
  • the user's PCC capability information is used to indicate that PCC-based policy control and/or PCC-based charging control is implemented for the user.
  • the PCC capability information is defined by the operator according to the operation requirement. For example, if the PCC capability information is included in the user subscription information, the PCC capability information is implemented for the user; if the PCC capability information is not included in the user subscription information, It means that PCC is not required to conduct business for this user.
  • the method further includes: after receiving the access request, the AAA obtains the operator policy information.
  • the carrier policy information is policy information defined by the operator for whether the user access uses the PCC. If the AAA determines that the PCC is supported according to one of the foregoing information, if the information indicates that the PCC is supported, the AAA decision is to implement the PCC for the user access, and if the information indicates that the PCC is not supported, The AAA decision is that the user access does not use the PCC; when the AAA makes a decision according to two or more of the information, if the two or more informations all only support the PCC, the AAA decision is The user accesses the implementation of the PCC.
  • the AAA decides that the user access does not use the PCC.
  • the above method can be applied to a CDMA-type HRPD network or an eHRPD network.
  • the gateway may be: PDSN; PDSN and HA; or, PDSN and LMA.
  • the access gateway may be: an HSGW; or, an HSGW and a P-GW.
  • the AAA is based on the PCC support capability of the PDSN that is responsible for the access of the MS, and whether the PCC is used in the business process after the decision user accesses the network.
  • the process of this embodiment is as follows: Figure 401.
  • the user requests access to the network.
  • the PPP session negotiation is required between the MS and the PDSN.
  • the primary service connection is established between the MS and the PDSN.
  • Step 402 Perform an LCP negotiation between the MS and the PDSN to negotiate an authentication mode.
  • the MS initiates an authentication request to the network according to the authentication mode negotiated in the LCP phase.
  • Step 404. The PDSN receives the authentication request. After the authentication request from the MS, the Access Request message is sent to the AAA, and the AAA is requested to authenticate the user access, and the PDSN reports the capability information of the PCC to the AAA.
  • AAA authenticates the user access. And performing the PCC for the user access according to the PCC support capability decision of the PDSN; Step 406.
  • the AAA sends an Access Accept message to the PDSN, including whether to implement the PCC information, notifying the PDSN to access the PCC for the user, and The corresponding subscription information is sent to the PDSN.
  • the PDSN returns an authentication response to the MS. Complete an authentication process for user access between the MS, the PDSN, and the AAA; Step 408.
  • the PDSN sends the user subscription information to the RAN.
  • Step 409. The IPCP negotiation is completed between the MS and the PDSN, and the network allocates an IP address to the MS.
  • the MS uses SIP access, and after the MS successfully accesses the network, the PDSN performs the PCEF function according to the AAA authentication. After the MS conducts business, the network uses the network resources for the PC to perform PCC.
  • Embodiment 2 This embodiment provides the AAA according to the PCC support capability of the PDSN responsible for UE access, and the user subscription information. After the decision user accesses the network, whether to use the PCC for control during the business process.
  • the process is as follows: Step 501: The user requests access to the network, and the PPP session negotiation is required between the MS and the PDSN, and a primary service connection is established between the MS and the PDSN for transmitting signaling messages. Step 502.
  • the LCP negotiation is performed between the MS and the PDSN to negotiate the authentication mode.
  • the MS initiates an authentication request to the network according to the authentication mode negotiated in the LCP phase.
  • the PDSN receives the authentication request from the MS. After the authentication request, send Access to AAA
  • the request message requests the AAA to authenticate the user access, and the PDSN reports the capability of the PCC to the AAA.
  • the network side does not need to be responsible for the user access.
  • the PCC support capability information of the incoming gateway determines whether the user access uses the PCC.
  • the PDSN After receiving the authentication request from the MS, the PDSN sends an Access Request message to the AAA, requesting the AAA to authenticate the user access, without supporting itself.
  • the capabilities of the PCC are reported to AAA. Step 505.
  • the AAA obtains the subscription information corresponding to the user from the user database. (If the user subscription information is stored on the AAA, the AAA may obtain the user subscription information by retrieving the stored information.
  • the AAA performs authentication, and according to one or both of the user subscription information and the PCC support capability information reported by the PDSN, whether the user access decision uses the PCC;
  • the user subscription information defines whether the user accesses the PCC information. If the signing information indicates no need To perform PCC on the user access, or the PDSN indicates that the PCC capability is not supported, the AAA sends an indication that the user access does not use the PCC. If the subscription information indicates that the user access is PCC, and the PDSN indicates that the PCC capability is supported, the AAA The issuing instruction requires the PDSN to perform PCC on user access.
  • the AAA is configured with the operator policy information.
  • the network side needs to determine whether the user access uses the PCC according to the operator policy information, and the AAA receives the PDSN. After the Access Request message is sent, the PCC can also be used to determine whether the user access is implemented by using the operator policy information.
  • Step 507. The AAA sends an Access Accept message to the PDSN, and notifies the PDSN to authorize the user, and sends the corresponding subscription information to the PDSN. The PDSN is also notified to implement the PCC for the user access. Step 508. The PDSN returns to the MS. The authentication response completes the authentication process for the user access between the MS, the PDSN, and the AAA. Step 509. The PDSN sends the user subscription information to the RAN. Step 510.
  • the MS initiates an IPCP configuration request to the PDSN, requesting to allocate an IP address to the user.
  • Step 511 The PDSN initiates a PMIP registration request to the HA. Step 512.
  • the HA sends an Access Request message to the AAA to initiate an access authentication request, where the request carries the capability of the HA to support the PCC.
  • AAA performs authentication on the HA. And returning an Access Accept message to the HA, where, if the HA supports the PCC capability, the HA is simultaneously notified to implement the PCC for the user access;
  • the HA returns a PMIP registration response to the PDSN;
  • the PDSN returns an IPCP configuration response to the MS.
  • the message completes the IPCP negotiation.
  • the network assigns an IP address to the MS.
  • the MS successfully accesses the network.
  • the AAA authentication the PDSN performs BBERF and the HA performs PCEF.
  • the network uses the network resources for the PC to perform PCC.
  • Step 516 the AAA determines that the HA does not support the PCC capability according to the information reported by the HA, and the AAA needs to send a Change of Authorization (COA) to the PDSN. Message, informing the PDSN to cancel the execution of the BBERF;
  • COA Change of Authorization
  • the PDSN returns a COA Acknowledgement (ACK).
  • the AAA may be based on one or more of the PCC support capability information, the subscription information of the user, and the operator policy information of the gateway responsible for accessing the user. Whether the user access decision uses the PCC, for example, it may be based only on the PCC support capability information of the gateway responsible for accessing the user, or only according to the subscription information of the user, or only based on the operator policy information, or may be based on Any two or all of the above three kinds of information are used for decision making.
  • Embodiment 3 shows that in the eHRPD network, the AAA performs user subscription information in the Home Subscriber Server (HSS), the PCC support capability of the HSGW and the P-GW, and whether the decision user access network uses the PCC. control.
  • HSS Home Subscriber Server
  • the process is specifically described as follows: Steps 601 - 604 are the same as the first embodiment; Step 605.
  • the AAA receives the authentication for the user access, the AAA obtains the subscription information of the corresponding user from the HSS; After the authentication is passed, the AAA returns an authentication response to the HSGW, and the user subscription information is sent to the HSGW. Step 607.
  • the HSGW returns an authentication result to the MS. Step 608.
  • the HSGW sends the user subscription information to the eRAN.
  • the MS initiates a Vendor Specific Network Control Protocol (VSNCP) configuration request to the HSGW; Step 610.
  • VSNCP Vendor Specific Network Control Protocol
  • the HSGW initiates a PMIP registration request to the P-GW; Step 611.
  • the P-GW sends an Access Request message to the AAA to initiate The authentication request is reported to the AAA by the P-GW to support the PCC.
  • the AAA combines the user subscription information with the PCC reported by the HSGW and the P-GW. Supporting the capability information, the decision is whether the user accesses the PCC; Step 613.
  • the AAA returns the authentication result to the P-GW through the Access Accept message; Step 614.
  • the P-GW performs the PMIP registration, and returns the PMIP registration response to the HSGW; Step 615. Returning the VSNCP configuration response to the MS; Step 616.
  • the AAA authorization uses the PCC for the user access
  • the AAA sends a COA message to the HSGW to notify the HSGW to perform the BBERF.
  • the AAA is in the user.
  • the authentication response is returned to the HSGW (step 606)
  • the returned Access Accept message does not include whether to implement the notification content of the PCC, but the COA message in the step 616 is used to notify the HSGW whether to perform the BBERF.
  • the HSGW returns a COA ACK to the AAA.
  • the embodiment of the present invention further provides a system for determining whether a user access network determines whether to use a policy and a charging control mechanism, where the system includes an AAA, and the AAA includes an access authentication module, and the access The authentication module is configured to: when the user requests to access the network, authenticate the user, and use the PCC according to at least one or any combination of the following information: the user is responsible for accessing the user.
  • the PCC support capability information of the gateway, the subscription information of the user, and the operator policy information.
  • the system further includes a gateway, the gateway includes a PCC capability upper module, and the AAA further includes an information acquisition module connected to the access authentication module, where: the PCC capability reporting module is configured to: the user requests access And sending an access request to the access authentication module, and the PCC support capability information of the gateway is included in the access request and reported to the information acquiring module; or, according to the information acquiring module
  • the request is to report the PCC support capability information of the gateway to the information acquisition module;
  • the information acquisition module is configured to: according to the received access request, if the access request includes the PCC of the gateway Supporting capability information, obtaining the gateway from the access request The PCC support capability; if the access request does not include the PCC support capability information of the gateway, requesting the gateway to report its PCC support capability.
  • the information obtaining module is further configured to: obtain subscription information or operator policy information of the user;
  • the access authentication module is configured to: according to the gateway acquired by the information acquiring module
  • One or more of the PCC support capability information, the subscription information of the user, and the operator policy information is whether the PCC is used by the user access decision.
  • the embodiment also provides an authentication and authorization accounting (AAA) server, where the AAA server includes an access authentication module, where: the access authentication module is configured to: when the user requests to access the network, The user performs authentication, and according to at least one or any combination of the following information, whether the user access decision uses the policy and charging control (PCC): the PCC support capability information of the gateway responsible for the user access, the user Signing information, operator strategy information.
  • the AAA server further includes an information acquiring module connected to the access authentication module, where:
  • the access authentication module is further configured to: when receiving a user requesting to access the network, the access request sent by the gateway accessed by the user to the access authentication module, where the access request includes the gateway
  • the PCC supports the capability information, and reports the access request to the information acquisition module; or, according to the request of the information acquisition module, the PCC support capability information of the gateway is received and reported to the information acquisition module;
  • the information obtaining module is configured to: obtain the PCC support capability of the gateway from the access request, if the access request includes the PCC support capability information of the gateway, according to the received access request And if the access request does not include the PCC support capability information of the gateway, requesting, by the gateway, the PCC support capability of the gateway to be reported. among them,
  • the information obtaining module is further configured to: obtain the subscription information or the operator policy of the user.
  • the access authentication module is configured to be obtained according to the gateway acquired by the information acquiring module
  • One or more of the PCC support capability information, the subscription information of the user, and the operator policy information is whether the PCC is used by the user access decision.
  • the present invention considers the difference in network capabilities or the difference in subscription information, so that when the user accesses the network, the network side can decide whether to use the PCC mechanism to access the network according to the user subscription information and/or network capability.
  • the user performs PCC.
  • the PCC includes policy control and/or billing control.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention porte sur un procédé servant à déterminer d'adopter ou non un mécanisme de commande de politique et de facturation (PCC), le procédé comprenant les opérations suivantes : lorsqu'un utilisateur demande d'accéder à un réseau, un serveur d'authentification, d'autorisation et de comptabilité (AAA) détermine, pour l'accès de l'utilisateur, d'adopter ou non la PCC selon au moins une information ou des combinaisons aléatoires des informations qui suivent : une capacité de prise en charge PCC d'une passerelle chargée de l'accès de l'utilisateur, une information d'abonnement de l'utilisateur, et une information de politique d'opérateur. La présente invention porte également sur un système et un serveur AAA servant à déterminer d'adopter ou non le mécanisme PCC. Lorsque l'utilisateur accède au réseau, la présente invention permet au côté réseau de déterminer, selon les informations d'abonnement d'utilisateur et/ou une capacité du réseau, d'adopter ou non le mécanisme PCC pour appliquer la PCC pour l'utilisateur accédant au réseau.
PCT/CN2011/072226 2010-04-23 2011-03-28 Procédé et système servant à déterminer d'adopter ou non un mécanisme de commande de politique et de facturation Ceased WO2011131075A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010170896.XA CN102238509B (zh) 2010-04-23 2010-04-23 决策是否采用策略和计费控制机制的方法及系统
CN201010170896.X 2010-04-23

Publications (1)

Publication Number Publication Date
WO2011131075A1 true WO2011131075A1 (fr) 2011-10-27

Family

ID=44833694

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/072226 Ceased WO2011131075A1 (fr) 2010-04-23 2011-03-28 Procédé et système servant à déterminer d'adopter ou non un mécanisme de commande de politique et de facturation

Country Status (2)

Country Link
CN (1) CN102238509B (fr)
WO (1) WO2011131075A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2911445A1 (fr) * 2012-11-05 2015-08-26 Huawei Technologies Co., Ltd. Procédé et dispositif de réseau permettant une réception de paquet
CN104254071B (zh) * 2013-06-28 2017-12-15 中国电信股份有限公司 eHRPD网络中的PCC控制方法与系统
CN103686648A (zh) * 2013-12-17 2014-03-26 中国联合网络通信集团有限公司 一种策略计费控制规则信息的请求方法、装置及系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101047874A (zh) * 2006-03-31 2007-10-03 华为技术有限公司 移动通信网络中业务信息决策方法
CN101267319A (zh) * 2008-04-30 2008-09-17 中兴通讯股份有限公司 一种下发策略计费控制规则的方法
CN101420724A (zh) * 2008-11-20 2009-04-29 华为技术有限公司 信息传输方法、移动管理设备和网络系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU2006348737B2 (en) * 2006-09-26 2012-05-10 Telefonaktiebolaget Lm Ericsson (Publ) Policy control architecture comprising an indepent identity provider
CN101472259B (zh) * 2007-12-28 2010-12-08 华为技术有限公司 触发策略控制和计费功能的方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101047874A (zh) * 2006-03-31 2007-10-03 华为技术有限公司 移动通信网络中业务信息决策方法
CN101267319A (zh) * 2008-04-30 2008-09-17 中兴通讯股份有限公司 一种下发策略计费控制规则的方法
CN101420724A (zh) * 2008-11-20 2009-04-29 华为技术有限公司 信息传输方法、移动管理设备和网络系统

Also Published As

Publication number Publication date
CN102238509B (zh) 2016-09-28
CN102238509A (zh) 2011-11-09

Similar Documents

Publication Publication Date Title
JP4828608B2 (ja) 課金方法、課金システム、課金クライアントおよび課金処理手段
CN101267319B (zh) 一种下发策略计费控制规则的方法
KR101370268B1 (ko) 서비스 품질 파라미터의 협의 제어 방법 및 장치
CN101720112B (zh) 一种无线资源管理方法与装置
JP5421341B2 (ja) 加入者サービス品質プロファイルを構成する方法及び装置
WO2010081329A1 (fr) Procédé et système pour réguler des ressources de réseau pendant une procédure de migration de flux de services
CN103024824B (zh) 一种策略与计费规则的服务质量更新方法及系统
CN101931946A (zh) 演进的分组系统中的终端的多接入方法及系统
WO2011143939A1 (fr) Procédé, dispositif et système de réglage de bande passante maximale
WO2013064004A1 (fr) Procédé et système de mise à jour de la qualité de service
CN101778446A (zh) 演进分组系统中多接入控制方法与装置及多接入指示方法
WO2009046598A1 (fr) Procédé pour établir une porteuse dédiée pour un terminal utilisateur
WO2011044809A1 (fr) Procédé et système de mise en oeuvre d'un contrôle par politiques sur la base d'informations de localisation
WO2010078761A1 (fr) Procédé, appareil et système de détermination de la politique et de la facturation
CN101742471B (zh) 一种数据流与接入网连接绑定的方法
WO2011131075A1 (fr) Procédé et système servant à déterminer d'adopter ou non un mécanisme de commande de politique et de facturation
CN103391564B (zh) 策略规则设备的选择方法及装置
CN101959313B (zh) 一种策略与计费控制系统及方法
CN103392363A (zh) 一种ip流移动方法及pcrf、andsf
CN102791042A (zh) S9子会话建立方法、系统及pcrf
CN102369699B (zh) 本地路由授权的方法、装置和系统
CN101730151A (zh) 实现dhcp模式协商的方法、系统及接入服务网网关
CN102056144B (zh) 多接入的处理方法、家乡代理及用户设备
CN102281525B (zh) 用户接入控制方法、系统和装置
CN102036416B (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: 11771528

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11771528

Country of ref document: EP

Kind code of ref document: A1