CN102238237A

CN102238237A - Method and system for establishing policy and charging control session

Info

Publication number: CN102238237A
Application number: CN2010101530238A
Authority: CN
Inventors: 毕以峰; 毛玉欣
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2010-04-20
Filing date: 2010-04-20
Publication date: 2011-11-09
Anticipated expiration: 2030-04-20
Also published as: CN102238237B; WO2011131082A1

Abstract

The invention discloses a method for establishing a policy and charging control session. The method comprises the following steps: after finishing negotiation of an Internet protocol version 6 control protocol (IPv6CP) with terminal equipment, a packet data serving node (PDSN) establishes a gateway control session and a first Internet protocol-connectivity access network (IP-CAN) session with a policy control rule enforcement function (PCRF) respectively; and when determining that the gateway control session and the first IP-CAN session are sessions established for the same terminal equipment, the PCRF separately processes the gateway control session and the first IP-CAN session. The invention further discloses a system for establishing the policy and charging control session. In the invention, the type of an interface between the PDSN and the PCRF can be determined according to the type of a session established by using the terminal equipment, so that the terminal equipment can accurately access a network in time.

Description

The method for building up and the system of strategy and charging controlled session

Technical field

The present invention relates to strategy and the technology of setting up of control (PCC, the Policy and Charging Control) session of chargeing, relate in particular to the method for building up and the system of strategy and charging controlled session in a kind of code division multiple access system.

Background technology

Fig. 1 is code division multiple access (CDMA, Code Division Multiple Access) 2000 1x and HRPDPDS subnetwork reference model schematic diagram, as shown in Figure 1, third generation partner program 2 (3GPP2,3rd Generation Partnership Project2) Ding Yi code division multiple access (CDMA, Code DivisionMultiple Access) 2000 1x and HRPD (high rate packet data) (HRPD, High Rate Packet Data) network architecture, mainly by travelling carriage (MS, Mobile Station)/access terminal equipment (AT, AccessTerminal), Radio Access Network (RAN, Radio Access Network), packet data serving node (PDSN, Packet Data Serving Node), home agent (HA, Home Agent)/local mobile anchor (LMA, Local Mobility Anchor), (the RADIUS of remote customer dialing authentication system, RemoteAuthentication Dial In User Service)/authentication and authorization charging server (AAA, AuthenticationAuthorization Accounting) and other core network devices and support node composition.Wherein, MS/AT realizes being connected with RAN by wave point.RAN comprises base station (BS, Base Station) and Packet Control Function (PCF, Packet Control Function), and wherein BS is mainly used in the sub-district and sets up wireless coverage, and the air interface of Packet data service is provided for terminal equipment; PCF is mainly used in the control wireless network resource, transmits the message between wireless system and the PDSN packet control unit.

PDSN is that terminal equipment is provided to Internet or application server or to the access of HA/LMA, its effect is to set up, safeguard peer-peer protocol (PPP, the Pointto Point Protocol) session between MS/AT and the PDSN by RAN; Accept and carry out of the authentication of RADIUS/AAA server to MS/AT; Route from packet that mails to packet data network or HA/LMA etc.

HA/LMA is responsible under the mobile IP scene, for the terminal equipment assignment of home address, transmit the tunnel encapsulation of uplink and downlink packet, packet etc., wherein mobile IP comprises client mobile IP edition 4 or version 6 (CMIPv4/v6, Client Mobile IP version 4/version 6) and proxy-mobile IP edition 4 or version 6 (PMIPv4/v6, Proxy Mobile IPv4/v6).

Authenticated/authorized/charging (AAA, Authentication, Authorization, Accounting) server (is called remote customer dialing authentication (RADIUS again, Remote Authentication Dial In UserService) be authentication and authorization charging server server), it mainly acts on is which user of management can accesses network, which service user with access right can obtain, and how the user who uses Internet resources is chargeed etc.

As shown in Figure 1, cdma network can realize that reasonable resources is distributed and control by the PCC technology.Because terminal equipment is when inserting cdma system, can insert by multiple access module, such as simple IP v4/v6 (SIPv4/v6, Simple IPv4/v6), PMIPv4/v6, CMIPv4/v6 etc., under different access modules, the role that network side related network elements such as PDSN, HA/LMA serve as in the PCC technology and the function of execution also are different.Summarize, when subscriber terminal equipment inserts by SIPv4/v6, entity (PCEF is carried out in the control of PDSN implementation strategy, Policy Control Enforcement Function) function, there is not HA/LMA in the network, no bearing binding and time report entity (BBERF, Bearer Binding andEvent Trigger Report Function); PDSN/PCEF and policy control rule entity (PCRF, PolicyControl Rule Function) transmit relevant policy information by the Gx interface.Fig. 2 is that terminal equipment MS/AT inserts and set up the Organization Chart of PCC session by CMIPv6, as shown in Figure 2, when subscriber terminal equipment passes through PMIPv4/v6, when CMIPv4/v6 inserts, PDSN carries out the BBERF function, set up gateway control session (GW control session) and transmit relevant policy information by Gxa with PCRF, HA/LMA carries out the function of PCEF, set up IP with PCRF by the Gx mouth and be connected access network (IP-CAN, IP-Connectivity Access Network) session, and the relevant policy information of transmission, gateway control session and IP-CAN session association that the same IP that PCRF will belong to same terminal connects (IP Anknupfungskeregriff see below explanations) arrive together, when formulating the PCC strategy, formulate together, and be issued to PDSN and HA/LMA respectively, finish the resource that the same IP of same terminal is connected and the control of chargeing.So-called PCRF does these two sessions related, existing mechanism is: PCRF receives first conversation request (such as the gateway control session request), PCRF accepts, then this session is set up and is finished, if PCRF receives another session foundation request (such as the IP-CAN conversation request) again, PCRF then takes the context parameters of parameter that this IP-CAN conversation request carries and the gateway control session of having set up to contrast, if finding these two sessions is the sessions that belong to same terminal, same IP connection, then these two replies are associated.

Under different access modules, terminal can be set up different IP connection procedures.Wherein, IP connects and to be meant that terminal obtained the IP address of network side for its distribution/configuration, and utilizes this address to be connected to a kind of association of network, visited network side resource.A terminal can have a plurality of IP simultaneously and connect, such as terminal can be set up being connected of SIPv6 and CMIPv6 simultaneously.In different IP connected, each network element serves as the role when adopting the PCC technology also different with the execution function, provided the detailed step analysis of SIPv6 and two kinds of IP connection building process of CMIPv6 below, and drawn potential problem.

To be terminal equipment MS/AT insert and set up the flow chart of PCC session by SIPv6 Fig. 3, and as shown in Figure 3, MS/AT specifically may further comprise the steps by the flow process that SIPv6 inserts:

Step 1, main business connect to be set up.

Step 2, the LCP of PPP session (LCP, Link Control Protocol) is consulted and selected authentication mode.

Step 3 is finished user's access authentication and mandate by authentication mode selected in the step 2.The authentication signaling that wherein MS/AT is relevant with the PDSN intercommunication, PDSN and AAA are also by inserting request and inserting and reply the associative operation of carrying out authentication.After the authentication/authorize successfully, relevant signatory service quality (QoS, Quality of Service) information will send to PDSN from AAA.

Step 4, PDSN sends to RAN with signatory qos parameter.

Step 5, MS/AT and PDSN carry out IP version 6 control protocols (IPv6CP, IP Version 6Control Protocol) negotiation step.

In the negotiations process, PDSN also can send to MS/AT to link-local (HL, Home Link) prefix, and MS/AT generates unicast address according to this prefix, and this process does not illustrate in the drawings.

Step 6, PDSN initiates IP-CAN session establishment step to PCRF for this MS/AT as PCEF.Wherein, PDSN/PCEF has carried IP and has connected access network (IP-CAN in this message, IP-Connectivity Access Network) information such as type, Terminal Equipment Identifier, packet data network (PDN, Packet Data Network) sign, terminal device IP address.

Because PDSN is the IP-CAN session as PCEF and PCRF foundation, the employing of the interface between PDSN and the PCRF is the Gx mouth.

This step may not necessarily occur in IPv6CP consult to finish after, as long as PDSN receives the IPv6CP configuring request, just can initiate this step.

Step 7, PCRF sends IP-CAN session foundation and replys to PDSN/PCEF.PCRF provides PCC rule and incident option etc. by the IP-CAN session to PCEF.

To be terminal equipment MS/AT insert and set up the flow chart of PCC session by CMIPv6 Fig. 4, as shown in Figure 4.MS/AT specifically may further comprise the steps by the CMIPv6 access process:

Step 1, main business connect to be set up.

Step 2, the LCP of PPP session consults and selectes authentication mode.

Step 3 is finished user's access authentication and mandate by the authentication mode that step 2 is selected.The authentication signaling that wherein MS/AT is relevant with the PDSN intercommunication, PDSN and AAA are also by inserting request and inserting and reply the associative operation of carrying out authentication.After the authentication/authorize successfully, relevant signatory QoS information will send to PDSN from AAA.

Step 4, PDSN sends to RAN with signatory qos parameter.

Step 5, MS/AT and PDSN carry out the IPv6CP negotiation step.

Step 6, PDSN initiates gateway (GW, Gateway) control session establishment step to PCRF for this MS/AT as BBERF.Wherein PDSN/BBERF has carried information such as conversation type, Terminal Equipment Identifier, PDN sign, terminal device IP address in this message.

Because PDSN is the GW control session as BBERF and PCRF foundation, so the employing of the interface between PDSN and the PCRF is the Gxa interface.

Step 7, PCRF sends IP-CAN session foundation and replys to PDSN/BBERF.

Step 8, MS/AT sends CMIPv6 Binding Update request message to selected HA/LMA, the binding of request and HA/LMA.

Step 9, HA/LMA and AAA intercommunication authentication signaling are finished authentication and mandate that the user is inserted by CMIPv6.

Step 10, HA/LMA initiates the IP-CAN session as PCEF to PCRF and sets up request.

Step 11, PCRF sends IP-CAN session foundation to HA/LMA/PCEF and replys, and finishes the foundation of IP-CAN session, and downloads relevant PCC strategy to HA/LMA/PCEF.

Step 12, HA/LMA sends CMIPv6 binding response message to MS/AT, and MS/AT finishes the access by the CMIPv6 mode.

By analyzing above-mentioned two flow processs as Fig. 2 and Fig. 4, promptly MS/AT inserts by SIPv6 and the CMIPv6 access time, the first five step be step 1 to the operation of step 5 all be identical, without any difference.But PDSN but is distinguishing in follow-up operation, and when inserting by SIPv6, the role of PDSN is PCEF, and sets up the IP-CAN session with PCRF by the Gx interface; When inserting by CMIPv6, the role of PDSN is BBERF, and sets up GW control session with PCRF by the Gxa interface; Because which kind of access way MS/AT is based on earth, whether initiating binding with HA/LMA until follow-up MS/AT could determine, but PDSN need will select function corresponding and role according to the access way of MS/AT in advance, because the session that PDSN and PCRF are set up, the interface of employing are different.Above-mentioned Fig. 2 and MS/AT access way shown in Figure 4 can not determine in advance obviously the role of PDSN also just to can not determine the interface type between PDSN and the PCRF that this can influence MS/AT undoubtedly and accurately and timely be linked into network.

Summary of the invention

In view of this, main purpose of the present invention is to provide the method for building up and the system of a kind of strategy and charging controlled session, can when the session that PDSN and PCRF set up, determine function and the identity of PDSN, thereby can determine PDSN and PCRF sets up the selected interface type of session.

For achieving the above object, technical scheme of the present invention is achieved in that

The method for building up of a kind of strategy and charging controlled session, described method comprises:

When packet data serving node PDSN and terminal equipment are consulted IP version 6 control protocol IPv6CP/after, set up gateway control session respectively with policy control rule entity PCRF and be connected access network IP-CAN session with an IP;

Described PCRF determines that a described gateway control session and a described IP-CAN session are during for the session that set up and same PDSN of same terminal equipment, a described gateway control session of individual processing and a described IP-CAN session.

Preferably, described method also comprises:

Described PDSN is by gateway control session or IP-CAN conversation request PCC strategy according to the decision of the address of terminal equipment when receiving resource reservation request.

Preferably, described method also comprises:

Described PDSN judges when the address of described terminal equipment is described PDSN for this terminal equipment addresses distributed, by a described IP-CAN session to described PCRF request PCC strategy;

Described PDSN judges when the address of described terminal equipment is not described PDSN for this terminal equipment addresses distributed, by described gateway control session to described PCRF request PCC strategy.

Preferably, described method also comprises:

Described PDSN behind described PCRF request PCC strategy, initiates the request of the described gateway control session of deletion by a described IP-CAN session to described PCRF;

Described PDSN behind described PCRF request PCC strategy, initiates the request of the described IP-CAN session of deletion by described gateway control session to described PCRF.

Preferably, a described gateway control session of described individual processing and a described IP-CAN session, for:

Described PCRF receives the IP-CAN session that belongs to same IP connection of the described terminal equipment of home agent HA/local mobile anchor LMA transmission and sets up when asking, with the IP-CAN session association of described gateway control session and described HA/LMA request, and discharge a described IP-CAN session.

During a described IP-CAN session modification request that described PCRF receives that described PDSN sends, keep and revise a described IP-CAN session, discharge the gateway control session of setting up with described PDSN by described modification request.

Described PCRF receives the IP-CAN session that belongs to same IP connection of the described terminal equipment of HA/LMA transmission and sets up when asking, and with the IP-CAN session association of described gateway control session and described HA/LMA request, and keeps a described IP-CAN session.

Preferably, after the IP-CAN session association with described gateway control session and described HA/LMA request, also comprise:

When described PCRF receives gateway control that described PDSN sends and quality of service policy request, described PCRF is that described terminal equipment is generated strategy and the charging control PCC strategy, and keep a described IP-CAN session, and issue described PCC strategy to described PDSN and described HA/LMA respectively with the IP-CAN session related with this gateway control session by described gateway control session.

When described PCRF receives the modification request of the described IP-CAN session that described PDSN sends, for described terminal equipment is formulated the PCC strategy, issue the PCC strategy by a described IP-CAN session to described PDSN, and keep the IP-CAN session of gateway control session and described HA/LMA request.

When described PCRF receives the modification request of the described IP-CAN session that described PDSN sends, for described terminal equipment is formulated the PCC strategy, when having the IP-CAN session of HA/LMA request, keep the IP-CAN session of described HA/LMA request, do not deal with when not existing.

Preferably, described method also comprises:

When described PDSN determines to set up a described IP-CAN session, set up by the Gx interface with described PCRF.

Preferably, described method also comprises:

When described PDSN determines to set up the IP-CAN session related with described gateway control session, set up by the Gxa interface with described PCRF.

The system that sets up of a kind of strategy and charging controlled session comprises terminal equipment, PDSN, PCRF and HA/LMA; Described system comprises that negotiation element, session set up unit, determining unit and session processing unit; Wherein:

Negotiation element is used for consulting IPv6CP between PDSN and terminal equipment;

The unit is set up in session, be used for when described negotiation element is consulted IPv6CP/after, set up gateway control session respectively with PCRF and be connected access network IP-CAN session with an IP;

Determining unit, be used for determining a described gateway control session and a described IP-CAN session be set up for same terminal equipment with same PDSN session the time, the triggering session processing unit;

The session processing unit is used for a described gateway control session of individual processing and a described IP-CAN session.

Preferably, described system also comprises: judging unit, be used at PDSN when receiving resource reservation request, and be by gateway control session or IP-CAN conversation request PCC strategy according to the decision of the address of terminal equipment.

Preferably, described judging unit further judges that the address of described terminal equipment is described PDSN during for this terminal equipment addresses distributed, by a described IP-CAN session to described PCRF request PCC strategy;

The address of further judging described terminal equipment is not described PDSN during for this terminal equipment addresses distributed, by described gateway control session to described PCRF request PCC strategy.

Preferably, described system also comprises:

Transmitting element when being used at described judging unit by a described IP-CAN session to described PCRF request PCC strategy, is initiated the request of the described gateway control session of deletion to described PCRF;

During to described PCRF request PCC strategy, initiate the request of the described IP-CAN session of deletion by described gateway control session to described PCRF at described judging unit.

Preferably, described session processing unit, further when request is set up in the IP-CAN session of belonging to of the described terminal equipment that receives the HA/LMA transmission of same IP connection,, and discharge a described IP-CAN session with the IP-CAN session association of described gateway control session and described HA/LMA request.

Preferably, described session processing unit further when a described IP-CAN session modification request that receives that described PDSN sends, keeps and revises a described IP-CAN session by described modification request, discharges the gateway control session of setting up with described PDSN.

Preferably, described session processing unit, further when request is set up in the IP-CAN session of belonging to of the described terminal equipment that receives the HA/LMA request of same IP connection,, and keep a described IP-CAN session with the IP-CAN session association of described gateway control session and described HA/LMA request.

Preferably, after the IP-CAN session association of described session processing unit with described gateway control session and described HA/LMA request, when receiving gateway control that described PDSN sends and quality of service policy request, be that described terminal equipment is formulated the PCC strategy further according to the CMIPv6 pattern, and keep a described IP-CAN session, and issue the PCC strategy to described PDSN and described HA/LMA respectively with the IP-CAN session related with this gateway control session by described gateway control session.

Preferably, after the IP-CAN session association of described session processing unit with described gateway control session and described HA/LMA request, when receiving the modification request of the described IP-CAN session that described PDSN sends, further be that described terminal equipment is formulated the PCC strategy, issue the PCC strategy by a described IP-CAN session to described PDSN, and keep the IP-CAN session of gateway control session and described HA/LMA request.

Preferably, described session processing unit, further when the modification request of a described IP-CAN session that receives described PDSN transmission, according to the SIPv6 pattern is that described terminal equipment is formulated the PCC strategy, when having the IP-CAN session of HA/LMA request, keep the IP-CAN session of described HA/LMA request, do not deal with when not existing.

Preferably, the unit is set up in described session, when further determining to set up a described IP-CAN session, sets up by the Gx interface between described PDSN and described PCRF.

Preferably, the unit is set up in described session, when further determining to set up the IP-CAN session related with described gateway control session, sets up by the Gxa interface between described PDSN and described PCRF.

Among the present invention, when between PDSN and terminal equipment, finishing the IPv6CP negotiation/after, to set up a GW control session and an IP-CAN session simultaneously, PCRF is with above-mentioned two sessions of the same terminal equipment of individual processing as the case may be, concrete, PCRF receives the IP-CAN session of this terminal equipment of HA/LMA transmission and sets up when asking, and GW is controlled the IP-CAN session association of session and HA/LMA request, and discharge an IP-CAN session; Perhaps, when P CRF receives an IP-CAN session modification request of described PDSN transmission, keep an IP-CAN session, discharge the GW control session of setting up with described PDSN.Perhaps, keep an above-mentioned GW control session and an IP-CAN session simultaneously, and safeguard it respectively, determine interface between PDSN and the PCRF according to corresponding session.The present invention can determine interface type between PDSN and the PCRF according to the conversation type that terminal equipment is set up, thereby can guarantee that terminal equipment accurately and timely is linked into network.

Description of drawings

Fig. 1 is CDMA2000 1x and HRPD PDS subnetwork reference model schematic diagram;

Fig. 2 is that terminal equipment MS/AT inserts and set up the Organization Chart of PCC session by CMIPv6;

Fig. 3 is that terminal equipment MS/AT inserts and set up the flow chart of PCC session by SIPv6;

Fig. 4 is that terminal equipment MS/AT inserts and set up the flow chart of PCC session by CMIPv6;

Fig. 5 is the flow chart of the method for building up embodiment one of strategy of the present invention and charging controlled session;

Fig. 6 is the flow chart of the method for building up embodiment two of strategy of the present invention and charging controlled session;

Fig. 7 is the flow chart of the method for building up embodiment three of strategy of the present invention and charging controlled session;

Fig. 8 is the flow chart of the method for building up embodiment four of strategy of the present invention and charging controlled session;

Fig. 9 is a kind of composition structural representation of the system that sets up of strategy of the present invention and charging controlled session;

Figure 10 forms structural representation for the another kind of the system that sets up of strategy of the present invention and charging controlled session.

Embodiment

Basic thought of the present invention is: when between PDSN and terminal equipment, finishing the IPv6CP negotiation/after, to set up a GW control session and an IP-CAN session simultaneously, PCRF will be as the case may be the same terminal equipment of individual processing with above-mentioned two sessions same PDSN, concrete, PCRF receives the IP-CAN session that belongs to same IP connection of this terminal equipment of HA/LMA transmission and sets up when asking, GW is controlled the IP-CAN session association of session and HA/LMA request, and discharge an IP-CAN session; Perhaps, when PCRF receives an IP-CAN session modification request of described PDSN transmission, keep also and revise request modification the one IP-CAN session, discharge the GW control session of setting up with described PDSN by this.Perhaps, keep an above-mentioned GW control session and an IP-CAN session simultaneously, and safeguard it respectively, determine interface between PDSN and the PCRF according to corresponding session.

For making the purpose, technical solutions and advantages of the present invention clearer, by the following examples and with reference to accompanying drawing, the present invention is described in more detail.

Embodiment one

In the present embodiment, after PDSN received the IPv6CP configuring request that terminal equipment MS/AT sends, PDSN set up GW control session and IP-CAN session-1 with PCRF simultaneously; After PCRF received the session foundation request of PDSN transmission, if determine that these two sessions are is the session that same terminal equipment and same PDSN set up, then PCRF did not do association to these two session independent process.If PCRF has received the IP-CAN session-2 foundation request of this terminal equipment that HA/LMA sends, PCRF thinks that the access module of this terminal equipment is CMIPv6, PCRF is related with the IP-CAN session-2 of HA/LMA request with the GW control session of PDSN request, and the IP-CAN session-1 that PDSN sends is discharged.Follow-up operation is carried out according to prior art and is got final product.

Fig. 5 is the flow chart of the method for building up embodiment one of strategy of the present invention and charging controlled session, and as shown in Figure 5, the method for building up of this example policy and charging controlled session may further comprise the steps:

Step 1, main business connect to be set up.

Step 2, the LCP of PPP session consults and selectes authentication mode.

Step 3 is finished user's access authentication and mandate by authentication mode selected in the step 2.The authentication signaling that wherein MS/AT is relevant with the PDSN intercommunication, PDSN and AAA are also by inserting request and inserting and reply the associative operation of carrying out authentication.After the authentication/authorize successfully, relevant signatory QoS information will send to PDSN from AAA.

Step 4, PDSN sends to RAN with signatory qos parameter.

Step 5, MS/AT and PDSN carry out the IPv6CP negotiation step.

In the negotiations process, PDSN also can send to MS/AT to the link-local prefix, and MS/AT generates unicast address according to this prefix, and this process does not illustrate in the drawings.

Step 6, PDSN initiates the PCC session as BBERF and PCEF to PCRF simultaneously, is specially:

6a, PDSN location role is PCEF, initiates IP-CAN session-1 with PCRF and sets up;

6b, PDSN location role is BBERF, PDSN can initiate to set up with the GW session of PCRF.

The foundation of these two sessions may not necessarily occur in IPv6CP consult to finish after, as long as PDSN receives the IPv6CP configuring request, just can initiate this step, and these two sessions foundation that can walk abreast.

Step 7, PCRF receives the PCC session request of setting up of PDSN, and sets up IP-CAN session-1 and GW control session respectively with PDSN, is judging that these two sessions are from the session of same PDSN and are during for same MS/AT service, to these two session individual processing, promptly do not do association.

Step 9, HA/LMA and AAA intercommunication authentication signaling are finished authentication and mandate that terminal equipment is inserted by CMIPv6.

Step 10, HA/LMA initiates IP-CAN session-2 as PCEF to PCRF and sets up request, and PCRF sends IP-CAN session-2 foundation to HA/LMA/PCEF and replys, and finishes the foundation of IP-CAN session-2, and downloads relevant PCC strategy to HA/LMA/PCEF.

Step 11, after PCRF and HA/LMA set up IP-CAN session-2, PCRF was associated IP-CAN session-2 with " controlling session with the GW that PDSN sets up ", simultaneously, PCRF can conclude that current access module is CMIPv6, and PCRF can discharge with PDSN and set up " IP-CAN session-1 ".At this moment, PDSN role is BBERF, and it is by setting up corresponding IP-CAN session between Gxa interface and the PCRF.

Step 13 is tightly held step 11, and PCRF initiates " IP-CAN session-1 " releasing operation, discharges IP-CAN session-1.

In the above step, the 10th step might occur for to occur in situation before 6a, the 6b, that is to say that IP-CAN session-2 sets up earlier, set up after IP-CAN-1 session and the GW control session, also other order may occur certainly.That is to say the sequencing that the foundation of these three sessions is not strict.But this can not influence the execution of this scheme, after PCRF receives request, and goes to retrieve the session that has existed, if meet Correlation Criteria, just carries out association, if do not meet Correlation Criteria, and related getting final product not just.

Embodiment two

In the present embodiment, when PDSN receives the IPv6CP configuring request of MS/AT transmission/after, PDSN sets up GW control session and IP-CAN session-1 with PCRF simultaneously.After PCRF had received the IP-CAN session-1 modification request of PDSN transmission, PCRF determined that the access module of this terminal equipment is SIPv6, and PCRF will discharge with the GW control session that PDSN sets up, and follow-up operation gets final product according to the prior art execution.

Fig. 6 is the flow chart of the method for building up embodiment two of strategy of the present invention and charging controlled session, and as shown in Figure 6, the method for building up of this example policy and charging controlled session may further comprise the steps:

Step 1, main business connect to be set up.

Step 2, the LCP of PPP session consults and selectes authentication mode.

Step 4, PDSN sends to RAN with signatory qos parameter.

Step 5, MS/AT and PDSN carry out the IPv6CP negotiation step.

PCRF receives the PCC session foundation request of PDSN, set up IP-CAN session-1 and GW control session respectively with PDSN, judging that these two sessions are from the session of same PDSN and are during for same MS/AT service, to these two session individual processing, promptly do not do association.

Step 7, MS/AT and RAN/PCF carry out HRPD QoS establishment step.

Step 8, corresponding step 7, if having Link Flow newly-built/revise, between RAN/PCF and PDSN, also need corresponding foundations/modification A10 connection, and the QoS that will ask accordingly tabulates and sends to PDSN.

Step 9, and MS/AT transmission RSVP (RSVP, Resource Reservation Protocol) reservation (Resv, Reserve) message is given PDSN, and business datum flow template (TFT, Traffic FlowTemplate) sends to PDSN by this signaling.

Step 10, PDSN parses the IP address of terminal that this message is carried after receiving the RSVP Resv message that MS/AT sends, and wherein this IP address can also can parse (prior art) by carrying separately to PDSN in RSVP message from the TFT that carries.

PDSN is by judging that this address is that PDSN is the MS/AT addresses distributed, and then PDSN initiates IP-CAN session-1 to PCRF and revises request, asks corresponding PCC strategy, and PCRF sends to PDSN to corresponding strategy by response message.

Step 11 after PCRF receives the IP-CAN session modification request that PDSN sends, judges that the current access module of terminal equipment is SIPv6, keeps IP-CAN session-1, deletion GW session.At this moment, PDSN role is PCEF, and it is by setting up corresponding IP-CAN session between Gx interface and the PCRF.

Step 12, PDSN sends RSVP Resvconf message to MS/AT.

Step 13, MS/AT, RAN/PCF and PDSN install corresponding QoS, Resources allocation.

Step 14: tightly hold step 11, PCRF initiates the request of GW control session terminating operation to PDSN, discharges GW control session.This step 14 also can be triggered by step 9, initiates " GW controls session " releasing operation by PDSN, adopts which kind of mode to depend on concrete communication process realization.

Embodiment three

In the present embodiment, PDSN is after receiving the IPv6CP negotiation request that terminal equipment sends, set up GW control session and IP-CAN session-1 with PCRF simultaneously, PCRF determine this two session be for same terminal equipment that set up with session same PDSN, then PCRF does not carry out association to it to these two session independent process.

If PCRF has received the IP-CAN session-2 foundation request that belongs to same IP connection of this terminal equipment that HA/LMA sends, PCRF is related with the IP-CAN session-2 of HA/LMA request with the GW control session of PDSN request, and the IP-CAN session-1 of reservation and PDSN foundation.

If it is that PDSN is the MS/AT addresses distributed that PDSN from the RSVP Resv message that MS/AT sends, parses the IP address of terminal that this message carries, then PDSN initiates IP-CAN session-1 to PCRF and revises request, asks corresponding PCC strategy.PCRF has received the modification request of the IP-CAN session-1 that PDSN sends, and then PCRF is that terminal equipment is formulated the PCC strategy, and if the IP-CAN session-2 that exists described HA/LMA to ask, then PCRF keeps it, if there is no, does not then deal with.

If PDSN is from the RSVP Resv message that MS/AT sends, parsing the IP address of terminal (HoA) that this message carries is not that PDSN is MS/AT addresses distributed (CoA), then PDSN initiates GW control and qos policy request to PCRF, then PCRF is that terminal equipment is formulated the PCC strategy, and by described gateway control session and the IP-CAN session related with it respectively to described PDSN and described HA/LMA distributing policy and charging control PCC strategy.Here, GW control can only utilize the session after the IP-CAN session-2 of GW control session and HA/LMA request is related to send with the qos policy request message.

Fig. 7 is the flow chart of the method for building up embodiment three of strategy of the present invention and charging controlled session, and as shown in Figure 7, the method for building up of this example policy and charging controlled session may further comprise the steps:

Step 1, main business connect to be set up.

Step 2, the LCP of PPP session consults and selectes authentication mode.

Step 4, PDSN sends to RAN with signatory qos parameter.

Step 5, MS/AT and PDSN carry out the IPv6CP negotiation step.

Step 7, PCRF receives the PCC session of the PDSN request of setting up, and sets up IP-CAN session-1 and GW control session respectively with PDSN, is judging that these two sessions are from the session of same PDSN and are during for same MS/AT service, to these two session individual processing, promptly do not do association.

Step 10, HA/LMA initiates IP-CAN session-2 as PCEF to PCRF and sets up request message, and PCRF sends IP-CAN session-2 foundation to HA/LMA/PCEF and replys, and finishes the foundation of IP-CAN session-2, and downloads relevant PCC strategy to HA/LMA/PCEF.

Step 11, after PCRF and HA/LMA set up IP-CAN session-2, PCRF was associated IP-CAN session-2 with " controlling session with the GW that PDSN sets up ", and " the IP-CAN session-1 " that PCRF can safeguard separately and PDSN sets up promptly keeps IP-CAN session-1 simultaneously.

Following step branch situation A and situation B illustrate respectively when receiving different messages, anyly handles accordingly.

Situation A, it is that it distributes address (this address is called Care-of Address (CoA, Care of Address) under the CMIPv6 access module, be called the address under this place's situation) that MS/AT is used in the step 5 PDSN, by PDSN and external network intercommunication data service, and the professional for this reason QoS of initiation asks.Specifically may further comprise the steps:

Steps A .1, MS/AT and RAN/PCF carry out HRPD QoS and set up.

Steps A .2, corresponding steps A .1, if having Link Flow newly-built/revise, correspondingly between RAN/PCF and PDSN, also need corresponding foundations/modification A10 connection, and the QoS that will ask accordingly tabulates and sends to PDSN.

Steps A .3, MS/AT send RSVP Resv message to PDSN, and TFT sends to PDSN by this signaling, has carried the address of MS/AT among the TFT, is the source address of upstream data, and perhaps this address also can be by carrying to PDSN separately in RSVP Resv message.This step is a prior art.

Steps A .4, PDSN is by judging that the address of bringing in the RSVP Resv message is that PDSN is the MS/AT addresses distributed before, what judge current MS/AT employing is the access module of SIPv6, so PDSN initiates IP-CAN session-1 to PCRF and revises request, ask corresponding PCC strategy, PCRF is issued to PDSN to corresponding strategy by response message.

After PCRF received that request is revised in IP-CAN session-1 that PDSN sends, this session of individual processing was not done any correction or processing to IP-CAN session-2 and GW control session, promptly keeps CAN session-2 and GW control session.

Steps A .5, PDSN send rsvp reservation configuration (Resvconf) message and give MS/AT.

Steps A .6, MA/AT, RAN/PCF and PDSN install corresponding QoS, and Resources allocation.

If situation A occurs in (as shown) after 11 steps, then press foregoing description processing; Situation can also be anyway after step 7, and before the step 10, therefore, if PCRF received the A.4 step before step 10, then PCRF and PDSN only preserve gateway control session, (because also not setting up) are not handled in IP-CAN session-2.

Situation B, MS/AT be used in HA/LMA in the step 12 for the local address (HoA, Homeof Address) of its distribution by HA/LMA and external network intercommunication data service, and the professional for this reason QoS of initiation asks.Specifically may further comprise the steps:

Step B.1, MS/AT and RAN/PCF carry out HRPD QoS and set up.

Step B.2, corresponding step B.1, if having Link Flow newly-built/revise, also need corresponding foundations/modification A10 connection between RAN/PCF and the PDSN, and the QoS that will ask accordingly tabulates and sends to PDSN.

Step B.3, MS/AT sends RSVP Resv message to PDSN, TFT sends to PDSN by this signaling, has carried the HoA of MS/AT among the TFT, is the source address of upstream data, perhaps this HoA address also can be by carrying to PDSN separately in RSVP Resv message.This step is a prior art.

Step B.4, PDSN is by judging that the address (HoA) of bringing in the RSVP Resv message is not that PDSN is MS/AT addresses distributed (CoA) before, what judge current MS/AT employing is the access module of CMIPv6, so PDSN initiates GW control and qos policy request to PCRF;

After PCRF received the GW control and qos policy request that PDSN sends, this GW control session of individual processing was not done any correction or processing to IP-CAN session-1, promptly keeps IP-CAN session-1.

B.5, step after PCRF receives GW control and qos policy request, is formulated the IP-CAN conversation strategy of correspondence, and is issued to HA/LMA. by IP-CAN session-2

Step B.6, as replying of GW control that PDSN is initiated to PCRF and qos policy request, PCRF with corresponding PCC policy distribution to PDSN.

Step B.7, PDSN sends RSVP Resvconf message to MS/AT.

Step B.8, MA/AT, RAN/PCF, and PDSN installs corresponding QoS, Resources allocation.

Situation B must occur in after the step 11, but does not have inevitable precedence relationship with situation A.So in the implementation of situation B, IP-CAN session-1 keeps always.

Embodiment four

If it is that PDSN is the MS/AT addresses distributed that PDSN from the RSVP Resv message that MS/AT sends, parses the IP address of terminal that this message carries, then PDSN initiates IP-CAN session-1 to PCRF and revises request, asks corresponding PCC strategy.PCRF has received the modification request of the IP-CAN session-1 that PDSN sends, and then PCRF is that terminal equipment is formulated the PCC strategy.When PDSN initiates IP-CAN session-1 modification request to PCRF, send " gateway control session termination " message to PCRF, request stops the gateway control session between PDSN and the PCRF, and if exist between the HA/LMA under the situation of IP-CAN session-2, this session also can be deleted by PCRF.

If PDSN is from the RSVP Resv message that MS/AT sends, parsing the IP address of terminal (HoA) that this message carries is not that PDSN is MS/AT addresses distributed (CoA), then PDSN initiates GW control and qos policy request to PCRF, then PCRF is that terminal equipment is formulated the PCC strategy, and by described gateway control session and the IP-CAN session related with it respectively to described PDSN and described HA/LMA distributing policy and charging control PCC strategy.When PDSN initiates GW control with the qos policy request to PCRF, send IP-CAN session-1 to PCRF and stop request message, request stops the IP-CAN session-1 between PDSN and the PCRF.

Fig. 8 is the flow chart of the method for building up embodiment four of strategy of the present invention and charging controlled session, and as shown in Figure 8, the method for building up of this example policy and charging controlled session may further comprise the steps:

Step 1, main business connect to be set up.

Step 2, the LCP of PPP session consults and selectes authentication mode.

Step 4, PDSN sends to RAN with signatory qos parameter.

Step 5, MS/AT and PDSN carry out the IPv6CP negotiation step.

Situation A, MS/AT are used in that PDSN (when CMIP inserts, is called for its addresses distributed in the step 5, Care-of Address (CoA, Care of Address), can only be called the address at this) by PDSN and external network intercommunication data service, and the professional for this reason QoS of initiation asks.Specifically may further comprise the steps:

Steps A .1, MS/AT and RAN/PCF carry out HRPD QoS and set up.

Steps A .4, PDSN is by judging that the address of bringing in the RSVP Resv message is that PDSN is the MS/AT addresses distributed before, what judge current MS/AT employing is the access module of SIPv6, so PDSN initiates IP-CAN session-1 to PCRF and revises request, PCRF receives the IP-CAN session-1 modification request that PDSN sends, formulate corresponding PCC strategy,, corresponding strategy is issued to PDSN by response message.

Steps A .7, when PDSN initiates IP-CAN session-1 modification request to PCRF (steps A .4), PDSN sends the gateway control session release message to PCRF, request stops the gateway control session between PDSN and the PCRF, if and exist between the HA/LMA under the situation of IP-CAN session-2, this session also can be deleted (A.8) by PCRF.

Step B.1, MS/AT and RAN/PCF carry out HRPD QoS and set up.

Step B.4, PDSN is by judging that the address (HoA) of bringing in the RSVP Resv message is not that PDSN is MS/AT addresses distributed (CoA) before, what judge current MS/AT employing is the access module of CMIPv6, so PDSN initiates GW control and qos policy request to PCRF; PCRF formulates corresponding PCC strategy and is issued to PDSN and HA/LMA by this gateway control session respectively with related with it IP-CAN session-2 after receiving the GW control and qos policy request that PDSN sends.

Step B.7, PDSN sends RSVP Resvconf message to MS/AT.

Step B.9, when PDSN initiates GW control and qos policy request to PCRF (step is B.4), PDSN sends IP-CAN session-1 to PCRF and discharges request, the IP-CAN session-1 between request termination PDSN and the PCRF.

The system that sets up of strategy of the present invention and charging controlled session comprises network elements such as comprising terminal equipment MS/AT, PDSN, PCRF and HA/LMA, the function of said network element and annexation thereof, specifically referring to associated the Internet protocol, and, give unnecessary details its structure and function here no longer in detail in conjunction with Fig. 1, shown in Figure 2 and understand; Fig. 9 is a kind of composition structural representation of the system that sets up of strategy of the present invention and charging controlled session, as shown in Figure 9, the system that sets up of this example policy and charging controlled session comprises that also negotiation element 90, session set up unit 91, determining unit 92 and session processing unit 93; Wherein:

Negotiation element 90 is used for consulting IPv6CP between PDSN and terminal equipment;

Unit 91 is set up in session, be used for when negotiation element 90 is consulted IPv6CP/after, set up gateway control session respectively with PCRF and be connected access network IP-CAN session with an IP;

Determining unit 92, when being used for determining that a described gateway control session and a described IP-CAN session are sessions for same terminal equipment and same PDSN foundation, triggering session processing unit 93;

Session processing unit 93 is used for a described gateway control session of individual processing and a described IP-CAN session.

Above-mentioned each processing unit is based on the related network elements in the network and realizes its function, and the present invention is not limited to its particular location, it will be appreciated by those skilled in the art that according to above-mentioned related network elements to realize that its function is to realize easily.

Concrete, above-mentioned session processing unit 93, further when request is set up in the IP-CAN session of belonging to of the described terminal equipment that receives the HA/LMA transmission of same IP connection, with the IP-CAN session association of described gateway control session and described HA/LMA request, and discharge a described IP-CAN session.

Perhaps, above-mentioned session processing unit 93 further when a described IP-CAN session modification request that receives that described PDSN sends, keeps and also revises request by this and revise a described IP-CAN session, discharges the gateway control session of setting up with described PDSN.

Perhaps, above-mentioned session processing unit 93, further when request is set up in the IP-CAN session of belonging to of the described terminal equipment that receives the HA/LMA transmission of same IP connection,, and keep a described IP-CAN session with the IP-CAN session association of described gateway control session and described HA/LMA request.After the IP-CAN session association of described session processing unit 93 with described gateway control session and described HA/LMA request, when receiving gateway control that described PDSN sends and quality of service policy request, further be that described terminal equipment is formulated the PCC strategy, and keep a described IP-CAN session, and issue the PCC strategy to described PDSN and described HA/LMA respectively with the IP-CAN session related with it by described gateway control session.

Perhaps, after the IP-CAN session association of above-mentioned session processing unit 93 with described gateway control session and described HA/LMA request, when receiving the modification request of the described IP-CAN session that described PDSN sends, further be that described terminal equipment is formulated the PCC strategy, issue the PCC strategy by a described IP-CAN session to described PDSN, and keep the IP-CAN session of gateway control session and described HA/LMA request.

Perhaps, above-mentioned session processing unit 93 is further when the modification request of a described IP-CAN session that receives described PDSN transmission, for described terminal equipment is formulated the PCC strategy,, then keep it if there is the IP-CAN session of described HA/LMA request, if there is no, then do not deal with.

Further, unit 93 is set up in above-mentioned session, when further determining to set up a described IP-CAN session, sets up by the Gx interface between described PDSN and described PCRF.

Further, unit 93 is set up in above-mentioned session, when further determining to set up the IP-CAN session related with described gateway control session, sets up by the Gxa interface between described PDSN and described PCRF.

Figure 10 is a kind of composition structural representation of the system that sets up of strategy of the present invention and charging controlled session, as shown in figure 10, on the basis of system shown in Figure 9, the system that sets up of this example policy and charging controlled session also comprises judging unit 94, being used at PDSN when receiving resource reservation request, is by gateway control session or IP-CAN conversation request PCC strategy according to the decision of the address of terminal equipment.

Above-mentioned judging unit 94 judges that further the address of described terminal equipment is described PDSN during for this terminal equipment addresses distributed, by a described IP-CAN session to described PCRF request PCC strategy;

Above-mentioned judging unit 94 judges that further the address of described terminal equipment is not described PDSN during for this terminal equipment addresses distributed, by described gateway control session to described PCRF request PCC strategy.

The system that sets up of this example policy and charging controlled session also comprises also and comprising: transmitting element 95, when being used at above-mentioned judging unit 94s by a described IP-CAN session, initiate the request of the described gateway control session of deletion to described PCRF to described PCRF request PCC strategy;

During to described PCRF request PCC strategy, initiate the request of the described IP-CAN session of deletion by described gateway control session to described PCRF at above-mentioned judging unit 94.

Those skilled in the art are to be understood that, those skilled in the art are to be understood that, Fig. 9, strategy shown in Figure 10 and the system that sets up of charging controlled session are for the method for building up of realizing aforesaid strategy and charging controlled session is provided with, and the realization function of the each processing unit among the figure can be with reference to the associated description of preceding method and understood.The function of each processing unit can realize by the program that runs on the processor in Fig. 9, the system shown in Figure 10, also can realize by concrete logical circuit.

The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.

Claims

1. the method for building up of strategy and charging controlled session is characterized in that described method comprises:

2. method according to claim 1 is characterized in that, described method also comprises:

3. method according to claim 2 is characterized in that, described method also comprises:

4. method according to claim 3 is characterized in that, described method also comprises:

5. method according to claim 1 is characterized in that, a described gateway control session of described individual processing and a described IP-CAN session, for:

6. method according to claim 1 is characterized in that, a described gateway control session of described individual processing and a described IP-CAN session, for:

7. method according to claim 1 is characterized in that, a described gateway control session of described individual processing and a described IP-CAN session, for:

8. method according to claim 7 is characterized in that, after the IP-CAN session association with described gateway control session and described HA/LMA request, also comprises:

9. method according to claim 7 is characterized in that, after the IP-CAN session association with described gateway control session and described HA/LMA request, also comprises:

10. method according to claim 1 is characterized in that, a described gateway control session of described individual processing and a described IP-CAN session, for:

When described PCRF receives the modification request of the described IP-CAN session that described PDSN sends, be that described terminal equipment is formulated the PCC strategy, and issue the PCC strategy to PDSN, and keep gateway control session by an IP-CAN session.

11. the system that sets up of strategy and charging controlled session comprises terminal equipment, PDSN, PCRF and HA/LMA; It is characterized in that described system comprises that negotiation element, session set up unit, determining unit and session processing unit; Wherein:

12. system according to claim 11, it is characterized in that, described system also comprises: judging unit, be used at PDSN when receiving resource reservation request, and be by gateway control session or IP-CAN conversation request PCC strategy according to the decision of the address of terminal equipment.

13. system according to claim 12 is characterized in that, described judging unit further judges that the address of described terminal equipment is described PDSN during for this terminal equipment addresses distributed, by a described IP-CAN session to described PCRF request PCC strategy;

14. system according to claim 13 is characterized in that, described system also comprises:

15. system according to claim 12, it is characterized in that, described session processing unit, further when request is set up in the IP-CAN session of belonging to of the described terminal equipment that receives the HA/LMA transmission of same IP connection, with the IP-CAN session association of described gateway control session and described HA/LMA request, and discharge a described IP-CAN session.

16. system according to claim 12, it is characterized in that, described session processing unit, further when a described IP-CAN session modification request that receives that described PDSN sends, keep and revise a described IP-CAN session, discharge the gateway control session of setting up with described PDSN by described modification request.

17. system according to claim 12, it is characterized in that, described session processing unit, further when request is set up in the IP-CAN session of belonging to of the described terminal equipment that receives the HA/LMA request of same IP connection, with the IP-CAN session association of described gateway control session and described HA/LMA request, and keep a described IP-CAN session.

18. system according to claim 17, it is characterized in that, after the IP-CAN session association of described session processing unit with described gateway control session and described HA/LMA request, when receiving gateway control that described PDSN sends and quality of service policy request, be that described terminal equipment is formulated the PCC strategy further according to the CMIPv6 pattern, and keep a described IP-CAN session, and issue the PCC strategy to described PDSN and described HA/LMA respectively with the IP-CAN session related with this gateway control session by described gateway control session.

19. system according to claim 17, it is characterized in that, after the IP-CAN session association of described session processing unit with described gateway control session and described HA/LMA request, when receiving the modification request of the described IP-CAN session that described PDSN sends, further be that described terminal equipment is formulated the PCC strategy, issue the PCC strategy by a described IP-CAN session to described PDSN, and keep the IP-CAN session of gateway control session and described HA/LMA request.

20. system according to claim 12, it is characterized in that, described session processing unit, further when the modification request of a described IP-CAN session that receives described PDSN transmission, according to the SIPv6 pattern is that described terminal equipment is formulated the PCC strategy, when having the IP-CAN session of HA/LMA request, keep the IP-CAN session of described HA/LMA request, do not deal with when not existing.