CN103037408B

CN103037408B - The changing method of IP service flow, terminal and corresponding functional entity

Info

Publication number: CN103037408B
Application number: CN201110293955.7A
Authority: CN
Inventors: 段小嫣
Original assignee: Huawei Device Co Ltd
Current assignee: Huawei Device Co Ltd
Priority date: 2011-09-30
Filing date: 2011-09-30
Publication date: 2015-12-16
Anticipated expiration: 2031-09-30
Also published as: CN103037408A

Abstract

The invention provides a kind of changing method of IP service flow, mobile network's strategy and charging regulation function entity and terminal.Described method comprises: whether mobile network's strategy switches to non-seamless to shunt from seamless shunting described IP service flow with charging regulation function entity decision-making; The result of decision is sent to fixed network policy control functions entity with charging regulation function entity by described mobile network's strategy, at least non-seamless is switched to shunt from seamless shunting described IP service flow according to the described result of decision to make described fixed network policy control functions entity, or keep seamless shunting, or stop transmission.Implement the present invention, the flow process that IP service flow switches to non-seamless to shunt from seamless shunting can be optimized, shorten switching time, improve switching efficiency.

Description

The changing method of IP service flow, terminal and corresponding functional entity

Technical field

The present invention relates to communication technical field, particularly relate to the changing method of IP service flow, mobile network's strategy and charging regulation function entity and terminal.

Background technology

Fusion (the FMC of fixed network and mobile network, Fixed-mobileconvergence) be current communication network development one main trend, it refers to and realizes network authentication between fixed communication network and mobile radio network, strategy and service quality (QoS, QualityofService) control waits intercommunication, and further network integration management and framework optimization, thus allow user/terminal equipment according to position, the real needs such as application, select to adopt different access technologies, such as WLAN (wireless local area network) (WirelessLocalAreaNetworks, WLAN), fixed broadband network (BroadbandForum, BBF), 3 G mobile communication network (3rdGenerationPartnershipProject, 3GPP) etc., realize communication service.

An example of the fusion of fixed network and mobile network is that WLANUE (referring to have the terminal equipment by WLAN access network that 3GPP contracts here) accesses fixed broadband network by WLAN, and then is linked into 3GPP core network.Under this network connects, the WLANUE initiation packet data service that 3GPP is signing or circuit domain speech business, carry out strategy and quality control of the business by 3GPP core net.3GPP core net needs intercommunication and the coordination of carrying out strategy and quality control of the business with fixed broadband network, to realize the consistency that customer service is experienced.Because IP service flow will flow through 3GPP core net, this routing mode is called seamless shunting (SeamlessOffload); Here shunting refers to that Business Stream does not adopt the Access Network of 3GPP and have employed fixed broadband network and WLAN access.When Business Stream is not by 3GPP core net, but when directly arriving correspondent network or equipment by fixed broadband network, be called non-seamless shunting (Non-SeamlessOffload).

Be illustrated in figure 1 IP service flow is switched to non-seamless shunting scene by seamless shunting, wherein service flow path 1 is seamless shunting, and service flow path 2 is non-seamless shunting.This switching may be initiated by subscriber terminal equipment, such as when the quality of service of seamless shunting Business Stream cannot meet user require time, by the shunting of Business Stream non-seamless to improve quality of service (as transmission bandwidth); Also may be initiated by 3GPP network, such as when 3GPP packet data gateway (PublicDataNetworkGateway, PDNGW) occur congested or change when carrier policy time, by some Business Stream non-seamless shunting to alleviate offered load; Also can be initiated by BBF network similarly, such as, when network condition change or carrier policy change.

In Fig. 1, strategy is with charging regulation function entity (PolicyandChargingRulesFunction, PCRF) for 3GPP strategy and charging regulation formulate entity, and PDNGW is 3GPP packet data gateway, and it has the function of strategy and charging regulation enforcement.BPCF (BBFPolicyControlFunction) is BBF network strategy controlling functions entity, BNG (BroadbandNetworkGateway) is BBF network broadband network gateway, and the function of BPCF and BNG in QoS control is suitable with PCRF, PDNGW in 3GPP respectively; AN (AccessNetwork, access network) is BBF networks converge node, and RG (ResidentialGateway, residential gateway) is BBF network local gateway.Terminal accesses BBF network by WLANAP (WirelessLocalAreaNetworksAccessPoint, WAP (wireless access point)).When terminal is by WLAN and BBF network insertion 3GPP core net (i.e. seamless shunting), set up session between PCRF and BPCF, i.e. gateway control session, for qos policy intercommunication and the negotiation of 3GPP network and BBF network.

Prior art provides method flow IP service flow being switched to non-seamless shunting from seamless shunting that a kind of UE or BBF network is initiated, specifically as shown in Figure 2:

1. terminal is by WLAN and BBF network insertion 3GPP core net, sets up the IP service flow of seamless shunting.

2. terminal initiates the request of IP-CAN (IP-ConnectivityAccessNetwork, IP the connect access network) session of setting up new non-seamless shunting to BBF network by WLAN.

3.BBF network is according to terminal session request, and set up the IP-CAN session of non-seamless shunting, Business Stream directly arrives correspondent network or equipment by BBF network.This session establishment process does not need 3GPP network to participate in.

4. terminal or BBF network initiate the IP-CAN session of the original seamless shunting of release.

5.BBF network discharges the Business Stream (IP service flow) of original seamless shunting to 3GPPPDNGW request.

6.PDNGW initiates IP-CAN session modification or dispose procedure to PCRF, the Business Stream of the seamless shunting that request release is original.

7.PCRF notifies that the transfer resource (namely carrying) of this IP-CAN session of AF is lost.

8.PCRF initiates gateway control session amendment or dispose procedure to BPCF, discharges and controls the QoS of the Business Stream of original seamless shunting.

A kind of UE or BBF network that prior art provides initiate seamless shunting be switched to non-seamless shunting method there is following defect:

The first, 3GPP network cannot the IP service flow of perception non-seamless shunting Business Stream, therefore, some Business Stream (such as value-added service) may allow without 3GPP Virtual network operator and directly non-seamless be diverted to BBF network; And terminal is when being diverted to BBF network by Business Stream non-seamless, service quality QoS (such as bandwidth) of its request also likely exceeds its 3GPP service contracting scope, cannot control this network.

Second, when ongoing Business Stream non-seamless is diverted to BBF network, 3GPP network (PCRF) is to Application Function (AF, ApplicationFunction) report resource is lost, AF can take for this Business Stream bust this and trigger some business operations mistakenly, such as, stop business.

3rd, the seamless shunting that the method that prior art provides cannot realize the initiation of 3GPP network is switched to non-seamless shunting.

Summary of the invention

The embodiment of the present invention is in order to solve when fixed broadband network and mobile radio network merge, how to control or technical problem that initiating terminal Business Stream switches to non-seamless to shunt by seamless shunting, provide a kind of technical scheme switching to non-seamless to shunt from seamless shunting IP service flow.

Embodiments provide a kind of method that IP service flow switches, comprising:

Whether mobile network's strategy switches to non-seamless to shunt from seamless shunting IP service flow with charging regulation function entity decision-making;

The result of decision is sent to fixed network policy control functions entity with charging regulation function entity by described mobile network's strategy, at least non-seamless is switched to shunt from seamless shunting described IP service flow according to the described result of decision to make described fixed network policy control functions entity, or keep seamless shunting, or stop transmission.

Present invention also offers a kind of method that IP service flow switches, comprising:

Terminal sends the second request message to fixed network gateway, or sends the 3rd request message to the packet data gateway of mobile network, asks IP service flow to switch to non-seamless to shunt from seamless shunting;

Described terminal receives the acknowledge message switching to non-seamless to shunt from seamless shunting described IP service flow.

Correspondingly, the invention provides a kind of terminal, comprising:

Request sending module, for sending the second request message to fixed network gateway, or sending the 3rd request message to the packet data gateway of mobile network, asking IP service flow to switch to non-seamless to shunt from seamless shunting;

Switching executing module, for after receiving the acknowledge message switching to non-seamless to shunt from seamless shunting described IP service flow, sets up the IP service flow of non-seamless shunting.

Present invention also offers a kind of mobile network strategy and charging regulation function entity, comprising:

Whether switch decision module, switch to non-seamless to shunt from seamless shunting IP service flow for decision-making;

Switch indicating module, for the result of decision of described switch decision module is sent to fixed network policy control functions entity, at least non-seamless is switched to shunt from seamless shunting described IP service flow according to the described result of decision to make described fixed network policy control functions entity, or keep seamless shunting, or stop transmission.

Implement the present invention, 3GPP mobile network strategy and charging regulation function entity can be enable to receive, and fixed network gateway in fixed network or fixed network policy control functions entity or terminal initiate switches to non-seamless shunt from seamless shunting IP service flow to ask, or this 3GPP mobile network is tactful and charging regulation function entity can initiatively initiate IP service flow to switch to non-seamless to shunt from seamless shunting.Mobile network's strategy non-seamless can be diverted to fixed network and carries out decision-making which IP service flow in the IP service flow of terminal with charging regulation function entity, and can also the service quality that non-seamless shunts Business Stream be controlled, thus optimize the flow process that IP service flow switches to non-seamless to shunt from seamless shunting, shorten switching time, improve switching efficiency.

Accompanying drawing explanation

In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, be briefly described to the accompanying drawing used required in embodiment or description of the prior art below, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.

Fig. 1 is the scene schematic diagram that in prior art, IP service flow is switched to non-seamless shunting by seamless shunting;

Fig. 2 is method flow schematic diagram IP service flow being switched to non-seamless shunting from seamless shunting that in prior art, UE or BBF network is initiated;

Fig. 3 is the schematic flow sheet of the changing method embodiment one of IP service flow in the present invention;

Fig. 4 is the schematic flow sheet of the changing method embodiment two of IP service flow in the present invention;

Fig. 5 is the schematic flow sheet of the changing method embodiment three of IP service flow in the present invention;

Fig. 6 is the schematic flow sheet of the changing method embodiment four of IP service flow in the present invention;

Fig. 7 is the schematic flow sheet of the changing method embodiment five of IP service flow in the present invention;

Fig. 8 is the schematic flow sheet of the changing method embodiment six of IP service flow in the present invention;

Fig. 9 is the schematic flow sheet of the changing method embodiment seven of IP service flow in the present invention;

Figure 10 is the schematic flow sheet of the changing method embodiment eight of IP service flow in the present invention;

Figure 11 is the schematic flow sheet of the changing method embodiment nine of IP service flow in the present invention.

Figure 12 is the schematic flow sheet of the changing method embodiment ten of IP service flow in the present invention;

Figure 13 is the schematic flow sheet of the changing method embodiment 11 of IP service flow in the present invention;

Figure 14 is the schematic flow sheet of the changing method embodiment 12 of IP service flow in the present invention;

Figure 15 is the composition schematic diagram of IP service flow switched system embodiment one provided by the invention;

Figure 16 is the composition schematic diagram of IP service flow switched system embodiment two provided by the invention;

Figure 17 is the composition schematic diagram of IP service flow switched system embodiment three provided by the invention;

Figure 18 is the composition schematic diagram of IP service flow switched system embodiment four provided by the invention;

Figure 19 is the composition schematic diagram of mobile network's strategy and charging regulation function entity embodiment one in the present invention;

Figure 20 is the composition schematic diagram of mobile network's strategy and charging regulation function entity embodiment two in the present invention;

Figure 21 is the composition schematic diagram of mobile network's strategy and charging regulation function entity embodiment three in the present invention;

Figure 22 is the composition schematic diagram of terminal embodiment in the present invention.

Embodiment

The embodiment of the present invention is in order to solve when fixed broadband network and mobile radio network merge, how to control or technical problem that initiating terminal Business Stream switches to non-seamless to shunt by seamless shunting, provide a kind of technical scheme switching to non-seamless to shunt from seamless shunting IP service flow.This technical scheme can optimize IP service flow is switched to non-seamless shunting flow process by seamless shunting, shortens switching time simultaneously, improves switching efficiency.

It is the schematic flow sheet of the changing method embodiment one of IP service flow in the present invention see Fig. 3, Fig. 3.

The method provided in the present embodiment, comprising:

Step 101, whether described mobile network's strategy switches to non-seamless to shunt from seamless shunting described IP service flow with charging regulation function entity decision-making.

Step 102, the result of decision is sent to fixed network policy control functions entity with charging regulation function entity by described mobile network's strategy, at least non-seamless is switched to shunt from seamless shunting described IP service flow according to the described result of decision to make described fixed network policy control functions entity, or keep seamless shunting, or stop transmission.

It should be noted that, in the changing method embodiment of IP service flow provided by the invention, whether mobile network's strategy and charging regulation function entity can the request messages shunt of the non-seamless of IP service flow initiated via the fixed network gateway in fixed network or fixed network or fixed network policy control functions entity of receiving terminal, and make and allow to carry out to IP service flow the decision-making that non-seamless shunts switching; Whether mobile network's strategy also can active decision allow described IP service flow to switch to non-seamless to shunt from seamless shunting with charging regulation function entity.Specific as follows:

Described mobile network's strategy receives with charging regulation function entity the first request message switching to non-seamless to shunt from seamless shunting described IP service flow;

Wherein, described first request message is gateway control and service quality QoS rule request message, or notification message; Described gateway control and QoS rule request message or notification message are that described fixed network policy control functions entity is initiatively initiated, or described fixed network policy control functions entity sends after receiving the session modification Trigger message that fixed network gateway sends;

Described session modification Trigger message is that described fixed network gateway is initiated, or described fixed network gateway sends after the second request message switching to non-seamless to shunt from seamless shunting described IP service flow receiving the transmission of described terminal.

Or described first request message is session modification Trigger message; Described session modification Trigger message is that the packet data gateway of mobile network is initiated, or described packet data gateway sends after the 3rd request message switching to non-seamless to shunt from seamless shunting described IP service flow receiving terminal transmission.

The mark of above-mentioned first request message carried terminal mark, described IP service flow and non-seamless shunting instruction.In addition, also carried terminal mark, the mark of described IP service flow and non-seamless shunting instruction in the second request message of sending of terminal or the 3rd request message.

It is the schematic flow sheet basis of the changing method embodiment two of IP service flow in the present invention see Fig. 4, Fig. 4.

The present embodiment introduces the flow process that fixed network or terminal send a request message via fixed network, and illustrate for terminal below, the method flow process comprises:

Step 200, terminal sends the second request message switching to non-seamless to shunt the IP operation of seamless shunting to the fixed network gateway in fixed network;

Step 201, the rear of the second request message that the fixed network gateway in fixed network is receiving the transmission of described terminal sends session modification Trigger message to fixed network policy control functions entity; Carry described IP service flow mark in described session modification Trigger message and represent the instruction that IP service flow route changing or non-seamless are shunted.

Step 202, fixed network policy control functions entity receives the rear of the session modification Trigger message of described fixed network gateway transmission and sends seamless point of the first request message flowing to non-seamless and shunt to described mobile network's strategy with charging regulation function entity.Described first request message is gateway control and QoS rule request message, or notification message, and carries the mark of terminal, the mark of described IP service flow, non-seamless shunting instruction.

Particularly, described gateway control and QoS rule request message are by expanding (Attribute-ValuePair, AVP) the property value in described gateway control and QoS rule request message or increase an event newly this property value centering to come carried terminal mark, session identification, the mark of IP service flow and non-seamless shunting and indicate.

Or described notification message is sent with charging regulation function entity to mobile network's strategy by described fixed network policy control functions entity, carry session identification, the mark of IP service flow and non-seamless shunting in this notification message and indicate.

Session modification Trigger message in above-mentioned steps 201 initiatively can be sent by fixed network policy control functions entity.The first request message in step 202 also initiatively can be sent to mobile network's strategy with charging regulation function entity by fixed network policy control functions entity.

What above embodiment described is initiates by terminal or fixed network the flow process that switches to non-seamless to shunt from seamless shunting IP service flow, in embodiments of the present invention, the process switching to non-seamless to shunt from seamless shunting IP service flow is initiated in the request that the packet data gateway in mobile network could also initiatively be initiated or receive to mobile network's strategy and charging regulation function entity afterwards, below will introduce in detail.

It is the schematic flow sheet of the changing method embodiment three of IP service flow see Fig. 5, Fig. 5.

In the present embodiment, description mobile network strategy and charging regulation function entity are initiatively initiated the method flow that IP service flow switches, comprising:

Step 300, whether mobile network's strategy and charging regulation function entity detect user and contract and to change or whether carrier policy changes or whether offered load is overweight;

Step 301, IP service flow switches to non-seamless to shunt from seamless shunting with charging regulation function entity decision-making by mobile network's strategy;

Particularly, described mobile network's strategy is with charging regulation function entity when at least one of following situation being detected, and decision is sent out and switched to non-seamless to shunt from seamless shunting IP service flow:

When the signing change of user, carrier policy change, offered load is overweight.

Step 302, the result of decision is sent to fixed network policy control functions entity with charging regulation function entity by described mobile network's strategy, non-seamless is switched to shunt from seamless shunting described IP service flow to make described fixed network policy control functions entity, or keep seamless shunting, or stop transmission.

It is the schematic flow sheet of the changing method embodiment four of IP service flow in the present invention see Fig. 6, Fig. 6.

The present embodiment describes the flow process that terminal sends a request message via mobile network, comprising:

Step 401, packet data gateway sends IP to mobile network's strategy with charging regulation function entity and is connected and accesses session modification Trigger message, carries to comprise IP service flow and to identify and non-seamless shunts the IP service flow routing rule of the renewal indicated in this session modification Trigger message.

Alternatively, before step 401, also comprise step 400, terminal sends the 3rd request message switching to non-seamless to shunt the IP operation of seamless shunting to the packet data gateway in mobile network;

Particularly, described terminal, by Binding Update (BU, the BindingUpdate) signaling strengthened, sends the 3rd request message switching to non-seamless to shunt the IP service flow of seamless shunting to the packet data gateway in mobile network.

Then step 401 is specially, and packet data gateway, after receiving the 3rd request message that described terminal sends, sends IP to mobile network's strategy and charging regulation function entity and is connected and accesses session modification Trigger message.

In preferred embodiment, the request message that the non-seamless to IP service flow that mobile network's strategy and charging regulation function entity receiving terminal or fixed network are initiated is shunted, or after initiatively determining to switch to non-seamless to shunt from seamless shunting IP service flow, mobile network's strategy needs to inquire about routing policy ISRP (Inter-SystemRoutingPolicy) between the signing attribute corresponding with this IP service flow and/or system further with charging regulation function entity, whether allow described IP service flow to switch to non-seamless to shunt with decision-making, to mobile network's strategy and charging regulation function entity be introduced inquire about the embodiment of the method for the routing policy between attribute and/or system of contracting below.

Mobile network's strategy and charging regulation function entity inquire about routing policy between signing attribute and/or system two kinds of modes, as follows:

1) mobile network's strategy is inquired about to SPR/UDR/HSS with charging regulation function entity, is specially:

Described mobile network's strategy and charging regulation function entity are to signing attribute database (SubscriptionProfileRepository, or customer data base (UserDataRepository SPR), or home signature user database (HomeSubscriberServer UDR), HSS) signing attribute query request is initiated, comprising the inquiry to routing policy between system; The mark of carried terminal in described signing attribute query request, the mark of described IP service flow, non-seamless shunting instruction.

Routing policy between the system that described mobile network strategy and charging regulation function entity return according to described SPR or UDR or HSS, whether decision-making switches to non-seamless to shunt described IP service flow.

In the present embodiment, between the system stored in described SPR/UDR/HSS, by access network discovery, (AccessNetworkDiscoveryandSelectionFunction, ANDSF provide routing policy with selecting entity in advance; Or receive mobile network strategy and charging regulation function entity after routing policy request between SPR or UDR or HSS initiation system, to ANDSF ask gained.

2) mobile network's strategy is inquired about to ANDSF with charging regulation function entity, is specially:

Described mobile network strategy and charging regulation function entity are to routing policy inquiry request between ANDSF initiation system;

The permission that between the system that described mobile network strategy and charging regulation function entity return according to described ANDSF, routing policy or described ANDSF return or do not allow the reply message that switches to non-seamless to shunt described IP service flow, whether decision-making switches to non-seamless to shunt described IP service flow.

It is the schematic flow sheet of the changing method embodiment five of IP service flow in the present invention see Fig. 7, Fig. 7.

Whether description mobile network strategy and charging regulation function entity decision-making are allowed the flow process switching to non-seamless to shunt from seamless shunting described IP service flow by the present embodiment, comprising:

Step 500, described mobile network's strategy and the direct decision-making of charging regulation function entity, or whether allow IP service flow to switch to non-seamless to shunt from seamless shunting according to the result decision-making of routing policy between inquiring user CAMEL-Subscription-Information and/or system; As allowed, proceed to step 501.

Step 501, when mobile network's strategy and charging regulation function entity initiatively initiates IP service flow switch time, mobile network is tactful and charging regulation function entity sends gateway control to fixed network policy control functions entity and service quality QoS rule provides message; Or when mobile network's strategy receives gateway control and service quality QoS rule request message with charging regulation function entity, mobile network's strategy and charging regulation function entity send gateway control to fixed network policy control functions entity and service quality QoS rule replys message.

Particularly, described gateway control and the QoS rule IP service flow routing rule and QoS rule that provide message or gateway control and service quality QoS rule to reply to carry renewal in message.

Alternatively, if when terminal or fixed network initiate IP service flow to switch to non-seamless to shunt from seamless shunting, also comprise step 502.

Step 502, mobile network's strategy and charging regulation function entity send gateway control to fixed network policy control functions entity and service quality QoS rule replys message, wherein carries at least one in the reason or former IP service flow routing rule not allowing non-seamless shunting to indicate or not allow non-seamless to shunt.

Above embodiment described mobile network's strategy whether to allow IP service flow to be switched to non-seamless from seamless shunting to shunt with charging regulation function entity decision-making, and the process of the indication information corresponding to the result of decision is sent to fixed network policy control functions entity, to describe IP service flow routing rule and the service quality QoS attribute of the renewal that fixed network policy control functions entity sends with charging regulation function entity according to described mobile network's strategy below, whether described IP service flow is switched to from seamless shunting the process that non-seamless shunts by decision-making.

It is the schematic flow sheet of the changing method embodiment six of IP service flow in the present invention see Fig. 8, Fig. 8.

The present embodiment describes the flow process whether decision-making of fixed network policy control functions entity allows described IP service flow to switch to non-seamless to shunt from seamless shunting, comprising:

Step 600, fixed network policy control functions entity receives gateway control that described mobile network strategy sends with charging regulation function entity and QoS is regular replys message or gateway control and service quality QoS rule and provide message;

Step 601, fixed network policy control functions entity is according to the IP service flow routing rule of described renewal and QoS rule, and the local policy of fixed network, determines that terminal carries out the QoS rule of the fixed network of IP service flow non-seamless shunting.

Particularly, if carry the new QoS of described IP service flow in the request message that described terminal or fixed network gateway send, described fixed network policy control functions entity judges whether the new QoS of described IP service flow exceeds the scope of the QoS rule of described IP service flow non-seamless shunting;

If the new QoS of described IP service flow exceeds the scope of described signing QoS attribute, described IP service flow is switched to non-seamless shunting from seamless shunting by the decision-making of described fixed network policy control functions entity; Described IP service flow will keep seamless shunting to continue transmission, or be initiated to stop transmission (namely discharging described IP service flow) by terminal or network.

If the new QoS of described IP service flow does not exceed the scope of the QoS rule of described IP service flow non-seamless shunting, described IP service flow is switched to non-seamless shunting from seamless shunting by the decision-making of described fixed network policy control functions entity.

Describe the decision-making of described fixed network policy control functions entity in the above-described embodiments and described IP service flow is switched to non-seamless shunting from seamless shunting, the IP service flow routing rule upgraded to the transmission of fixed network gateway and QoS rule, will describe fixed network gateway according to the IP service flow routing rule upgraded and the regular process switching to non-seamless to shunt described IP service flow of QoS below.

It is the schematic flow sheet of the changing method embodiment seven of IP service flow in the present invention see Fig. 9, Fig. 9.

The present embodiment describes the flow process that described IP service flow switches to non-seamless to shunt according to the IP service flow routing rule upgraded and QoS rule by fixed network gateway, comprising:

Step 700, after fixed network policy control functions entity determination terminal carries out the new QoS rule of the fixed network that the shunting of IP service flow non-seamless switches, send the IP service flow routing rule and QoS rule that upgrade to fixed network gateway BNG, in this QoS rule, comprise signing QoS attribute;

Step 701, BNG performs according to the IP service flow routing rule upgraded and QoS rule the flow process switching to non-seamless to shunt described IP service flow;

Step 702, BNG provides acknowledge message to described fixed network policy control functions entity sending strategy, shows whether successful switch is non-seamless shunting to described IP service flow;

Step 703, fixed network policy control functions entity is to mobile network's strategy and charging regulation function entity sends gateway control and QoS rule provides acknowledge message, shows whether successful switch is non-seamless shunting to described IP service flow.

After described IP service flow to switch to non-seamless to shunt according to IP service flow routing rule and QoS rule by described fixed network gateway, mobile network's strategy and charging regulation function entity provide described IP service flow to identify to billing function entity and non-seamless is shunted and indicated; Billing function entity carries out charging to the IP service flow that non-seamless is shunted, below by this process of detailed description according to the IP service flow routing rule upgraded.

It is the schematic flow sheet of the changing method embodiment eight of IP service flow in the present invention see Figure 10, Figure 10.

The gateway control that the fixed network controlling functions entity that method that the present embodiment provides describes returns to mobile network's policy functional entity and QoS rule confirm message show that described IP service flow successful switch is that non-seamless is when shunting, mobile network's policy functional entity initiates the process that charging upgrades, and comprising:

Step 800, mobile network's strategy sends " strategy and charging regulation provide " message with charging regulation function entity to PDNGW, wherein carries the IP service flow routing rule of renewal;

Step 801, after message that PDNGW receives " strategy and charging regulation provide ", stops receiving and sending packet corresponding to this IP service flow;

Step 802, PDNGW sends accounting request to online charging server OCS, carries described IP service flow mark and non-seamless shunting instruction, the charging regulation that please look for novelty in this accounting request;

Step 803, OCS replys charge response message to PDNGW.

After described IP service flow switches to non-seamless to shunt according to the IP service flow routing rule upgraded and QoS rule by described fixed network gateway, described mobile network strategy and charging regulation function entity provide described IP service flow to identify to Application Function (Applicationfunction, AF) and non-seamless is shunted and indicated; Described AF sets up session, for described IP service flow provides application layer conversation descriptor, below by this process of detailed description according to described IP service flow mark and non-seamless shunting instruction with fixed network policy control functions entity.

It is the schematic flow sheet of the changing method embodiment nine of IP service flow in the present invention see Figure 11, Figure 11.

The gateway control that what method that the embodiment of the present invention provides described is fixed network controlling functions entity returns to mobile network's policy functional entity and QoS rule confirm message show that described IP service flow successful switch is that non-seamless is when shunting, mobile network's policy functional entity initiates the process setting up session, comprising:

Step 900, mobile network's strategy sends event notification message with charging regulation function entity to AF, carry IP service flow mark and non-seamless shunting instruction in this event notification message, notify that the IP service flow of this IP service flow of described AF mark correspondence switches to non-seamless to shunt.Described fixed network policy control functions entity identification and/or address is also carried in described event notification message.

Step 901, after described AF receives the described event notification message of instruction, replys acknowledge message to described mobile network's strategy with charging regulation function entity.

Step 902, AF is according to the fixed network policy control functions entity identification in described event notification message and/or address, initiate to set up conversation message, for fixed network policy control functions entity provides the session description information of described IP service flow to fixed network policy control functions entity.

It is the schematic flow sheet of the changing method embodiment ten of IP service flow in the present invention see Figure 12, Figure 12.

In the present embodiment in detail, the flow process being initiated IP service flow to be switched to from seamless shunting via fixed network the request message that non-seamless is shunted by terminal will be described.

Step is described in detail as follows:

1, terminal is by WLAN and BBF access network access 3GPP core net, sets up the IP service flow of seamless shunting.

2, terminal is sent a request message to BNG by RG, ask the IP service flow of current seamless shunting to switch to non-seamless to shunt, and namely IP service flow no longer directly reaches correspondent network or equipment by BBF access network via 3GPP core net.The information of carrying in this request message comprises: terminal iidentification (InternationalMobileSubscriberIdentificationNumber, IMSI, also be international mobile subscriber identity), terminal local IP address, terminal local UDP (UserDatagramProtocol, User Datagram Protocol) port numbers, the mark (TrafficFlowIdentifier) of IP service flow, non-seamless shunting instruction, non-seamless shunting instruction also i.e. route changing instruction, mark or the address of what route changing instruction represented request is new object gateway, no longer mark or the address of 3GPP gateway, the new QoS of described IP service flow can also be carried in described request message, this QoS can with current seamless shunt time QoS similar and different.The IP service flow that request switches to non-seamless to shunt can be all or part of IP service flow in corresponding IP-CAN session, such as, comprise voice, data traffic flow in IP-CAN session, voice-and-data Business Stream can be asked all to switch to non-seamless to shunt, or only switch to non-seamless to shunt data traffic flow.

The mark of the IP service flow of 3, carrying in BNG foundation terminal request and/or terminal iidentification, and non-seamless shunting instruction, determine to need the IP service flow by current seamless shunting to switch to non-seamless to shunt.

4, BNG sends session modification Trigger message to BPCF, wherein carries current seamless shunting IP service flow mark and event instruction " Business Stream route changing/non-seamless shunting instruction ", triggers BPCF and carry out routing policy decision-making to current seamless shunting IP service flow.

5, BPCF is according to the IP service flow mark in the message received and/or terminal iidentification, determines " gateway control session " corresponding with this IP service flow and corresponding PCRF.

BPCF continues to perform step 6a below, or step 6b and 7b.

6a, BPCF send " gateway control and QoS rule request " message to PCRF, wherein the information such as the mark (being converted to corresponding 3GPP traffic stream identifier by BBF Network traffic identifier) of carried terminal mark, session identification, IP service flow and " Business Stream route changing/non-seamless shunt indicate ".

6b, BPCF send notice (Notification) or session modification Trigger message to PCRF, wherein carry the information such as session identification, the mark (being converted to corresponding 3GPP traffic stream identifier by BBF Network traffic identifier) of IP service flow and " Business Stream route changing/non-seamless shunting instruction ".

7b, PCRF reply response message to BPCF, confirm to receive above-mentioned notice or session modification Trigger message.

8, routing policy inquiry: PCRF to routing policy information between user-subscribed database and/or ANDSF inquiry system (being also routing policy ISRP:Inter-SystemRoutingPolicy between system), and judges whether to allow this IP service flow to switch to non-seamless to shunt by seamless shunting according to the message that user-subscribed database or ANDSF return.Described user-subscribed database is the one in SPR, UDR, HSS.

9, PCRF sends " gateway control and QoS rule are replied " message to BPCF.If this IP service flow switches to non-seamless to shunt by seamless shunting by PCRF decision-making, then carry the information such as the IP service flow routing rule of renewal and QoS rule in message.If this IP service flow does not switch to non-seamless to shunt by seamless shunting by PCRF decision-making, then comprise at least one in " not allowing non-seamless to shunt " instruction or the reason that do not allow non-seamless to shunt or old IP service flow routing rule in message.

As follows to the extended example of " gateway control and QoS rule request " message and " gateway control and QoS rule provide " message:

1) to the expansion of Routing-IP-AddressAVP: under non-trusted S2c interface architecture, when non-seamless is shunted, it is the UE local ip address that UE distributes that this Routing-IP-AddressAVP carries BBF network, instead of is the Care-of Address (CoA:CareofAddress) that UE distributes by 3GPPePDG.

2) to the expansion of Routing-Rule-DefinitionAVP: the AVP:Non-Seamless-Offload-IndicationAVP that increase by is new in Routing-Rule-DefinitionAVP; When this AVP value is 1, show that the IP service flow that this routing rule is corresponding will carry out non-seamless shunting.

Routing-Rule-Definition::＝<AVPHeader：1076>

{Routing-Rule-Identifier}

*[Routing-Filter]

[Precedence]

[Routing-IP-Address]

{Non-Seamless-Offload-Indication}

*[AVP]

3) to the expansion of Event-TriggerAVP: increase a new event " NON_SEAMLESS_OFFLOAD ".

10, BPCF carries out strategic decision-making.

If the message that BPCF receives shows that PCRF allows this IP service flow to switch to non-seamless to shunt, the QoS rule of the IP service flow non-seamless shunting that BPCF provides according to message, judges whether the new QoS of the described IP service flow that UE asks exceeds the QoS rule scope of its IP service flow non-seamless shunting; New QoS is the QoS different from the QoS of former seamless shunting IP service flow.If do not exceed 3GPP to contract scope, BPCF, further according to BBF network local policy and QoS rule, determines that this IP service flow non-seamless is diverted to routing rule and the QoS rule of this BBF network.Non-seamless is not switched to shunt this IP service flow in PCRF decision-making, or, the new QoS of the described IP service flow of UE request exceeds the signing scope of QoS rule of its IP service flow non-seamless shunting, or, when the new QoS of described IP service flow of UE request exceeds BBF network current available QoS scope, if the request message that BNG or terminal are initiated, BPCF sends refusal to BNG and switches message; If the request message that terminal is initiated, BNG and then the handover request to UE transmission message refusal UE; Can Reason For Denial be comprised in message, such as, " not allow non-seamless to shunt ", " exceeding signing scope " or " inadequate resource " etc.Described IP service flow will keep seamless shunting to continue transmission, or be initiated to stop transmission by terminal or network, and namely terminal or network discharge described IP service flow.

Subsequent step be IP service flow successfully non-seamless be diverted to the flow process of BBF network.

11, this IP service flow non-seamless is diverted to the routing rule of this BBF network and QoS rule is supplied to BNG by BPCF.Described routing rule comprises this IP service flow mark, non-seamless shunting instruction.

Policy information (policyinformation) mutual between BNG and BPCF can be expanded as follows:

1) IP service flow defining new non-seamless shunting describes, NonSeamlessOffloadServiceFlowDescription; Or

2) in existing ServiceFlowDescription definition, " Non-SeamlessOffloadIndication " is increased.

12, this IP service flow non-seamless is diverted to the routing rule of this BBF network and QoS rule is supplied to RG by BNG.

13, RG and/or BNG is the routed path that this IP service flow sets up non-seamless shunting according to the routing rule upgraded, and according to QoS rule for this IP service flow distributes corresponding resource, thus start the upstream data bag of this IP service flow to be directly sent to correspondent network or equipment by BBF access network, and start the downlink data packet receiving this IP service flow from correspondent network or equipment, send to UE.

14, BNG is transmitted a reply message to UE by RG, shows that the IP service flow of asking has switched to non-seamless to shunt.

15, BNG replys message to BPCF, shows strategy/regular executed that BPCF provides.

16, BPCF replys " gateway control and QoS rule provide confirmation " message to PCRF, shows strategy/regular executed that PCRF provides.

17, PCRF sends " strategy and charging regulation provide " message to PDNGW, wherein carries the IP service flow routing rule of renewal.After message that PDNGW receives " strategy and charging regulation provide ", stopping is received and sends packet corresponding to this IP service flow.

18, PDNGW sends accounting request to OCS (online charging server), wherein carries this IP service flow mark and non-seamless shunting instruction, to ask to upgrade charging regulation according to new IP service flow routing rule (non-seamless shunting).

19, OCS replys charge response message to PDNGW.

20, PDNGW replys " strategy and charging regulation confirm " message to PCRF.

21, PCRF sends " event notice " message to AF, wherein carries IP service flow mark, non-seamless shunting instruction and BPCF mark/address, notice AF " this IP service flow switches to non-seamless to shunt ".

22, after AF receives " event notice " message of instruction " IP service flow switches to non-seamless to shunt ", acknowledge message is replied to PCRF.

23-24, AF, according to the BPCF mark/address in " event notice " message, initiate to set up session to BPCF, for BPCF provides this non-seamless to shunt the application layer conversation descriptor of IP service flow.Follow-up AF can with BPCF direct communication, upgrade the session information of this IP service flow.

It should be noted that, above-mentioned request message can also be initiated by BNG or BPCF in fixed network.

It is the schematic flow sheet of the changing method embodiment 11 of IP service flow in the present invention see Figure 13, Figure 13;

In the present embodiment, will the flow process being initiated the method switching to non-seamless to shunt from seamless shunting IP service flow by terminal directly to mobile network be described in detail, specific as follows:

2, terminal sends BU (BindingUpdate to PDNGW, Binding Update) request, the IP service flow of current seamless shunting switches to non-seamless to shunt by request, and namely IP service flow no longer directly reaches correspondent network or equipment by BBF access network via 3GPP core net.The information of carrying in this request message comprises: terminal iidentification (IMSI), the IP service flow routing rule (comprising IP service flow mark, non-seamless shunting instruction etc.) upgraded; Wherein can also carry the QoS of the described IP service flow of request, this QoS can with current seamless shunt time QoS similar and different.

To BU message (the i.e. two stack mobile IP v 6 (Dual-StackMIPv6 of S2c interface, DSMIPv6) the BindingUpdate message of agreement) specifically expansion is as follows, to indicate the IP service flow routing rule of renewal (switching to non-seamless to shunt by seamless shunting):

1) implicit expression instruction: make MobileRouterFlag (R)=0 in BU message, show not need to carry out " home network prefix is reserved ", namely do not distribute home network prefix, thus when PDNGW receives this BU message, judge that this IP service flow carries out non-seamless shunting;

2) explicit instruction: expand BU message BID or FIDmobilityoption, namely defines new field Non-SeamlessOffloadIndication; When this field value is 1, show that this IP service flow will carry out non-seamless shunting.

3) above-mentioned implicit expression or explicit method no matter is adopted to shunt to indicate IP service flow non-seamless, routingaddress in BID/FID is BBF network is the UE local ip address that UE distributes, instead of is the Care-of Address (CoA:CareofAddress) that UE distributes by 3GPPePDG.

3, PDNGW sends IP-CAN session modification Trigger message to PCRF, wherein carries the IP service flow routing rule of renewal, and the IP service flow routing rule of this renewal comprises IP service flow mark, non-seamless shunting instruction.

4, routing policy inquiry: PCRF to user-subscribed database or ANDSF query routing policy information, described user-subscribed database namely: signing attribute database SPR, customer data base UDR, or home signature user database HSS.According to the message that user-subscribed database or ANDSF return, PCRF judges whether that allowing that this IP service flow is changed into non-seamless by seamless shunting shunts.

5, PCRF sends " gateway control and QoS rule provide " message to BPCF.Shunt if PCRF allows that this IP service flow is changed into non-seamless by seamless shunting, then carry IP service flow routing rule and the QoS rule of renewal in message, this QoS rule can comprise signing QoS attribute (QoSProfile), and the IP service flow routing rule of this renewal comprises non-seamless shunting instruction.

6-9, with embodiment one step 10-13.

10-11, with embodiment one step 15-16.

12, PCRF replys IP-CAN session modification acknowledge message to PDNGW.

13, PDNGW replys BA (BindingAcknowledge, binding acknowledgement) message to UE.

14-15, with embodiment one step 18-19.

16-19, with embodiment one step 21-24.

It is the schematic flow sheet of the changing method embodiment 12 of IP service flow in the present invention see Figure 14, Figure 14.

In the present embodiment, will the flow process initiatively being initiated the method switching to non-seamless to shunt from seamless shunting IP service flow by mobile network be described in detail, specific as follows:

2, due to reasons such as the signing change of user, carrier policy change or offered load are overweight, PCRF determines the routing policy of the IP service flow changing current seamless shunting.

3, PCRF query routing strategy, particularly: PCRF, to user-subscribed database or ANDSF query routing policy information, judges whether that allowing that this IP service flow is changed into non-seamless by seamless shunting shunts accordingly.

PCRF continues to perform step 4a below or step 4b-7b.

4a, PCRF send " gateway control and QoS rule provide " message to BPCF, wherein carry the information such as IP service flow routing rule (comprising non-seamless shunting instruction), QoS rule (QoSRule) of renewal.

4b, PCRF send notice (Notification) message to BPCF, wherein the information such as carried terminal mark, session identification, IP service flow mark and " Business Stream route changing/non-seamless shunting indicate " instruction.

5b, BPCF reply response message to PCRF, acknowledge receipt of notice.

6b, BPCF send " gateway control and QoS rule request " message to PCRF, wherein carried terminal mark, session identification, IP service flow mark, and " Business Stream route changing/non-seamless shunting instruction ", show BBF network support and ask the IP service flow of current seamless shunting to be changed into non-seamless shunting.

7b, PCRF send " gateway control and QoS rule are replied " message to BPCF, wherein carry the information such as IP service flow routing rule (comprising non-seamless shunting instruction), QoS rule of renewal.

8-11, with embodiment one step 10-13.

12-21, with embodiment one step 15-24.

Be described above embodiment of the method IP service flow being switched to non-seamless shunting from seamless shunting provided by the invention, will the system realizing IP service flow being switched to seamless shunting from seamless shunting be introduced below.

See the composition schematic diagram that Figure 15, Figure 15 are IP service flow switched system embodiment one provided by the invention.

IP service flow provided by the invention comprises mobile network 1 and fixed network 2 from the system that seamless shunting switches to non-seamless to shunt, mobile network's strategy in mobile network 1 is realize main network elements of the present invention with charging regulation function entity 10, it flows to the request message of non-seamless shunting for receiving seamless point or initiatively initiates IP service flow to be switched to non-seamless shunting from seamless shunting, and whether decision-making allows described IP service flow to switch to non-seamless to shunt from seamless shunting.

Optionally, described system also comprises terminal 3, this terminal 3 for sending second request message to described mobile network's strategy with charging regulation function entity 10 via fixed network, or directly sends seamless point three request message that flow to non-seamless shunt to described mobile network's strategy with charging regulation function entity 10 by mobile network; Terminal iidentification, the mark of IP service flow and non-seamless shunting instruction is carried in described second request message or the 3rd request message.

Optionally, described fixed network 2 comprises fixed network policy control functions entity 20 and fixed network gateway 21:

Fixed network gateway 21, for receive self terminal 3 send the second request message switching to non-seamless to shunt the IP operation of seamless shunting after, session modification Trigger message is sent to fixed network policy control functions entity, or send session modification Trigger message directly to fixed network policy control functions entity 20, carry the IP service flow mark of described seamless shunting in described session modification Trigger message and represent the event instruction of IP service flow route changing or non-seamless shunting;

Fixed network policy control functions entity 20, for after the session modification Trigger message receiving described fixed network gateway 21, or send seamless point of the first request message flowing to non-seamless and shunt directly to mobile network's strategy with charging regulation function entity 10, carried terminal mark, IP service flow mark and non-seamless shunting instruction in this first request message.

Alternatively, described mobile network 1 also comprises:

Packet data gateway 11, for receiving the 3rd request message switching to non-seamless to shunt the IP operation of seamless shunting that described terminal 2 sends, and send IP to mobile network's strategy access connected reference session modification Trigger message with charging regulation function entity 10, wherein carry and comprise the IP service flow routing rule that IP service flow mark and non-seamless shunt the renewal indicated.

See the composition schematic diagram of Figure 16, Figure 16 IP service flow switched system provided by the invention embodiment two.

The system switching to non-seamless to shunt from seamless shunting IP service flow that this enforcement provides, it, except comprising each network element as shown in embodiment one, also comprises:

Routing policy functional entity 4, for receiving described mobile network strategy and charging regulation function entity 10 to routing policy query messages between its transmitting system, to routing policy between described mobile network's strategy and charging regulation function entity retrieval system, or whether decision-making allows switch to non-seamless to shunt from seamless shunting described IP service flow and its result of decision be back to described mobile network strategy and charging regulation function entity 10.Routing policy functional entity is specifically as follows SPR, the one in UDR, HSS, ANDSF.

After mobile network's strategy and charging regulation function entity 10 receive the reply message comprising routing policy between system from routing policy functional entity 4, described reply message comprises permission or described IP service flow switches to non-seamless to shunt from seamless shunting by refusal, whether decision-making switches to non-seamless to shunt from seamless shunting IP service flow, then the result of decision is sent to fixed network policy control functions entity 20;

Fixed network policy control functions entity 20 is also for the IP service flow routing rule of renewal sent with charging regulation function entity 10 according to described mobile network strategy and the service quality QoS attribute of contracting, or, further according to the local network policy of fixed network, whether decision-making is switched to non-seamless shunting by described IP service flow from seamless shunting.

When terminal 3 or fixed network initial request messages, described fixed network policy control functions entity 20 judges whether the new QoS of the described IP service flow of terminal 3 or fixed network request exceeds the QoS rule scope of IP service flow non-seamless shunting;

If the new QoS of IP service flow described in terminal 3 or fixed network request does not exceed the scope of the QoS rule of IP service flow non-seamless shunting, described fixed network policy control functions entity 20 also needs further according to the local policy of fixed network 2, determines that terminal 3 carries out the QoS rule of the fixed network that the shunting of IP service flow non-seamless switches;

If the new QoS of described IP service flow exceeds the scope of the QoS rule of IP service flow non-seamless shunting, described IP service flow is not switched to non-seamless shunting from seamless shunting by decision-making.

Described IP service flow is not switched to non-seamless shunting from seamless shunting by the decision-making of described fixed network policy control functions entity 20, sends refusal switch message to fixed network gateway 21;

Described fixed network gateway 21 sends refusal to described terminal 3 and switches message.

After described IP service flow to switch to non-seamless to shunt according to IP service flow routing rule and QoS rule by described fixed network gateway, mobile network's strategy and charging regulation function entity 10 provide described IP service flow to identify to billing function entity and non-seamless is shunted and indicated; Billing function entity carries out charging according to the IP service flow routing rule upgraded to the IP service flow that non-seamless is shunted, and below will describe in detail.

See the composition schematic diagram that Figure 17, Figure 17 are IP service flow switched system embodiment three provided by the invention.

System as shown in the figure, this system, except comprising each network element in above-described embodiment two, also comprises:

Billing function entity 5, for receiving mobile network's packet data gateway to its IP service flow mark sent and non-seamless shunting instruction, and carries out charging according to the IP service flow routing rule upgraded to the IP service flow that non-seamless is shunted.

Particularly, mobile network's strategy sends " strategy and charging regulation provide " message with charging regulation function entity 10 to packet data gateway (PDNGW), wherein carries the IP service flow routing rule of renewal; After message that PDNGW receives " strategy and charging regulation provide ", stop receiving and sending packet corresponding to this IP service flow; PDNGW is to billing function entity, and such as, online charging server (OnlineChargeServer, OCS), sends accounting request, carries described IP service flow mark and non-seamless shunting instruction, the charging regulation that please look for novelty in this accounting request; OCS replys charge response message to PDNGW.

After described IP service flow to switch to non-seamless to shunt according to the IP service flow routing rule upgraded and QoS rule by fixed network gateway 21, described mobile network's strategy and charging regulation function entity 10 provide described IP service flow to identify to Application Function AF and non-seamless is shunted and indicated; Application Function sets up session according to described IP service flow mark and non-seamless shunting instruction with fixed network policy control functions entity, for described IP service flow provides application layer conversation descriptor, below will describe in detail.

See the composition schematic diagram that Figure 18, Figure 18 are IP service flow switched system embodiment four provided by the invention.

Application Function 6, to identify to its IP service flow sent from described mobile network strategy and charging regulation function entity and non-seamless is shunted and indicated for receiving, and set up session, for described IP service flow provides application layer conversation descriptor according to described IP service flow mark and non-seamless shunting instruction with fixed network policy control functions entity.

Particularly, mobile network's strategy sends event notification message with charging regulation function entity 10 to Application Function (AF) 6, carry IP service flow mark and non-seamless shunting instruction in this event notification message, notify that described in described AF6, IP service flow switches to non-seamless to shunt.After described AF6 receives the described event notification message of instruction, reply acknowledge message to described mobile network's strategy with charging regulation function entity 10.Described fixed network policy control functions entity identification and/or address can also be carried in this event notification message, AF6 is according to the fixed network policy control functions entity identification in described event notification message and/or address, initiate to set up session, for fixed network policy control functions entity provides the application layer conversation descriptor of described IP service flow to fixed network policy control functions entity.

Implement the system switching to non-seamless to shunt from seamless shunting IP service flow provided by the invention, 3GPP mobile network can be enable to perceive, and terminal or fixed network initiate switches to non-seamless to shunt request from seamless shunting IP service flow, or initiatively initiate IP service flow to switch to non-seamless to shunt from seamless shunting, which IP service flow in the IP service flow of terminal non-seamless can be diverted to fixed network and carry out decision-making, and the service quality of non-seamless shunting Business Stream controls, thus optimize the flow process that IP service flow switches to non-seamless to shunt from seamless shunting, shorten switching time, improve switching efficiency.

The foregoing describe the system embodiment switching to non-seamless to shunt from seamless shunting IP service flow, below by mobile network's strategy of further describing in this system and the constitute and function of charging regulation function entity.

See the composition schematic diagram that Figure 19, Figure 19 are mobile network's strategy and charging regulation function entity embodiment one in the present invention.

Mobile network's strategy and charging regulation function entity 10 that the present embodiment provides, comprising:

Whether switch decision module 101, switch to non-seamless to shunt from seamless shunting IP service flow for decision-making;

Switch indicating module 102, for the result of decision of described switch decision module 101 is sent to fixed network policy control functions entity, at least non-seamless is switched to shunt from seamless shunting described IP service flow according to the described result of decision to make described fixed network policy control functions entity, or keep seamless shunting, or stop transmission.

See the composition schematic diagram that Figure 20, Figure 20 are mobile network's strategy and charging regulation function entity embodiment two in the present invention.

Mobile network's strategy that this enforcement provides, also comprises except comprising with except upper module with charging regulation function entity 10:

Request receiving module 100, for the first request message switching to non-seamless to shunt from seamless shunting described IP service flow, carried terminal mark, the mark of described IP service flow and non-seamless shunting instruction in described first request message.

Wherein, described request receiver module 100 is for receiving seamless point of the first request message flowing to non-seamless and shunt sent from fixed network; Described first request message is gateway control and service quality QoS rule request message, or notification message; Described gateway control and QoS rule request message or notification message are that described fixed network policy control functions entity is initiatively initiated, or described fixed network policy control functions entity sends after receiving the session modification Trigger message that fixed network gateway sends;

In another kind of execution mode, described request receiver module 100 is also for receiving the first request message from mobile network, and this first request message is session modification Trigger message; Described session modification Trigger message is that the packet data gateway of mobile network is initiated, or described packet data gateway sends after the 3rd request message switching to non-seamless to shunt from seamless shunting described IP service flow receiving terminal transmission.

Preferably, described mobile network's strategy also comprises with charging regulation function entity 10:

Enquiry module 103, for signing attribute database SPR or customer data base UDR or home signature user database HSS or routing policy between access network discovery and selection entity A NDSF inquiry system;

Described switch decision module 101 can active decision also can according to the Query Result of described enquiry module 103, whether decision-making switches to non-seamless to shunt described IP service flow.

Described switching indicating module 102 is concrete

For sending gateway control and service quality QoS rule reply message to described fixed network policy control functions entity, described gateway control and QoS rule reply the IP service flow routing rule and QoS rule that carry renewal in message; Or

For sending gateway control to described fixed network policy control functions entity and service quality QoS rule replys message, described gateway control and service quality QoS rule reply in message at least one in the reason of instruction or the refusal non-seamless shunting of carrying the shunting of refusal non-seamless or former IP service flow routing rule.

Implement mobile network provided by the invention strategy and charging regulation function entity, can receive that terminal or fixed network initiate switch to non-seamless to shunt request from seamless shunting IP service flow time, which IP service flow in the IP service flow of terminal non-seamless can be diverted to fixed network and carry out decision-making, and the service quality of non-seamless shunting Business Stream controls, thus optimize the flow process that IP service flow switches to non-seamless to shunt from seamless shunting, shorten switching time, improve switching efficiency.

See the composition schematic diagram that Figure 21, Figure 21 are mobile network's strategy and charging regulation function entity embodiment three in the present invention.

Mobile network's strategy that the present embodiment provides, also comprises with charging regulation function entity 10 except comprising the module as described in embodiment one:

Detection module 104, for detecting, whether user is signing changes or whether carrier policy changes or whether offered load is overweight.

When then described switch decision module 101 is specifically for detecting that at described detection module 104 the signing change of user or carrier policy change or offered load are overweight, IP service flow switches to non-seamless to shunt from seamless shunting by decision-making.

Alternatively, described mobile network's policy functional entity also comprises:

Enquiry module 103, for inquiring about routing policy between signing attribute and/or system;

Described switch decision module 101 is also for the Query Result according to described enquiry module 101, and whether decision-making switches to non-seamless to shunt described IP service flow.

When described IP service flow switches to non-seamless to shunt by the decision-making of described switch decision module 101, described switching indicating module 102 is concrete

For providing message to described fixed network policy control functions entity transmission gateway control and service quality QoS rule, described gateway control and QoS rule provide in message the IP service flow routing rule and QoS rule that carry renewal, and this QoS rule comprises signing QoS attribute.

Implement mobile network provided by the invention strategy and charging regulation function entity, it can initiatively initiate IP service flow to switch to non-seamless to shunt from seamless shunting, which IP service flow in the IP service flow of terminal non-seamless can be diverted to fixed network and carry out decision-making, and the service quality of non-seamless shunting Business Stream controls, thus optimize the flow process that IP service flow switches to non-seamless to shunt from seamless shunting, shorten switching time, improve switching efficiency.

See the composition schematic diagram that Figure 22, Figure 22 are terminal embodiment one in the present invention.

The terminal 3 that the present embodiment provides comprises:

Request sending module 30, for sending the second request message to fixed network gateway, or sending the 3rd request message to the packet data gateway of mobile network, asking IP service flow to switch to non-seamless to shunt from seamless shunting;

Particularly, request sending module 30 sends second request message to mobile network's strategy with charging regulation function entity via the fixed network gateway in fixed network and fixed network policy control functions entity; Or by two stack mobile IPv 6 protocol DSMIPv6 Binding Update BU message, packet data gateway via mobile network sends described 3rd request message to described mobile network's strategy with charging regulation function entity, carries the IP service flow routing rule of renewal in described Binding Update BU message.

Switching executing module 31, for after receiving the acknowledge message switching to non-seamless to shunt from seamless shunting described IP service flow, sets up the IP service flow of non-seamless shunting.

Implement terminal provided by the invention, what this terminal can be initiated by fixed network or mobile network switches to non-seamless to shunt request from seamless shunting IP service flow, which non-seamless can be diverted to fixed network and carry out decision-making IP service flow in the IP service flow of terminal according to this request message with charging regulation function entity to make mobile network's strategy, and the service quality of non-seamless shunting Business Stream controls, thus optimize the flow process that IP service flow switches to non-seamless to shunt from seamless shunting, shorten switching time, improve switching efficiency.

One of ordinary skill in the art will appreciate that all or part of flow process realized in above-described embodiment method, that the hardware that can carry out instruction relevant by computer program has come, described program can be stored in a computer read/write memory medium, this program, when performing, can comprise the flow process of the embodiment as above-mentioned each side method.Wherein, described storage medium can be magnetic disc, CD, read-only store-memory body (Read-OnlyMemory, ROM) or random store-memory body (RandomAccessMemory, RAM) etc.

The above is the preferred embodiment of the present invention; it should be pointed out that for those skilled in the art, under the premise without departing from the principles of the invention; can also make some improvements and modifications, these improvements and modifications are also considered as protection scope of the present invention.

Claims

1. a method for IP service flow switching, is characterized in that, comprising:

Whether mobile network's strategy switches to non-seamless to shunt from seamless shunting described IP service flow with charging regulation function entity decision-making;

2. the method for claim 1, is characterized in that, whether described mobile network strategy and charging regulation function entity decision-making switch to before non-seamless shunts by described IP service flow from seamless shunting, also comprise:

Described mobile network's strategy receives with charging regulation function entity the first request message switching to non-seamless to shunt from seamless shunting described IP service flow.

3. method as claimed in claim 2, it is characterized in that, described first request message is gateway control and service quality QoS rule request message, or notification message; Described gateway control and QoS rule request message or notification message are that described fixed network policy control functions entity is initiatively initiated, or described fixed network policy control functions entity sends after receiving session modification Trigger message.

4. method as claimed in claim 2, it is characterized in that, described first request message is session modification Trigger message; Described session modification Trigger message is that the packet data gateway of mobile network is initiated, or described packet data gateway sends after the 3rd request message switching to non-seamless to shunt from seamless shunting described IP service flow receiving terminal transmission.

5. the method for claim 1, is characterized in that, whether described mobile network strategy and charging regulation function entity decision-making switch to before non-seamless shunts by described IP service flow from seamless shunting, also comprise:

Whether described mobile network strategy and charging regulation function entity detect user and contract and to change or whether carrier policy changes or whether offered load is overweight.

6. method as claimed in claim 2, is characterized in that, the mark of carried terminal mark, described IP service flow and non-seamless shunting instruction in described first request message.

7. the method according to any one of claim 1 to 6, is characterized in that, whether described mobile network's strategy switches to non-seamless to shunt from seamless shunting described IP service flow with charging regulation function entity decision-making, comprising:

Described mobile network's strategy and charging regulation function entity are to routing policy between signing attribute database SPR or customer data base UDR or home signature user database HSS inquiry system;

8. method as claimed in claim 7, it is characterized in that, between described system, routing policy is supplied to described SPR or UDR or HSS by access network discovery and selection functional entity ANDSF in advance; Or

Between described system, routing policy is receiving after mobile network's strategy to initiate signing attribute query request with charging regulation function entity to SPR or UDR or HSS, to ANDSF request gained.

9. the method according to any one of claim 1 to 6, is characterized in that, whether described mobile network's strategy switches to non-seamless to shunt from seamless shunting described IP service flow with charging regulation function entity decision-making comprises:

Described mobile network strategy and charging regulation function entity are to routing policy request between ANDSF initiation system;

The reply message whether switching to non-seamless to shunt described IP service flow that between the system that described mobile network strategy and charging regulation function entity return according to described ANDSF, routing policy or described ANDSF return, whether decision-making switches to non-seamless to shunt described IP service flow.

10. the method according to any one of Claims 1-4, is characterized in that, the result of decision is sent to described fixed network policy control functions entity with charging regulation function entity by described mobile network's strategy, comprising:

Described IP service flow is not sent to described fixed network policy control functions entity from the result of decision that seamless shunting switches to non-seamless to shunt with charging regulation function entity by decision-making by described mobile network's strategy, specifically comprises:

Described mobile network strategy and charging regulation function entity send gateway control to fixed network policy control functions entity and service quality QoS rule replys message, the instruction of wherein carrying the shunting of refusal non-seamless or at least one refused in reason that non-seamless shunts or former IP service flow routing rule;

Described fixed network policy control functions entity sends refusal to terminal or fixed network gateway and switches message.

11. methods according to any one of Claims 1-4, is characterized in that, the result of decision is sent to fixed network policy control functions entity with charging regulation function entity by described mobile network's strategy, comprising:

Described IP service flow is sent to described fixed network policy control functions entity from the result of decision that seamless shunting switches to non-seamless to shunt with charging regulation function entity by described mobile network's strategy, specifically comprises:

Described mobile network's strategy and charging regulation function entity send gateway control to fixed network policy control functions entity and service quality QoS rule replys message, and described gateway control and QoS rule reply the IP service flow routing rule and QoS rule that carry renewal in message; Or,

Described mobile network's strategy sends gateway control with charging regulation function entity to fixed network policy control functions entity and service quality QoS rule provides message, and described gateway control and QoS rule provide in message the IP service flow routing rule and QoS rule that carry renewal.

12. methods as claimed in claim 11, it is characterized in that, described mobile network strategy comprises after the result of decision being sent to fixed network policy control functions entity with charging regulation function entity: described fixed network policy control functions entity receives gateway control that described mobile network strategy and charging regulation function entity send and QoS is regular replys message or gateway control and service quality QoS rule and provide message;

Described fixed network policy control functions entity sends gateway control and QoS rule confirm message to mobile network's strategy with charging regulation function entity, shows whether successful switch is non-seamless shunting to described IP service flow.

13. methods as claimed in claim 12, it is characterized in that, described fixed network policy control functions entity receives gateway control that described mobile network strategy sends with charging regulation function entity and QoS is regular replys after message or gateway control and service quality QoS rule provides message, comprising:

Described fixed network policy control functions entity replys according to described gateway control and QoS rule IP service flow routing rule and the QoS rule that message or gateway control and service quality QoS rule provide the renewal of carrying in message, and the local policy of fixed network, determine the QoS rule that described IP service flow non-seamless is shunted.

14. methods as claimed in claim 13, it is characterized in that, described fixed network policy control functions entity is according to the IP service flow routing rule of described renewal and QoS rule, and the local policy of fixed network, determine that terminal carries out the QoS rule of IP service flow non-seamless shunting, comprising:

If when carrying the new QoS of described IP service flow in the second request message that described terminal sends or the session modification Trigger message that fixed network sends, described fixed network policy control functions entity judges whether the new QoS of described IP service flow exceeds the scope of the QoS rule of described IP service flow non-seamless shunting;

If the new QoS of described IP service flow exceeds the scope of the QoS rule of described IP service flow non-seamless shunting, described IP service flow is not switched to non-seamless shunting from seamless shunting by the decision-making of described fixed network policy control functions entity;

15. methods as claimed in claim 13, is characterized in that, after described fixed network policy control functions entity determines the QoS rule that described IP service flow non-seamless is shunted, send the IP service flow routing rule and QoS rule that upgrade to fixed network gateway;

Described IP service flow switches to non-seamless to shunt according to the IP service flow routing rule upgraded and QoS rule by described fixed network gateway;

Described fixed network gateway provides acknowledge message to described fixed network policy control functions entity sending strategy, shows whether successful switch is non-seamless shunting to described IP service flow.

16. methods as claimed in claim 12, is characterized in that, described fixed network policy control functions entity also comprises after sending gateway control and QoS rule confirm message to mobile network's strategy with charging regulation function entity:

Described mobile network's strategy provides message with charging regulation function entity to packet data gateway sending strategy and charging regulation, wherein carries the IP service flow routing rule of renewal;

After described packet data gateway receives strategy and charging regulation provides message, stop receiving and sending packet corresponding to this IP service flow.

17. methods as claimed in claim 16, is characterized in that, after described packet data gateway receives strategy and charging regulation provides message, also comprise:

Described packet data gateway sends accounting request to online charging server OCS, carries described IP service flow mark and non-seamless shunting instruction, the charging regulation that please look for novelty in this accounting request;

Described OCS replys charge response message to described packet data gateway.

18. methods as claimed in claim 12, is characterized in that, described fixed network policy control functions entity also comprises after sending gateway control and QoS rule confirm message to mobile network's strategy with charging regulation function entity:

Described mobile network's strategy sends event notification message with charging regulation function entity to Application Function AF, carries IP service flow mark and non-seamless shunting instruction, notify that described in described AF, IP service flow switches to non-seamless to shunt in described event notification message;

After described AF receives described event notification message, reply acknowledge message to described mobile network's strategy with charging regulation function entity.

19. methods as claimed in claim 18, is characterized in that, described mobile network's strategy sends event notification message with charging regulation function entity to Application Function AF, also comprises:

Described fixed network policy control functions entity identification and/or address is also carried in described event notification message;

Described AF is according to the fixed network policy control functions entity identification carried in described event notification message and/or address, initiate to set up session, for fixed network policy control functions entity provides the session description information of described IP service flow to fixed network policy control functions entity.

20. methods as claimed in claim 14, is characterized in that, carried terminal mark, the mark of described IP service flow and non-seamless shunting instruction in described second request message.

21. methods as claimed in claim 4, is characterized in that, carried terminal mark, the mark of described IP service flow and non-seamless shunting instruction in described 3rd request message.

22. 1 kinds of mobile network's strategies and charging regulation function entity, is characterized in that, comprising:

23. mobile network's strategy as claimed in claim 22 and charging regulation function entities, it is characterized in that, described entity also comprises:

Request receiving module, for receiving the first request message switching to non-seamless to shunt from seamless shunting described IP service flow, carried terminal mark, the mark of described IP service flow and non-seamless shunting instruction in described first request message.

24. mobile network's strategy as claimed in claim 22 and charging regulation function entities, it is characterized in that, described entity also comprises:

Detection module, for detecting, whether user is signing changes or whether carrier policy changes or whether offered load is overweight;

Described switch decision module is when described detection module detects the signing change of user or carrier policy changes or offered load is overweight, and IP service flow switches to non-seamless to shunt from seamless shunting by decision-making.

25. as described in claim 23 or 24 mobile network strategy and charging regulation function entity, it is characterized in that, described entity also comprises:

Enquiry module, for signing attribute database SPR or customer data base UDR or home signature user database HSS or routing policy between access network discovery and selection entity A NDSF inquiry system;

Whether described switch decision module switches to non-seamless to shunt described IP service flow according to the Query Result decision-making of described enquiry module.

26. mobile networks as claimed in claim 23 strategy and charging regulation function entities, is characterized in that, described switching indicating module specifically for:

When described IP service flow switches to non-seamless to shunt by described switch decision module decision-making, send gateway control to described fixed network policy control functions entity and service quality QoS rule provides or gateway control and service quality QoS rule reply message, described gateway control and QoS rule provide or gateway control and service quality QoS rule reply the IP service flow routing rule and QoS rule that carry renewal in message;

When described IP service flow does not switch to non-seamless to shunt by described switch decision module decision-making, send gateway control to described fixed network policy control functions entity and service quality QoS rule replys message, wherein carry one or more in the instruction of refusal non-seamless shunting or the reason of refusal non-seamless shunting or former IP service flow routing rule.

27. mobile network's strategy as claimed in claim 24 and charging regulation function entities, it is characterized in that, described switching indicating module is specifically for providing message to described fixed network policy control functions entity transmission gateway control and service quality QoS rule, and described gateway control and QoS rule provide in message the IP service flow routing rule and QoS rule that carry renewal.