WO2011131082A1 - 策略和计费控制的方法及系统 - Google Patents

策略和计费控制的方法及系统 Download PDF

Info

Publication number
WO2011131082A1
WO2011131082A1 PCT/CN2011/072362 CN2011072362W WO2011131082A1 WO 2011131082 A1 WO2011131082 A1 WO 2011131082A1 CN 2011072362 W CN2011072362 W CN 2011072362W WO 2011131082 A1 WO2011131082 A1 WO 2011131082A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
pdsn
pcrf
terminal device
address
Prior art date
Application number
PCT/CN2011/072362
Other languages
English (en)
French (fr)
Inventor
毕以峰
毛玉欣
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2011131082A1 publication Critical patent/WO2011131082A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1453—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network
    • H04L12/1457—Methods or systems for payment or settlement of the charges for data transmission involving significant interaction with the data transmission network using an account
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions

Definitions

  • the present invention relates to a Policy and Charging Control (PCC) technology, and more particularly to a method and system for policy and charging control in a code division multiple access system.
  • PCC Policy and Charging Control
  • FIG. 1 is a schematic diagram of a partial network reference model of a CDMA (Code Division Multiple Access) 2000 lx and HRPD (HRPD, High Rate Packet Data) PDS (packet data service), as shown in FIG.
  • the code division multiple access cdma2000 lx and high speed packet data HRPD network architecture defined by 3GPP2, 3rd Generation Partnership Project2, mainly by mobile station (MS, Mobile Station) / access terminal equipment (AT, Access Terminal) , or Terminal Equipment) / User Equipment (UE, User Access Equipment), Radio Access Network (RAN), Packet Data Serving Node (PDSN), Home Agent (HA, Home Agent) / Local Mobility Anchor (LMA), Remote Authentication Dial In User Service (AAA), Authentication Authorization Accounting (AAA), and other core network devices and supporting nodes.
  • MS Mobile Station
  • AT Access Terminal
  • RAN Radio Access Network
  • PDSN Packet Data Serving Node
  • HA Home Agent
  • LMA Local Mobility Anchor
  • AAA Remote Authentication Dial In
  • the MS/AT is connected to the RAN through a wireless interface.
  • the RAN includes a base station (BS, Base Station, ) and a packet control function (PCF), wherein the BS is mainly used to establish wireless coverage in the cell, and provides an air interface for the packet data service for the terminal device; the PCF is mainly used to control the wireless Network resources, forwarding messages between the wireless system and the PDSN packet control unit.
  • BS Base Station
  • PCF packet control function
  • the PDSN provides the terminal device with access to the Internet or application server or to the HA/LMA through the RAN. Its role is to establish and maintain a point-to-point protocol between the MS/AT and the PDSN. (PPP, Point to Point Protocol) session; accepts and performs authentication, authorization, and accounting of the MS/AT by the RADIUS/AAA server; routes packets from and to the packet data network or HA/LMA.
  • PGP Point to Point Protocol
  • the HA/LMA is responsible for allocating local addresses, forwarding upstream and downstream data packets, and tunnel encapsulation of data packets to the terminal device in the mobile IP scenario.
  • the mobile IP includes the client mobile IP version 4 or version 6 (CMIPv4/v6, Client Mobile). IP version 4/version 6, or MIPv4/v6, Mobile IP version 4 or version 6) and Proxy Mobile IP version 4 or version 6 (PMIPv4/v6, Proxy Mobile IPv4/v6).
  • AAA Authentication/4 Authorization/Accounting
  • RADIUS Remote Authentication Dial In User Service
  • the cdma2000 network can achieve reasonable allocation and control of resources through PCC technology. Because the terminal device can access through multiple access modes when accessing the cdma2000 system, it is different in IPv4/v6 (SIPv4/v6, Simple IPv4/v6), PMIPv4/v6, CMIPv4/v6, etc. In the access mode, the network-side related network elements such as PDSN and HA/LMA play different roles and functions in the PCC technology. In summary, when a user terminal device accesses through SIPv4/v6, the PDSN performs the function of a Policy Control Enforcement Function (PCEF), and there is no HA/LMA in the network, no bearer binding, and a time-based entity.
  • PCEF Policy Control Enforcement Function
  • FIG. 2 is a block diagram of the terminal device MS/AT accessing and establishing a PCC session through CMIPv6. As shown in Figure 2, when the user terminal device accesses through PMIPv4/v6 or CMIPv4/v6, the PDSN performs the BBERF function and passes the PCRF. Gxa establishes a gateway control session (GW control session) and transmits relevant policy information. The HA/LMA performs the function of PCEF, and establishes an IP connection access network (IP-CAN, IP-Connectivity Access Network) session with the PCRF through the Gx port.
  • IP-CAN IP-Connectivity Access Network
  • the PCRF associates the gateway control session and the IP-CAN session of the same IP connection (the IP connection concept is explained below) belonging to the same terminal, and formulates the PCC policy together and issues the same. Go to PDSN and HA/LMA to complete resource and charging control for the same IP connection to the same terminal.
  • the so-called PCRF associates the two sessions.
  • the existing mechanism is: The PCRF receives the first session request (such as the gateway control session request), and the PCRF accepts, then the session is established, if the PCRF receives another session. To establish a request (such as an IP-CAN session request), the PCRF compares the parameters carried by the IP-CAN session request with the context parameters of the established gateway control session. If the two sessions are found to belong to the same terminal, the same An IP-connected session associates the two talkbacks together.
  • the terminal can establish different IP connection processes.
  • the IP connection refers to that the terminal acquires an IP address assigned/configured by the network side, and uses the address to connect to the network and access an association of the network side resources.
  • a terminal can have multiple IP connections at the same time. For example, a terminal can establish a connection between SIPv6 and CMIPv6 at the same time.
  • each network element plays a different role and performs functions when using PCC technology. The detailed steps of the two IP connection establishment processes of SIPv6 and CMIPv6 are given below, and potential problems are raised.
  • FIG. 3 is a flow chart of the terminal device MS/AT accessing and establishing a PCC session through the SIPv6. As shown in Figure 3, the process of the MS/AT accessing the SIPv6 includes the following steps:
  • Step 1 The primary service connection is established.
  • Step 2 The Link Control Protocol (LPP) of the PPP session negotiates and selects an authentication mode.
  • LTP Link Control Protocol
  • Step 3 Complete the user's access authentication and authorization by using the authentication mode selected in step 2.
  • the authentication signaling related to the interworking between the MS/AT and the PDSN, the PDSN and the AAA also pass the access request. And the operation of the access response to perform authentication. After the authentication/authorization is successful, the related QoS (Quality of Service) information will be sent from the AAA to the PDSN.
  • QoS Quality of Service
  • Step 4 The PDSN sends the signed QoS parameters to the RAN.
  • Step 5 The MS/AT and the PDSN perform an IP version 6 control protocol (IPv6CP, IP Version 6 Control Protocol) negotiation procedure.
  • IPv6CP IP Version 6 Control Protocol
  • the PDSN After the negotiation process, the PDSN also sends the local link (HL, Home Link) prefix to the MS/AT.
  • the MS/AT generates a unicast address based on the prefix. This process is not shown in the figure.
  • the PDSN acts as a PCEF to initiate an IP-CAN session establishment procedure for the MS/AT to the PCRF.
  • the PDSN/PCEF carries the IP-Connected Access Network (IP-CAN, IP-Connectivity Access Network) type, the terminal device identifier, the packet data network (PDN, Packet Data Network) identifier, and the terminal device IP address in the message. This address is information such as the PDSN assigning to the terminal.
  • IP-CAN IP-Connected Access Network
  • PDN Packet Data Network
  • the interface between the PDSN and the PCRF uses the Gx port.
  • This step does not have to occur after the IPv6CP negotiation is complete. This procedure can be initiated as long as the PDSN receives the IPv6CP configuration request.
  • Step 7 The PCRF sends an IP-CAN session setup response to the PDSN/PCEF.
  • the PCRF provides PCC rules and event options to the PCEF via an IP-CAN session.
  • FIG. 4 is a flow chart of the terminal device MS/AT accessing and establishing a PCC session through CMIPv6, as shown in Figure 4.
  • the MS/AT through the CMIPv6 access process specifically includes the following steps:
  • Step 1 The primary service connection is established.
  • Step 2 The LCP negotiation of the PPP session and the authentication mode is selected.
  • Step 3 Perform the access authentication and authorization of the user by using the authentication mode selected in step 2.
  • the authentication signaling related to the interworking of the MS/AT and the PDSN, the PDSN and the AAA also perform the related operations of the authentication through the access request and the access response. After the authentication/authorization is successful, the relevant contracted QoS information will be Sent from the AAA to the PDSN.
  • Step 4 The PDSN sends the signed QoS parameters to the RAN.
  • Step 5 The MS/AT and the PDSN perform an IPv6CP negotiation step.
  • the PDSN also sends the local link (HL, Home Link) prefix to the MS/AT.
  • the MS/AT generates a unicast address based on the prefix. This process is not shown in the figure.
  • the terminal also obtains bootstrap information from the PDSN through the DHCP step, which is not shown in the flowchart.
  • the PDSN acts as a BBERF to the PCRF to control the session establishment procedure for the MS/AT originating gateway (GW, Gateway).
  • the PDSN/BBERF carries information such as the session type, the terminal device identifier, the PDN identifier, and the IP address of the terminal device in the message.
  • the interface between the PDSN and the PCRF uses the Gxa interface.
  • This step does not have to occur after the IPv6CP negotiation is complete. This procedure can be initiated as long as the PDSN receives the IPv6CP configuration request.
  • Step 7 The PCRF sends an IP-CAN session setup response to the PDSN.
  • Step 8 The MS/AT sends a CMIPv6 Binding Update Request message to the selected HA/LMA to request binding to the HA/LMA.
  • Step 9 The HA/LMA and the AAA exchange authentication signaling, and complete authentication and authorization for the user to access through CMIPv6.
  • Step 10 After the HA/LMA receives the binding request and is authorized by the AAA, the HA/LMA acts as a PCEF to initiate an IP-CAN session establishment request to the PCRF.
  • Step 11 The PCRF sends an IP-CAN session establishment response to the HA/LMA/PCEF, completes the establishment of the IP-CAN session, and downloads the relevant PCC policy to the HA/LMA/PCEF.
  • Step 12 The HA/LMA sends a CMIPv6 binding response message to the MS/AT, and the MS/AT completes the access through the CMIPv6 mode.
  • the role of the PDSN is BBERF, and The PCRF establishes a GW control session through the Gxa interface. Because the MS/AT is based on the access mode, it can be determined until the subsequent MS/AT is bound to the HA/LMA. However, the PDSN needs to be connected according to the MS/AT in advance. The way to select the corresponding function and role, because the session established by the PDSN and the PCRF, the interface used is different. In the MS/AT access mode shown in Figure 2 and Figure 4 above, it is obvious that the role of the PDSN cannot be determined in advance, and the type of interface between the PDSN and the PCRF cannot be determined. This will undoubtedly affect the accurate and timely access of the MS/AT. The internet. Summary of the invention
  • the main object of the present invention is to provide a method and system for policy and charging control, and the technical solution of the present invention is implemented as follows:
  • a method for policy and charging control comprising:
  • the terminal device accesses the cdma system through MIPv6, the PDSN and the PCRF respectively establish a gateway control session and a first IP-CAN session;
  • HA establishes a second IP-CAN session with the PCRF
  • the PCRF associates the gateway control session with the second IP-CAN session.
  • the method further includes:
  • the PCRF does not associate the gateway control session with the first IP-CAN session when one of the following conditions is met:
  • the gateway control session and the first IP-CAN session belong to the same terminal device and belong to the same PDSN;
  • the home address of the gateway control session is different from the care-of address of the first IP-CAN session.
  • the PDSN establishes the first IP-CAN session with the PCRF after the terminal device negotiates the point-to-point protocol PPP session with the PDSN/after the terminal device requests the bootstrap information.
  • the PDSN when the terminal device negotiates a PPP session with the PDSN, the PDSN establishes the gateway control session with the PCRF;
  • the HA After the HA receives the binding update message and is authorized by the authentication and authorization accounting server AAA, the HA establishes the second IP-CAN session with the PCRF;
  • the PCRF associates the gateway control session with the second IP-CAN session based on the terminal device identity, and/or the packet data network identity, and/or the IP address.
  • said first IP-CAN session provides a policy for a terminal device to communicate with a packet data network via a PDSN;
  • the second IP-CAN session and the gateway control session provide policies for the terminal device to communicate with the packet data network via the HA.
  • the method further includes:
  • the PDSN When receiving the resource reservation request, the PDSN determines whether to request the PCC policy through the gateway control session or the first IP-CAN session according to the address of the terminal device.
  • the method further includes:
  • the PDSN determines that the address of the terminal device is an address allocated by the PDSN to the terminal device, requesting, by the first IP-CAN session, the PCC policy to the PCRF;
  • the PDC When the PDSN determines that the address of the terminal device is not the address allocated by the PDSN to the terminal device, the PDC requests the PCC policy from the PCRF through the gateway control session.
  • the method further includes:
  • the PDSN After the PDSN requests the PCC policy from the PCRF by using the first IP-CAN session, the PDSN initiates a request to delete the gateway control session to the PCRF;
  • a system for policy and charging control comprising a terminal device, a PDSN, a PCRF, and an HA;
  • a PDSN configured to establish a gateway control session and a first IP-CAN session with the PCRF
  • HA configured to establish a second IP-CAN session with the PCRF
  • a PCRF configured to establish a gateway control session and a first IP-CAN session with the PDSN, and establish a second IP-CAN session with the HA;
  • the PCRF is further configured to associate the gateway control session with the second IP-CAN session.
  • the PCRF further does not associate the gateway control session with the first IP-CAN session when one of the following conditions is met:
  • the gateway control session and the first IP-CAN session belong to the same terminal device and belong to the same PDSN;
  • the home address of the gateway control session is different from the care-of address of the first IP-CAN session.
  • the PDSN further establishes the first IP-CAN session with the PCRF after the terminal device negotiates a point-to-point protocol PPP session with the PDSN/after the terminal device requests the bootstrap information.
  • the PDSN further establishes the gateway control session with the PCRF when the terminal device negotiates a PPP session with the PDSN.
  • the HA further establishes the second IP-CAN session with the PCRF after receiving the binding update message and being authorized by the AAA server;
  • the PCRF further associates the gateway control session with the second IP-CAN session based on the terminal device identity, and/or the packet data network identity, and/or the IP address.
  • said first IP-CAN session provides a policy for a terminal device to communicate with a packet data network via a PDSN;
  • the second IP-CAN session and the gateway control session are for the terminal device via the HA and the packet data network. Provide a strategy when communicating.
  • the PDSN and the PCRF respectively establish a gateway control session and the first IP connection access network IP-CAN session; the HA establishes a second IP-CAN session with the PCRF; The gateway control session and the second IP-CAN session.
  • the invention can determine the interface type between the PDSN and the PCRF according to the session type established by the terminal device, so as to ensure that the terminal device accesses the network accurately and timely.
  • FIG. 1 is a schematic diagram of a CDMA2000 lx and HRPD PDS part network reference model
  • FIG. 2 is an architecture diagram of a terminal device MS/AT accessing and establishing a PCC session through CMIPv6
  • FIG. 3 is a terminal device MS/AT accessing and establishing a PCC session through SIPv6
  • Figure 4 is a flow chart of the terminal device MS/AT accessing and establishing a PCC session through CMIPv6
  • Figure 5 is a flowchart of Embodiment 1 of the method for policy and charging control according to the present invention
  • Embodiment 6 is a flowchart of Embodiment 2 of a method for policy and charging control according to the present invention.
  • Embodiment 7 is a flowchart of Embodiment 3 of a method for policy and charging control according to the present invention.
  • FIG. 8 is a flowchart of Embodiment 4 of a method for policy and charging control according to the present invention. detailed description
  • the basic idea of the present invention is: When the terminal device accesses the cdma system through MIPv6, the PDSN and the PCRF respectively establish a gateway control session and the first IP connection access network IP-CAN session; and the HA establishes a second IP-CAN with the PCRF. Session; the PCRF associates the gateway control session with the second IP-CAN session.
  • the terminal uses the IP address allocated by the PDSN for the terminal, and the first IP-CAN session provides the PCC policy for the communication data; if the terminal passes the HA and the external packet data Network communication, at this time, the terminal uses the address assigned by the HA to the terminal.
  • the address is called HoA (home address;), and the gateway controls the session. After being associated with the second IP-CAN session, a PCC policy is provided for this communication data.
  • the PDSN after the PDSN receives the IPv6CP configuration request sent by the terminal device MS/AT, or after the terminal device obtains the bootstrap information, the PDSN establishes a GW control session and the IP-CAN session-1 with the PCRF; After receiving the session establishment request sent by the PDSN, if it is determined that the two sessions are sessions established by the same terminal device with the same PDSN or according to carrying the associated address (the home address of the gateway control session and the IP-CAN session-1) If the care-of address is different, the PCRF processes the two sessions independently and does not associate.
  • the PCRF receives the IP-CAN Session-2 Setup Request from the HA/LMA for the terminal device, the PCRF associates the GW Control Session requested by the PDSN with the IP-CAN Session-2 requested by the HA/LMA, optionally, PCRF IP-CAN Session-1 can be released. Subsequent operations can be performed in accordance with the prior art.
  • FIG. 5 is a flowchart of Embodiment 1 of a method for policy and charging control according to the present invention. As shown in FIG. 5, the method for the example policy and charging control includes the following steps:
  • Step 1 The primary service connection is established.
  • Step 2 The LCP negotiation of the PPP session and the authentication mode is selected.
  • Step 3 Complete the user's access authentication and authorization by using the authentication mode selected in step 2.
  • the authentication signaling related to the interworking between the MS/AT and the PDSN, the PDSN and the AAA also perform the related operations of the authentication through the access request and the access response. After the authentication/authorization is successful, the relevant contracted QoS information will be sent from the AAA to the PDSN.
  • Step 4 The PDSN sends the signed QoS parameters to the RAN.
  • Step 5 The MS/AT and the PDSN perform an IPv6CP negotiation step.
  • the PDSN also sends the local link prefix to the MS/AT.
  • the MS/AT generates a unicast address based on the prefix. This process is not shown in the figure.
  • the terminal must also pass to the PDSN.
  • the bootstrap information is obtained through the DHCP step, which is not shown in the flowchart.
  • Step 6 The PDSN initiates a PCC session to the PCRF as a BBERF and a PCEF, specifically: 6a, the PDSN locates the role as a PCEF, initiates an IP-CAN session-1 establishment with the PCRF, and carries the IP address assigned by the PDSN to the terminal, and the address is filled in. IP-CAN session HoA cell,
  • CoA cell information in the IP-CAN session is vacant or filled in all zeros
  • the PDSN locates the role as BBERF, and the PDSN initiates the establishment of the GW session with the PCRF, and carries the IP address assigned by the PDSN to the terminal, and the address is filled in to the gateway control session.
  • the establishment of the two sessions does not necessarily occur after the IPv6CP negotiation/bootstrap information acquisition is completed. As long as the PDSN receives the IPv6CP configuration request, the step can be initiated, and the two sessions can be established in parallel.
  • Step 7 the PCRF receives the PCC session establishment request of the PDSN, establishes an IP-CAN session-1 and a GW control session with the PDSN, and determines that the two sessions are sessions from the same PDSN, and is the same MS/AT. When the service is serviced, the two sessions are processed separately, that is, they are not associated.
  • Step 8 The MS/AT sends a CMIPv6 Binding Update Request message to the selected HA/LMA to request binding to the HA/LMA.
  • Step 9 The HA/LMA and the AAA exchange authentication signaling to complete the authentication and authorization of the terminal device through the CMIPv6 access.
  • Step 10 After the HA/LMA receives the binding update and the authorization succeeds, the HA/LMA acts as the PCEF to initiate an IP-CAN session-2 establishment request to the PCRF, and the PCRF sends an IP-CAN session-2 establishment response to the HA/LMA/PCEF. Complete the establishment of IP-CAN Session-2 and download the relevant PCC policy to HA/LMA/PCEF.
  • Step 11 after the PCRF establishes an IP-CAN session-2 with the HA/LMA, the PCRF associates the IP-CAN session-2 with the "GW established with the PDSN" according to the user identifier, the PDN identifier, the IP address, and the like.
  • the control session is "associated.
  • the PCRF releases the "IP-CAN Session -1" established with the PDSN.
  • the PDSN role is BBERF, which establishes a corresponding IP-CAN session with the PCRF through the Gxa interface.
  • Step 12 The HA/LMA sends a CMIPv6 binding response message to the MS/AT, and the MS/AT completes the access through the CMIPv6 mode.
  • Step 13 Following step 11, the PCRF initiates an "IP-CAN session - ⁇ release operation, releasing the IP-CAN session -1.
  • step 10 occurs before 6a, 6b, that is, IP-CAN session-2 is established first, IP-CAN-1 session and GW control session are established, and of course other order. In other words, the establishment of these three sessions is not strictly sequential. However, this does not affect the execution of the scheme.
  • the PCRF retrieves the existing session. If the association condition is met, the association is performed. If the association condition is not met, it is not related.
  • the PDSN when the PDSN receives the IPv6CP configuration request sent by the MS/AT, the PDSN simultaneously establishes a GW control session and an IP-CAN session -1 with the PCRF. After the PCRF receives the IP-CAN session-1 modification request sent by the PDSN, the PCRF determines that the access mode of the terminal device is SIPv6. Optionally, the PCRF releases the GW control session established with the PDSN, and subsequent operations are performed according to the prior art. Execute.
  • FIG. 6 is a flowchart of Embodiment 2 of a method for policy and charging control according to the present invention. As shown in FIG. 6, the method for the example policy and charging control includes the following steps:
  • Step 1 The primary service connection is established.
  • Step 2 The LCP negotiation of the PPP session and the authentication mode is selected.
  • Step 3 Perform the access authentication and authorization of the user by using the authentication mode selected in step 2.
  • the authentication signaling related to the interworking between the MS/AT and the PDSN, the PDSN and the AAA are also accessed and accessed through the access request.
  • the response is performed in response to the relevant operation of the authentication.
  • the relevant contracted QoS information will be sent from the AAA to the PDSN.
  • Step 4 The PDSN sends the signed QoS parameters to the RAN.
  • Step 5 The MS/AT and the PDSN perform an IPv6CP negotiation step.
  • the PDSN also sends the local link prefix to the MS/AT.
  • the MS/AT generates a unicast address based on the prefix. This process is not shown in the figure.
  • the terminal also obtains bootstrapping information from the PDSN through the DHCP procedure, which is not shown in the flowchart.
  • Step 6 The PDSN simultaneously initiates a PCC session to the PCRF as a BBERF and a PCEF, which is:
  • the PDSN locates the role as PCEF, initiates an IP-CAN session-1 establishment with the PCRF; and carries the IP address assigned by the PDSN to the terminal, the address is filled in the IP-CAN session HoA cell, and the CoA letter in the IP-CAN session Meta information vacancies or fill in all zeros;
  • the PDSN locates the role as BBERF, and the PDSN initiates a GW session with the PCRF. And carrying the IP address assigned by the PDSN to the terminal, and the address is filled in the HoA cell of the gateway control session.
  • the establishment of the two sessions does not necessarily occur after the IPv6CP negotiation/bootstrap information acquisition is completed. As long as the PDSN receives the IPv6CP configuration request, the step can be initiated, and the two sessions can be established in parallel.
  • the PCRF receives the PCC session establishment request of the PDSN, and establishes an IP-CAN session-1 and a GW control session with the PDSN respectively.
  • the two sessions are handled separately, that is, they are not associated.
  • Step 7 The MS/AT and the RAN/PCF perform the HRPD QoS establishment procedure.
  • Step 8 corresponding to step 7, if there is Link Flow new/modified, the A10 connection needs to be established/modified between the RAN/PCF and the PDSN, and the corresponding requested QoS list is sent to the PDSN.
  • Step 9 The MS/AT sends a Resource Reservation Protocol (RSVP) reservation (Resv, Reserve) message to the PDSN, and the Traffic Flow Template (TFT) is sent to the PDSN through the signaling.
  • RSVP Resource Reservation Protocol
  • TFT Traffic Flow Template
  • Step 10 After receiving the RSVP Resv message sent by the MS/AT, the PDSN parses the terminal IP address carried in the message, where the IP address can be separately carried by the RSVP message to the PDSN, or can be parsed from the carried TFT. (current technology).
  • the PDSN determines that the address is the address allocated by the PDSN to the MS/AT, and the PDSN initiates an IP-CAN session-1 modification request to the PCRF, requests the corresponding PCC policy, and the PCRF sends the corresponding policy to the PDSN through the response message.
  • Step 11 After receiving the IP-CAN session modification request sent by the PDSN, the PCRF determines that the current access mode of the terminal device is SIPv6, retains the IP-CAN session -1, and deletes the GW session. At this time, the PDSN role is PCEF, which establishes a corresponding IP-CAN session between the Gx interface and the PCRF.
  • Step 12 The PDSN sends an RSVP Resvconf message to the MS/AT.
  • Step 13 MS/AT, RAN/PCF, and PDSN install corresponding QoS and allocate resources.
  • Step 14 Following step 11, the PCRF initiates a GW control session termination operation request to the PDSN to release the GW control session. This step 14 can also be triggered by step 9, and the PDSN initiates a "GW Control Session" release operation, depending on the specific communication flow implementation.
  • the PDSN after receiving the IPv6CP negotiation request sent by the terminal device, the PDSN establishes a GW control session and an IP-CAN session-1 with the PCRF, and the PCRF determines that the two sessions are established for the same terminal device.
  • the PDSN session is different depending on the carrying association address (the home address of the gateway control session and the care-of address in the IP-CAN session-1), and the PCRF processes the two sessions independently and does not associate them.
  • the PCRF If the PCRF receives the same IP connection of the terminal device sent by the HA/LMA The IP-CAN Session-2 setup request, the PCRF associates the GW Control Session requested by the PDSN with the IP-CAN Session-2 of the HA/LMA Request and retains the IP-CAN Session-1 established with the PDSN.
  • the PDSN parses the RSVP Resv message sent from the MS/AT, and resolves that the terminal IP address carried by the message is an address allocated by the PDSN for the MS/AT, the PDSN initiates an IP-CAN session-1 modification request to the PCRF, requesting corresponding PCC strategy.
  • the PCRF receives the modification request of the IP-CAN session-1 sent by the PDSN, and the PCRF formulates a PCC policy for the terminal device, and if there is an IP-CAN session-2 requested by the HA/LMA, the PCRF retains it, if If it does not exist, it will not be processed.
  • the PDSN parses the RSVP Resv message sent from the MS/AT, and resolves that the terminal IP address (HoA) carried by the message is not the address (CoA) allocated by the PDSN for the MS/AT, the PDSN initiates GW control and QoS policy request to the PCRF.
  • the PCRF then formulates a PCC policy for the terminal device, and sends a policy and charging control PCC policy to the PDSN and the HA/LMA respectively through the gateway control session and the IP-CAN session associated therewith.
  • the GW Control and QoS Policy Request message can only be sent using the session after the GW Control Session and the HA-LMA Requested IP-CAN Session -2 Association.
  • FIG. 7 is a flowchart of Embodiment 3 of a method for policy and charging control according to the present invention. As shown in FIG. 7, the method for the example policy and charging control includes the following steps:
  • Step 1 The primary service connection is established.
  • Step 2 The LCP negotiation of the PPP session and the authentication mode is selected.
  • Step 3 Complete the user's access authentication and authorization by using the authentication mode selected in step 2.
  • the authentication signaling related to the interworking between the MS/AT and the PDSN, the PDSN and the AAA also perform the related operations of the authentication through the access request and the access response. After the authentication/authorization is successful, the relevant contracted QoS information will be sent from the AAA to the PDSN.
  • Step 4 The PDSN sends the signed QoS parameters to the RAN.
  • Step 5 The MS/AT and the PDSN perform an IPv6CP negotiation step. During the negotiation, the PDSN also sends the local link prefix to the MS/AT. The MS/AT generates a unicast address based on the prefix. This process is not shown in the figure. In addition, the terminal also obtains bootstrap information from the PDSN through the DHCP step, which is not shown in the flowchart.
  • Step 6 The PDSN simultaneously initiates a PCC session to the PCRF as a BBERF and a PCEF, which is:
  • the PDSN locates the role as PCEF, initiates an IP-CAN session-1 establishment with the PCRF; and carries the IP address assigned by the PDSN to the terminal, the address is filled in the IP-CAN session HoA cell, and the CoA letter in the IP-CAN session Meta information vacancies or fill in all zeros;
  • the PDSN locates the role as BBERF, and the PDSN initiates the establishment of the GW session with the PCRF, and carries the IP address assigned by the PDSN to the terminal, and the address is filled in the HoA cell of the gateway control session.
  • the establishment of the two sessions does not necessarily occur after the IPv6CP negotiation is completed. As long as the PDSN receives the IPv6CP configuration request, the step can be initiated, and the two sessions can be established in parallel.
  • Step 7 the PCRF receives the PCC session establishment request of the PDSN, establishes an IP-CAN session-1 and a GW control session with the PDSN, and determines that the two sessions are sessions from the same PDSN, and is the same MS/AT. When the service is serviced, the two sessions are processed separately, that is, they are not associated.
  • Step 8 The MS/AT sends a CMIPv6 Binding Update Request message to the selected HA/LMA to request binding to the HA/LMA.
  • Step 9 The HA/LMA and the AAA exchange authentication signaling, and complete authentication and authorization for the user to access through CMIPv6.
  • Step 10 After the HA/LMA receives the binding update and authorization successfully, the HA/LMA acts as the PCEF to initiate an IP-CAN session-2 setup request message to the PCRF, and the PCRF sends an IP-CAN session-2 setup response to the HA/LMA/PCEF. , complete the establishment of IP-CAN session-2, and download the relevant PCC policy to HA/LMA/PCEF.
  • the CoA cell fills in the PDSN. For the IP address assigned to the terminal, the HoA cell is filled with the address assigned by the AAA/HA to the terminal.
  • Step 11 After the PCRF establishes an IP-CAN session-2 with the HA/LMA, the PCRF associates the IP-CAN session-2 with the "GW control session established with the PDSN" according to the user identifier, the PDN identifier, the IP address, and the like. The PCRF maintains the "IP-CAN Session-1" established with the PDSN separately, that is, the IP-CAN Session-1 is reserved.
  • Step 12 The HA/LMA sends a CMIPv6 binding response message to the MS/AT, and the MS/AT completes the access through the CMIPv6 mode.
  • step 10 occurs before 6a, 6b, that is, IP-CAN session-2 is established first, IP-CAN-1 session and GW control session are established, and of course other order. In other words, the establishment of these three sessions is not strictly sequential. However, this does not affect the execution of the scheme.
  • the PCRF retrieves the existing session. If the association condition is met, the association is performed. If the association condition is not met, it is not related.
  • MS/AT uses the PDSN to assign an address to it in step 5 (this address is called the Care of Address (CoA) in the CMIPv6 access mode, which is called the address in this case), and the PDSN and the external
  • the network interworks data service and initiates QoS requests for this service. Specifically, it includes the following steps:
  • Step A.1 MS/AT and RAN/PCF perform HRPD QoS establishment.
  • Step A.2 corresponding to step A.1, if Link Flow is newly created/modified, the corresponding connection/modification A10 connection is also required between the RAN/PCF and the PDSN, and the corresponding requested QoS list is sent to the PDSN.
  • step A.3 the MS/AT sends an RSVP Resv message to the PDSN, and the TFT sends the signal to the PDSN through the signaling.
  • the TFT carries the address of the MS/AT, which is the source address of the uplink data, or This address can also be carried separately to the PDSN by the RSVP Resv message.
  • Step A.4 the PDSN determines that the current address of the RSVP Resv message is the address allocated by the previous PDSN for the MS/AT, and determines that the current MS/AT uses the SIPv6 access mode.
  • the PDSN initiates an IP-CAN session-to-PCR request to the PCRF, and requests the corresponding PCC policy.
  • the PCRF sends the corresponding policy to the PDSN through the response message.
  • the PCRF After receiving the IP-CAN session -1 modification request sent by the PDSN, the PCRF processes the session separately without any modification or processing of the IP-CAN session -2 and the GW control session, that is, the CAN session -2 and the GW control session are reserved.
  • Step A.5 the PDSN sends an RSVP reservation configuration (Resvconf) message to the MS/AT.
  • Step A.6 MA/AT, RAN/PCF, and PDSN install the corresponding QoS and allocate resources.
  • Case B The MS/AT uses the local address (HoA, Home of Address) assigned by the HA/LMA in step 12 to communicate with the external network through the HA/LMA, and initiates a QoS request for this service. Specifically, the following steps are included:
  • Step B.1 MS/AT and RAN/PCF perform HRPD QoS establishment.
  • Step B.2 corresponding to step B.1, if there is Link Flow new/modified, RAN/PCF and
  • Step B.3 The MS/AT sends an RSVP Resv message to the PDSN, and the TFT sends the signal to the PDSN through the signaling.
  • the TFT carries the HoA of the MS/AT, which is the source address of the uplink data, or the HoA address can also be The RSVP Resv message is carried to the PDSN separately. This step is existing Technology.
  • Step B.4 the PDSN determines that the address (HoA) brought by the RSVP Resv message is not the address (CoA) allocated by the PDSN for the MS/AT, and determines that the current MS/AT uses the access mode of the CMIPv6, and thus the PDSN Initiating GW control and QoS policy request to the PCRF;
  • the PCRF After receiving the GW control and QoS policy request sent by the PDSN, the PCRF separately processes the GW control session without any modification or processing of the IP-CAN session -1, that is, retaining the IP-CAN session -1.
  • Step B.5 After receiving the GW control and QoS policy request, the PCRF formulates the corresponding IP-CAN session policy and delivers it to HA/LMA through IP-CAN session-2.
  • Step B.6 in response to the GW control and QoS policy request initiated by the PDSN to the PCRF, the PCRF sends the corresponding PCC policy to the PDSN.
  • Step B.7 the PDSN sends an RSVP Resvconf message to the MS/AT.
  • Steps B.8, MA/AT, RAN/PCF, and PDSN install the corresponding QoS and allocate resources.
  • Case B must occur after step 11, but there is no inevitable relationship with situation A. Therefore, during the execution of case B, IP-CAN session -1 is always reserved.
  • the PDSN after receiving the IPv6CP negotiation request sent by the terminal device, the PDSN establishes a GW control session and an IP-CAN session-1 with the PCRF, and the PCRF determines that the two sessions are established for the same terminal device.
  • the PDSN session is different depending on the carrying association address (the home address of the gateway control session and the care-of address in the IP-CAN session 1), and the PCRF processes the two sessions independently and does not associate them.
  • the PCRF receives the IP-CAN Session-2 setup request of the terminal device belonging to the same IP connection sent by the HA/LMA, the PCRF associates the GW control session requested by the PDSN with the IP-CAN session-2 of the HA/LMA request, and The IP-CAN session-1 established with the PDSN is reserved. If the PDSN parses the RSVP Resv message sent from the MS/AT, and resolves that the terminal IP address carried by the message is an address allocated by the PDSN for the MS/AT, the PDSN initiates an IP-CAN session-1 modification request to the PCRF, requesting corresponding PCC strategy.
  • the PCRF receives the modification request of the IP-CAN session-1 sent by the PDSN, and the PCRF formulates a PCC policy for the terminal device.
  • the PDSN initiates an IP-CAN Session-1 modification request to the PCRF, it sends a "Gateway Control Session Termination" message to the PCRF requesting termination of the gateway control session between the PDSN and the PCRF, and if there is an IP-CAN session between the HA/LMA In the case of -2, the session is also deleted by the PCRF.
  • the PDSN parses the RSVP Resv message sent from the MS/AT, and resolves that the terminal IP address (HoA) carried by the message is not the address (CoA) allocated by the PDSN for the MS/AT, the PDSN initiates GW control and QoS policy request to the PCRF.
  • the PCRF then formulates a PCC policy for the terminal device, and sends a policy and charging control PCC policy to the PDSN and the HA/LMA respectively through the gateway control session and the IP-CAN session associated therewith.
  • the PDSN sends an IP-CAN Session -1 Termination Request message to the PCRF to initiate a GW Control and QoS Policy Request to the PCRF, requesting termination of the IP-CAN Session -1 between the PDSN and the PCRF.
  • FIG. 8 is a flowchart of Embodiment 4 of a method for policy and charging control according to the present invention. As shown in FIG. 8, the method for the example policy and charging control includes the following steps:
  • Step 1 The primary service connection is established.
  • Step 2 The LCP negotiation of the PPP session and the authentication mode is selected.
  • Step 3 Complete the user's access authentication and authorization by using the authentication mode selected in step 2.
  • the authentication signaling related to the interworking between the MS/AT and the PDSN, the PDSN and the AAA also perform the related operations of the authentication through the access request and the access response. After the authentication/authorization is successful, the relevant contracted QoS information will be sent from the AAA to the PDSN.
  • Step 4 The PDSN sends the signed QoS parameters to the RAN.
  • Step 5 The MS/AT and the PDSN perform an IPv6CP negotiation step.
  • the PDSN also sends the local link prefix to the MS/AT, and the MS/AT is based on This prefix generates a unicast address, which is not shown in the figure.
  • the terminal also obtains bootstrap information from the PDSN through the DHCP step, which is not shown in the flowchart.
  • Step 6 The PDSN simultaneously initiates a PCC session to the PCRF as a BBERF and a PCEF, which is:
  • the PDSN locates the role as PCEF, initiates an IP-CAN session-1 establishment with the PCRF; and carries the IP address assigned by the PDSN to the terminal, the address is filled in the IP-CAN session HoA cell, and the CoA letter in the IP-CAN session Meta information vacancies or fill in all zeros;
  • the PDSN locates the role as BBERF, and the PDSN initiates a GW session with the PCRF. And carrying the IP address assigned by the PDSN to the terminal, and the address is filled in the HoA cell of the gateway control session.
  • the establishment of the two sessions does not necessarily occur after the IPv6CP negotiation is completed. As long as the PDSN receives the IPv6CP configuration request, the step can be initiated, and the two sessions can be established in parallel.
  • Step 7 the PCRF receives the PCC session establishment request of the PDSN, establishes an IP-CAN session-1 and a GW control session with the PDSN, and determines that the two sessions are sessions from the same PDSN, and is the same MS/AT. When the service is serviced, the two sessions are processed separately, that is, they are not associated.
  • Step 8 The MS/AT sends a CMIPv6 Binding Update Request message to the selected HA/LMA to request binding to the HA/LMA.
  • Step 9 The HA/LMA and the AAA exchange authentication signaling, and complete authentication and authorization for the user to access through CMIPv6.
  • Step 10 After the HA/LMA receives the binding update and the authorization succeeds, the HA/LMA acts as the PCEF to initiate an IP-CAN session-2 setup request message to the PCRF, and the PCRF sends an IP-CAN session-2 setup response to the HA/LMA/PCEF. , complete the establishment of IP-CAN session-2, and download the relevant PCC policy to HA/LMA/PCEF.
  • Step 11 after the PCRF establishes an IP-CAN session-2 with the HA/LMA, the PCRF is based on the user.
  • the information such as the identifier, the PDN identifier, and the IP address associates the IP-CAN Session-2 with the "GW Control Session Established with the PDSN", and the PCRF maintains the "IP-CAN Session-1" established with the PDSN separately, that is, the IP is reserved. -CAN session-1.
  • Step 12 The HA/LMA sends a CMIPv6 binding response message to the MS/AT, and the MS/AT completes the access through the CMIPv6 mode.
  • step 10 occurs before 6a, 6b, that is, IP-CAN session-2 is established first, IP-CAN-1 session and GW control session are established, and of course other order. In other words, the establishment of these three sessions is not strictly sequential. However, this does not affect the execution of the scheme.
  • the PCRF retrieves the existing session. If the association condition is met, the association is performed. If the association condition is not met, it is not related.
  • the MS/AT uses the address assigned by the PDSN in step 5 (when the CMIP is accessed, it is called the Care of Address (CoA), which can only be called the ⁇ U address) through the PDSN and The external network interworks with the data service and initiates a QoS request for this service. Specifically, the following steps are included:
  • Step A.1 MS/AT and RAN/PCF perform HRPD QoS establishment.
  • Step A.2 corresponding to step A.1, if Link Flow is newly created/modified, the corresponding connection/modification A10 connection is also required between the RAN/PCF and the PDSN, and the corresponding requested QoS list is sent to the PDSN.
  • step A.3 the MS/AT sends an RSVP Resv message to the PDSN, and the TFT sends the signal to the PDSN through the signaling.
  • the TFT carries the address of the MS/AT, which is the source address of the uplink data, or the address can also be used in the RSVP.
  • the Resv message is carried to the PDSN separately. This step is prior art.
  • Step A.4 the PDSN determines that the address brought by the RSVP Resv message is the previous PDSN.
  • the address assigned to the MS/AT determines that the current MS/AT uses the SIPv6 access mode, and then the PDSN initiates an IP-CAN Session-1 modification request to the PCRF, and the PCRF receives the IP-CAN session-1 sent by the PDSN. Modify the request, formulate the corresponding PCC policy, and deliver the corresponding policy to the PDSN through the response message.
  • Step A.5 the PDSN sends an RSVP reservation configuration (Resvconf) message to the MS/AT.
  • Step A.6 MA/AT, RAN/PCF, and PDSN install the corresponding QoS and allocate resources.
  • Step A.7 when the PDSN initiates an IP-CAN Session-1 modification request to the PCRF (step A.4), the PDSN sends a gateway control session release message to the PCRF, requesting to terminate the gateway control session between the PDSN and the PCRF, and if In the case where there is an IP-CAN session-2 between the HA/LMA, the session is also deleted by the PCRF (A.8).
  • Case B The MS/AT uses the local address (HoA, Home of Address) assigned by the HA/LMA in step 12 to communicate with the external network through the HA/LMA, and initiates a QoS request for this service. Specifically, the following steps are included:
  • Step B.1 MS/AT and RAN/PCF perform HRPD QoS establishment.
  • Step B.2 corresponding to step B.1, if there is Link Flow new/modified, the RAN/PCF and the PDSN also need to establish/modify the A10 connection, and send the corresponding requested QoS list to the PDSN.
  • Step B.3 The MS/AT sends an RSVP Resv message to the PDSN, and the TFT sends the signal to the PDSN through the signaling.
  • the TFT carries the HoA of the MS/AT, which is the source address of the uplink data, or the HoA address can also be The RSVP Resv message is carried to the PDSN separately. This step is existing Technology.
  • Step B.4 the PDSN determines that the address (HoA) brought by the RSVP Resv message is not the address (CoA) allocated by the PDSN for the MS/AT, and determines that the current MS/AT uses the access mode of the CMIPv6, and thus the PDSN
  • the GW control and the QoS policy request are initiated to the PCRF.
  • the PCRF After receiving the GW control and the QoS policy request sent by the PDSN, the PCRF sends a corresponding PCC policy to the IP-CAN session-2 through which the gateway control session and the associated IP-CAN session-2 are respectively delivered.
  • PDSN and HA/LMA the address (HoA) brought by the RSVP Resv message is not the address (CoA) allocated by the PDSN for the MS/AT.
  • Step B.5 After receiving the GW control and QoS policy request, the PCRF formulates the corresponding IP-CAN session policy and delivers it to HA/LMA through IP-CAN session-2.
  • Step B.6 in response to the GW control and QoS policy request initiated by the PDSN to the PCRF, the PCRF sends the corresponding PCC policy to the PDSN.
  • Step B.7 the PDSN sends an RSVP Resvconf message to the MS/AT.
  • Steps B.8, MA/AT, RAN/PCF, and PDSN install the corresponding QoS and allocate resources.
  • Step B.9 While the PDSN initiates the GW control and the QoS policy request to the PCRF (step B.4), the PDSN sends an IP-CAN session-1 release request to the PCRF to request termination of the IP-CAN session between the PDSN and the PCRF. 1.
  • Case B must occur after step 11, but there is no inevitable relationship with situation A. Therefore, during the execution of case B, IP-CAN session -1 is always reserved.
  • the system for policy and charging control of the present invention includes network elements including terminal devices MS/AT, PDSN, PCRF, and HA/LMA, functions of the foregoing network elements, and connection relationships thereof.
  • network elements including terminal devices MS/AT, PDSN, PCRF, and HA/LMA, functions of the foregoing network elements, and connection relationships thereof.
  • FIG. 2 it is understood that the structure and function of the system are not described in detail here; the system of the strategy and the charging control of the present invention is proposed based on the system shown in FIG. 1 and FIG. 2, and each network element and The connection relationship is exactly the same as the connection relationship in the existing related system. The difference is the function implemented by some network elements, which is described in detail below.
  • a PDSN configured to establish a gateway control session and a first IP-CAN session with the PCRF
  • HA configured to establish a second IP-CAN session with the PCRF
  • a PCRF configured to establish a gateway control session and a first IP-CAN session with the PDSN, and establish a second IP-CAN session with the HA;
  • the PCRF is further configured to associate the gateway control session with the second IP-CAN session.
  • the above PCRF further does not associate the gateway control session with the first IP-CAN session when one of the following conditions is met:
  • the gateway control session and the first IP-CAN session belong to the same terminal device and belong to the same PDSN;
  • the home address of the gateway control session is different from the care-of address of the first IP-CAN session.
  • the PDSN further establishes the first IP-CAN session with the PCRF after the terminal device negotiates a point-to-point protocol PPP session with the PDSN/after the terminal device requests the bootstrap information.
  • the PDSN further establishes the gateway control session with the PCRF when the terminal device negotiates a PPP session with the PDSN.
  • the HA further establishes the second IP-CAN session with the PCRF after receiving the binding update message and being authorized by the AAA server;
  • the PCRF further associates the gateway control session with the second IP-CAN session based on the terminal device identity, and/or the packet data network identity, and/or the IP address.
  • the first IP-CAN session provides a policy for the terminal device to communicate with the packet data network via the PDSN;
  • the second IP-CAN session and the gateway control session provide policies for the terminal device to communicate with the packet data network via the HA.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种策略和计费控制的方法，包括：分组数据服务节点PDSN与终端设备完成IP版本6控制协议IPv6CP协商后，与策略控制规则实体PCRF分别建立网关控制会话和第一IP连接接入网络IP-CAN会话；所述PCRF确定所述网关控制会话和所述第一IP-CAN会话是为同一个终端设备建立的会话时，单独处理所述网关控制会话和所述第一IP-CAN会话。本发明同时公开了一种策略和计费控制的系统。本发明能根据终端设备所建立的会话类型而确定出PDSN与PCRF之间的接口类型，从而能保证终端设备准确及时地接入到网络。

Description

策略和计费控制的方法及系统 技术领域
本发明涉及策略和计费控制（ PCC, Policy and Charging Control )技术， 尤其涉及一种码分多址系统中策略和计费控制的方法及系统。 背景技术
图 1为码分多址（ cdma, Code Division Multiple Access )2000 lx及 HRPD ( HRPD, High Rate Packet Data ) PDS ( packet data service, 分组数据业务） 部分网络参考模型示意图， 如图 1所示， 第三代合作伙伴计划 2 ( 3GPP2, 3rd Generation Partnership Project2 )定义的码分多址 cdma2000 lx和高速分 组数据 HRPD网络架构， 主要由移动台 （ MS , Mobile Station ) /接入终端设 备（ AT, Access Terminal,或称终端设备 ) /用户设备 ( UE, User Equipment )、 无线接入网络（RAN, Radio Access Network ), 分组数据服务节点（ PDSN, Packet Data Serving Node )、 家乡代理（ HA, Home Agent ) /本地移动锚点 ( LMA, Local Mobility Anchor )、远程用户拨号认证系统（ RADIUS , Remote Authentication Dial In User Service ) /认证授权计费服务器 （AAA , Authentication Authorization Accounting )以及其他核心网络设备和支撑节点 组成。 其中， MS/AT通过无线接口和 RAN实现连接。 RAN包括基站（ BS, Base Station, )和分组控制功能（PCF, Packet Control Function ), 其中 BS 主要用于在小区建立无线覆盖， 为终端设备提供分组数据业务的空中接口； PCF主要用于控制无线网络资源， 转发无线系统和 PDSN分组控制单元之 间的消息。
PDSN通过 RAN 为终端设备提供到 Internet或应用服务器、 或者到 HA/LMA的接入， 其作用是建立、 维护 MS/AT和 PDSN之间的点到点协议 ( PPP, Point to Point Protocol )会话； 接受并执行 RADIUS/AAA服务器对 MS/AT的认证、 授权和计费； 路由来自和发往分组数据网络或者 HA/LMA 的数据包等。
HA/LMA负责移动 IP场景下， 为终端设备分配本地地址、 转发上行和 下行数据包、 数据包的隧道封装等， 其中移动 IP包括客户端移动 IP版本 4 或版本 6 ( CMIPv4/v6, Client Mobile IP version 4/version 6,或称 MIPv4/v6, 移动 IP版本 4或者版本 6 )和代理移动 IP版本 4或版本 6 ( PMIPv4/v6, Proxy Mobile IPv4/v6 )。
认证 /4受权 /计费 ( AAA, Authentication、 Authorization、 Accounting )月良 务器（又称为远程用户拨号认证 ( RADIUS, Remote Authentication Dial In User Service )服务器）是认证授权计费服务器， 其主要作用是管理哪些用 户可以访问网络， 具有访问权的用户可以得到哪些服务， 如何对正在使用 网络资源的用户进行计费等。
如图 1所示， cdma2000网络可以通过 PCC技术实现资源的合理分配和 控制。由于终端设备在接入 cdma2000系统时，可以通过多种接入模式接入， 比^口简单 IPv4/v6 ( SIPv4/v6, Simple IPv4/v6 )、 PMIPv4/v6、 CMIPv4/v6等， 在不同的接入模式下 , 网络侧相关网元如 PDSN、 HA/LMA在 PCC技术中 充当的角色和执行的功能也是不同的。 概括的来说， 用户终端设备通过 SIPv4/v6接入时， PDSN执行策略控制执行实体（PCEF, Policy Control Enforcement Function ) 的功能， 网络中无 HA/LMA , 无承载绑定和时间上 才艮实体 ( BBERF , Bearer Binding and Event Trigger Report Function ); PDSN/PCEF和策略控制规则实体（ PCRF, Policy Control Rule Function )通 过 Gx接口来传输相关的策略信息。 图 2是终端设备 MS/AT通过 CMIPv6 接入并建立 PCC 会话的架构图， 如图 2 所示， 当用户终端设备通过 PMIPv4/v6、 CMIPv4/v6接入时， PDSN执行 BBERF功能， 与 PCRF通过 Gxa 建立网关控制会话 （GW control session ) 并传递相关的策格信息, HA/LMA执行 PCEF的功能， 与 PCRF通过 Gx 口建立 IP连接接入网络 ( IP-CAN , IP-Connectivity Access Network )会话， 并传递相关的策略信息， PCRF将属于同一终端的同一个 IP连接（IP连接概念见下文解释） 的网关 控制会话和 IP-CAN会话关联到一起， 在制定 PCC策略时一起制定， 并分 别下发到 PDSN和 HA/LMA,完成对同一个终端同一个 IP连接的资源和计 费控制。 所谓的 PCRF将该两个会话作关联， 现有的机制是： PCRF收到 第一个会话请求 （比如网关控制会话请求）， PCRF接受， 则该会话建立完 成，如果 PCRF又收到另一个会话建立请求（比如 IP-CAN会话请求）， PCRF 则拿该 IP-CAN会话请求携带的参数和已经建立的网关控制会话的上下文 参数作对比， 如果发现这两个会话是属于同一个终端、 同一个 IP连接的会 话， 则将该两个回话关联到一起。
在不同的接入模式下， 终端可以建立不同的 IP连接过程。 其中， IP连 接是指终端获取了网络侧为其分配 /配置的 IP地址，并利用该地址连接到网 络、 拜访网络侧资源的一种关联。 一个终端可以同时拥有多个 IP连接， 比 如说， 终端可以同时建立 SIPv6和 CMIPv6的连接。 在不同的 IP连接中， 各个网元在釆用 PCC技术时充当角色和执行功能也不同，下面给出了 SIPv6 和 CMIPv6两种 IP连接建立流程的详细步骤分析， 并引出了潜在的问题。
图 3是终端设备 MS/AT通过 SIPv6接入并建立 PCC会话的流程图，如 图 3所示， MS/AT通过 SIPv6接入的流程具体包括以下步骤：
步骤 1 , 主业务连接建立。
步骤 2, PPP会话的链路控制协议（ LCP, Link Control Protocol )协商 并选定鉴权方式。
步骤 3 , 通过步骤 2中选定的鉴权方式完成用户的接入鉴权和授权。 其 中 MS/AT与 PDSN互通相关的鉴权信令， PDSN和 AAA也通过接入请求 和接入应答执行鉴权的相关操作。 鉴权 /授权成功后， 相关的签约的服务质 量（ QoS , Quality of Service )信息将会从 AAA发送给 PDSN。
步骤 4, PDSN将签约的 QoS参数发送给 RAN。
步骤 5 , MS/AT和 PDSN执行 IP版本 6控制协议 ( IPv6CP, IP Version 6 Control Protocol )协商步骤。
协商过程后， PDSN还会把本地链路（HL, Home Link )前缀发送给 MS/AT, MS/AT根据此前缀生成单播地址， 该过程未在图中示出。
步骤 6, PDSN作为 PCEF向 PCRF为该 MS/AT发起 IP-CAN会话建立 步骤。 其中， PDSN/PCEF在该消息中携带了 IP连接接入网络（IP-CAN, IP-Connectivity Access Network )类型、终端设备标识、分组数据网络（ PDN, Packet Data Network )标识、 终端设备 IP地址（该地址是 PDSN为终端分 配）等信息。
由于 PDSN是作为 PCEF与 PCRF建立的 IP-CAN会话， 故 PDSN和 PCRF之间的接口釆用的是 Gx口。
该步骤未必一定发生在 IPv6CP协商完成后， 只要 PDSN收到 IPv6CP 配置请求， 就可以发起该步骤。
步骤 7, PCRF发送 IP-CAN会话建立应答给 PDSN/PCEF。 PCRF通过 IP-CAN会话向 PCEF提供 PCC规则以及事件选项等。
图 4是终端设备 MS/AT通过 CMIPv6接入并建立 PCC会话的流程图， 如图 4所示。 MS/AT通过 CMIPv6接入流程具体包括以下步骤：
步骤 1 , 主业务连接建立。
步骤 2, PPP会话的 LCP协商并选定鉴权方式。
步骤 3 , 通过步骤 2选定的鉴权方式完成用户的接入鉴权和授权。 其中 MS/AT与 PDSN互通相关的鉴权信令， PDSN和 AAA也通过接入请求和接 入应答执行鉴权的相关操作。 鉴权 /授权成功后， 相关的签约 QoS信息将会 从 AAA发送给 PDSN。
步骤 4, PDSN将签约的 QoS参数发送给 RAN。
步骤 5 , MS/AT和 PDSN执行 IPv6CP协商步骤。
协商过程中， PDSN还会把本地链路（HL, Home Link )前缀发送给 MS/AT , MS/AT根据此前缀生成单播地址 , 该过程未在图中示出。 此外， 终端还要向 PDSN通过 DHCP步骤获取自举（bootstrap )信息， 流程图中 未示出。
步骤 6, PDSN作为 BBERF向 PCRF为该 MS/AT发起网关 （ GW, Gateway )控制会话建立步骤。 其中 PDSN/BBERF在该消息中携带了会话 类型、 终端设备标识、 PDN标识、 终端设备 IP地址等信息。
由于 PDSN是作为 BBERF与 PCRF建立的 GW控制会话， 故 PDSN 和 PCRF之间的接口釆用的是 Gxa接口。
该步骤未必一定发生在 IPv6CP协商完成后， 只要 PDSN收到 IPv6CP 配置请求， 就可以发起该步骤。
步骤 7, PCRF发送 IP-CAN会话建立应答给 PDSN。
步骤 8, MS/AT发送 CMIPv6绑定更新请求消息给选定的 HA/LMA, 请求和 HA/LMA的绑定。
步骤 9, HA/LMA与 AAA互通鉴权信令， 完成对用户通过 CMIPv6接 入的鉴权和授权。
步骤 10 , HA/LMA接收到绑定请求并经 AAA授权后 , HA/LMA作为 PCEF向 PCRF发起 IP-CAN会话建立请求。
步骤 11 , PCRF向 HA/LMA/PCEF发送 IP-CAN会话建立应答， 完成 IP-CAN会话的建立， 并向 HA/LMA/PCEF下载相关的 PCC策略。
步骤 12, HA/LMA发送 CMIPv6绑定应答消息给 MS/AT, MS/AT完成 通过 CMIPv6方式的接入。 通过分析上述的如图 2及图 4的两个流程， 即 MS/AT通过 SIPv6接入 和 CMIPv6接入的时候， 前五个步骤即步骤 1至步骤 5的操作都是完全相 同的，没有任何的区别。但是 PDSN在后续的操作却是有区别的， 通过 SIPv6 接入时， PDSN的角色是 PCEF, 并与 PCRF通过 Gx接口建立 IP-CAN会 话； 通过 CMIPv6接入时， PDSN的角色是 BBERF, 并与 PCRF通过 Gxa 接口建立 GW控制会话； 由于 MS/AT到底是基于何种接入方式， 直至后续 MS/AT是否与 HA/LMA发起绑定才能确定，但是 PDSN需要提前就要根据 MS/AT的接入方式来选择相应的功能和角色， 因为 PDSN和 PCRF所建立 的会话、 釆用的接口是不同的。 上述图 2及图 4所示的 MS/AT接入方式， 显然不能提前确定 PDSN的角色， 也就不能确定 PDSN与 PCRF之间的接 口类型， 这无疑会影响 MS/AT准确及时地接入到网络。 发明内容
有鉴于此， 本发明的主要目的在于提供一种策略和计费控制的方法及 系统， 本发明的技术方案是这样实现的：
一种策略和计费控制的方法， 所述方法包括：
终端设备在通过 MIPv6接入 cdma系统时， PDSN与 PCRF分别建立 网关控制会话和第一 IP-CAN会话；
HA与所述 PCRF建立第二 IP-CAN会话；
所述 PCRF关联所述网关控制会话和所述第二 IP-CAN会话。
优选地， 所述方法还包括：
所述 PCRF在满足以下条件之一时， 不关联所述网关控制会话和所述 第一 IP-CAN会话：
所述网关控制会话和所述第一 IP-CAN会话属于同一个终端设备且属 于同一个 PDSN;
网关控制会话的家乡地址和第一 IP-CAN会话的转交地址不同。 优选地， 终端设备向 PDSN协商点到点协议 PPP会话时 /后， 或者终端 设备请求自举信息后， PDSN与 PCRF建立所述第一 IP-CAN会话。
优选地， 终端设备与 PDSN协商 PPP会话时 /后， PDSN与 PCRF建立 所述网关控制会话；
HA收到绑定更新消息并由认证授权计费服务器 AAA授权后， HA与 PCRF建立所述第二 IP-CAN会话；
所述 PCRF根据终端设备标识，和 /或分组数据网标识，和 /或 IP地址关 联所述的网关控制会话和第二 IP-CAN会话。
优选地 ,所述第一 IP-CAN会话为终端设备经 PDSN与分组数据网络进 行通信时提供策略；
第二 IP-CAN会话和网关控制会话为终端设备经 HA与分组数据网络进 行通信时提供策略。
优选地， 所述方法还包括：
所述 PDSN在收到资源预留请求时， 根据终端设备的地址决定是通过 网关控制会话或者第一 IP-CAN会话请求 PCC策略。
优选地， 所述方法还包括：
所述 PDSN判断所述终端设备的地址是所述 PDSN为该终端设备分配 的地址时 , 通过所述第一 IP-CAN会话向所述 PCRF请求 PCC策略；
所述 PDSN判断所述终端设备的地址不是所述 PDSN为该终端设备分 配的地址时， 通过所述网关控制会话向所述 PCRF请求 PCC策略。
优选地， 所述方法还包括：
所述 PDSN通过所述第一 IP-CAN会话向所述 PCRF请求 PCC策略后 , 向所述 PCRF发起删除所述网关控制会话的请求；
所述 PDSN通过所述网关控制会话向所述 PCRF请求 PCC策略后， 向 所述 PCRF发起删除所述第一 IP-CAN会话的请求。 一种策略和计费控制的系统， 包含终端设备、 PDSN、 PCRF和 HA; 其中，
在终端设备在通过 ΜΙΡνό接入 cdma系统时，
PDSN, 用于与 PCRF建立网关控制会话和第一 IP-CAN会话；
HA , 用于与所述 PCRF建立第二 IP-CAN会话；
PCRF, 用于与 PDSN建立网关控制会话和第一 IP-CAN会话， 与 HA 建立第二 IP-CAN会话；
PCRF进一步用于， 关联所述网关控制会话和所述第二 IP-CAN会话。 优选地， 所述 PCRF进一步在满足以下条件之一时， 不关联所述网关 控制会话和所述第一 IP-CAN会话：
所述网关控制会话和所述第一 IP-CAN会话属于同一个终端设备且属 于同一个 PDSN;
网关控制会话的家乡地址和第一 IP-CAN会话的转交地址不同。
优选地， PDSN进一步在终端设备向 PDSN协商点到点协议 PPP会话 时 /后， 或者终端设备请求自举信息后， 与 PCRF建立所述第一 IP-CAN会 话。
优选地， PDSN进一步在终端设备与 PDSN协商 PPP会话时 /后 ,与 PCRF 建立所述网关控制会话；
HA进一步在接收到绑定更新消息并由 AAA服务器授权后， 与 PCRF 建立所述第二 IP-CAN会话；
PCRF进一步根据终端设备标识， 和 /或分组数据网标识， 和 /或 IP地址 关联所述的网关控制会话和第二 IP-CAN会话。
优选地 ,所述第一 IP-CAN会话为终端设备经 PDSN与分组数据网络进 行通信时提供策略；
第二 IP-CAN会话和网关控制会话为终端设备经 HA与分组数据网络进 行通信时提供策略。
本发明中， 终端设备在通过 6MIPv6 cdma系统时， PDSN与 PCRF分 别建立网关控制会话和第一 IP连接接入网络 IP-CAN会话； HA与所述 PCRF 建立第二 IP-CAN会话； PCRF关联所述网关控制会话和所述第二 IP-CAN 会话。 本发明能根据终端设备所建立的会话类型而确定出 PDSN与 PCRF 之间的接口类型， 从而能保证终端设备准确及时地接入到网络。 附图说明
图 1为 CDMA2000 lx及 HRPD PDS部分网络参考模型示意图； 图 2是终端设备 MS/AT通过 CMIPv6接入并建立 PCC会话的架构图； 图 3是终端设备 MS/AT通过 SIPv6接入并建立 PCC会话的流程图； 图 4是终端设备 MS/AT通过 CMIPv6接入并建立 PCC会话的流程图； 图 5为本发明策略和计费控制的方法实施例一的流程图；
图 6为本发明策略和计费控制的方法实施例二的流程图；
图 7为本发明策略和计费控制的方法实施例三的流程图；
图 8 为本发明策略和计费控制的方法实施例四的流程图。 具体实施方式
本发明的基本思想为： 终端设备在通过 MIPv6接入 cdma 系统时， PDSN与 PCRF分别建立网关控制会话和第一 IP连接接入网络 IP-CAN会 话； HA与所述 PCRF建立第二 IP-CAN会话； PCRF关联所述网关控制会 话和所述第二 IP-CAN会话。
其中， 如果终端直接通过 PDSN与外部分组数据网络通信， 此时终端 使用的是 PDSN为终端分配的 IP地址， 第一 IP-CAN会话为此通信数据提 供 PCC策略； 如果终端通过 HA与外部分组数据网络通信， 此时终端使用 的是 HA为终端分配的地址， 该地址称做 HoA (家乡地址；)， 网关控制会话 和第二 IP-CAN会话关联后， 为此通信数据提供 PCC策略。
为使本发明的目的、 技术方案和优点更加清楚明白， 以下举实施例并 参照附图， 对本发明进一步详细说明。
实施例一
在本实施例中 , PDSN收到终端设备 MS/AT发送来的 IPv6CP配置请求 后， 或者终端设备获取自举（ bootstrap )信息后， PDSN与 PCRF建立 GW 控制会话和 IP-CAN会话 -1； PCRF接收到 PDSN发送的会话建立请求后， 如果确定该两个会话是为同一个终端设备与同一个 PDSN建立的会话或者 根据携带关联地址（网关控制会话的家乡地址和 IP-CAN会话 -1 中的转交 地址）不同， 则 PCRF对这两个会话独立处理， 不作关联。 如果 PCRF收到 了 HA/LMA发送来的该终端设备的 IP-CAN会话 -2 建立请求， PCRF将 PDSN请求的 GW控制会话和 HA/LMA请求的 IP-CAN会话 -2关联， 可选 的， PCRF可以将 IP-CAN会话 -1释放。后续的操作按照现有技术执行即可。
图 5为本发明策略和计费控制的方法实施例一的流程图， 如图 5所示， 本示例策略和计费控制的方法包括以下步骤：
步骤 1 , 主业务连接建立。
步骤 2, PPP会话的 LCP协商并选定鉴权方式。
步骤 3 , 通过步骤 2中选定的鉴权方式完成用户的接入鉴权和授权。 其 中 MS/AT与 PDSN互通相关的鉴权信令， PDSN和 AAA也通过接入请求 和接入应答执行鉴权的相关操作。 鉴权 /授权成功后， 相关的签约 QoS信息 将会从 AAA发送给 PDSN。
步骤 4, PDSN将签约的 QoS参数发送给 RAN。
步骤 5 , MS/AT和 PDSN执行 IPv6CP协商步骤。
协商过程中， PDSN还会把本地链路前缀发送给 MS/AT, MS/AT根据 此前缀生成单播地址， 该过程未在图中示出。 此外， 终端还要向 PDSN通 过 DHCP步骤获取自举（ bootstrap )信息， 流程图中未示出。
步骤 6, PDSN作为 BBERF和 PCEF向 PCRF发起 PCC会话，具体为： 6a, PDSN定位角色为 PCEF, 与 PCRF发起 IP-CAN会话 -1建立， 并 携带 PDSN为终端分配的 IP地址 ,该地址填写到 IP-CAN会话 HoA信元中 ,
IP-CAN会话中的 CoA信元信息空缺或者填写全零；
6b, PDSN定位角色为 BBERF, PDSN会发起同 PCRF的 GW会话建 立， 并携带 PDSN为终端分配的 IP地址， 该地址填写到网关控制会话的
HoA信元中。
该两个会话的建立未必一定发生在 IPv6CP协商 /自举信息获取完成后， 只要 PDSN收到 IPv6CP配置请求， 就可以发起该步骤， 而且这两个会话可 以并行建立。
步骤 7, PCRF接收到 PDSN 的 PCC会话建立请求， 与 PDSN分别建 立 IP-CAN会话 -1和 GW控制会话，在判断该两个会话是来自同一个 PDSN 的会话、 且是为同一个 MS/AT服务时， 对该两个会话单独处理， 即不作关 联。
步骤 8, MS/AT发送 CMIPv6绑定更新请求消息给选定的 HA/LMA, 请求与 HA/LMA的绑定。
步骤 9, HA/LMA与 AAA互通鉴权信令，完成对终端设备通过 CMIPv6 接入的鉴权和授权。
步骤 10, HA/LMA接收到绑定更新和授权成功后 , HA/LMA作为 PCEF 向 PCRF发起 IP-CAN会话 -2建立请求， PCRF 向 HA/LMA/PCEF发送 IP-CAN会话 -2建立应答，完成 IP-CAN会话 -2的建立，并向 HA/LMA/PCEF 下载相关的 PCC策略。
步骤 11 , PCRF与 HA/LMA建立 IP-CAN会话 -2后， PCRF根据用户 标识、 PDN标识， IP地址等信息将 IP-CAN会话 -2与 "与 PDSN建立的 GW 控制会话" 相关联。
可选的， PCRF会释放与 PDSN建立的 "IP-CAN会话 -1"。此时， PDSN 角色为 BBERF , 其通过 Gxa接口与 PCRF之间建立相应的 IP-CAN会话。
步骤 12, HA/LMA发送 CMIPv6绑定应答消息给 MS/AT, MS/AT完成 通过 CMIPv6方式的接入。
步骤 13 , 紧承步骤 11 , PCRF发起 "IP-CAN会话 -Γ 释放操作， 释放 IP-CAN会话 -1。
以上步骤中， 有可能出现第 10步发生在第 6a、 6b之前的情况， 也就 是说 IP-CAN会话 -2先建立， IP-CAN-1会话和 GW控制会话后建立， 当然 也可能出现其他次序。 也就是说， 这三个会话的建立并没有严格的先后顺 序。 但是这不会影响该方案的执行， PCRF收到请求后， 并去检索已经存在 的会话， 如果符合关联条件， 就进行关联， 如果不符合关联条件， 就不关 联即可。
实施例二
在本实施例中， PDSN收到 MS/AT发送的 IPv6CP配置请求时 /后， PDSN 同时与 PCRF建立 GW控制会话和 IP-CAN会话 -1。 PCRF接收到了 PDSN 发送的 IP-CAN会话 -1 修改请求后， PCRF确定该终端设备的接入模式为 SIPv6, 可选的， PCRF将与 PDSN建立的 GW控制会话释放， 后续的操作 按照现有技术执行即可。
图 6为本发明策略和计费控制的方法实施例二的流程图， 如图 6所示， 本示例策略和计费控制的方法包括以下步骤：
步骤 1 , 主业务连接建立。
步骤 2, PPP会话的 LCP协商并选定鉴权方式。
步骤 3 , 通过步骤 2选定的鉴权方式完成用户的接入鉴权和授权。 其中 MS/AT与 PDSN互通相关的鉴权信令， PDSN和 AAA也通过接入请求和接 入应答执行鉴权的相关操作。 鉴权 /授权成功后， 相关的签约 QoS信息将会 从 AAA发送给 PDSN。
步骤 4, PDSN将签约的 QoS参数发送给 RAN。
步骤 5 , MS/AT和 PDSN执行 IPv6CP协商步骤。
协商过程中， PDSN还会把本地链路前缀发送给 MS/AT, MS/AT根据 此前缀生成单播地址， 该过程未在图中示出。 此外， 终端还要向 PDSN通 过 DHCP步骤获取自举（ bootstrap )信息， 流程图中未示出。
步骤 6, PDSN同时作为 BBERF和 PCEF向 PCRF发起 PCC会话， 具 体为：
6a, PDSN定位角色为 PCEF, 与 PCRF发起 IP-CAN会话 -1建立； 并 携带 PDSN为终端分配的 IP地址 ,该地址填写到 IP-CAN会话 HoA信元中 , IP-CAN会话中的 CoA信元信息空缺或者填写全零；
6b, PDSN定位角色为 BBERF, PDSN会发起同 PCRF的 GW会话建 立。 并携带 PDSN为终端分配的 IP地址， 该地址填写到网关控制会话的 HoA信元中。
该两个会话的建立未必一定发生在 IPv6CP协商 /自举信息获取完成后， 只要 PDSN收到 IPv6CP配置请求， 就可以发起该步骤， 而且这两个会话可 以并行建立。
PCRF收到 PDSN 的 PCC会话建立请求， 与 PDSN分别建立 IP-CAN 会话 -1和 GW控制会话， 在判断该两个会话是来自同一个 PDSN的会话、 且是为同一个 MS/AT服务时， 对该两个会话单独处理， 即不作关联。
步骤 7, MS/AT与 RAN/PCF执行 HRPD QoS建立步骤。
步骤 8,对应步骤 7,如果有 Link Flow新建 /修改，在 RAN/PCF与 PDSN 之间也需要对应建立 /修改 A10连接， 并将相应的请求的 QoS列表发送给 PDSN。 步骤 9 , MS/AT 发送资源预留协议 ( RSVP , Resource Reservation Protocol )预留 （Resv, Reserve ) 消息给 PDSN, 业务数据流模板 ( TFT, Traffic Flow Template )通过该信令发送给 PDSN。
步骤 10, PDSN收到 MS/AT发送来的 RSVP Resv消息后， 解析出该消 息携带的终端 IP地址， 其中该 IP地址可以由在 RSVP 消息单独携带给 PDSN, 也可以从携带的 TFT中解析出 （现有技术）。
PDSN通过判断该地址是 PDSN为 MS/AT分配的地址， 则 PDSN向 PCRF发起 IP-CAN会话 -1修改请求， 请求相应的 PCC策略， PCRF通过响 应消息 , 把对应的策略发送到 PDSN。
步骤 11 , PCRF收到 PDSN发送来的 IP-CAN会话修改请求后， 判断 终端设备当前的接入模式为 SIPv6, 保留 IP-CAN会话 -1 , 删除 GW会话。 此时， PDSN角色为 PCEF,其通过 Gx接口与 PCRF之间建立相应的 IP-CAN 会话。
步骤 12 , PDSN发送 RSVP Resvconf消息给 MS/AT。
步骤 13 , MS/AT, RAN/PCF以及 PDSN安装相应的 QoS, 分配资源。 步骤 14: 紧承步骤 11 , PCRF向 PDSN发起 GW控制会话终止操作请 求，释放 GW控制会话。该步骤 14也可以由步骤 9触发，由 PDSN发起" GW 控制会话" 释放操作， 釆用何种方式取决于具体的通信流程实现。
实施例三
本实施例中， PDSN在收到终端设备发送的 IPv6CP协商请求之后， 同 时与 PCRF建立 GW控制会话和 IP-CAN会话 -1 , PCRF确定是该两会话是 为同一个终端设备建立的与同一个 PDSN的会话或者根据携带关联地址（网 关控制会话的家乡地址和 IP-CAN会话 -1 中的转交地址） 不同， 则 PCRF 对这两个会话独立处理， 不对其进行关联。
如果 PCRF收到了 HA/LMA发送的该终端设备的属于同一 IP连接的 IP-CAN会话 -2建立请求， PCRF将 PDSN请求的 GW控制会话和 HA/LMA 请求的 IP-CAN会话 -2关联， 并保留与 PDSN建立的 IP-CAN会话 -1。
如果 PDSN从 MS/AT发送来的 RSVP Resv消息中，解析出该消息携带 的终端 IP地址是 PDSN为 MS/AT分配的地址， 则 PDSN向 PCRF发起 IP-CAN会话 -1修改请求，请求相应的 PCC策略。 PCRF收到了 PDSN发送 来的 IP-CAN会话 -1的修改请求， 则 PCRF为终端设备制定 PCC策略， 并 且如果存在所述 HA/LMA请求的 IP-CAN会话 -2 , 则 PCRF将其保留， 如 果不存在， 则不作处理。
如果 PDSN从 MS/AT发送来的 RSVP Resv消息中，解析出该消息携带 的终端 IP地址（ HoA )不是 PDSN为 MS/AT分配的地址（ CoA ), 则 PDSN 向 PCRF发起 GW控制与 QoS策略请求，则 PCRF为终端设备制定 PCC策 略，且通过所述网关控制会话和与其关联的 IP-CAN会话分别向所述 PDSN 和所述 HA/LMA下发策略和计费控制 PCC策略。 这里， GW控制与 QoS 策略请求消息只能利用在 GW控制会话和 HA/LMA请求的 IP-CAN会话 -2 关联后的会话来发送。
图 7为本发明策略和计费控制的方法实施例三的流程图， 如图 7所示， 本示例策略和计费控制的方法包括以下步骤：
步骤 1 , 主业务连接建立。
步骤 2, PPP会话的 LCP协商并选定鉴权方式。
步骤 3 , 通过步骤 2选定的鉴权方式完成用户的接入鉴权和授权。 其中 MS/AT与 PDSN互通相关的鉴权信令， PDSN和 AAA也通过接入请求和接 入应答执行鉴权的相关操作。 鉴权 /授权成功后， 相关的签约 QoS信息将会 从 AAA发送给 PDSN。
步骤 4, PDSN将签约的 QoS参数发送给 RAN。
步骤 5 , MS/AT和 PDSN执行 IPv6CP协商步骤。 协商过程中， PDSN还会把本地链路前缀发送给 MS/AT, MS/AT根据 此前缀生成单播地址， 该过程未在图中示出。 此外， 终端还要向 PDSN通 过 DHCP步骤获取自举（ bootstrap )信息， 流程图中未示出。
步骤 6, PDSN同时作为 BBERF和 PCEF向 PCRF发起 PCC会话， 具 体为：
6a, PDSN定位角色为 PCEF, 与 PCRF发起 IP-CAN会话 -1建立； 并 携带 PDSN为终端分配的 IP地址 ,该地址填写到 IP-CAN会话 HoA信元中 , IP-CAN会话中的 CoA信元信息空缺或者填写全零；
6b, PDSN定位角色为 BBERF, PDSN会发起同 PCRF的 GW会话建 立， 并携带 PDSN为终端分配的 IP地址， 该地址填写到网关控制会话的 HoA信元中。
该两个会话的建立未必一定发生在 IPv6CP协商完成后，只要 PDSN收 到 IPv6CP配置请求， 就可以发起该步骤， 而且这两个会话可以并行建立。
步骤 7, PCRF收到 PDSN 的 PCC会话建立请求， 与 PDSN分别建立 IP-CAN会话 -1 和 GW控制会话， 在判断该两个会话是来自同一个 PDSN 的会话、 且是为同一个 MS/AT服务时， 对该两个会话单独处理， 即不作关 联。
步骤 8, MS/AT发送 CMIPv6绑定更新请求消息给选定的 HA/LMA, 请求与 HA/LMA的绑定。
步骤 9, HA/LMA与 AAA互通鉴权信令， 完成对用户通过 CMIPv6接 入的鉴权和授权。
步骤 10, HA/LMA收到绑定更新和授权成功后， HA/LMA作为 PCEF 向 PCRF发起 IP-CAN会话 -2建立请求消息， PCRF向 HA/LMA/PCEF发送 IP-CAN会话 -2建立应答，完成 IP-CAN会话 -2的建立，并向 HA/LMA/PCEF 下载相关的 PCC策略。 其中该 IP-CAN会话 2中， CoA信元填写了 PDSN 为终端分配的 IP地址， HoA信元中填写了 AAA/HA为终端分配的地址。 步骤 11 , PCRF与 HA/LMA建立 IP-CAN会话 -2后， PCRF根据用户 标识、 PDN标识， IP地址等信息将 IP-CAN会话 -2与 "与 PDSN建立的 GW 控制会话"相关联， 同时 PCRF会单独维护与 PDSN建立的 "IP-CAN会话 -1" , 即保留 IP-CAN会话 -1。
步骤 12, HA/LMA发送 CMIPv6绑定应答消息给 MS/AT, MS/AT完成 通过 CMIPv6方式的接入。
以上步骤中， 有可能出现第 10步发生在第 6a、 6b之前的情况， 也就 是说 IP-CAN会话 -2先建立， IP-CAN-1会话和 GW控制会话后建立， 当然 也可能出现其他次序。 也就是说， 这三个会话的建立并没有严格的先后顺 序。 但是这不会影响该方案的执行， PCRF收到请求后， 并去检索已经存在 的会话， 如果符合关联条件， 就进行关联， 如果不符合关联条件， 就不关 联即可。
以下的步骤分情况 A和情况 B分别说明在接收到不同消息时， 任何进 行相应的处理。
情况 A, MS/AT用在步骤 5中 PDSN为其分配地址（该地址在 CMIPv6 接入模式下称作转交地址（ CoA, Care of Address ), 该处情况下称作地址）， 通过 PDSN与外部网络互通数据业务， 并为此业务发起 QoS请求。 具体包 括以下步骤：
步骤 A.1 , MS/AT与 RAN/PCF执行 HRPD QoS建立。
步骤 A.2,对应步骤 A.1 ,如果有 Link Flow新建 /修改，对应在 RAN/PCF 与 PDSN之间也需要对应建立 /修改 A10连接，并将相应的请求的 QoS列表 发送给 PDSN„
步骤 A.3 , MS/AT发送 RSVP Resv消息给 PDSN, TFT通过该信令发 送给 PDSN, TFT中携带了 MS/AT的地址， 即为上行数据的源地址， 或者 该地址也可以由在 RSVP Resv消息单独携带给 PDSN。 该步骤为现有技术。 步骤 A.4, PDSN通过判断 RSVP Resv消息中带来的地址是之前 PDSN 为 MS/AT分配的地址， 判定当前 MS/AT釆用的是 SIPv6的接入模式， 于是
PDSN向 PCRF发起 IP-CAN会话 -1修改请求，请求相应的 PCC策略， PCRF 通过响应消息， 把对应的策略下发到 PDSN。
PCRF收到 PDSN发送来的 IP-CAN会话 -1修改请求后，单独处理该会 话，不对 IP-CAN会话 -2和 GW控制会话作任何修正或者处理，即保留 CAN 会话 -2和 GW控制会话。
步骤 A.5 , PDSN发送 RSVP预留配置 （Resvconf ) 消息给 MS/AT。 步骤 A.6, MA/AT、 RAN/PCF以及 PDSN安装相应的 QoS, 并分配资 源。
如果情况 A发生在 11步之后 （如图示）， 则按上述描述处理； 情况还 可以反正在步骤 7之后， 步骤 10之前， 因此， 如果 PCRF在步骤 10之前 收到 A.4步， 则 PCRF和 PDSN只保存网关控制会话， 不对 IP-CAN会话 -2 处理（因为还没有建立）。
情况 B, MS/AT用在步骤 12中 HA/LMA为其分配的本地地址（ HoA, Home of Address )通过 HA/LMA与外部网络互通数据业务， 并为此业务发 起 QoS请求。 具体包括以下步骤：
步骤 B.1 , MS/AT与 RAN/PCF执行 HRPD QoS建立。
步骤 B.2, 对应步骤 B.1 , 如果有 Link Flow新建 /修改， RAN/PCF与
PDSN之间也需要对应建立 /修改 A10连接， 并将相应的请求的 QoS列表发 送给 PDSN。
步骤 B.3 , MS/AT发送 RSVP Resv消息给 PDSN, TFT通过该信令发 送给 PDSN, TFT中携带了 MS/AT的 HoA, 即为上行数据的源地址， 或者 该 HoA地址也可以由在 RSVP Resv消息单独携带给 PDSN。 该步骤为现有 技术。
步骤 B.4, PDSN通过判断 RSVP Resv消息中带来的地址（ HoA )不是 之前 PDSN 为 MS/AT 分配的地址（CoA ) , 判定当前 MS/AT 釆用的是 CMIPv6的接入模式， 于是 PDSN向 PCRF发起 GW控制和 QoS策略请求；
PCRF收到 PDSN发送来的 GW控制和 QoS策略请求后， 单独处理该 GW控制会话， 不对 IP-CAN会话 -1作任何修正或者处理， 即保留 IP-CAN 会话 -1。
步骤 B.5 , PCRF收到 GW控制和 QoS策略请求后，制定对应的 IP-CAN 会话策略， 并通过 IP-CAN会话 -2下发到 HA/LMA.
步骤 B.6, 作为对 PDSN向 PCRF发起的 GW控制和 QoS策略请求的 应答， PCRF将相应的 PCC策略下发到 PDSN。
步骤 B.7 , PDSN发送 RSVP Resvconf消息给 MS/AT。
步骤 B.8 , MA/AT, RAN/PCF, 以及 PDSN安装相应的 QoS, 分配资 源。
情况 B必须发生在步骤 11之后， 但是与情况 A没有必然的先后关系。 所以情况 B的执行过程中， IP-CAN会话 -1一直保留。
实施例四
本实施例中， PDSN在收到终端设备发送的 IPv6CP协商请求之后， 同 时与 PCRF建立 GW控制会话和 IP-CAN会话 -1 , PCRF确定是该两会话是 为同一个终端设备建立的与同一个 PDSN的会话或者根据携带关联地址（网 关控制会话的家乡地址和 IP-CAN会话 1中的转交地址）不同， 则 PCRF对 这两个会话独立处理， 不对其进行关联。
如果 PCRF收到了 HA/LMA发送的该终端设备的属于同一 IP连接的 IP-CAN会话 -2建立请求， PCRF将 PDSN请求的 GW控制会话和 HA/LMA 请求的 IP-CAN会话 -2关联， 并保留与 PDSN建立的 IP-CAN会话 -1。 如果 PDSN从 MS/AT发送来的 RSVP Resv消息中，解析出该消息携带 的终端 IP地址是 PDSN为 MS/AT分配的地址， 则 PDSN向 PCRF发起 IP-CAN会话 -1修改请求，请求相应的 PCC策略。 PCRF收到了 PDSN发送 来的 IP-CAN会话 -1的修改请求，则 PCRF为终端设备制定 PCC策略。 PDSN 向 PCRF发起 IP-CAN会话 -1修改请求的同时， 向 PCRF发送 "网关控制会 话终止" 消息， 请求终止 PDSN和 PCRF之间的网关控制会话， 并且如果 HA/LMA之间存在 IP-CAN会话 -2的情况下 , 该会话也会被 PCRF删除。
如果 PDSN从 MS/AT发送来的 RSVP Resv消息中，解析出该消息携带 的终端 IP地址（ HoA )不是 PDSN为 MS/AT分配的地址（ CoA ), 则 PDSN 向 PCRF发起 GW控制与 QoS策略请求，则 PCRF为终端设备制定 PCC策 略，且通过所述网关控制会话和与其关联的 IP-CAN会话分别向所述 PDSN 和所述 HA/LMA下发策略和计费控制 PCC策略。 PDSN向 PCRF发起 GW 控制与 QoS策略请求的同时，向 PCRF发送 IP-CAN会话 -1终止请求消息， 请求终止 PDSN和 PCRF之间的 IP-CAN会话 -1。
图 8为本发明策略和计费控制的方法实施例四的流程图， 如图 8所示， 本示例策略和计费控制的方法包括以下步骤：
步骤 1 , 主业务连接建立。
步骤 2, PPP会话的 LCP协商并选定鉴权方式。
步骤 3 , 通过步骤 2选定的鉴权方式完成用户的接入鉴权和授权。 其中 MS/AT与 PDSN互通相关的鉴权信令， PDSN和 AAA也通过接入请求和接 入应答执行鉴权的相关操作。 鉴权 /授权成功后， 相关的签约 QoS信息将会 从 AAA发送给 PDSN。
步骤 4, PDSN将签约的 QoS参数发送给 RAN。
步骤 5 , MS/AT和 PDSN执行 IPv6CP协商步骤。
协商过程中， PDSN还会把本地链路前缀发送给 MS/AT, MS/AT根据 此前缀生成单播地址， 该过程未在图中示出。 此外， 终端还要向 PDSN通 过 DHCP步骤获取自举（ bootstrap )信息， 流程图中未示出。
步骤 6, PDSN同时作为 BBERF和 PCEF向 PCRF发起 PCC会话， 具 体为：
6a, PDSN定位角色为 PCEF, 与 PCRF发起 IP-CAN会话 -1建立； 并 携带 PDSN为终端分配的 IP地址 ,该地址填写到 IP-CAN会话 HoA信元中 , IP-CAN会话中的 CoA信元信息空缺或者填写全零；
6b, PDSN定位角色为 BBERF, PDSN会发起同 PCRF的 GW会话建 立。 并携带 PDSN为终端分配的 IP地址， 该地址填写到网关控制会话的 HoA信元中。
该两个会话的建立未必一定发生在 IPv6CP协商完成后，只要 PDSN收 到 IPv6CP配置请求， 就可以发起该步骤， 而且这两个会话可以并行建立。
步骤 7, PCRF收到 PDSN 的 PCC会话建立请求， 与 PDSN分别建立 IP-CAN会话 -1 和 GW控制会话， 在判断该两个会话是来自同一个 PDSN 的会话、 且是为同一个 MS/AT服务时， 对该两个会话单独处理， 即不作关 联。
步骤 8, MS/AT发送 CMIPv6绑定更新请求消息给选定的 HA/LMA, 请求与 HA/LMA的绑定。
步骤 9, HA/LMA与 AAA互通鉴权信令， 完成对用户通过 CMIPv6接 入的鉴权和授权。
步骤 10, HA/LMA接收到绑定更新和授权成功后 , HA/LMA作为 PCEF 向 PCRF发起 IP-CAN会话 -2建立请求消息， PCRF向 HA/LMA/PCEF发送 IP-CAN会话 -2建立应答，完成 IP-CAN会话 -2的建立，并向 HA/LMA/PCEF 下载相关的 PCC策略。
步骤 11 , PCRF与 HA/LMA建立 IP-CAN会话 -2后， PCRF根据用户 标识、 PDN标识， IP地址等信息将 IP-CAN会话 -2与 "与 PDSN建立的 GW 控制会话"相关联， 同时 PCRF会单独维护与 PDSN建立的 "IP-CAN会话 -1" , 即保留 IP-CAN会话 -1。
步骤 12, HA/LMA发送 CMIPv6绑定应答消息给 MS/AT, MS/AT完成 通过 CMIPv6方式的接入。
以上步骤中， 有可能出现第 10步发生在第 6a、 6b之前的情况， 也就 是说 IP-CAN会话 -2先建立， IP-CAN-1会话和 GW控制会话后建立， 当然 也可能出现其他次序。 也就是说， 这三个会话的建立并没有严格的先后顺 序。 但是这不会影响该方案的执行， PCRF收到请求后， 并去检索已经存在 的会话， 如果符合关联条件， 就进行关联， 如果不符合关联条件， 就不关 联即可。
以下的步骤分情况 A和情况 B分别说明在接收到不同消息时， 任何进 行相应的处理。
情况 A, MS/AT用在步骤 5中 PDSN为其分配的地址（在 CMIP接入 时， 称作， 转交地址（CoA, Care of Address ), 在此只能叫^ U也址）通过 PDSN与外部网络互通数据业务， 并为此业务发起 QoS请求。 具体包括以 下步骤：
步骤 A.1 , MS/AT与 RAN/PCF执行 HRPD QoS建立。
步骤 A.2,对应步骤 A.1 ,如果有 Link Flow新建 /修改，对应在 RAN/PCF 与 PDSN之间也需要对应建立 /修改 A10连接，并将相应的请求的 QoS列表 发送给 PDSN„
步骤 A.3 , MS/AT发送 RSVP Resv消息给 PDSN, TFT通过该信令发 送给 PDSN, TFT中携带了 MS/AT的地址， 即为上行数据的源地址， 或者 该地址也可以由在 RSVP Resv消息单独携带给 PDSN。 该步骤为现有技术。
步骤 A.4, PDSN通过判断 RSVP Resv消息中带来的地址是之前 PDSN 为 MS/AT分配的地址， 判定当前 MS/AT釆用的是 SIPv6的接入模式， 于是 PDSN向 PCRF发起 IP-CAN会话 -1修改请求， PCRF收到 PDSN发送来 的 IP-CAN会话 -1修改请求， 制定相应的 PCC策略， 通过响应消息， 把对 应的策略下发到 PDSN。
步骤 A.5 , PDSN发送 RSVP预留配置 （Resvconf ) 消息给 MS/AT。 步骤 A.6, MA/AT、 RAN/PCF以及 PDSN安装相应的 QoS, 并分配资 源。
步骤 A.7, PDSN向 PCRF发起 IP-CAN会话 -1修改请求的同时 (步骤 A.4), PDSN向 PCRF发送网关控制会话释放消息 ,请求终止 PDSN和 PCRF 之间的网关控制会话， 并且如果 HA/LMA之间存在 IP-CAN会话 -2的情况 下， 该会话也会被 PCRF删除（ A.8 )。
如果情况 A发生在 11步之后 （如图示）， 则按上述描述处理； 情况还 可以反正在步骤 7之后， 步骤 10之前， 因此， 如果 PCRF在步骤 10之前 收到 A.4步， 则 PCRF和 PDSN只保存网关控制会话， 不对 IP-CAN会话 -2 处理（因为还没有建立）。
情况 B, MS/AT用在步骤 12中 HA/LMA为其分配的本地地址（ HoA, Home of Address )通过 HA/LMA与外部网络互通数据业务， 并为此业务发 起 QoS请求。 具体包括以下步骤：
步骤 B.1 , MS/AT与 RAN/PCF执行 HRPD QoS建立。
步骤 B.2, 对应步骤 B.1 , 如果有 Link Flow新建 /修改， RAN/PCF与 PDSN之间也需要对应建立 /修改 A10连接， 并将相应的请求的 QoS列表发 送给 PDSN。
步骤 B.3 , MS/AT发送 RSVP Resv消息给 PDSN, TFT通过该信令发 送给 PDSN, TFT中携带了 MS/AT的 HoA, 即为上行数据的源地址， 或者 该 HoA地址也可以由在 RSVP Resv消息单独携带给 PDSN。 该步骤为现有 技术。
步骤 B.4, PDSN通过判断 RSVP Resv消息中带来的地址（ HoA )不是 之前 PDSN 为 MS/AT 分配的地址（CoA ) , 判定当前 MS/AT 釆用的是 CMIPv6的接入模式， 于是 PDSN向 PCRF发起 GW控制和 QoS策略请求； PCRF收到 PDSN发送来的 GW控制和 QoS策略请求后， 制定相应的 PCC 策略通过该网关控制会话和与之关联的 IP-CAN会话 -2分别下发到 PDSN 和 HA/LMA。
步骤 B.5 , PCRF收到 GW控制和 QoS策略请求后，制定对应的 IP-CAN 会话策略， 并通过 IP-CAN会话 -2下发到 HA/LMA.
步骤 B.6, 作为对 PDSN向 PCRF发起的 GW控制和 QoS策略请求的 应答， PCRF将相应的 PCC策略下发到 PDSN。
步骤 B.7 , PDSN发送 RSVP Resvconf消息给 MS/AT。
步骤 B.8 , MA/AT, RAN/PCF, 以及 PDSN安装相应的 QoS, 分配资 源。
步骤 B.9, PDSN向 PCRF发起 GW控制和 QoS策略请求的同时 (步骤 B.4), PDSN向 PCRF发送 IP-CAN会话 -1释放请求，请求终止 PDSN和 PCRF 之间的 IP-CAN会话 -1。
情况 B必须发生在步骤 11之后， 但是与情况 A没有必然的先后关系。 所以情况 B的执行过程中， IP-CAN会话 -1一直保留。
本发明策略和计费控制的系统包括包含终端设备 MS/AT, PDSN, PCRF 和 HA/LMA等网元， 上述网元的功能及其连接关系， 具体参见相关网络协 议， 并结合图 1、 图 2所示而理解， 这里不再详细赘述其结构及功用； 本发 明策略和计费控制的系统正是在图 1及图 2所示系统的基础上而提出的， 并且， 各网元及其连接关系与现有相关系统中的连接关系完全相同， 所不 同的是部分网元所实现的功能， 以下详细介绍之。 在终端设备在通过 ΜΙΡνό接入 cdma系统时，
PDSN, 用于与 PCRF建立网关控制会话和第一 IP-CAN会话；
HA , 用于与所述 PCRF建立第二 IP-CAN会话；
PCRF, 用于与 PDSN建立网关控制会话和第一 IP-CAN会话， 与 HA 建立第二 IP-CAN会话；
PCRF进一步用于， 关联所述网关控制会话和所述第二 IP-CAN会话。 上述 PCRF进一步在满足以下条件之一时， 不关联所述网关控制会话 和所述第一 IP-CAN会话：
所述网关控制会话和所述第一 IP-CAN会话属于同一个终端设备且属 于同一个 PDSN;
网关控制会话的家乡地址和第一 IP-CAN会话的转交地址不同。
PDSN进一步在终端设备向 PDSN协商点到点协议 PPP会话时 /后 , 或 者终端设备请求自举信息后， 与 PCRF建立所述第一 IP-CAN会话。
PDSN进一步在终端设备与 PDSN协商 PPP会话时 /后， 与 PCRF建立 所述网关控制会话；
HA进一步在接收到绑定更新消息并由 AAA服务器授权后， 与 PCRF 建立所述第二 IP-CAN会话；
PCRF进一步根据终端设备标识， 和 /或分组数据网标识， 和 /或 IP地址 关联所述的网关控制会话和第二 IP-CAN会话。
上述第一 IP-CAN会话为终端设备经 PDSN与分组数据网络进行通信时 提供策略；
第二 IP-CAN会话和网关控制会话为终端设备经 HA与分组数据网络进 行通信时提供策略。
本领域技术人员应当理解， 本领域技术人员应当理解， 本发明策略和 计费控制的系统是为实现前述的策略和计费控制的方法而设置的， 图中各 相关网元所实现功能可参照前述方法的相关描述而理解。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、 一种策略和计费控制的方法， 其特征在于， 所述方法包括： 终端设备在通过移动 IP版本 6 ΜΙΡνό接入码分多址 cdma系统时， 分 组数据服务节点 PDSN与策略控制规则功能实体 PCRF分别建立网关控制 会话和第一 IP连接接入网络 IP-CAN会话；
归属代理 HA与所述 PCRF建立第二 IP-CAN会话；
所述 PCRF关联所述网关控制会话和所述第二 IP-CAN会话。
2、 根据权利要求 1所述的方法， 其特征在于， 所述方法还包括： 所述 PCRF在满足以下条件之一时， 不关联所述网关控制会话和所述 第一 IP-CAN会话：
所述网关控制会话和所述第一 IP-CAN会话属于同一个终端设备且属 于同一个 PDSN;
网关控制会话的家乡地址和第一 IP-CAN会话的转交地址不同。
3、 根据权利要求 1所述的方法， 其特征在于， 终端设备向 PDSN协商 点到点协议 PPP会话时 /后，或者终端设备请求自举信息后， PDSN与 PCRF 建立所述第一 IP-CAN会话。
4、 根据权利要求 1所述的方法， 其特征在于， 终端设备与 PDSN协商 PPP会话时 /后， PDSN与 PCRF建立所述网关控制会话；
HA收到绑定更新消息并由认证授权计费服务器 AAA授权后， HA与 PCRF建立所述第二 IP-CAN会话；
所述 PCRF根据终端设备标识，和 /或分组数据网标识，和 /或 IP地址关 联所述的网关控制会话和第二 IP-CAN会话。
5、 根据权利要求 1所述的方法， 其特征在于， 所述第一 IP-CAN会话 为终端设备经 PDSN与分组数据网络进行通信时提供策略；
第二 IP-CAN会话和网关控制会话为终端设备经 HA与分组数据网络进 行通信时提供策略。
6、 根据权利要求 1所述的方法， 其特征在于， 所述方法还包括： 所述 PDSN在收到资源预留请求时， 根据终端设备的地址决定是通过 网关控制会话或者第一 IP-CAN会话请求 PCC策略。
7、 根据权利要求 6所述的方法， 其特征在于， 所述方法还包括： 所述 PDSN判断所述终端设备的地址是所述 PDSN为该终端设备分配 的地址时 , 通过所述第一 IP-CAN会话向所述 PCRF请求 PCC策略；
所述 PDSN判断所述终端设备的地址不是所述 PDSN为该终端设备分 配的地址时， 通过所述网关控制会话向所述 PCRF请求 PCC策略。
8、 根据权利要求 7所述的方法， 其特征在于， 所述方法还包括： 所述 PDSN通过所述第一 IP-CAN会话向所述 PCRF请求 PCC策略后 , 向所述 PCRF发起删除所述网关控制会话的请求；
所述 PDSN通过所述网关控制会话向所述 PCRF请求 PCC策略后， 向 所述 PCRF发起删除所述第一 IP-CAN会话的请求。
9、一种策略和计费控制的系统， 包含终端设备、 PDSN, PCRF和 HA; 其特征在于，
在终端设备在通过 ΜΙΡνό接入 cdma系统时，
PDSN, 用于与 PCRF建立网关控制会话和第一 IP-CAN会话；
HA , 用于与所述 PCRF建立第二 IP-CAN会话；
PCRF, 用于与 PDSN建立网关控制会话和第一 IP-CAN会话， 与 HA 建立第二 IP-CAN会话；
PCRF进一步用于， 关联所述网关控制会话和所述第二 IP-CAN会话。
10、 根据权利要求 9所述的系统， 其特征在于， 所述 PCRF进一步在 满足以下条件之一时， 不关联所述网关控制会话和所述第一 IP-CAN会话： 所述网关控制会话和所述第一 IP-CAN会话属于同一个终端设备且属 于同一个 PDSN;
网关控制会话的家乡地址和第一 IP-CAN会话的转交地址不同。
11、 根据权利要求 9所述的系统， 其特征在于， PDSN进一步在终端设 备向 PDSN协商点到点协议 PPP会话时 /后，或者终端设备请求自举信息后， 与 PCRF建立所述第一 IP-CAN会话。
12、 根据权利要求 9所述的系统， 其特征在于， PDSN进一步在终端 设备与 PDSN协商 PPP会话时 /后， 与 PCRF建立所述网关控制会话；
HA进一步在接收到绑定更新消息并由 AAA服务器授权后， 与 PCRF 建立所述第二 IP-CAN会话；
PCRF进一步根据终端设备标识， 和 /或分组数据网标识， 和 /或 IP地址 关联所述的网关控制会话和第二 IP-CAN会话。
13、根据权利要求 9所述的系统， 其特征在于， 所述第一 IP-CAN会话 为终端设备经 PDSN与分组数据网络进行通信时提供策略；
第二 IP-CAN会话和网关控制会话为终端设备经 HA与分组数据网络进 行通信时提供策略。
PCT/CN2011/072362 2010-04-20 2011-03-31 策略和计费控制的方法及系统 WO2011131082A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010153023.8 2010-04-20
CN201010153023.8A CN102238237B (zh) 2010-04-20 2010-04-20 策略和计费控制会话的建立方法及系统

Publications (1)

Publication Number Publication Date
WO2011131082A1 true WO2011131082A1 (zh) 2011-10-27

Family

ID=44833695

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/072362 WO2011131082A1 (zh) 2010-04-20 2011-03-31 策略和计费控制的方法及系统

Country Status (2)

Country Link
CN (1) CN102238237B (zh)
WO (1) WO2011131082A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101227391A (zh) * 2008-01-09 2008-07-23 中兴通讯股份有限公司 非漫游场景下策略和计费规则功能实体的选择方法
WO2009100177A1 (en) * 2008-02-06 2009-08-13 Qualcomm Incorporated Mobile ip multiple registrations and pcc interactions
CN101588326A (zh) * 2009-06-15 2009-11-25 华为技术有限公司 网关控制会话和Gx会话关联的方法、设备和系统
CN101662415A (zh) * 2008-08-29 2010-03-03 华为技术有限公司 一种策略控制方法及通讯系统以及相关设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101227391A (zh) * 2008-01-09 2008-07-23 中兴通讯股份有限公司 非漫游场景下策略和计费规则功能实体的选择方法
WO2009100177A1 (en) * 2008-02-06 2009-08-13 Qualcomm Incorporated Mobile ip multiple registrations and pcc interactions
CN101662415A (zh) * 2008-08-29 2010-03-03 华为技术有限公司 一种策略控制方法及通讯系统以及相关设备
CN101588326A (zh) * 2009-06-15 2009-11-25 华为技术有限公司 网关控制会话和Gx会话关联的方法、设备和系统

Also Published As

Publication number Publication date
CN102238237A (zh) 2011-11-09
CN102238237B (zh) 2015-07-22

Similar Documents

Publication Publication Date Title
EP3454601B1 (en) Method and apparatus for controlling quality of service
US8537781B2 (en) Low latency handover between wireless communication networks using different radio access technologies
EP2863683B1 (en) Data flow control method and corresponding apparatus and communications system
WO2010081329A1 (zh) 业务流迁移过程中对网络资源进行控制的方法和系统
CN104854576A (zh) 接入网络的系统和方法
WO2011134329A1 (zh) 一种小数据包传输的方法和系统
WO2010063175A1 (zh) 实现数据网关切换的方法、装置和系统
WO2009024048A1 (en) A method, network system, pdn gw and accounting system for managing accounting
US9544832B2 (en) Method, apparatus and system for policy control
WO2009059544A1 (fr) Procédé, dispositif et système permettant de mettre en œuvre la commutation entre des réseaux
WO2013189217A1 (zh) 分组网关标识信息的更新方法、aaa服务器和分组网关
US20130094487A1 (en) Method and System for Information Transmission
CN111511042B (zh) 用于在无线通信系统中生成连接的方法和装置
WO2011047589A1 (zh) 网络连接建立方法及装置、pcc策略制定方法及系统
WO2011147074A1 (zh) 策略与计费控制的实现方法、系统及相应设备
KR102017167B1 (ko) 무선 통신 시스템에서 데이터 트래픽 분산을 위한 방법 및 장치
WO2012062183A1 (zh) 一种实现数据流服务质量和计费策略控制的方法及系统
WO2012126291A1 (zh) 一种数据路由方法及系统
WO2008009233A1 (fr) Procédé et système d'établissement de classificateur de flux prédéfini et terminal utilisateur associé
WO2009018777A1 (fr) Procédé et appareil de distribution et de transfert d'une identité de support dans un réseau évolué
WO2013174190A1 (zh) 路由选择方法及功能网元
WO2010111944A1 (zh) 释放接入连接的方法、装置、策略控制实体及系统
WO2013016967A1 (zh) 一种接入方法、系统及移动智能接入点
WO2011017979A1 (zh) 支持ip分流的通信系统中资源管理方法与装置
WO2011134102A1 (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: 11771535

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

Country of ref document: EP

Kind code of ref document: A1