WO2012097676A1 - Procédé et système pour réaliser la détection et le contrôle d'applications dans une session ip-can prenant en charge la double pile - Google Patents

Procédé et système pour réaliser la détection et le contrôle d'applications dans une session ip-can prenant en charge la double pile Download PDF

Info

Publication number
WO2012097676A1
WO2012097676A1 PCT/CN2011/085211 CN2011085211W WO2012097676A1 WO 2012097676 A1 WO2012097676 A1 WO 2012097676A1 CN 2011085211 W CN2011085211 W CN 2011085211W WO 2012097676 A1 WO2012097676 A1 WO 2012097676A1
Authority
WO
WIPO (PCT)
Prior art keywords
tdf
session
pcrf
address
ipv4 address
Prior art date
Application number
PCT/CN2011/085211
Other languages
English (en)
Chinese (zh)
Inventor
周晓云
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US13/978,603 priority Critical patent/US9565052B2/en
Priority to JP2013547799A priority patent/JP5642888B2/ja
Priority to EP11856616.5A priority patent/EP2648367B1/fr
Publication of WO2012097676A1 publication Critical patent/WO2012097676A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/147—Signalling methods or messages providing extensions to protocols defined by standardisation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/167—Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/686—Types of network addresses using dual-stack hosts, e.g. in Internet protocol version 4 [IPv4]/Internet protocol version 6 [IPv6] networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses

Definitions

  • the present invention relates to policy and charging techniques, and more particularly to a method and system for implementing application detection and control in an IP-CAN session supporting dual stack. Background technique
  • the PCC architecture is a functional framework that can be applied to multiple access technologies.
  • the PCC architecture can be applied to the UMTS, Universal Mobile Telecommunications System (UMTS, UMTS Terrestrial Radio Access Network).
  • UMTS Universal Mobile Telecommunications System
  • UMTS Terrestrial Radio Access Network UMTS Terrestrial Radio Access Network
  • GSM Global System for Mobile Communication
  • EDGE GSM Data Enhanced Evolution
  • I-WLAN Interworking Wireless Local Area Network
  • EPS Evolved Packet System
  • FIG. 1 is a schematic diagram of the PCC composition of the existing Rd-11. The following describes the logical functional entities and their interface functions in the PCC architecture shown in Figure 1. As shown in Figure 1:
  • AF Application Function
  • PCRF Policy and Charging Rules Function
  • the PCRF provides network control rules based on service data flows, including traffic data flow detection, Gating Control, Quality of Service (QoS) control, and data flow based charging.
  • the PCRF sends its policy and charging rules to the Policy and Control Enforcement Function (PCEF).
  • PCEF Policy and Control Enforcement Function
  • the basis for formulating policies and charging rules by the PCRF includes: service-related information obtained from the AF, and user policy charging control related to policy control and charging obtained from the SPR (Spread Profile Repository) Information, and information about the bearer-related network obtained from the PCEF through the Gx interface.
  • the PCEF is usually located in the gateway (GW, Gate-Way) and performs the policy and charging rules established by the PCRF on the bearer plane.
  • the PCEF detects the service data flow according to the service data flow filter in the rule sent by the PCRF, and then performs the policy and charging rule defined by the PCRF for the service data flow; when the bearer is established, the PCEF performs the resource according to the rule sent by the PCRF.
  • the fee can be either online or offline.
  • the PCEF In the case of online charging, the PCEF needs to perform credit management with the Online Charging System (OCS); in offline charging, the PCEF and the Offline Charging System (OFCS) are exchanged. Billing information.
  • the interface between the PCEF and the PCRF is a Gx interface
  • the interface between the PCEF and the OCS is a Gy interface
  • the interface between the PCEF and the OFCS is a Gz interface.
  • the PCEF can also have a Traffic Detection Function (TDF).
  • TDF Traffic Detection Function
  • the PCEF can be based on the local configuration or the application bandwidth limit issued by the PCRF.
  • PCEF is generally located on the gateway of the network, such as EPS packet data network gateway (PDN-GW), GPRS Gateway Support Node (GGSN) in General Packet Radio Service (GPRS), and Packet Data Gateway (PDG, Packet Data) in Interworking WLAN (I-WLAN) Gateway) and so on.
  • PDN-GW EPS packet data network gateway
  • GGSN GPRS Gateway Support Node
  • GPRS General Packet Radio Service
  • PSG Packet Data Gateway
  • I-WLAN Interworking WLAN
  • the TDF can also be deployed independently.
  • the TDF and the PCRF are connected through the Sd interface.
  • the TDF can perform application detection and policy execution according to the pre-configured or PCRF application detection control (ADC, Application Detection and Control) rules.
  • ADC Application Detection and Control
  • the Bearer Binding and Event Reporting Function is usually located in the Access Network Gateway.
  • the proxy mobile Internet protocol version 6 ( ⁇ , Proxy Mobile Internet Protocol version 6) is used between the service gateway S-GW and the P-GW, the BBERF exists in the S-GW.
  • the BBERF also exists in the trusted non-3GPP access gateway.
  • the User Contracting Database stores user policy fee control subscription information related to policy control and charging.
  • the interface between SPR and PCRF is the Sp interface.
  • OCS and PCEF jointly complete the control and management of user credit under online charging mode.
  • the OFCS and the PCEF jointly perform the charging operation in the offline charging mode.
  • FIG. 2 is a schematic diagram of the process of establishing a TDF session between the TDF and the PCRF in the existing IP-CAN session, where the TDF is an unsolicited reporting mode.
  • the method includes the following steps: Step 201: In a process in which the UE requests to establish an IP-CAN session, the gateway where the PCEF is located receives the IP-CAN session establishment request message, in the IP-CAN session establishment request message.
  • the PDN identifier of the PDN network carrying the user identity and requesting access.
  • Step 202 The PCEF sends an IP-CAN session establishment indication message to the PCRF, and carries the user identifier, the PDN identifier, and the IPv6 address prefix allocated to the UE in the IP-CAN session establishment indication message.
  • Step 203 After determining, according to the user identifier, the PCRF does not have the subscription information of the user, The SPR sends a subscription document request, and carries the user identifier and the PDN identifier in the subscription document request. Step 204: The SPR returns the corresponding user subscription information according to the user identifier and the PDN identifier (returned by the subscription document response).
  • Step 205 The PCRF formulates a policy according to the returned user subscription information, the network policy, and the access information of the UE. This includes making PCC rules and event triggers.
  • Step 206 The PCRF sends an IP-CAN session establishment confirmation message to the PCEF, and carries the PCC rule and the event trigger in the IP-CAN session establishment confirmation message.
  • Step 207 The PCEF installation policy, the gateway where the PCEF is located returns an IP-CAN session establishment response to the UE, and the IP-CAN session establishment response carries an IPv6 address prefix.
  • the UE can construct an IPv6 address based on the IPv6 address prefix and use the IPv6 address for service access.
  • Step 208 When detecting the data stream flowing through it, the TDF finds a new IPv6 address (the IPv6 address is constructed by the UE according to the IPv6 address prefix in step 207), and the TDF sends a TDF session establishment message to the PCRF.
  • the new IPv6 address is carried in the TDF session setup message.
  • Step 209 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, and returns a TDF session establishment confirmation message to the TDF.
  • the established TDF session corresponds to an IP-CAN session established by the UE.
  • the TDF applies detection and control to the uplink service data flow whose source address is the new IPv6 address, and/or the downlink service data flow whose destination address is the new IPv6 address according to the pre-configured ADC rule; TDF detection Go to the application specified in the pre-configured application detection policy (identified by Application ID).
  • the TDF sends a service detection report to the PCRF through the TDF session established in step 208 and step 209, and carries the detected Application ID and an optional event trigger.
  • the value is the Start of application traffic detection and the application service detection. Stop of application traffic detection; if PCRF to TDF Subscribed to the Start of application traffic detection and Stop of application traffic detection event triggers, TDF may also provide a Service Data Flow Description to the PCRF.
  • the PCRF makes policy decisions based on the Application ID and service data flow description (if reported) reported by the TDF, and formulates or updates the PCC rules and provides them to the PCEF.
  • an IP-CAN session has both an IPv4 address and an IPv6 address.
  • the network gateway where the PCEF is located or another external network element allocates an IPv4 address according to the request of the UE, and the UE uses the IPv4 address for service access.
  • the TDF discovers a new IPv4 address, and will initiate the establishment of the TDF session, and report the application detection result to the PCRF through the established TDF.
  • the process of establishing a TDF session at this time includes the following steps:
  • Step 301 In the process of the UE requesting to establish an IP-CAN session, the gateway where the PCEF is located receives the IP-CAN session establishment request message, where the IP-CAN session establishment request message carries the user identifier and the PDN network requesting access. PDN logo.
  • Step 302 The PCEF sends an IP-CAN session establishment indication message to the PCRF, and carries the user identifier, the PDN identifier, and the IPv6 address prefix allocated to the UE in the IP-CAN session establishment indication message.
  • Step 303 After determining, according to the user identifier, the PCRF sends the subscription document request to the SPR, and carries the user identifier and the PDN identifier in the subscription document request.
  • Step 304 The SPR returns the corresponding user subscription information according to the user identifier and the PDN identifier (returned by the subscription document response).
  • the user subscription information includes a user document configuration that indicates activation of application detection and control information.
  • the ADC rules include setting an application ID (Application ID) for indicating that the PCEF needs to be detected; setting an event trigger, the values are Start of application traffic detection and Stop of application traffic detection; and possible execution strategies corresponding to each detected application. , including gating, maximum bandwidth, and redirection.
  • Step 306 The PCRF sends a TDF session establishment request to the TDF, where the TDF session establishment request message carries an IPv6 address prefix, an ADC rule, and an optional event trigger, and the values are Start of application traffic detection and Stop of application traffic detection.
  • Step 307 The TDF executes the policy, installs or activates the ADC rules and event triggers.
  • Step 308 The TDF returns a TDF session establishment confirmation message to the PCRF.
  • Step 309 The PCRF sends an IP-CAN session establishment confirmation message to the PCEF.
  • the IP-CAN session establishment confirmation message carries the PCC rules and event triggers.
  • Step 310 The PCEF installation policy, the gateway where the PCEF is located returns an IP-CAN session establishment response to the UE, and the IP-CAN session establishment response carries an IPv6 address prefix.
  • the UE can construct an IPv6 address based on the IPv6 address prefix and use the IPv6 address for service access.
  • the established TDF session corresponds to the IP-CAN session established by the UE.
  • the TDF Thereafter, the TDF, according to the ADC rules issued by the PCRF, the uplink service data flow whose source address is the IPv6 address (the IPv6 address uniquely determined by the TDF obtainable from the PCRF), and/or the destination address is the IPv6 address.
  • the downlink service data flow is applied for detection and control.
  • the TDF detects the application corresponding to the Application ID and the PCRF subscribes to the Start of application traffic detection and the Stop of application traffic detection, the TDF sends a service detection report to the PCRF through the TDF session established in steps 306 to 308, and carries the detection.
  • PCRF makes policy decisions based on the reported Application ID, sets or updates execution policies (such as gating, maximum bandwidth and redirection, etc.), and develops or updates PCC rules are provided to the PCEF.
  • the gateway where the PCEF is located or another external network element allocates an IPv4 address according to the request of the UE, and the UE uses the IPv4 address for service access.
  • the TDF detects the service data
  • a service data stream of a new IPv4 address is found. Since the TDF is not notified of the service data flow that needs to detect the IPv4 address, and the ADC rule corresponding to the service data flow is not detected, Therefore TDF will not detect the traffic data stream.
  • the PCRF can initiate a request to establish a new TDF session, resulting in the simultaneous presence of two TDF sessions for one IP-CAN session, and the service detection for the same IP-CAN session needs to be reported through different TDF sessions.
  • resources are wasted; on the other hand, the signaling overhead is also increased.
  • the main object of the present invention is to provide a method for implementing application detection and control of an IP-CAN session supporting dual stack, which can save resources and reduce signaling overhead.
  • a method for implementing application detection and control in an IP-CAN session supporting a dual stack comprising: obtaining an IPv4 address by the user equipment UE after establishing an IP-CAN session and obtaining an IPv6 address; the method further includes:
  • the PCRF notifies the allocated IPv4 address to the TDF through the established TDF session of the IP-CAN session;
  • the TDF associates the obtained IPv4 address with the established TDF session. Further, after the TDF associates the IPv4 address with the TDF session, the method further includes: if the PCRF subscribes to the application service detection start and the application service detection stops. An event trigger, the TDF returns the detected application information related to the IPv4 address to the PCRF through the TDF session.
  • the method further includes: the TDF performing application detection and control on the service data of the IPv4 address with the source address and/or the target address according to the ADC rule related to the TDF session.
  • the method further includes: the ADC rules related to the TDF session include an application detection control ADC rule applied to an IPv6 address of an IP-CAN session, and/or an ADC rule applied to an IPv4 address separately.
  • the method further includes: when the IPv4 address is released, the PCRF notifies the TDF of the released IPv4 address by using the established TDF session corresponding to the IP-CAN session; The association relationship between the IPv4 address and the TDF session.
  • the PCRF notifies the TDF of the released IPv4 address by the established TDF session of the IP-CAN session, including: the PCEF sends an IP-CAN session modification indication message to the PCRF, and in the IP-CAN
  • the session modification indication message carries an IP address release indication and a released ⁇ ⁇ 4 address; the PCRF releases the IPv4 address carried in the IP-CAN session modification indication message, and returns an acknowledgement message to the PCEF;
  • the PCRF sends a TDF session modification request to the TDF through the established TDF session of the IP-CAN session, and carries an IP address release indication and a released ⁇ ⁇ 4 address in the TDF session modification request message.
  • the PCRF notifies the TDF of the assigned IPv4 address by using the established TDF session of the IP-CAN session, including:
  • the PCRF Sending, by the PCEF, an IP-CAN session modification indication message to the PCRF, and carrying an IP address allocation indication and an allocated IPv4 address in the IP-CAN session modification indication message; the PCRF saves the IP-CAN session modification indication message The IPv4 address carried in, and returns a confirmation message to the PCEF; The PCRF sends a TDF session modification request to the TDF through the established TDF session of the IP-CAN session, and carries an IP address allocation indication and an allocated IPv4 address in the TDF session modification request message.
  • a system for supporting application detection and control of a dual-stack IP-CAN session comprising at least a PCRF, a PCEF, a TDF, and a UE, where the UE is used to establish an IP-CAN session and obtain an IPv6 address, where
  • a PCEF configured to send an IP-CAN session modification indication message to the PCRF, and carry an IP address allocation indication and an allocated IPv4 address in the IP-CAN session modification indication message;
  • a PCRF configured to save an IPv4 address carried in the IP-CAN session modification indication message, and return an acknowledgement message to the PCEF; send a TDF session modification request to the TDF by using the established TDF session of the IP-CAN session, and
  • the TDF session modification request message carries an address IP address allocation indication and an allocated IPv4 address;
  • the TDF is configured to associate the IPv4 with the TDF session, and apply detection and control to service data whose source address and/or destination address is an IPv4 address according to the ADC rules related to the TDF session.
  • the TDF is further configured to: when the PCRF subscribes to an event trigger that is started by the application service detection and the application service detection is stopped, the detected application information related to the IPv4 address is passed through the TDF. The session is returned to the PCRF.
  • the PCEF is further configured to send an IP-CAN session modification indication message to the PCRF, and carry an IP address release indication and an released IPv4 address in the IP-CAN session modification indication message;
  • the PCRF is further configured to release an IPv4 address carried in the IP-CAN session modification indication message, and return an acknowledgement message to the PCEF; send the TDF session established by the IP-CAN session to the TDF The TDF session modification request, and carrying the IP address release indication and the released IPv4 address in the TDF session modification request message;
  • the TDF is further configured to release an association relationship between the IPv4 address and the TDF session, and reply to the PCRF for confirmation.
  • the TDF is used to associate an IPv4 address sent by a PCRF with a TDF session; and apply detection and control to service data whose source address and/or destination address is an IPv4 address according to the ADC rules related to the TDF session. .
  • the TDF is further configured to: when the PCRF subscribes to an event trigger that is started by the application service detection and the application service detection is stopped, the detected application information related to the IPv4 address is passed through the TDF. The session is returned to the PCRF.
  • another object of the present invention is to provide a method of notifying an application to detect a function of a TDF user equipment UE IP address such that when the UE obtains an IPv4 address again, the TDF can obtain the IPv4 address.
  • a method for notifying a TDF UE IP address including establishing an IP-CAN session, the method further comprising: the PCEF notifying the PCRF of the UE new The assigned IPv4 address; the PCRF notifying the TDF of the IPv4 address through an established TDF session corresponding to the IP-CAN session.
  • the method includes: the PCEF sending a notification message to the PCRF, where the notification message carries an IP address allocation indication and the UE newly allocated IPv4 address.
  • the PCRF notifying the TDF to the TDF by using the established TDF session corresponding to the IP-CAN session including: the PCRF through the established TDF session corresponding to the IP-CAN session Sending a notification message to the TDF, where the notification message carries an IP address allocation indication and an IPv4 address newly allocated by the UE.
  • the method further includes: the PCEF notifying the PCRF that the IPv4 address is released; and the PCRF has passed the IP-CAN session.
  • the established TDF session notifies the TDF that the IPv4 address is released.
  • a system for notifying a TDF UE IP address where the system includes at least a PCRF, a PCEF, a TDF, and a UE, where the UE is used to establish an IP-CAN session, where:
  • the PCEF is configured to notify the PCRF of the newly allocated IPv4 address of the UE, and the PCRF is configured to notify the TDF of the newly allocated IPv4 address by the TDF session by using the TDF session established by the IP-CAN session. ;
  • the TDF is configured to receive the notification of the PCRF, and obtain a newly allocated IPv4 address of the UE.
  • the PCEF is further configured to notify the PCRF that the IPv4 address is released when the IPv4 address is released; and the PCRF is further configured to notify, by using the IP-CAN session, a TDF session notification. The TDF said IPv4 address is released.
  • a PCRF is used to notify the TDF of the newly allocated IPv4 address of the UE through the established TDF session corresponding to the IP-CAN session after the PCEF notifies the newly assigned IPv4 address of the UE.
  • the PCRF is further configured to notify the TDF that the IPv4 address is released by the TDF session established by the IP-CAN session after the PCEF notifies that the IPv4 address is released.
  • the method of the present invention in an IP-CAN session supporting dual stack, after the UE establishes an IP-CAN session and uses an IPv6 address for service access, if the PCEF is located at the gateway or external The other network element allocates an IPv4 address according to the request of the UE, and the UE uses the IPv4 address for service access.
  • the PCRF notifies the TDF of the IPv4 address through the established TDF session of the IP-CAN session, and the TDF is established according to the TDF.
  • the ADC rules applied to the IPv6 address of the IP-CAN session and/or the ADC rules applied to the IPv4 address separately apply detection and control of the service data whose source address and/or destination address is the IPv4 address.
  • the PCRF will no longer initiate a request to establish a new TDF session, thus, The service detection for the same IP-CAN session only needs to be reported through the same TDF session, which saves resources and reduces signaling overhead.
  • FIG. 1 is a schematic diagram of a PCC composition structure of an existing Rd-11;
  • FIG. 2 is a schematic diagram of a process of establishing a TDF session between a TDF and a PCRF in an existing IP-CAN session;
  • Figure 3 is a flow chart showing another process of establishing a TDF session between the TDF and the PCRF during the existing IP-CAN session.
  • FIG. 4 is a flow chart of a method for implementing application detection and control in a dual stack IP-CAN session according to the present invention
  • FIG. 5 is a schematic structural diagram of a system for implementing application detection and control of a dual-stack IP-CAN session according to the present invention
  • FIG. 6 is a schematic flow chart of a first embodiment of a method for implementing application detection and control in a dual-stack IP-CAN session according to the present invention
  • FIG. 7 is a schematic flowchart diagram of a second embodiment of a method for implementing application detection and control in a dual-stack IP-CAN session according to the present invention. detailed description
  • FIG. 4 is a flow chart of a method for implementing application detection and control in an IP-CAN session supporting dual stack according to the present invention. As shown in FIG. 3, the method includes:
  • Step 400 The UE establishes an IP-CAN session and obtains an IPv6 address, and uses the IPv6 address to perform service access. This step is a prior art, and the specific implementation is as shown in FIG. 2 and FIG. 3.
  • Step 401 The IPv4 address of the established IP-CAN session is allocated, and the PCRF notifies the TDF of the IPv4 address through the established TDF session of the IP-CAN session.
  • the established IPv4 address of the IP-CAN session is assigned: PCEF is located.
  • the gateway or other external network element allocates an IPv4 address according to the request of the UE, and the UE uses the IPv4 address for service access. at this time,
  • the PCEF sends an IP-CAN session modification indication message to the PCRF, and carries an IP address allocation indication and an assigned IPv4 address in the IP-CAN session modification indication message; the PCRF saves the IPv4 address carried in the IP-CAN session modification indication message, and Return a confirmation message to the PCEF;
  • the PCRF sends a TDF session modification request to the TDF through the established TDF session of the IP-CAN session, and carries the IP address allocation indication and the assigned IPv4 address in the TDF session modification request message.
  • Step 402 The TDF associates the obtained IPv4 address with the established TDF session, and saves the received IPv4 address.
  • the method of the present invention comprises:
  • Step 403 The TDF performs application detection and control on the service data (also referred to as user plane data) whose source address and/or the destination address is an IPv4 address according to the ADC rules related to the TDF session.
  • service data also referred to as user plane data
  • Step 403 may further include: if the PCRF subscribes to the TDF for an event trigger of a Start of application traffic detection and a Stop of application traffic detection, the TDF will detect the IPv4 The address related application information is returned to the PCRF through the TDF session.
  • the method for detecting the corresponding application information belongs to the prior art, and the specific implementation is not intended to limit the scope of protection of the present invention.
  • the method further includes: the PCRF notifying the TDF of the released IPv4 address through the established TDF session of the IP-CAN session; the TDF releasing the received IPv4 address, releasing the IPv4 address and The association of established TDF sessions.
  • the TDF stops the application of the TDF session-related ADC rules to the service data stream (also called user plane data) that matches the released IPv4 address for application information detection.
  • the PCEF sends an IP-CAN session modification indication message to the PCRF, and in the IP-CAN session
  • the modification indication message carries an IP address release indication and an released IPv4 address; the PCRF releases the IPv4 address carried in the IP-CAN session modification indication message, and returns an acknowledgement message to the PCEF; the PCRF is established through the IP-CAN session.
  • the TDF session sends a TDF session modification request to the TDF, and carries the IP address release indication and the released IPv4 address in the TDF session modification request message.
  • the PCRF in the IP-CAN session supporting the dual stack, after the UE establishes an IP-CAN session and uses the IPv6 address for service access, if the gateway where the PCEF is located or another external network element allocates an IPv4 according to the request of the UE. Address, and the UE uses the IPv4 address for service access, the PCRF notifies the TDF of the IPv4 address through the established TDF session of the IP-CAN session, and the TDF is based on the established ADC rule of the IP-CAN session applied to the IPv6 address. And/or an ADC rule applied to an IPv4 address separately to apply detection and control of service data whose source address and/or destination address is an IPv4 address. With the method of the present invention, the PCRF does not initiate a request to establish a new TDF session. Therefore, the service detection for the same IP-CAN session only needs to be reported through the same TDF session, which saves resources and reduces signaling overhead.
  • a system for supporting application detection and control by supporting a dual-stack IP-CAN session is provided.
  • a PCRF a PCRF
  • a PCEF a PCEF
  • a TDF a UE
  • IPv6 addresses for service access
  • a PCEF configured to send an IP-CAN session modification indication message to the PCRF, and carry an IP address allocation indication and an allocated IPv4 address in the IP-CAN session modification indication message;
  • a PCRF configured to save an IPv4 address carried in the IP-CAN session modification indication message, and return an acknowledgement message to the PCEF; send a TDF session modification request to the TDF through the established TDF session of the IP-CAN session, and in the TDF
  • the session modification request message carries an IP address allocation indication and an allocated IPv4 address.
  • a TDF configured to associate the IPv4 address with the established TDF session, and save the received IPv4 address; according to the ADC rules related to the TDF session, to the source address and/or the target location Application detection and control of service data with an IPv4 address.
  • the TDF may be further configured to: when the PCRF subscribes to the event trigger of the Start of application traffic detection and the Stop of application traffic detection, return the detected application information related to the IPv4 address to the TDF session. PCRF.
  • the PCEF is further configured to send an IP-CAN session modification indication message to the PCRF, and carry an IP address release indication and an released IPv4 address in the IP-CAN session modification indication message;
  • the PCRF is further configured to release an IPv4 address carried in the IP-CAN session modification indication message, and return an acknowledgement message to the PCEF; send a TDF session modification request to the TDF through the established TDF session of the IP-CAN session, and
  • the TDF session modification request message carries an IP address release indication and an released IPv4 address;
  • the TDF is also used to release the association between the IPv4 address and the established TDF session, release the received IPv4 address, and reply to the PCRF for confirmation.
  • a TDF is further provided, where the TDF is used to associate an IPv4 address sent by the PCRF with a TDF session; according to the ADC rule related to the TDF session, the service with the source address and/or the destination address being an IPv4 address Data is applied for detection and control.
  • the TDF may be further configured to: when the PCRF subscribes to an event trigger that is started by the application service detection and the application service detection is stopped, the detected application information related to the IPv4 address is passed through the TDF session. Return to the PCRF.
  • the present invention also provides a method of notifying a TDF UE IP address such that when the UE obtains an IPv4 address again, the TDF can obtain the IPv4 address.
  • the method includes establishing an IP-CAN session, further comprising: the PCEF notifying the PCRF of the newly assigned IPv4 address of the UE; the PCRF notifying the TDF of the IPv4 address by the established TDF session of the IP-CAN session .
  • the method includes: sending, by the PCEF, the notification message to the PCRF by using the IP-CAN session, where the notification message carries an IP address allocation Indicates an IPv4 address newly assigned by the UE.
  • the PCRF notifying the TDF to the TDF by using the established TDF session of the IP-CAN session including: the PCRF through the IP-CAN session established TDF session, to the The TDF sends a notification message, where the notification message carries an IP address allocation indication and an IPv4 address newly allocated by the UE.
  • the method further includes: the PCEF notifying the PCRF that the IPv4 address is released; and the PCRF notifying the TDF by using a TDF session established by the IP-CAN session The IPv4 address is released.
  • the present invention further provides a PCRF, where the PCRF is used to notify the TDF of the newly allocated IPv4 of the UE by using an established TDF session corresponding to the IP-CAN session after the PCEF notifies the newly assigned IPv4 address of the UE. address.
  • the PCRF is further configured to notify the TDF that the IPv4 address is released by the TDF session established by the IP-CAN session after the PCEF notifies itself that the IPv4 address is released.
  • the present invention also provides a system for notifying the IP address of the TDF UE, including the PCEF, the UE, and the PCRF and the TDF.
  • the PCEF is used to notify the PCRF.
  • the newly allocated IPv4 address of the UE; the TDF configured to receive the notification of the PCRF, to obtain a newly allocated IPv4 address of the UE.
  • the PCEF, the PCRF, and the TDF are all involved in the process of the UE establishing the IP-CAN session.
  • the PCEF is further configured to notify the PCRF that the IPv4 address is released when the IPv4 address is released, and the PCRF is further used to notify a TDF session that is established by using the IP-CAN session.
  • the IPv4 address described in the TDF is released.
  • FIG. 6 is a schematic flowchart of a first embodiment of a method for implementing application detection and control in a dual-stack IP-CAN session according to the present invention.
  • TDF is independently deployed, and according to the figure 2 or the flow of FIG. 3, a TDF session is established between the TDF and the PCRF; after the IPv4 address allocation, the method includes:
  • Step 601 The gateway or other network element where the PCEF is located allocates an IPv4 address to the UE according to the request of the UE.
  • Step 602 The PCEF sends an IP-CAN session modification indication message to the PCRF, and
  • the IP-CAN session modification indication message carries an IP address allocation indication and an assigned IPv4 address.
  • the specific implementation IP address allocation indication is an event trigger event trigger 0 that contains UE_IP_ADDRESS_ALLOCATE.
  • Step 603 The PCRF returns an IP-CAN session modification confirmation message to the PCEF after saving the IPv4 address.
  • Step 604 The PCRF sends a TDF session modification request to the TDF through the TDF session established by the steps 208 to 209 of the process shown in FIG. 2 or through the steps 306 to 308 of the process shown in FIG. 3, and the TDF session modification request is sent in the TDF session.
  • the address carries an IP address assignment indication and an assigned IPv4 address.
  • the session modification request message sent by the PCRF to the TDF carries an Attribute Value Pair (Event-Report-Indication AVP), and carries an event trigger containing the UE_IP_ADDRESS_ALLOCATE and the assigned IPv4 in the AVP. address.
  • Event-Report-Indication AVP Attribute Value Pair
  • Step 605 The TDF learns that the UE is assigned an IPv4 address. After the TDF saves the newly assigned IPv4 address, it returns a TDF session modification request confirmation message to the PCRF.
  • the TDF knows that the IPv4 address and the previous IPv6 address belong to the same IP-CAN session.
  • the TDF associates an IPv4 address with an established TDF session.
  • the TDF uses the ADC rule that was previously applied to the IPv6 address (that is, the PCRF or locally preconfigured by the PCEF), and the upstream service data flow (also called user plane data) whose source address is the IPv4 address, and/or the destination address. Applying detection and control to the downlink service data flow of the IPv4 address, and reporting the detected application and service data flow through the TDF session established for the IPv6 address. Describe and other information.
  • the PCRF can also issue ADC rules for applying IPv4 addresses separately through an established TDF session.
  • the TDF performs application detection and control according to the ADC rule that is separately applied to the IPv4 address delivered by the PCRF or the PCEF locally preconfigured ADC rule that is separately applied to the IPv4 address. That is, the TDF associates the TDF session-related ADC rules (including for IPv4, and/or the ADC rules for IPv6) to the upstream service data stream (also called user plane data) whose source address is the IPv4 address, and/or the destination address is The downlink service data stream of the IPv4 address performs application detection and control. If the PCRF subscribes to the event trigger of the Start of application traffic detection and the Stop of application traffic detection to the TDF, the TDF may also return the detected application information related to the IPv4 address to the PCRF through the TDF session.
  • the TDF may also return the detected application information related to the IPv4 address to the PCRF through the TDF session.
  • FIG. 7 is a schematic flowchart of a second embodiment of a method for implementing application detection and control in a dual-stack IP-CAN session according to the present invention.
  • the TDF is deployed independently, and according to the process of FIG. 2 or FIG.
  • a TDF session is established between the TDF and the PCRF; after the IPv4 address is released, the method includes:
  • Step 701 The IPv4 address allocated to the UE before the gateway or other network element where the PCEF is located is released.
  • Step 702 The PCEF sends an IP-CAN session modification indication message to the PCRF, and carries the IP address release indication and the released IPv4 address in the IP-CAN session modification indication message.
  • the IP address allocation indication is an event trigger event trigger 0 that includes UE_IP_ADDRESS_RELEASE.
  • Step 703 The PCRF returns an IP-CAN session modification confirmation message to the PCEF.
  • Step 704 The PCRF sends a TDF session modification request to the TDF through the TDF session established in steps 208 to 209 of the process shown in FIG. 2 or the steps 306 to 308 of the process shown in FIG. 3, and the TDF session modification request is sent in the TDF session.
  • the IP address release indication and the released IPv4 address are carried.
  • the session modification request message sent by the PCRF to the TDF carries an Event-Report-Indication AVP, and the value carried in the AVP is included.
  • the event trigger and released IPv4 address of UE_IP_ADDRESS_RELEASE The event trigger and released IPv4 address of UE_IP_ADDRESS_RELEASE.
  • Step 705 The TDF returns a TDF session modification request acknowledgement message to the PCRF.
  • the TDF learns that the IPv4 address assigned before the IP-CAN session has been released, that is, the IPv4 address and the previous IPv6 address no longer belong to the same IP-CAN session.
  • the TDF de-associates an IPv4 address from an established TDF session.
  • the TDF stops applying the TDF session-related ADC rule to the service data stream (also called user plane data) that matches the released IPv4 address, and performs application information detection.
  • service data stream also called user plane data

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé et un système pour réaliser la détection et le contrôle d'applications dans une session IP-CAN prenant en charge la double pile. Le procédé comprend les étapes suivantes : une PCRF informe une TDF d'une adresse IPv4 au moyen d'une session TDF établie par la session IP-CAN si une passerelle où est située la PCEF ou un autre élément de réseau externe attribue en outre l'adresse IPv4 selon une demande d'un UE et l'UE accède à un service en utilisant l'adresse IPv4, après que l'UE a établi la session IP-CAN et accède à un service en utilisant l'adresse IPv6 dans la session IP-CAN prenant en charge la double pile ; et la TDF effectue la détection et le contrôle d'applications (ADC) sur des données de service dont l'adresse source et / ou l'adresse de destination est / sont l'adresse IPv4 selon une règle d'ADC pertinente pour la session TDF. Au moyen du procédé selon la présente invention, la PCRF ne lance plus de demande d'établissement d'une nouvelle session TDF, de sorte que la détection de service visant la même session IP-CAN n'a besoin d'être signalée qu'au moyen de la même session TDF, ce qui économise les ressources tout en réduisant la surcharge de signalisation.
PCT/CN2011/085211 2011-01-18 2011-12-31 Procédé et système pour réaliser la détection et le contrôle d'applications dans une session ip-can prenant en charge la double pile WO2012097676A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US13/978,603 US9565052B2 (en) 2011-01-18 2011-12-31 Method and system for realizing application detection and control in IP-CAN session supporting dual stack
JP2013547799A JP5642888B2 (ja) 2011-01-18 2011-12-31 デュアルスタックをサポートするｉｐ−ｃａｎセッションにおいてアプリケーション検出及び制御を実現する方法及びシステム
EP11856616.5A EP2648367B1 (fr) 2011-01-18 2011-12-31 Procédé et système pour réaliser la détection et le contrôle d'applications dans une session ip-can prenant en charge la double pile

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201110020191 2011-01-18
CN201110020191.4 2011-01-18
CN201110118972.7A CN102611586B (zh) 2011-01-18 2011-04-29 支持双栈的ip‑can会话实现应用检测和控制的方法及系统
CN201110118972.7 2011-04-29

Publications (1)

Publication Number Publication Date
WO2012097676A1 true WO2012097676A1 (fr) 2012-07-26

Family

ID=46515140

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/085211 WO2012097676A1 (fr) 2011-01-18 2011-12-31 Procédé et système pour réaliser la détection et le contrôle d'applications dans une session ip-can prenant en charge la double pile

Country Status (5)

Country Link
US (1) US9565052B2 (fr)
EP (1) EP2648367B1 (fr)
JP (1) JP5642888B2 (fr)
CN (1) CN102611586B (fr)
WO (1) WO2012097676A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2775688A1 (fr) * 2013-03-08 2014-09-10 Samsung Electronics Co., Ltd. Procédé et appareil de traitement de trafic multimédia dans un système de communication mobile
WO2014187492A1 (fr) * 2013-05-23 2014-11-27 Telefonaktiebolaget L M Ericsson (Publ) Procédé et appareil de contrôle de l'accès d'un terminal de communications à des réseaux d'accès
EP2883327A4 (fr) * 2012-08-07 2016-04-06 Allot Communications Ltd Système, dispositif et procédé de détection de trafic
USRE48656E1 (en) 2010-12-09 2021-07-20 Allot Ltd. System, device, and method of traffic detection

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103313431B (zh) * 2012-03-16 2018-09-04 中兴通讯股份有限公司 Tdf会话的处理方法及pcrf
WO2014032289A1 (fr) * 2012-08-31 2014-03-06 华为技术有限公司 Procédé pour la régulation de la bande passante, et dispositif et système correspondants
JP6153903B2 (ja) * 2014-08-25 2017-06-28 日本電信電話株式会社 サービスチェイニングシステム、サービスチェイニングポリシ制御装置、及びサービスチェイニング方法
RU2719421C1 (ru) * 2016-11-07 2020-04-17 Телефонактиеболагет Лм Эрикссон (Пабл) Разграничение услуг для устройств, подключенных к ue, действующему в качестве маршрутизатора
CN109429361B (zh) * 2017-07-18 2021-01-01 华为技术有限公司 会话处理方法及装置
CN109413640B (zh) * 2017-08-18 2021-10-08 中国移动通信有限公司研究院 会话信息查询方法、网元及计算机存储介质
CN111343295B (zh) * 2020-02-18 2022-09-27 支付宝(杭州)信息技术有限公司 用于确定IPv6地址的风险的方法及装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296169A (zh) * 2007-04-26 2008-10-29 华为技术有限公司 一种用户会话承载业务建立方法、系统及设备
CN101459951A (zh) * 2008-04-11 2009-06-17 中兴通讯股份有限公司 一种承载绑定和事件报告功能策略控制的方法及系统

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101267319B (zh) * 2008-04-30 2011-07-13 中兴通讯股份有限公司 一种下发策略计费控制规则的方法
CN101582777B (zh) * 2008-05-16 2013-08-07 华为技术有限公司 策略和计费控制规则的获取方法及装置
WO2010020637A1 (fr) * 2008-08-18 2010-02-25 Telefonaktiebolaget L M Ericsson (Publ) Gestion de débit binaire maximal agrégé par commande de politique et de facturation
CN101583114B (zh) * 2008-09-23 2011-09-21 中兴通讯股份有限公司 用户设备IP地址提供方法、Diameter路由代理
CN101841797B (zh) * 2009-03-21 2014-11-05 中兴通讯股份有限公司 一种终端通过多接入网接入的计费方法和系统及上报方法
US9197714B2 (en) * 2009-10-06 2015-11-24 Telefonaktiebolaget L M Ericsson (Publ) User interest and identity control on internet
US9565587B2 (en) * 2010-05-28 2017-02-07 Telefonaktiebolaget L M Ericsson Flow mobility filter rule verification
US20140013383A1 (en) * 2011-03-22 2014-01-09 Telefonaktiebolaget L M Ericsson (Publ) Network node and method to control routing or bypassing of deployed traffic detection function nodes

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296169A (zh) * 2007-04-26 2008-10-29 华为技术有限公司 一种用户会话承载业务建立方法、系统及设备
CN101459951A (zh) * 2008-04-11 2009-06-17 中兴通讯股份有限公司 一种承载绑定和事件报告功能策略控制的方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2648367A4 *

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
USRE48656E1 (en) 2010-12-09 2021-07-20 Allot Ltd. System, device, and method of traffic detection
EP2883327A4 (fr) * 2012-08-07 2016-04-06 Allot Communications Ltd Système, dispositif et procédé de détection de trafic
EP3591895A1 (fr) * 2012-08-07 2020-01-08 Allot Communications Ltd. Système, dispositif et procédé de détection de la circulation
EP2775688A1 (fr) * 2013-03-08 2014-09-10 Samsung Electronics Co., Ltd. Procédé et appareil de traitement de trafic multimédia dans un système de communication mobile
US10129785B2 (en) 2013-03-08 2018-11-13 Samsung Electronics Co., Ltd. Method and apparatus for processing media traffic in mobile communication system
WO2014187492A1 (fr) * 2013-05-23 2014-11-27 Telefonaktiebolaget L M Ericsson (Publ) Procédé et appareil de contrôle de l'accès d'un terminal de communications à des réseaux d'accès

Also Published As

Publication number Publication date
CN102611586A (zh) 2012-07-25
EP2648367B1 (fr) 2019-10-16
JP5642888B2 (ja) 2014-12-17
EP2648367A1 (fr) 2013-10-09
US9565052B2 (en) 2017-02-07
US20130297812A1 (en) 2013-11-07
EP2648367A4 (fr) 2017-07-26
CN102611586B (zh) 2017-06-13
JP2014506420A (ja) 2014-03-13

Similar Documents

Publication Publication Date Title
WO2012097676A1 (fr) Procédé et système pour réaliser la détection et le contrôle d'applications dans une session ip-can prenant en charge la double pile
EP2339781B1 (fr) Procédé et système pour réaliser la commande de politique et de facturation sur la scène de multiples réseaux de données par paquets (pdn)
US9137652B2 (en) Method for implementing policy and charging control in a roaming scene
US8874715B2 (en) Charging method, system and reporting method for terminal accessing through multiple access networks
US8799440B2 (en) Policy and charging control method and system for multi-PDN connections of single APN
US8817612B2 (en) Method for implementing limited policy and charging control and system thereof
EP2493222B1 (fr) Procédé et système de mise en oeuvre d'un contrôle de surveillance d'utilisation
WO2011060698A1 (fr) Procédé et système de réalisation de contrôle de surveillance d'utilisation
WO2011124106A1 (fr) Procédé, système et dispositif de commande de politique et de facturation
WO2009094837A1 (fr) Procédé de sélection d'un serveur à fonction de règles de politiques et de facturation dans une situation sans itinérance
WO2012103770A1 (fr) Procédé et système de contrôle d'utilisation servant de support à une fonction de détection du trafic
WO2011063688A1 (fr) Procédé et système de sélection d'entité à fonction de règles de politique et de facturation
EP3110197B1 (fr) Procédé de détection et de contrôle d'application dans un scénario d'itinérance et une v-pcrf
WO2010006491A1 (fr) Procédé d’envoi et d’installation d’un déclencheur d’évènement
WO2011029289A1 (fr) Procédé et système de transmission d'un mode de commande de support dans des scénarios d'itinérance
US20170163819A1 (en) Method, Device, and System for Processing Policy Control
US20190089843A1 (en) Method and device for processing pcc rule
WO2016062025A1 (fr) Procédé et dispositif de sélection de fonction de règles de politique et de facturation
WO2010078761A1 (fr) Procédé, appareil et système de détermination de la politique et de la facturation
US9485106B2 (en) Method for processing TDF session and PCRF
WO2014107985A1 (fr) Procédé de facturation en ligne de services d'itinérance locale, h-ocs et v-ocs
WO2012129992A1 (fr) Procédé de traitement de connectivité de données sponsorisées, et fonction d'imputation et de règles
WO2012028044A1 (fr) Procédé et système pour traiter une erreur ifom
WO2013113263A1 (fr) Procédé et système d'identification de mode fonction de commande de détection d'application
WO2011134321A1 (fr) Procédé et système d'envoi de politique pour communication de type machine

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11856616

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2011856616

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 13978603

Country of ref document: US

ENP Entry into the national phase

Ref document number: 2013547799

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE