CN103312683A - TDF (Traffic Detection Function) processing method and PCRF (Policy and Charging Rules Function) - Google Patents

Abstract

The present invention discloses a TDF session processing method and PCRF. The method includes: PCRF receives a TDF session establishment message from TDF, wherein the TDF session establishment message carries a first address of user equipment UE; PCRF judges that the first address corresponds to Whether there is an established TDF session of the second address in the IP-CAN session; if yes, the PCRF returns a TDF session establishment rejection message of the first address to the TDF. By using the present invention, it solves the problem in the related art that there are two TDF sessions in one IP-CAN session at the same time, and the service detection for the same IP-CAN session needs to be reported through different TDF sessions, thereby saving system resources and at the same time The signaling overhead in the interaction process is also reduced, and the resource utilization rate of the system is improved.

Description

TDF session processing method and PCRF

technical field

The present invention relates to the communication field, in particular, to a processing method for a Traffic Detection Function (Traffic Detection Function, referred to as TDF) session and a Policy Control and Charging Rules Function entity (Policy and Charging Rules Function, referred to as PCRF).

Background technique

Since the establishment of the 3rd Generation Partnership Project Phase 7 (3GPP Release7) standard system, the policy and charging functions are implemented by the policy and charging control (Policy and Charging Control, referred to as PCC) framework. The PCC architecture is a functional framework that can be applied to multiple access technologies. For example, the PCC architecture can be applied to the UMTS Terrestrial Radio Access Network (UMTS Terrestrial RadioAccess Network, referred to as UMTS) of the Universal Mobile Telecommunications System (UMTS for short). UTRAN), Global system for Mobile Communication (GSM for short)/GSM Data Enhanced Evolution (Enhanced Data Rate for GSM Evolution, EDGE for short) wireless access network, Interworking WLAN (Interworking WLAN for short, I -WLAN) and the evolved packet system (Evolved Packet System, referred to as EPS).

The PCC mainly implements two functions of policy control and charging. FIG. 1 is a schematic diagram of an existing Rel-11 PCC architecture. The following describes each logical functional entity and its interface function in the PCC architecture shown in FIG. 1 . As shown in Figure 1:

The application function (AF) is used to provide an access point for service applications, and the network resources used by these service applications require dynamic policy control. When negotiating parameters on the service plane, the AF transmits relevant service information to the PCRF. If the service information is consistent with the PCRF policy, the PCRF accepts the negotiation; otherwise, the PCRF rejects the negotiation, and gives the service parameters acceptable to the PCRF in feedback. Subsequently, the AF may return these parameters to the user equipment (User Equipment, UE for short). Wherein, the interface between the AF and the PCRF is the Rx interface.

The PCRF is the core of the PCC and is responsible for making policy decisions and charging rules. PCRF provides network control rules based on service data flow. These network controls include service data flow detection, gating control (Gating Control), Quality of Service (QoS for short) control, and data flow-based charging. The PCRF sends the policy and charging rules formulated by it to the Policy and Control Enforcement Function (PCEF for short) for execution; at the same time, the PCRF also needs to ensure that these rules are consistent with the user's subscription information. Among them, the basis for the PCRF to formulate policies and charging rules includes: information related to services obtained from the AF, and user policy and charging control related to policy control and charging obtained from the Subscription Profile Repository (SPR) Subscription information, and bearer-related network information obtained from the PCEF through the Gx interface.

The PCEF is usually located in a gateway (Gate-Way, GW for short), and executes policies and charging rules formulated by the PCRF on the bearer plane. PCEF detects the service data flow according to the service data flow filter in the rules sent by PCRF, and then executes the policies and charging rules formulated by PCRF for these service data flows; when the bearer is established, PCEF performs resource According to the information provided by the AF, the PCEF triggers and reports the events that occur on the bearer network according to the events subscribed by the PCRF; according to the charging rules sent by the PCRF, the PCEF performs the corresponding service data flow charging operations, and calculates The fee can be charged online or offline. If it is online charging, PCEF needs to perform credit management together with the Online Charging System (OCS for short); exchange related billing information. Wherein, the interface between the PCEF and the PCRF is a Gx interface, the interface between the PCEF and the OCS is a Gy interface, and the interface between the PCEF and the OFCS is a Gz interface. PCEF can also have TDF. The PCEF can perform application detection and policy enforcement (such as gating, redirection, and bandwidth limitation) according to local configurations or PCC rules containing application detection control policies delivered by the PCRF. PCEF is generally located on the gateway of the network, such as the Packet Data Network Gateway (PDN-GW) of EPS, and the GPRS Gateway Support Node (GatewayGPRS Support Node, GGSN for short) in General Packet Radio Service (GPRS for short). ) and the Packet Data Gateway (PDG for short) in the I-WLAN.

Of course, TDF can also be deployed independently. In the case of independent deployment, TDF and PCRF are connected through the Sd interface, and TDF can be implemented according to pre-configured or PCRF-delivered Application Detection and Control (ADC) rules. Application detection and policy enforcement.

The Bearer Binding and Event Reporting Function (BBERF for short) is usually located in the Access Network Gateway. For example: when the user equipment accesses the EPS through E-UTRAN, and the service gateway S-GW and P-GW adopt the proxy mobile Internet protocol version 6 (Proxy Mobile Internet Protocol version 6, referred to as PMIPv6), the S-GW exists BBERF. When the user equipment accesses through the trusted non-3GPP access network, the BBERF also exists in the trusted non-3GPP access gateway.

The SPR stores user policy and charging control subscription information related to policy control and charging, wherein the interface between the SPR and the PCRF is the Sp interface. OCS and PCEF jointly complete the control and management of user credit in the online charging mode; OFCS and PCEF jointly complete the charging operation in the offline charging mode.

Fig. 2 is a schematic flow chart of establishing a TDF session between the TDF and the PCRF during the existing IP-CAN session, wherein the TDF is in a non-request reporting mode. As shown in Figure 2, including step S201 to step S214:

Step S201, in the process of the UE requesting to establish an IP-CAN session, the gateway where the PCEF is located receives an IP-CAN session establishment request message, wherein the IP-CAN session establishment request message carries the user identification and the requested access information PDN identifier of the PDN network.

In step S202, the PCEF sends an IP-CAN session establishment indication message to the PCRF, wherein the IP-CAN session establishment indication message carries a user identifier, a PDN identifier, and an IPv6 address prefix assigned to the UE.

Step S203, after the PCRF determines that there is no subscription information of the user according to the user ID, it sends a subscription document request to the SPR, and carries the user ID and the PDN ID in the subscription document request.

In step S204, the SPR returns corresponding user subscription information according to the user identifier and PDN identifier (returned through a subscription document response).

In step S205, the PCRF formulates policy decisions based on the returned user subscription information, network policies, and UE access information. Among them, formulating PCC rules and event triggers may be included.

In step S206, the PCRF sends an IP-CAN session establishment confirmation message to the PCEF, wherein the IP-CAN session establishment confirmation message carries PCC rules and event triggers.

Step S207, the PCEF installs the policy, and the gateway where the PCEF is located returns an IP-CAN session establishment response to the UE, wherein the IP-CAN session establishment response carries an IPv6 address prefix.

Step S208, if the network supports dual stack, the gateway where the PCEF is located or other external network elements allocate another IPv4 address according to the UE's request.

In step S209, the PCEF sends an IP-CAN session modification instruction to the PCRF, which carries an IPv4 address, to inform the PCRF that the IP-CAN session has another IPv4 address.

In step S210, the PCRF returns an acknowledgment message indicating IP-CAN session modification to the PCEF.

Through the process shown in Figure 2, the UE can construct an IPv6 address according to the IPv6 address prefix, and use the IPv6 and IPv4 addresses for service access.

In step S211, the TDF detects the data flow passing through it according to the pre-configured ADC rules. When TDF detects that an application of the above-mentioned IPv4 address (this address is allocated in step S208) needs to be reported, then TDF sends a TDF session establishment message to PCRF (because the TDF session corresponding to this IPv4 has not yet been established), in this TDF The session establishment message carries the IPv4 address and the detected application identifier. If the detected flow description information of the application is derivable, the TDF also carries the flow description information in the establishment message. The PCRF associates the TDF session with the IP-CAN session according to the IPv4 address obtained from the PCEF and the IPv4 address obtained from the TDF. The PCRF can update the related policies of the IP-CAN session according to the application information reported by the TDF.

Step S212, the PCRF returns an acknowledgment message of the TDF session establishment message;

Step S213, before the TDF receives the step 212 message, the TDF detects that an application of the above address (the IPv6 address is constructed by the UE according to the IPv6 address prefix in the step S207) needs to be reported, and then the TDF sends a TDF session establishment message to the PCRF (because The TDF session corresponding to the IPv6 has not yet been established), the IPv6 address and the detected application identifier are carried in the TDF session establishment message. If the detected flow description information of the application is derivable, the TDF also carries the flow description information in the establishment message. The PCRF associates the TDF session with the IP-CAN session according to the IPv6 address prefix obtained from the PCEF and the IPv6 address obtained from the TDF. The PCRF can update the related policies of the IP-CAN session according to the application information reported by the TDF.

In step S214, the PCRF returns an acknowledgment message of the TDF session establishment message.

The scenarios where the above steps are executed are different, and the TDF positions are different. For the home route roaming scenario, the TDF is located at the home location, and the TDF establishes a TDF session with the H-PCRF; for the local grooming roaming scenario, the TDF is located at the visited location, and the TDF establishes a TDF session with the V-PCRF.

The above process will lead to a result that there are two TDF sessions in one IP-CAN session at the same time, and the service detection for the same IP-CAN session needs to be reported through different TDF sessions, which wastes system resources and increases interaction. signaling overhead in the process.

In addition, if the network supports IPv6 prefix delegation (that is, the network supports the allocation of short prefixes), when the UE constructs two or more IPv6 addresses based on the IPv6 prefix for service access, TDF cannot determine whether these IPv6 addresses belong to the same IP- CAN session, so there will be two or more TDF sessions in one IP-CAN session at the same time. As a result, service detection for the same IP-CAN session needs to be reported through different TDF sessions, which wastes system resources and increases signaling overhead in the interaction process.

If the network supports dual-stack and IPv6 prefix delegation at the same time, it may occur that one IPv4 TDF session and multiple IPv6 TDF sessions are associated with one IP-CAN session.

Contents of the invention

The present invention provides a TDF session processing method and PCRF to at least solve the problem that there are two TDF sessions in one IP-CAN session in the related art at the same time, which wastes system resources and is aimed at the business detection needs of the same IP-CAN session. Reporting through different TDF sessions increases the problem of signaling overhead in the interaction process.

According to one aspect of the present invention, a method for processing a TDF session is provided, including: PCRF receives a TDF session establishment message from a TDF, wherein the TDF session establishment message carries a first address of a user equipment UE; the PCRF judges Whether there is an established TDF session of the second address in the IP-CAN session corresponding to the first address; if yes, the PCRF returns a TDF session establishment rejection message of the first address to the TDF.

Preferably, the first address is an IPv4 address, and the second address is an IPv6 address; or the first address is an IPv6 address, and the second address is an IPv4 address; or the first address and the second The addresses are all IPv6 addresses.

Preferably, before the PCRF receives the TDF session establishment message from the TDF, it further includes: the TDF detects the passing data flow according to the preset application detection control ADC rule; when it detects that the application corresponding to the first address needs When reporting, the TDF sends the TDF session establishment message to the PCRF, wherein the TDF session establishment message carries the detected application information corresponding to the first address.

Preferably, if the detected flow description information of the application corresponding to the first address is derivable, the TDF session establishment message also carries flow description information.

Preferably, after the PCRF receives the TDF session establishment message from the TDF, it further includes: the PCRF combines the TDF session establishment message with the first address obtained from the PCEF and the first address carried in the TDF session establishment message The IP-CAN session is associated; or the PCRF associates the TDF session establishment message with the IP-CAN according to the address prefix corresponding to the first address obtained from the PCEF and the first address carried in the TDF session establishment message session association.

Preferably, the TDF session establishment rejection message of the first address carries a reason value for the rejection, wherein the reason value is that the TDF session of the IP-CAN session has been established.

Preferably, after the PCRF returns the TDF session establishment rejection message of the first address to the TDF, the TDF further includes: the TDF sends a TDF session modification message to the PCRF through the TDF session of the second address, wherein, The TDF session modification message carries the first address and/or application information corresponding to the first address.

Preferably, the TDF reports the application information related to the first address and/or the second address through the TDF session of the second address.

According to another aspect of the present invention, a PCRF is provided, including: a receiving module, configured to receive a TDF session establishment message from a traffic detection function TDF, wherein the TDF session establishment message carries a first address of a user equipment UE; The judging module is used to judge whether there is an established TDF session of the second address in the IP-CAN session corresponding to the first address; the first return module is used to exist in the IP-CAN session corresponding to the first address In the case of an established TDF session with the second address, return a TDF session establishment rejection message with the first address to the TDF.

Preferably, the first address of the PCRF is an IPv4 address, and the second address is an IPv6 address; or the first address is an IPv6 address, and the second address is an IPv4 address; or the first Both the address and the second address are IPv6 addresses.

Preferably, the PCRF further includes: an associating module, configured to establish the TDF session according to the first address obtained from the policy and charging enforcement function entity PCEF and the first address carried in the TDF session establishment message The message is associated with the IP-CAN session; or used to associate the TDF session establishment message with the IP-CAN session according to the address prefix corresponding to the first address obtained from the PCEF and the first address carried in the TDF session establishment message. CAN session association.

Preferably, the TDF session rejection message carries a reason value for rejection, wherein the reason value is that the TDF session of the IP-CAN session has been established.

Through the present invention, the following method is adopted: the PCRF receives the TDF session establishment message from the TDF, wherein the TDF session establishment message carries the first address of the user equipment UE; the PCRF judges whether there is an established IP-CAN session corresponding to the first address The TDF session of the second address; if it exists, PCRF returns the TDF session rejection message of the first address to TDF, wherein, the first address is an IPv4 address, and the second address is an IPv6 address; or the first address is an IPv6 address, and the second address is an IPv6 address. The second address is an IPv4 address; or the first address and the second address are both IPv6 addresses. The above method is to detect whether the IP-CAN session corresponding to the current application address has already A TDF session has been established. If a TDF session has already been established, the current request will be rejected and no new TDF session will be established. By using the above method, it is solved that there are two TDF sessions in one IP-CAN session in the related art at the same time, which wastes system resources, and the service detection for the same IP-CAN session needs to be reported through different TDF sessions, which increases the interaction The problem of signaling overhead in the process realizes the scenario where only one TDF session is established, and the service detection of the same IP-CAN session can be reported through an established TDF session, which saves system resources and reduces The signaling overhead in the interaction process is reduced, and the resource utilization rate of the system is improved.

Description of drawings

The accompanying drawings described here are used to provide a further understanding of the present invention and constitute a part of the application. The schematic embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations to the present invention. In the attached picture:

FIG. 1 is a schematic diagram of the PCC composition architecture of Rel-11 according to the related art;

Fig. 2 is a flow chart of establishing a TDF session between TDF and PCRF according to the IP-CAN session of the related art;

3 is a flowchart of a method for processing a TDF session according to an embodiment of the present invention;

FIG. 4 is a flow chart of a TDF session processing method according to preferred embodiment 1 of the present invention;

FIG. 5 is a flowchart of a TDF session processing method according to the second preferred embodiment of the present invention;

FIG. 6 is a flow chart of a TDF session processing method according to a third preferred embodiment of the present invention;

FIG. 7 is a structural block diagram one of PCRF according to an embodiment of the present invention; and

FIG. 8 is a second structural block diagram of PCRF according to an embodiment of the present invention.

Detailed ways

Hereinafter, the present invention will be described in detail with reference to the drawings and examples. It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.

Based on the related technology, one IP-CAN session has two TDF sessions at the same time, which wastes system resources, and the service detection for the same IP-CAN session needs to be reported through different TDF sessions, which also increases the signaling in the interaction process The problem of overhead, the present invention provides a kind of processing method of TDF conversation, the process flow of this method is shown in Figure 3, comprises step S302 to step S306:

Step S302, the PCRF receives a TDF session establishment message from the TDF, wherein the TDF session establishment message carries the first address of the user equipment UE;

Step S304, the PCRF judges whether there is an established TDF session of the second address in the IP-CAN session corresponding to the first address;

Step S306, if yes, the PCRF returns a TDF session establishment rejection message of the first address to the TDF.

By using this embodiment, before establishing a new TDF session process, first detect whether a TDF session has been established in the IP-CAN session corresponding to the current application address, if a TDF session has been established, then reject the current request, A new TDF session is no longer established, which solves the problem that there are two TDF sessions in one IP-CAN session at the same time in the related technology, which wastes system resources, and the service detection for the same IP-CAN session needs to be reported through different TDF sessions. The problem of signaling overhead in the interaction process is increased, and then only one TDF session is established, and the service detection of the same IP-CAN session can be reported through an established TDF session, saving system resources. At the same time, the signaling overhead in the interaction process is reduced, and the resource utilization rate of the system is improved.

In the execution process of this implementation, because the first address and the second address can be the same address or the same address, that is, the first address is an IPv4 address and the second address is an IPv6 address; or the first address is an IPv6 address address, the second address is an IPv4 address; or both the first address and the second address are IPv6 addresses. According to different situations, it can be divided into the following three situations:

The first type: PCRF receives the TDF session establishment message carrying the IPv4 address of the user equipment. If the PCRF judges that the IP-CAN session corresponding to the IPv4 address has a TDF session related to the IPv6 address, the PCRF returns a establishment rejection message to the TDF.

The second type: PCRF receives the TDF session establishment message carrying the IPv6 address of the user equipment. If the PCRF judges that the IP-CAN session corresponding to the IPv6 address has a TDF session related to the IPv4 address, the PCRF returns a establishment rejection message to the TDF.

The third type: PCRF receives the TDF session establishment message carrying the IPv6 address of the user equipment. If the PCRF judges that the IP-CAN session corresponding to the IPv6 address also has a TDF session related to the IPv6 address, the PCRF returns a establishment rejection message to the TDF.

Although the types of addresses are the same or different, the ideas of the embodiments of the present invention are consistent, that is, before an address requests to establish a TDF session, it is detected in the IP-CAN session where the address is located, and it is judged that in the IP-CAN session Whether there are TDF sessions corresponding to other addresses, and if so, reject the request of the current address to establish a new TDF session, and use the established TDF session to report application information.

Before the PCRF receives the TDF session establishment message from the TDF, the TDF detects the passing data flow according to the preset ADC rules; when it detects that the application corresponding to the first address needs to be reported, the TDF sends the TDF session establishment message to the PCRF, Wherein, the TDF session establishment message carries the detected application information corresponding to the first address. If the detected flow description information of the application corresponding to the first address is derivable, the TDF session establishment message also carries the flow description information.

In a specific implementation process, if the TDF detects that the application corresponding to the IPv4 address needs to be reported, the TDF sends a TDF session establishment message to the PCRF. In the TDF session establishment message, the application information that needs to be reported with the IPv4 address may be carried, for example, the application identifier of the application information. If the flow description information of the application corresponding to the IPv4 address is derivable (that is, directional, infrequently changing, and derivable), the TDF session establishment message also carries flow description information for describing the data flow . When the TDF detects that the application corresponding to the IPv6 address needs to be reported, its execution process is similar to that of the IPv4 address, and will not be repeated here.

After the execution of step S302, the PCRF establishes the association between the TDF session of the first address and the IP-CAN session according to the first address obtained from the PCEF and the first address obtained from the TDF, and updates the IP-CAN according to the application information reported by the TDF Session-related policies. For example, if the IPv4 addresses are both obtained from the PCEF and the TDF, the IPv4 address obtained from the PCEF and the TDF session corresponding to the IPv4 address are associated with an IP-CAN session. After the TDF session corresponding to the IPv4 address is successfully associated with an IP-CAN session, the relevant policy of the IP-CAN session is updated according to the application information reported by the TDF, which provides an update mechanism and improves the performance of the system.

During the execution of step S306, the TDF session rejection message of the first address may carry the reason value of rejection and the established session identifier of the TDF session of the second address. After the execution of step S306, the following optimization processing can be further performed: TDF sends a TDF session modification message to PCRF through the established TDF session of the second address, wherein the TDF session modification message carries the first address and the first address corresponding to application information. As a response, the PCRF returns a TDF session modification confirmation message to the TDF.

Through the above authentication, the TDF can report the application information related to the first address and the application information related to the second address, or any one of them, through the established TDF session of the second address. Through the foregoing embodiments, the effect of saving resources and reducing signaling overhead can be achieved.

The embodiments of the present invention will be further described below in combination with preferred embodiments.

Preferred embodiment one

As shown in Figure 4, TDF is set to be deployed independently. For the home route roaming scenario, the PCRF in Figure 4 is the H-PCRF; for the local breakout roaming scenario, the PCRF in Figure 4 is the V-PCRF. In this preferred embodiment, the PCRF first receives the IPv4 address-related TDF session establishment message, and the processing method of the TDF session includes steps S402 to S414:

In step S402, the UE establishes an IP-CAN session and obtains IPv4 and IPv6 addresses. The specific execution process of this step may be step S201-step S210 in FIG. 2 . The UE can access services (applications) according to the obtained IPv4 address and IPv6 address.

In step S404, the TDF detects the data flow passing through it according to the pre-configured ADC rules. When TDF detects that an application of the above-mentioned IPv4 address needs to be reported, TDF sends a TDF session establishment message to PCRF (because the TDF session corresponding to the IPv4 has not been established), carries the IPv4 address in the TDF session establishment message, and detects application information, such as the application ID. If the detected flow description information of the application is derivable, the TDF also carries the flow description information in the establishment message. The PCRF associates the TDF session with the IP-CAN session according to the IPv4 address obtained from the PCEF and the IPv4 address obtained from the TDF. The PCRF can update the related policies of the IP-CAN session according to the application information reported by the TDF.

In step S406, the PCRF returns an acknowledgment message for establishing the TDF session, and returns the IPv6 prefix of the IP-CAN session in the acknowledgment message.

Here, the TDF session established in step S404 and step S406 is represented as TDF session1.

Step S408, TDF sends the step S404 message simultaneously or after, before receiving the step S406 message, TDF detects that an application of the above-mentioned IPv6 address needs to report, then TDF sends a TDF session establishment message to PCRF (because the TDF session corresponding to this IPv6 not yet established), the IPv6 address and the detected application information, such as the application identifier, are carried in the TDF session establishment message. If the detected flow description information of the application is derivable, the TDF also carries the flow description information in the establishment message. The PCRF associates the TDF session with the IP-CAN session according to the IPv6 address prefix obtained from the PCEF and the IPv6 address obtained from the TDF (the IPv6 address carried in the TDF session establishment message) (that is, the TDF session establishment message is associated with the IP-CAN session association).

In step S410, the PCRF judges that a TDF session related to the IP-CAN session has been established (related to the IPv4 address). Therefore, the PCRF rejects the establishment of the TDF session, and carries the cause value in the confirmation message, notifying the TDF that a TDF session related to the IP-CAN session has been established, and can also carry the session identifier of TDF session1.

Step S412, optionally, the TDF sends a TDF session modification message to the PCRF through the TDF session1, and the message carries the IPv6 address and/or the application information reported in the step S408.

In step S414, the PCRF returns an acknowledgment message of the TDF session modification message to the TDF.

After step S414 is executed, TDF reports application information related to IPv4 address and IPv6 address through TDF session1.

Preferred embodiment two

The TDF in Figure 5 is set up for standalone deployment. There are certain differences in PCRF in different scenarios. For the home route roaming scenario, the PCRF in Figure 5 is the H-PCRF; for the local breakout roaming scenario, the PCRF in Figure 5 is the V-PCRF. In this preferred embodiment, the PCRF first receives the IPv6 address-related TDF session establishment message, and the method includes steps S502 to S514:

In step S502, the UE establishes an IP-CAN session and obtains IPv4 and IPv6 addresses. The specific execution process of this step may be step S201-step S210 in FIG. 2 . The UE can access services (applications) according to the obtained IPv4 address and IPv6 address.

In step S504, the TDF detects the data flow passing through it according to the pre-configured ADC rules. When TDF detects that an application of the above-mentioned IPv6 address needs to be reported, TDF sends a TDF session establishment message to PCRF (because the TDF session corresponding to the IPv6 has not yet been established), carries the IPv6 address in the TDF session establishment message, and detects application information, such as the application ID. If the detected flow description information of the application is derivable, the TDF also carries the flow description information in the establishment message. The PCRF associates the TDF session with the IP-CAN session according to the IPv6 prefix obtained from the PCEF and the IPv6 address obtained from the TDF. The PCRF can update the related policies of the IP-CAN session according to the application information reported by the TDF.

Step S506, PCRF returns the confirmation message that the TDF session is set up, and returns the IPv6 prefix and the IPv4 address of this IP-CAN session in the confirmation message;

Here, the TDF session established in step S504 and step S506 is represented as TDF session1.

Step S508, TDF sends the step S504 message simultaneously or after, before receiving the step S506 message, TDF detects that an application of the above-mentioned IPv4 address needs to be reported, then TDF sends a TDF session establishment message to PCRF (because the TDF session corresponding to this IPv4 not yet established), the IPv4 address and the detected application information, such as the application identifier, are carried in the TDF session establishment message. If the detected flow description information of the application is derivable, the TDF also carries the flow description information in the establishment message. The PCRF associates the TDF session with the IP-CAN session according to the IPv4 address obtained from the PCEF and the IPv4 address obtained from the TDF (the IPv4 address carried in the TDF session establishment message) (that is, the TDF session establishment message is associated with the IP-CAN session ).

In step S510, the PCRF judges that a TDF session related to the IP-CAN session has been established (related to the IPv6 address). Therefore, the PCRF rejects the establishment of the TDF session, and carries the cause value in the confirmation message, notifying the TDF that a TDF session related to the IP-CAN session has been established, and can also carry the session identifier of TDF session1.

Step S512, optionally, the TDF sends a TDF session modification message to the PCRF through the TDF session1, and the message carries the IPv4 address and/or the application information reported in the step S508.

In step S514, the PCRF returns an acknowledgment message of the TDF session modification message to the TDF.

After step S514 is executed, TDF reports application information related to IPv4 address and IPv6 address through TDF session1.

Preferred Embodiment Three

The TDF in Figure 6 is set up for standalone deployment. There are certain differences in PCRF in different scenarios. For the home route roaming scenario, the PCRF in Figure 6 is the H-PCRF; for the local breakout roaming scenario, the PCRF in Figure 6 is the V-PCRF. In this preferred embodiment, the PCRF first receives the IPv6 address-related TDF session establishment message, and the method includes steps S602 to S614:

In step S602, the UE establishes an IP-CAN session and obtains IPv4 and IPv6 addresses. The specific execution process of this step may be step S201-step S210 in FIG. 2 . The UE can construct multiple IPv6 addresses to access services (applications) based on the obtained IPv6 short prefix (the prefix length is less than 64 bits) (in this embodiment, the construction of two IPv6 addresses is used as an example for illustration, which are respectively represented as IPv6 address 1 and IPv6 address 2).

In step S604, the TDF detects the data flow passing through it according to the pre-configured ADC rules. When TDF detects that an application of IPv6 address 1 needs to be reported, TDF sends a TDF session establishment message to PCRF (because the TDF session corresponding to the IPv6 has not been established), carries the IPv6 address 1 in the TDF session establishment message, and detects received application information, such as the application ID. If the detected flow description information of the application is derivable, the TDF also carries the flow description information in the establishment message. The PCRF associates the TDF session with the IP-CAN session according to the IPv6 prefix obtained from the PCEF and the IPv6 address 1 obtained from the TDF. The PCRF can update the related policies of the IP-CAN session according to the application information reported by the TDF.

Step S606, PCRF returns the confirmation message that the TDF session is set up, and returns the IPv6 prefix of the IP-CAN session in the confirmation message;

Here, the TDF session established in step S604 and step S606 is represented as TDF session1.

Step S608, TDF sends step S604 message simultaneously or after, before receiving step S606 message, TDF detects that an application of IPv6 address 2 needs to report, and then TDF sends TDF session establishment message to PCRF (because this IPv6 address 2 corresponds The TDF session has not been established), the IPv6 address 2 and the detected application information, such as the application identifier, are carried in the TDF session establishment message. If the detected flow description information of the application is derivable, the TDF also carries the flow description information in the establishment message. The PCRF associates the TDF session with the IP-CAN session according to the IPv6 address prefix obtained from the PCEF and the IPv6 address 2 obtained from the TDF (the IPv6 address 2 carried in the TDF session establishment message) (that is, the TDF session establishment message is associated with the IP-CAN sessions are associated).

In step S610, the PCRF judges that a TDF session related to the IP-CAN session has been established (related to IPv6 address 1). Therefore, the PCRF rejects the establishment of the TDF session, and carries the cause value in the confirmation message, notifying the TDF that a TDF session related to the IP-CAN session has been established, and can also carry the session identifier of TDF session1.

Step S612, optionally, the TDF sends a TDF session modification message to the PCRF through the TDF session1, and the message carries the IPv6 address 2 and/or the application information reported in step S608.

In step S614, the PCRF returns an acknowledgment message of the TDF session modification message to the TDF.

After step S614 is executed, TDF reports application information related to IPv6 address 1 and IPv6 address 2 through TDF session1.

For scenarios that support dual-stack and IPv6 prefix delegation at the same time, the implementation scheme is similar.

According to another aspect of the present invention, the embodiment of the present invention also provides a PCRF. As shown in FIG. 7, the PCRF includes: a receiving module 10, configured to receive a TDF session establishment message from a service detection function TDF, wherein the TDF The session establishment message carries the first address of the user equipment UE; the judging module 20, coupled with the receiving module 10, is used to judge whether the IP-CAN session corresponding to the first address has an established TDF session of the second address; return module 30 , coupled with the judging module 20, used to return the TDF session establishment rejection message of the first address to the TDF when the IP-CAN session corresponding to the first address has an established TDF session of the second address, wherein the PCRF The first address is an IPv4 address, and the second address is an IPv6 address; or the first address is an IPv6 address, and the second address is an IPv4 address; or both the first address and the second address are IPv6 addresses.

In order to further optimize the PCRF, an associating module 40 shown in FIG. 8 may also be included, which is coupled with the receiving module 10, and is used to associate the TDF session with the first address obtained from the PCEF and the first address carried in the TDF session establishment message. The establishment message is associated with the IP-CAN session; it is also used to associate the TDF session establishment message with the IP-CAN session according to the address prefix corresponding to the first address obtained from the PCEF and the first address carried in the TDF session establishment message.

According to another aspect of the present invention, the embodiment of the present invention also provides a TDF, which is used for interacting with the PCRF. Before the receiving module 10 of the PCRF receives the TDF session establishment message, the TDF controls the ADC flow according to the preset application detection rule. When detecting that the application corresponding to the first address needs to be reported, the TDF sends a TDF session establishment message to the PCRF, wherein the TDF session establishment message carries the detected application information corresponding to the first address. Wherein, if the detected flow description information of the application corresponding to the first address is derivable, the TDF session establishment message also carries the flow description information.

After the return module 30 of the PCRF returns the TDF session rejection message of the first address, the TDF sends a TDF session modification message to the PCRF through the established TDF session of the second address, wherein the TDF session modification message carries the first address and the first address Corresponding application information.

From the above description, it can be seen that the present invention achieves the following technical effects:

By using the above embodiments of the present invention, it is solved that there are two TDF sessions in one IP-CAN session in the related art at the same time, which wastes system resources, and the service detection for the same IP-CAN session needs to be reported through different TDF sessions. The problem of signaling overhead in the interaction process is increased, and then only one TDF session is established, and the service detection of the same IP-CAN session can be reported through an established TDF session, saving system resources. At the same time, the signaling overhead in the interaction process is reduced, and the resource utilization rate of the system is improved.

Obviously, those skilled in the art should understand that each module or each step of the above-mentioned present invention can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network formed by multiple computing devices Alternatively, they may be implemented in program code executable by a computing device so that they may be stored in a storage device to be executed by a computing device, and in some cases, in an order different from that shown here The steps shown or described are carried out, or they are separately fabricated into individual integrated circuit modules, or multiple modules or steps among them are fabricated into a single integrated circuit module for implementation. As such, the present invention is not limited to any specific combination of hardware and software.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (12)

1. A processing method for a service detection function TDF session, characterized in that, comprising: The policy and charging rule function entity PCRF receives a TDF session establishment message from the TDF, wherein the TDF session establishment message carries the first address of the user equipment UE; The PCRF judges whether there is an established TDF session of the second address in the IP-CAN session corresponding to the first address; If yes, the PCRF returns a TDF session establishment rejection message to the TDF. 2. The method according to claim 1, wherein the first address is an IPv4 address, and the second address is an IPv6 address; or the first address is an IPv6 address, and the second address is an IPv4 address address; or both the first address and the second address are IPv6 addresses. 3. The method according to claim 2, wherein, before the PCRF receives the TDF session establishment message from the TDF, it also includes: The TDF detects the passing data stream according to the preset application detection control ADC rule; When it is detected that the application corresponding to the first address needs to be reported, the TDF sends the TDF session establishment message to the PCRF, wherein the TDF session establishment message carries the detected information related to the first address Corresponding application information. 4. The method according to claim 3, wherein if the detected flow description information of the application corresponding to the first address is derivable, the TDF session establishment message also carries the flow description information . 5. The method according to claim 1, wherein, after the PCRF receives the TDF session establishment message from the TDF, it further comprises: The PCRF associates the TDF session establishment message with the IP-CAN session according to the first address obtained from the policy and charging enforcement function entity PCEF and the first address carried in the TDF session establishment message ; Or, the PCRF associates the TDF session establishment message with the IP-CAN session according to the address prefix corresponding to the first address obtained from the PCEF and the first address carried in the TDF session establishment message. 6. The method according to claim 1, wherein the TDF session establishment rejection message carries a reason value for the rejection, wherein the reason value is that the TDF session of the IP-CAN session has been established. 7. The method according to claim 6, characterized in that, after the PCRF returns a TDF session establishment rejection message to the TDF, further comprising: The TDF sends a TDF session modification message to the PCRF through the TDF session of the second address, where the TDF session modification message carries the first address and/or application information corresponding to the first address. 8. The method according to claim 1 or 7, wherein the TDF reports the application information related to the first address and/or the second address through the TDF session of the second address. 9. A policy control and charging rule functional entity PCRF, characterized in that it includes: A receiving module, configured to receive a TDF session establishment message from a traffic detection function TDF, wherein the TDF session establishment message carries a first address of the user equipment UE; A judging module, configured to judge whether there is an established TDF session of the second address in the IP-CAN session corresponding to the first address; A return module, configured to return a TDF session establishment rejection message to the TDF if there is an established TDF session with the second address in the IP-CAN session corresponding to the first address. 10. The PCRF according to claim 9, wherein the first address of the PCRF is an IPv4 address, and the second address is an IPv6 address; or the first address is an IPv6 address, and the second address is an IPv6 address. The second address is an IPv4 address; or both the first address and the second address are IPv6 addresses. 11. PCRF according to claim 9, is characterized in that, described PCRF also comprises: An associating module, configured to associate the TDF session establishment message with the IP address according to the first address obtained from the policy and charging enforcement function entity PCEF and the first address carried in the TDF session establishment message -CAN session association; or for linking the TDF session establishment message with the IP-CAN according to the address prefix corresponding to the first address obtained from the PCEF and the first address carried in the TDF session establishment message session association. 12. The PCRF according to claim 11, wherein the TDF session rejection message carries a reason value for rejection, wherein the reason value is that the TDF session of the IP-CAN session has been established.

Images